On Thu, Jun 25, 2009 at 5:53 PM, Robert LeBlanc <rob...@leblancnet.us>wrote:

> I've set-up a migration job to migrate jobs from one set of tape volumes to
> disk volumes. I've configured the destination pool to use the volume once
> and have a retention period of 2 months. For some reason when the migration
> job completes and gets to the next queued migration job it marks the
> destination volume as purged and then overwrites the contents with the next
> job. The Jobs from the source pool are being marked as purged, so the data
> is going straight into the bit bucket!
>
> I'm using version 2.4.4 from Debian and here is the pool and job portion of
> my conf files.
>
> Pool {
>   Name = 454FLX
>   Pool Type = Backup
>   AutoPrune = yes
>   Storage = Neo8000-LTO4
>   VolumeRetention = 3 years
>   Recycle = yes
>   Next Pool = DD-454FLX
> }
>
> Pool {
>   Name = DD-454FLX
>   Pool Type = Backup
>   LabelFormat = "454FLX-"
>   Recycle = yes
>   AutoPrune = yes
>   Storage = DD-454FLX
>   Volume Retention = 2 months
>   Use Volume Once = yes
> }
>
> Job {
>   Name = "Migrate_454FLX"
>   Type = Migrate
>   Level = Full
>   Client = 454datarig-fd
>   FileSet = "FULL Windows"
>   Messages = Standard
>   Pool = 454FLX
>   Maximum Concurrent Jobs = 4
>   Selection Type = Volume
>   Selection Pattern = ".*L4"
> }
>
> Here is a piece of the output that is confirming my bit bucket suspicion:
>
> 25-Jun 17:50 babacula-dir JobId 37438: Start Migration JobId 37438,
> Job=Migrate_454FLX.2009-06-25_15.15.54.27
> 25-Jun 17:50 babacula-dir JobId 37438: There are no more Jobs associated
> with Volume "454FLX-0169". Marking it purged.
> 25-Jun 17:50 babacula-dir JobId 37438: All records pruned from Volume
> "454FLX-0169"; marking it "Purged"
> 25-Jun 17:50 babacula-dir JobId 37438: Recycled volume "454FLX-0169"
> 25-Jun 17:50 babacula-dir JobId 37438: Using Device "DD-454FLX"
> 25-Jun 17:50 lsbacsd0-sd JobId 37438: Ready to read from volume "000002L4"
> on device "Drive-2" (/dev/tape/drive2).
> 25-Jun 17:50 lsbacsd0-sd JobId 37438: Recycled volume "454FLX-0169" on
> device "DD-454FLX" (/backup/pools/454FLX), all previous data lost.
> 25-Jun 17:51 babacula-dir JobId 37438: Volume used once. Marking Volume
> "454FLX-0169" as Used.
> 25-Jun 17:50 lsbacsd0-sd JobId 37438: Forward spacing Volume "000002L4" to
> file:block 418:0.
>
> So, two questions. 1. What am I doing wrong? 2. Is there an easy way to
> unpurge the jobs on the tape since they have not been recycled, or do I have
> to run bscan on them?
>
> Thanks,
>
> Robert LeBlanc
> Life Sciences & Undergraduate Education Computer Support
> Brigham Young University
>

Since no one offered any alternative suggestions, I've run bscan on all the
tapes, but all the jobs are still showing as purged in the database. How do
I get the jobs to be unpurged short of manually changing the database?

Thanks,

Robert LeBlanc
Life Sciences & Undergraduate Education Computer Support
Brigham Young University
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to