How to enable abusive file backups in CubeBackup for Google Workspace.
Google Workspace may flag files deemed suspicious, and for security reasons, CubeBackup skips these by default. If you wish to back up these files in spite of the warnings, follow these steps to disable the filter in CubeBackup:
- Log (or SSH) into your backup server.
Open the config file config.toml on the backup server using a text editor.
Note:
Starting with version 4.7, the configuration file is located at <installation directory>/etc/config.toml for fresh installations of CubeBackup. For installations upgraded through the console, or versions prior to 4.7, the configuration file is still located at <installation directory>/bin/config.toml.
On Windows, the installation directory is located at C:\Program Files\CubeBackup4 by default.
On Linux, the installation directory is located at /opt/cubebackup by default.In the [Backup] section, remove the comment sign
#
in the front of theAcknowledgeAbuse = false
line. Set the value totrue
and save the changes.[Backup] ... AcknowledgeAbuse = true ...
Restart the CubeBackup service to apply the new settings.
Please run this command.
sudo /opt/cubebackup/bin/cbsrv restart
Open a Command Prompt as Administrator, and run this command.
"C:\Program Files\CubeBackup4\bin\cbsrv.exe" restart
Open the Windows PowerShell as Administrator, and run this command.
& "C:\Program Files\CubeBackup4\bin\cbsrv.exe" restart
Please run this command to restart the container.
sudo docker restart <container-name>
Start a new backup in CubeBackup. Files previously flagged as abusive will now be included in the snapshots.
If you're using a version earlier than 4.11 and encounter issues with files flagged as abusive, there are some additional steps to redownload problematic files in Google Drive.
Upgrade to at least version 4.11.
Follow this provided link to run the
cbackup fullSync
command.Go back to the CubeBackup web console and click the Backup now button to initiate a full backup.
Wait for the full synchronization to complete and verify that all files, including those previously flagged as abusive, are now properly backed up.