Are Google Workspace accounts backed up one by one or in parallel?
CubeBackup backs up user accounts in parallel. That is, CubeBackup will backup multiple accounts simultaneously. The number of parallel accounts is decided automatically by CubeBackup depending on the number of cores in your CPU, the available network bandwidth, and the type of backup storage.
- In most cases, the number of parallel accounts is between 5 and 10.
- Each account is handled by several threads simultaneously.
Set the number of parallel accounts
In most cases, CubeBackup will choose a reasonable number of parallel accounts for your system, and there should be no reason to adjust it. However, this number can be modified in the configuration file if you wish.
Modify the configuration file
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 default installation directory is located at c:\Program Files\CubeBackup4.
On Linux, the default installation directory is located at /opt/cubebackup.
In the [Backup] section, add (or modify) the WorkerCount value:
WorkerCount = 10 # Backup 10 accounts simultaneously
Note: The recommended value for WorkerCount is 5 if you are doing an on-premises backup. You can set a higher value if CubeBackup is running on a cloud instance and backing up to cloud storage, which can accept a greater writing load than a local machine.
After changing the value of WorkerCount, you need to restart CubeBackup to let it take effect.
- In the CubeBackup console, click the Stop backup button if the backup is running.
Log/SSH into the backup server, restart the backup service:
sudo /opt/cubebackup/bin/cbsrv restart
On Windows: Enter services.msc in the command line, in the Services list that pops up, right-click CubeBackup Service entry, then select Restart.
sudo docker restart <container-name>