I recommend that you break your backup up into smaller FileSets and Jobs. Any Job that runs 13 days will run a high probability of failing, and if it succeeds I don't know how you will ever restore it. IMO, no single Job should run more than 10 hours. Break it into smaller Jobs and you can even run a reasonable number of the at the same time possibly reducing the overall time.
On Wednesday 17 January 2007 21:02, David Romerstein wrote: > On Wed, 17 Jan 2007, Arno Lehmann wrote: > > > Ok, so we have an SD in inconsistent state. You'll have to restart it, I > > assume. > > Right. This was why I assumed the job was still running. :-/ > > > If you want to know more about the underlying problem, reading through > > the console messages file should give you the information that couldn't > > be mailed to you. > > Yep, found it: > > 14-Jan 16:32 srv01-sd: Job BackupFileStore.2007-01-08_17.07.02 waiting. > Cannot find any appendable volumes. > Please use the "label" command to create a new Volume for: > Storage: "DellUltrium" (/dev/nst0) > Media type: LTO-3 > Pool: Default > 14-Jan 17:07 srv01-dir: BackupFileStore.2007-01-08_17.07.02 Error: > Watchdog sending kill after 518417 secs to thread stall > ed reading File daemon. > 14-Jan 17:07 srv01-dir: BackupFileStore.2007-01-08_17.07.02 Fatal error: > Network error with FD during Backup: ERR=Interrup > ted system call > 14-Jan 17:07 srv01-dir: BackupFileStore.2007-01-08_17.07.02 Fatal error: > No Job status returned from FD. > 14-Jan 17:07 srv01-dir: BackupFileStore.2007-01-08_17.07.02 Error: Bacula > 2.0.0 (04Jan07): 14-Jan-2007 17:07:27 > JobId: 9 > Job: BackupFileStore.2007-01-08_17.07.02 > Backup Level: Full > Client: "srv01-fd" 2.0.0 (04Jan07) > i686-pc-linux-gnu,redhat,Enterprise release > FileSet: "xRaid1" 2007-01-08 15:41:22 > Pool: "Default" (From Job resource) > Storage: "Ultrium" (From Job resource) > Scheduled time: 08-Jan-2007 17:07:00 > Start time: 08-Jan-2007 17:07:05 > End time: 14-Jan-2007 17:07:27 > Elapsed time: 6 days 22 secs > Priority: 5 > FD Files Written: 0 > SD Files Written: 0 > FD Bytes Written: 0 (0 B) > SD Bytes Written: 0 (0 B) > Rate: 0.0 KB/s > Software Compression: None > VSS: no > Encryption: no > Volume name(s): xRaid1|xRaid1_2 > Volume Session Id: 1 > Volume Session Time: 1168293869 > Last Volume Bytes: 0 (0 B) > Non-fatal FD errors: 1 > SD Errors: 0 > FD termination status: Error > SD termination status: Error > Termination: *** Backup Error *** > > Looking at the mailing list archive, it looks like there was a thread > about a length-of-time limit for a backup (Arno, you posted to the thread, > actually). Was it ever determined if this was hard-coded and, if not, > where I can set the length? I'm expecting this backup, all told, to run > about 13 days. > > -- D > > ------------------------------------------------------------------------- > 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
