The best way to tell it is to move them to a Pool that only the new SD can read, or to change the Media Type of the Volumes.  The storageid helps Bacula find the right storage device when it is not specified, but it *should* not be required.  I have never personally tried this situation, so there may be some problems.  I am interested in getting to the bottom of this, because setting up off-site SDs and moving volumes to them should be something relatively simple and if it is not, it is time for me to plan some time to fix it.

Best regards,
Kern

On 12/08/2016 09:00 PM, Dan Langille wrote:
OK, but how will Bacula know that the files/Volumes are now on a new SD?  The db is still pointing to the old SD.

-- 
Dan Langille - BSDCan / PGCon
d...@langille.org


On Dec 8, 2016, at 10:50 AM, Kern Sibbald <k...@sibbald.com> wrote:

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:
I added another bacula-sd to my configuration.  It has more storage than the existing SD.  Both SD use file-based storage.

All new backups are going to the new SD.

I want to copy all the old Volumes to the new SD and have them available there. 

I suspect all I need to do is copy the Volumes over, then run an SQL command to adjust the storageid for all volumes which refer to old SD. 

I think some of you have already done this. I know I have: https://dan.langille.org/2013/08/06/moving-bacula-volumes-from-one-storage-to-another/

-- 
Dan Langille - BSDCan / PGCon
d...@langille.org




------------------------------------------------------------------------------
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






------------------------------------------------------------------------------
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

Reply via email to