#Origin Pool

Pool {

Name = Monthly-Disk

Pool Type = backup

Next Pool = another_pool

Storage = File1   # origin storage

...

}

# Destination Pool

Pool {

Name = another_pool

Pool Type = backup

Storage =File2    # destination storage

...

}

b) Job Resource (bacula-dir.conf):

Job {

Name = “MigrateAdHocJob”

JobDefs = DefaultJob

Type = Migrate

Pool = Monthly-Disk # Origin Pool

     Selection Type = Job

     Selection Pattern = job_name

Schedule = an_empty_schedule # Advisable

}

From: "Heitor Faria" <heitor AT bacula.com DOT br>
To: "Александр Чапкин" <watashi AT reisei DOT ru>
Cc: bacula-users AT lists.sourceforge DOT net
Sent: Tuesday, March 22, 2016 10:12:45 AM
Subject: Re: [Bacula-users] Properly storage changing

My name is Alex :) I did exactly what you describe: create another Device and attach it to the director, so I should move volumes with Migrate Job now? Can you give me an example of that job? There are a lot of examples in the internet, I understand, but I don't understand how define from what storage and where to migrate.

Hello, Alex: I think it should be something like this.

a) Pools Resource (bacula-dir.conf):

#Origin Pool

Pool {

Name = Monthly-Disk

Pool Type = backup

Next Pool = another_pool

Storage = File1   # origin storage

...

}

# Destination Pool

Pool {

Name = Tape

Pool Type = backup

Storage =File2    # destination storage

...

}

b) Job Resource (bacula-dir.conf):

Job {

Name = “MigrateAdHocJob”

JobDefs = DefaultJob

Type = Migrate

Pool = Monthly-Disk # Origin Pool

     Selection Type = Job

     Selection Pattern = job_name

Schedule = an_empty_schedule # Advisable

}

On 22 March 2016 at 15:40, Heitor Faria <heitor AT bacula.com DOT br> wrote:

That's very useful advice, thank you! And that will be a great option,

but situation is a bit more complicated: I have job1 and job2, that uses one storage /home/bacula1 (I understand, that it's not very clever). I need to separate those jobs to different storages, for example, job1 stays in /home/bacula1 and job2 should work with /mnt/bacula2, what is the right way to do that without breaking the bacula?  

Welcome back, Watashi [how do I call you? =)]: in this scenario just create a second Device (bacula-sd.conf); a second Director Storage attachment (bacula-dir.conf); set the job2 to use the new Storage.

If you want to migrate the job2 legacy that will be still in the 1st storage probably the best way to go is to use Migrate Jobs; or just wait until every volume from 1st storage get recycled.

Hello.

I have a question about storage changing: for example, I have backups in /home/bacula1, but after some time I need to move backups of the job to the /mnt/bacula2, how can do it properly? Is it enough just change storage name in config file and move files from one directory to another?

Hello, Watashi: I think it's more reasonable to change Archive Device and copy disk volumes to /mnt/bacula2.

If you Change Storage Name you will probably have a bad time, mostly because each Storage has an ID.

(Bacula version is 5.2.6)

Regards,

--

===========================================================================
Heitor Medrado de Faria - LPIC-III | ITIL-F |  Bacula Systems Certified Administrator II

Do you need Bacula training? http://bacula.us/video-classes/

+55 61 8268-4220

Site: http://bacula.us FB: heitor.faria 

===========================================================================