Hello Dan,
From what users have reported, one must update the storageid, and it is clear to me that if you use the same name for the Storage in the Director's resource but it points to a different machine, you must update the storageid. However, if you use a new name for the new storage daemon, in theory one should not need to update the storageid. If it is required then in my view there is a problem, because Bacula *should* be relatively transparent to allowing you to move volumes from one Storage definition to another. Best regards, Kern On 12/08/2016 03:47 PM, Dan Langille wrote:
|
------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/xeonphi
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users