Are Google Workspace accounts backed up one by one or in parallel?
Parallel backup
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
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, add (or modify) the WorkerCount value:
WorkerCount = 10 # Backup 10 accounts simultaneouslyNote: 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.
Restart CubeBackup
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 CubeBackup service using the following command.
Please run this command.
sudo /opt/cubebackup/bin/cbsrv restartOpen a Command Prompt as Administrator, and run this command.
"C:\Program Files\CubeBackup4\bin\cbsrv.exe" restartOpen the Windows PowerShell as Administrator, and run this command.
& "C:\Program Files\CubeBackup4\bin\cbsrv.exe" restartPlease run this command to restart the container.
sudo docker restart <container-name>Set the number of concurrent restoration tasks
By default, CubeBackup runs up to three restoration tasks in parallel. Under unusual circumstances, when it is necessary to perform bulk restoration, you may extend the number of concurrent restoration tasks by following the instructions below to modify the config file:
Open the configuration file <installation directory>/etc/config.toml on your backup server.
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 [Restore] section, add the WorkerCount field and assign a value according to the hardware capabilities of your backup server (5-8 tasks are recommended).
Note: Please note that there is a
WorkerCountfield in the [Backup] section as well, which determines the number of concurrent backup tasks. Detailed instructions on modifying this value can be found at this section.After modification, the [Restore] section should look like this.
Restart the CubeBackup service using the following command.
Please run this command.
sudo /opt/cubebackup/bin/cbsrv restartOpen a Command Prompt as Administrator, and run this command.
"C:\Program Files\CubeBackup4\bin\cbsrv.exe" restartOpen the Windows PowerShell as Administrator, and run this command.
& "C:\Program Files\CubeBackup4\bin\cbsrv.exe" restartPlease run this command to restart the container.
sudo docker restart <container-name>
This will interrupt any running tasks and cancel all scheduled restoration tasks. All future restoration tasks will run in parallel according to the value you have set.