• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarded to devs [Google Drive Backup] Shared Drives uses personal Drive usage

MSWeb

New Pleskian
TITLE:
[Google Drive Backup] Shared Drives uses personal Drive usage
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Google Drive Backup 1.1.2-62, Plesk Onyx 17.8.11 Update Nr. 68, Ubuntu 18.04.3 LTS
PROBLEM DESCRIPTION:
When using a Shared Drive (Team Drive) on Google Drive as a backup location for Plesk, using the Google Drive Backup extension, it does not show the correct drive usage.
Instead it displays the drive usage of the personal drive of the linked account. If the user does not have enough space on his personal drive, the backup will fail, with "Not enough free space", even though there is plenty of space available on the Shared Drive.​
STEPS TO REPRODUCE:
(A) Google Drive
1. Create a free Google account or use an account with limited Google Drive storage, smaller than your Plesk backup.
2. Give the account access to a Shared Drive (Team Drive) on an account with sufficient storage.

(B) Plesk
1. Install Google Drive Backup.
2. Go to "Backup Manager" -> "Remote Storage Options".
3. Log in the account from A.1, choose the Shared Drive (A.2) and supply a path.
4. Schedule a backup for the storage that needs more storage than there is available on the personal storage of A.1, but should fit on the Shared Drive (A.2).​


ACTUAL RESULT:
1. "Remote Storage Settings" -> "Google Drive Backup" shows the drive usage of the personal storage of the account (A.1), in row "Storage".
2. The backup fails with the message "Not enough free space at the external storage to backup selected objects. At least ... MBytes free disk space is required."​
EXPECTED RESULT:
1. "Remote Storage Settings" -> "Google Drive Backup" should show the drive usage of the Shared Drive (A.2) in the row "Storage".
2. The backup should successfully run and be stored on the Shared Drive.​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 
Thank you for the report. The issue has been confirmed and submitted as EXTPLESK-1322
 
Back
Top