Re: [Bacula-users] Verify Jobs

I was using /dev/nst0 but I'm trying the /dev/st0 just for testing, because I've notice that even with any of them, Bacula controls if it will rewind or not. At least, this was I could to notice.

On Thu, Jul 14, 2011 at 4:51 PM, John Drescher <drescherjm AT gmail DOT com> wrote:

> I'm running Verify Tests with the VolumeToCatalog list and nothing is making
> sense.
>
> For example, I've configured my FileSet to use the MD5 signature and in the
> Verify Job I've also used MD5 but with the "verify=pins1" intentionally to
> see if it would fail, but it didn't. How you can see below, it says that is
> all right with the files even compare with a different algorithm. A few days
> ago I've tried do this with DiskToCatalog to compare the files of the
> Catalog with the client disk and it worked successfully, but now using on
> Tape with VolumeToCatalog, the results didn't seem reliable. Somebody here
> have had the same problem?
>
>
> Job{
> Name = "Backup Test"
> Type = Backup
> Level = Full
> Client = test-nb
> FileSet = "Test"
> Schedule = GFS-A
> Storage = TapeDriveLTO-4
> Messages = Standard
> Pool = Monthly
> Priority = 10
> Write Bootstrap = "/var/lib/bacula/%c.bsr"
> }
>
> Job {
> Name = "Verify Test"
> Type = Verify
> Level = VolumeToCatalog
> Client = test-nb
> FileSet = "Verify Set Test"
> Messages = Standard
> Schedule = Verify
> Storage = TapeDriveLTO-4
> Pool = Yearly
> Priority = 11
> }
>
> FileSet {
> Name = "Test"
> Include {
>     Options {
>       signature = MD5
>       compression = gzip
>     }
>     File = "C:/Backup"
> }
> }
>
> FileSet {
> Name = "Verify Set Test"
> Include {
>     Options {
>       signature = MD5
>       verify = pins1
>     }
>     File = "C:/Backup"
> }
> }
>
>
> 14-Jul 15:58 frajola-dir JobId 34: Start Backup JobId 34,
> Job=Backup_Test.2011-07-14_15.58.41_03
> 14-Jul 15:58 frajola-dir JobId 34: Using Device "LTO-4"
> 14-Jul 15:58 frajola-sd JobId 34: Wrote label to prelabeled Volume "FW3-001"
> on device "LTO-4" (/dev/st0)
> 14-Jul 15:59 test-nb JobId 34: Generate VSS snapshots. Driver="VSS Vista",
> Drive(s)="C"
> 14-Jul 16:00 test-nb JobId 34: VSS Writer (BackupComplete): "Task Scheduler
> Writer", State: 0x1 (VSS_WS_STABLE)
> 14-Jul 15:59 test-sd JobId 34: Job write elapsed time = 00:01:02, Transfer
> rate = 3.695 M Bytes/second
> 14-Jul 16:00 test-nb JobId 34: VSS Writer (BackupComplete): "VSS Metadata
> Store Writer", State: 0x1 (VSS_WS_STABLE)
> 14-Jul 16:00 test-nb JobId 34: VSS Writer (BackupComplete): "Performance
> Counters Writer", State: 0x1 (VSS_WS_STABLE)
> 14-Jul 16:00 test-nb JobId 34: VSS Writer (BackupComplete): "System Writer",
> State: 0x1 (VSS_WS_STABLE)
> 14-Jul 16:00 test-nb JobId 34: VSS Writer (BackupComplete): "ASR Writer",
> State: 0x1 (VSS_WS_STABLE)
> 14-Jul 16:00 test-nb JobId 34: VSS Writer (BackupComplete): "COM+ REGDB
> Writer", State: 0x1 (VSS_WS_STABLE)
> 14-Jul 16:00 test-nb JobId 34: VSS Writer (BackupComplete): "Registry
> Writer", State: 0x1 (VSS_WS_STABLE)
> 14-Jul 16:00 test-nb JobId 34: VSS Writer (BackupComplete): "BITS Writer",
> State: 0x1 (VSS_WS_STABLE)
> 14-Jul 16:00 test-nb JobId 34: VSS Writer (BackupComplete): "WMI Writer",
> State: 0x1 (VSS_WS_STABLE)
> 14-Jul 16:00 test-nb JobId 34: VSS Writer (BackupComplete): "MSSearch
> Service Writer", State: 0x1 (VSS_WS_STABLE)
> 14-Jul 15:59 frajola-dir JobId 34: Bacula frajola-dir 5.0.2 (28Apr10):
> 14-Jul-2011 15:59:47
> Build OS:               x86_64-pc-linux-gnu debian squeeze/sid
> JobId:                  34
> Job:                    Backup_Test.2011-07-14_15.58.41_03
> Backup Level:           Full
> Client:                 "test-nb" 5.0.3 (04Aug10)
> Linux,Cross-compile,Win32
> FileSet:                "Test" 2011-07-12 09:27:47
> Pool:                   "Monthly" (From Job resource)
> Catalog:                "MyCatalog" (From Client resource)
> Storage:                "TapeDriveLTO-4" (From Job resource)
> Scheduled time:         14-Jul-2011 15:58:39
> Start time:             14-Jul-2011 15:58:43
> End time:               14-Jul-2011 15:59:47
> Elapsed time:           1 min 4 secs
> Priority:               10
> FD Files Written:       431
> SD Files Written:       431
> FD Bytes Written:       229,038,970 (229.0 MB)
> SD Bytes Written:       229,115,283 (229.1 MB)
> Rate:                   3578.7 KB/s
> Software Compression:   20.6 %
> VSS:                    yes
> Encryption:             no
> Accurate:               no
> Volume name(s):         FW3-001
> Volume Session Id:      23
> Volume Session Time:    1310579995
> Last Volume Bytes:      229,404,672 (229.4 MB)
> Non-fatal FD errors:    0
> SD Errors:              0
> FD termination status: OK
> SD termination status: OK
> Termination:            Backup OK
>
> 14-Jul 15:59 frajola-dir JobId 34: Begin pruning Jobs older than 6 months .
> 14-Jul 15:59 frajola-dir JobId 34: No Jobs found to prune.
> 14-Jul 15:59 frajola-dir JobId 34: Begin pruning Jobs.
> 14-Jul 15:59 frajola-dir JobId 34: No Files found to prune.
> 14-Jul 15:59 frajola-dir JobId 34: End auto prune.
>
> 14-Jul 15:59 frajola-dir JobId 35: Verifying against JobId=34
> Job=Backup_Test.2011-07-14_15.58.41_03
> 14-Jul 15:59 frajola-dir JobId 35: Bootstrap records written to
> /var/lib/bacula/frajola-dir.restore.1.bsr
> 14-Jul 15:59 frajola-dir JobId 35: Start Verify JobId=35
> Level=VolumeToCatalog Job=Verify_Test.2011-07-14_15.58.54_04
> 14-Jul 15:59 frajola-dir JobId 35: Using Device "LTO-4"
> 14-Jul 15:59 frajola-sd JobId 35: Ready to read from volume "FW3-001" on
> device "LTO-4" (/dev/st0).
> 14-Jul 15:59 frajola-sd JobId 35: Forward spacing Volume "FW3-001" to
> file:block 0:1.
> 14-Jul 16:00 frajola-sd JobId 35: End of Volume at file 1 on device "LTO-4"
> (/dev/st0), Volume "FW3-001"
> 14-Jul 16:00 frajola-sd JobId 35: End of all volumes.
> 14-Jul 16:00 frajola-dir JobId 35: Bacula frajola-dir 5.0.2 (28Apr10):
> 14-Jul-2011 16:00:21
> Build OS:               x86_64-pc-linux-gnu debian squeeze/sid
> JobId:                  35
> Job:                    Verify_Test.2011-07-14_15.58.54_04
> FileSet:                Verify Set Test
> Verify Level:           VolumeToCatalog
> Client:                 test-nb
> Verify JobId:           34
> Verify Job:
> Start time:             14-Jul-2011 15:59:49
> End time:               14-Jul-2011 16:00:21
> Files Expected:         431
> Files Examined:         431
> Non-fatal FD errors:    0
> FD termination status: OK
> SD termination status: OK
> Termination:            Verify OK
>
> 14-Jul 16:00 frajola-dir JobId 35: Begin pruning Jobs older than 6 months .
> 14-Jul 16:00 frajola-dir JobId 35: No Jobs found to prune.
> 14-Jul 16:00 frajola-dir JobId 35: Begin pruning Jobs.
> 14-Jul 16:00 frajola-dir JobId 35: No Files found to prune.
> 14-Jul 16:00 frajola-dir JobId 35: End auto prune.
>
>
> Thanks in advance.
>

I do not know about this particular quirk however I have to say be
careful with verify. Verify does not always do what you expect. One
example I mean is that it takes a fileset but ignores this and
verifies against the last job run on the client. This had me puzzled
for some time.

BTW. I see you are using /dev/st0. You should use /dev/nst0 instead
with bacula. /dev/st0 can cause a tape with useful to be overwritten
and corrupted. Search the archives for the reason.

John

------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on "Lean Startup 
Secrets Revealed." This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users