On 7/20/21 2:53 PM, William Muriithi wrote:
Hello We are using bacula version 9 and we have been happy with it. We have 2 quantum superloader 3 we use to offload the data, one for Linux system and the other one for Windows systems. In short, the two storage devices don't have any inter-dependency other than they share the same director.
Are you sure that one superloader is dedicated to Linux systems and one to Windows? If the two Device definitions have the same Media Type string and both Windows and Linux backups are being written to the same Pool, then they are not dedicated. A volume containing Windows backups could be loaded in the 'Linux' superloader and vice versa. We would need to see your configuration files to know.
Whenever, we attempt to do any data restore for verification, we find that we have to stop backup running from both the storage systems? For example, if cancel all the Windows jobs, and the run a restore job from one of the Windows machine to another windows machine, wouldn't one expect this to execute irrespective of the status of the alternate storage subsystem? However, that is not what we notice. The restore job on one superloader end up waiting for a backup on the alternate superloader finishing. Is this what is expected? Its nothing to do with concurrent jobs, because if I start a new job on the Windows superloader (Storage), it start spooling asap.
The restore job could be assigned the Windows superloader, but need the volume that is currently being used in the Linux superloader.
Regards, William _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
