Re: [Bacula-users] Migration job(s)

2024-06-07 Thread Lionel PLASSE
By experience:

* If this gets started it generates 2 jobs per "source job", it seems.
Is that correct?

> One for the migrate job and one for the migrated job

* PurgeMigrationJob: if I set this to Yes, does that mean that the "source job" 
is deleted after a successful migration? Only the job in terms of "that one 
run" and not its definition, right?

> In that case The original job (well migrated ) is deleted from the catalog  
> only,  not from the source disk the data are already present on the disk.

* Would a SelectionPattern like this "Vol-0." work? A wildcard with "*"

> Personally I used selectiontype 'client' and I wrote the client name as it is 
> configured in clients list and I used too  'volume' selectiontype  and I 
> wrote the colume name as it is too.
But to be noted that  : For the Client, Volume, and Job keywords, this pattern 
must be a valid regular expression that will filter the appropriate item names 
found in the Pool
Have you written "Vol-0." Or 'Vol-0'
Never tested wildcard but you must use regular expression as the doc specified








-Message d'origine-
De : Stefan G. Weichinger 
Envoyé : vendredi 7 juin 2024 07:59
À : bacula-users 
Objet : [Bacula-users] Migration job(s)


I had to run backups to Disk only while the tape drive was repaired.

Now the drive returned and I would like to migrate all the backups on disk to 
tape.

"Migrate" Jobs should help here, right?

I defined a job like this:

Job {
   Name = "migrate-to-tape"
   Type = "Migrate"
   Storage = "File"
   Pool = "File"
   NextPool = "Daily"
   JobDefs = "DefaultJob"
   PurgeMigrationJob = no
   MaximumSpawnedJobs = 20
   SelectionPattern = "."
   SelectionType = "Volume"
}

* If this gets started it generates 2 jobs per "source job", it seems.
Is that correct?

* Do I have to remove the source volumes from disk by myself? I was assuming I 
could have Bacula do that: as soon as the backups are migrated to tape, the 
original disk-based volumes could/should be removed in my case. I don't want to 
keep them.

* PurgeMigrationJob: if I set this to Yes, does that mean that the "source job" 
is deleted after a successful migration? Only the job in terms of "that one 
run" and not its definition, right?

* Would a SelectionPattern like this "Vol-0." work? A wildcard with "*"
did not work as I expected.

Thanks all!


___
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


[Bacula-users] Migration job(s)

2024-06-07 Thread Stefan G. Weichinger



I had to run backups to Disk only while the tape drive was repaired.

Now the drive returned and I would like to migrate all the backups on 
disk to tape.


"Migrate" Jobs should help here, right?

I defined a job like this:

Job {
  Name = "migrate-to-tape"
  Type = "Migrate"
  Storage = "File"
  Pool = "File"
  NextPool = "Daily"
  JobDefs = "DefaultJob"
  PurgeMigrationJob = no
  MaximumSpawnedJobs = 20
  SelectionPattern = "."
  SelectionType = "Volume"
}

* If this gets started it generates 2 jobs per "source job", it seems. 
Is that correct?


* Do I have to remove the source volumes from disk by myself? I was 
assuming I could have Bacula do that: as soon as the backups are 
migrated to tape, the original disk-based volumes could/should be 
removed in my case. I don't want to keep them.


* PurgeMigrationJob: if I set this to Yes, does that mean that the 
"source job" is deleted after a successful migration? Only the job in 
terms of "that one run" and not its definition, right?


* Would a SelectionPattern like this "Vol-0." work? A wildcard with "*" 
did not work as I expected.


Thanks all!


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users