Cloud Plugin: Limitations

The support of RHEL 6 has been deprecated with Bacula Enterprise Cloud storage driver version 8.10.
MaximumVolumeBytes and MaximumPoolBytes directives is not implemented in cloud volumes like in regular volumes. Other directives, like MaximumVolumeParts, VolumeUseDuration or MaximumVolumeJobs (with concurrent jobs =1) must be used to set a limit on these volumes. The MaximumVolumeParts can be used to limit the size of a cloud volume, used along with the MaximumPartSize directive. Setting MaximumPartSize will also help controlling the part size on the cloud.
On restore, all cloud volume parts that are needed will be downloaded from the cloud into the local cache storage before being transferred to the FD. This means that if you have a Full backup of 20TB (for example) that needs to be restored, you will need to have at least 20TB of local cache storage available. Consider also, if there are backups running at the time of restore, or if there are local cloud volume parts that have not yet been truncated, there will be cloud storage space already in use so you will need to pay close attention before and during large restores from the cloud to be sure that the local cloud cache storage space is not filled to capacity.
The restart command has limitations with plugins, as it initiates the Job from scratch rather than continuing it. Bacula determines whether a Job is restarted or continued, but using the restart command will result in a new Job.