Hi,

On 2/27/2007 5:04 PM, Kern Sibbald wrote:
> Hello Arno,
> 
> It looks like the retention periods are set incorrectly since the Volume was 
> pruned while the job was running.

Ah, ok... in that case, you should do an 'llist volume=...' (IIRC) with 
the volume in question. And,of course, also check your pool and client 
settings for their retention times, and also keep in mind that 
individual volumes may need to be updated to have their retention times 
updated after a pool change...

And, of course, this shows how important it is to report problems with 
the right sort of information attached to it :-)

Arno

> On Tuesday 27 February 2007 16:03, Arno Lehmann wrote:
> 
>>Hi,
>>
>>On 2/27/2007 3:24 PM, Andreas Lüdtke wrote:
>>
>>>Hi Arno,
>>>
>>>thanks for your comments. Please find my answers inline.
>>>
>>>
>>>>-----Original Message-----
>>>>From: [EMAIL PROTECTED]
>>>>[mailto:[EMAIL PROTECTED] On Behalf
>>>>Of Arno Lehmann
>>>>Sent: Monday, February 26, 2007 8:44 PM
>>>>To: 'bacula-users'
>>>>Subject: Re: [Bacula-users] Mounting/Label question
>>>>
>>>>
>>>>>Device config:
>>>>>
>>>>>Device {
>>>>> Name = Quantum
>>>>> Changer Device = tape0
>>>>> Media Type = DLT-V4
>>>>> Device Type = Tape
>>>>> Archive Device = Tape0
>>>>> AutomaticMount = yes
>>>>> AlwaysOpen = yes
>>>>> RemovableMedia = yes
>>>>> RandomAccess = no
>>>>> AutoChanger = no
>>>>> Alert Command = "tapeinfo -f %c | findstr TapeAlert"
>>>>> Spool Directory = "V:\\BaculaSpool"
>>>>> Maximum Spool Size = 2 GB
>>>>> Changer Command = "mtx-changer %o %a %S"
>>>>> Maximum Changer Wait = 4d
>>>>> Offline On Unmount = yes
>>>>> Label media = yes
>>>>>}
>>>>
>>>>That configuration looks funny... is that an autochanger or a single
>>>>drive? The configuration looks like a 1.36 one - i.e. no separate
>>>>autochanger section - but that was not ported to windows.
>>>
>>>I don't have an autochanger. The last four lines were added recently to
>>>achive that a tape is automatically ejected, that a new inserted tape is
>>>mounted automatically and that a new tape is also automatically labeled.
>>>The idea behind was, that a normal user could change the tape himself and
>>>that no admin is needed to mount the tape etc.. These lines were actually
>>>taken from this list some days ago(Erich Prinz - "Win32 mtx-changer.cmd
>>>and single drive").
>>
>>Ah, ok. Well, unfortunately I didn't follow that thread, but I think I
>>get a general understanding of what you set up...
>>
>>
>>>>>Data spooling: 0 active jobs, 0 bytes; 7 total jobs, 2,000,050,371 max
>>>>>bytes/job. Attr spooling: 1 active jobs, 9,135,494 bytes; 6 total jobs,
>>>>>17,783,343 max bytes.
>>>>
>>>>But there are attributes still spooled... looks like the SD
>>>>is currently despooling attributes after a completed job.
>>>>
>>>>Is that possible, i.e. did the Job finish some time after you
>>>>wrote your mail?
>>>
>>>I looked in the log and the Full Backup showed a "Termination:           
>>>*** Backup Error ***". See below for the whole log entry of that job.
>>>
>>>
>>>>If it did not, I'd like to see the 'sta dir' output, because above you
>>>>state that "the director is still waiting for a tape" but didn't give
>>>>any output showing us how it did wait :-)
>>>
>>>Arno you're right, that was a mistake on my side. The yesterday evening
>>>backup was normally executed.
>>
>>Good to hear.
>>
>>
>>>Do you have a clue why the director couldn't get the record for JobId 97?
>>
>>No, that's hard to tell... usually, that would indicate a database
>>problem. Like when your database was shutdown and immediately restarted,
>>but then you would normally see more errors.
>>
>>Anyway, this is hard to analyze whan it was a unique, one-time problem.
>>
>>If this problem persists, you should closely observer the backups, and
>>tje database, too.
>>
>>
>>>Thanks
>>>
>>>     Andreas
>>>
>>>Log entry for job:
>>>
>>>25-Feb 23:05 srv-dir: Start Backup JobId 97,
>>>Job=PTHHSrv.2007-02-25_23.05.00 25-Feb 23:05 srv-dir: Max configured use
>>>duration exceeded. Marking Volume "Tape04" as Used.
>>>25-Feb 23:06 srv-sd: Please mount Volume "FirstTape" on Storage Device
>>>"Quantum" (Tape0) for Job Srv.2007-02-25_23.05.00
>>>26-Feb 00:06 srv-sd: Please mount Volume "FirstTape" on Storage Device
>>>"Quantum" (Tape0) for Job Srv.2007-02-25_23.05.00
>>>26-Feb 02:06 srv-sd: Please mount Volume "FirstTape" on Storage Device
>>>"Quantum" (Tape0) for Job Srv.2007-02-25_23.05.00
>>>26-Feb 06:06 srv-sd: Please mount Volume "FirstTape" on Storage Device
>>>"Quantum" (Tape0) for Job Srv.2007-02-25_23.05.00
>>>26-Feb 09:37 srv-sd: Wrote label to prelabeled Volume "Tape05" on device
>>>"Quantum" (Tape0) 26-Feb 09:37 srv-sd: Spooling data ...
>>>26-Feb 09:37 srv-fd: Generate VSS snapshots. Driver="VSS Win 2003",
>>>Drive(s)="CDEV" 26-Feb 09:40 srv-sd: User specified spool size reached.
>>>26-Feb 09:40 srv-sd: Writing spooled data to Volume. Despooling
>>>2,000,050,371 bytes ... 26-Feb 09:43 srv-sd: Despooling elapsed time =
>>>00:02:07, Transfer rate = 15.74 M bytes/second
>>>26-Feb 09:43 srv-sd: Spooling data again ...
>>>26-Feb 09:45 srv-sd: User specified spool size reached.
>>>26-Feb 09:45 srv-sd: Writing spooled data to Volume. Despooling
>>>2,000,050,386 bytes ... 26-Feb 09:47 srv-sd: Despooling elapsed time =
>>>00:01:55, Transfer rate = 17.39 M bytes/second
>>>26-Feb 09:47 srv-sd: Spooling data again ...
>>>26-Feb 09:50 srv-sd: User specified spool size reached.
>>>26-Feb 09:50 srv-sd: Writing spooled data to Volume. Despooling
>>>2,000,050,389 bytes ... 26-Feb 09:52 srv-sd: Despooling elapsed time =
>>>00:01:43, Transfer rate = 19.41 M bytes/second
>>>26-Feb 09:52 srv-sd: Spooling data again ...
>>>26-Feb 09:53 srv-sd: User specified spool size reached.
>>>26-Feb 09:53 srv-sd: Writing spooled data to Volume. Despooling
>>>2,000,050,350 bytes ... 26-Feb 09:56 srv-sd: Despooling elapsed time =
>>>00:02:18, Transfer rate = 14.49 M bytes/second
>>>26-Feb 09:56 srv-sd: Spooling data again ...
>>>26-Feb 09:57 srv-sd: User specified spool size reached.
>>>26-Feb 09:57 srv-sd: Writing spooled data to Volume. Despooling
>>>2,000,050,383 bytes ... 26-Feb 09:59 srv-sd: Despooling elapsed time =
>>>00:02:16, Transfer rate = 14.70 M bytes/second
>>>26-Feb 09:59 srv-sd: Spooling data again ...
>>>26-Feb 10:00 srv-sd: Job write elapsed time = 00:22:02, Transfer rate =
>>>7.759 M bytes/second
>>>26-Feb 10:00 srv-sd: Committing spooled data to Volume "Tape05".
>>>Despooling 268,975,553 bytes ...
>>>26-Feb 10:00 srv-sd: Despooling elapsed time = 00:00:20, Transfer rate =
>>>13.44 M bytes/second
>>>26-Feb 10:00 srv-sd: Alert: cannot open SCSI device 'tape0' - Permission
>>>denied
>>
>>This one here looks more interesting, but I have no idea how you fix
>>that sort of permission problems under windows.
>>
>>
>>>26-Feb 10:00 srv-sd: 3997 Bad alert command: tapeinfo -f tape0 | findstr
>>>TapeAlert: ERR=Unknown error.
>>>26-Feb 10:00 srv-sd: Sending spooled attrs to the Director. Despooling
>>>17,783,343 bytes ...
>>>26-Feb 11:45 srv-fd: VSS Writer (BackupComplete): "MSDEWriter", State:
>>>0x1 (VSS_WS_STABLE) 26-Feb 11:45 srv-fd: VSS Writer (BackupComplete):
>>>"System Writer", State: 0x1 (VSS_WS_STABLE)
>>>26-Feb 11:45 srv-fd: VSS Writer (BackupComplete): "WINS Jet Writer",
>>>State: 0x1 (VSS_WS_STABLE)
>>>26-Feb 11:45 srv-fd: VSS Writer (BackupComplete): "IIS Metabase Writer",
>>>State: 0x1 (VSS_WS_STABLE)
>>>26-Feb 11:45 srv-fd: VSS Writer (BackupComplete): "WMI Writer", State:
>>>0x1 (VSS_WS_STABLE) 26-Feb 11:45 srv-fd: VSS Writer (BackupComplete):
>>>"Event Log Writer", State: 0x1 (VSS_WS_STABLE)
>>>26-Feb 11:45 srv-fd: VSS Writer (BackupComplete): "FRS Writer", State:
>>>0x1 (VSS_WS_STABLE) 26-Feb 11:45 srv-fd: VSS Writer (BackupComplete):
>>>"TermServLicensing", State: 0x1 (VSS_WS_STABLE)
>>>26-Feb 11:45 srv-fd: VSS Writer (BackupComplete): "NTDS", State: 0x1
>>>(VSS_WS_STABLE) 26-Feb 11:45 srv-fd: VSS Writer (BackupComplete):
>>>"Registry Writer", State: 0x1 (VSS_WS_STABLE)
>>>26-Feb 11:45 srv-fd: VSS Writer (BackupComplete): "COM+ REGDB Writer",
>>>State: 0x1 (VSS_WS_STABLE)
>>>26-Feb 11:45 srv-dir: Srv.2007-02-25_23.05.00 Warning: Error getting job
>>>record for stats: ../../cats/sql_get.c:293 No Job found for JobId 97
>>
>>Looks like this is the last access to the catalog after the job was done
>>- inserting the attributes worked, but some final book-keeping did not.
>>If this persists, it might be a bug in the code, but since I don't
>>recall similar problem reports I suspect it is something related to your
>>setup.
>>
>>
>>>26-Feb 11:45 srv-dir: Srv.2007-02-25_23.05.00 Error: Bacula 2.0.1
>>>(12Jan07): 26-Feb-2007 11:45:31
>>>  JobId:                  97
>>>  Job:                    Srv.2007-02-25_23.05.00
>>>  Backup Level:           Full
>>>  Client:                 "srv-fd" 2.0.1 (12Jan07)
>>>Linux,Cross-compile,Win32 FileSet:                "Windows Full Set"
>>>2007-01-10 23:05:01 Pool:                   "Default" (From Job resource)
>>>  Storage:                "DLT-V4" (From Job resource)
>>>  Scheduled time:         25-Feb-2007 23:05:00
>>>  Start time:             25-Feb-2007 23:05:04
>>>  End time:               26-Feb-2007 11:45:31
>>>  Elapsed time:           12 hours 40 mins 27 secs
>>>  Priority:               10
>>>  FD Files Written:       54,811
>>>  SD Files Written:       54,811
>>>  FD Bytes Written:       10,247,973,355 (10.24 GB)
>>>  SD Bytes Written:       10,257,628,006 (10.25 GB)
>>>  Rate:                   224.6 KB/s
>>>  Software Compression:   None
>>>  VSS:                    yes
>>>  Encryption:             no
>>>  Volume name(s):
>>>  Volume Session Id:      13
>>>  Volume Session Time:    1171896482
>>>  Last Volume Bytes:      10,267,084,800 (10.26 GB)
>>>  Non-fatal FD errors:    0
>>>  SD Errors:              0
>>>  FD termination status:  OK
>>>  SD termination status:  OK
>>>  Termination:            *** Backup Error ***
>>>
>>>26-Feb 11:45 srv-dir: Begin pruning Jobs.
>>>26-Feb 11:45 srv-dir: Pruned 2 Jobs for client pthh-fs-fd from catalog.
>>
>>Here, catalog acces works again...
>>
>>
>>>26-Feb 11:45 srv-dir: Begin pruning Files.
>>>26-Feb 11:45 srv-dir: No Files found to prune.
>>>26-Feb 11:45 srv-dir: End auto prune.
>>
>>Interesting problem. You should observe this :-)
>>
>>Arno
>>
>>
>>>-------------------------------------------------------------------------
>>>Take Surveys. Earn Cash. Influence the Future of IT
>>>Join SourceForge.net's Techsay panel and you'll get the chance to share
>>>your opinions on IT & business topics through brief surveys-and earn cash
>>>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>>>_______________________________________________
>>>Bacula-users mailing list
>>>Bacula-users@lists.sourceforge.net
>>>https://lists.sourceforge.net/lists/listinfo/bacula-users
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users

-- 
IT-Service Lehmann                    [EMAIL PROTECTED]
Arno Lehmann                  http://www.its-lehmann.de


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to