Greetings List! I've recently adopted bacula as a network backup solution for a small number of servers. After working with it for a few hours, I stand impressed. The flexibility and configuration options are awesome.
One thing I need help with is ejecting the tape, before it is full. I would like to do a 5 week rotation on my tapes. The tapes are 400gb LTO3, but right now I'm only writing about 200gb to them. I run a full backup Monday night and differential backups Tuesday-Friday. I would like the tape to eject on Monday morning so I can swap it for the next week's tape. My storage server is a Windows 2003 machine, which I understand comes with risks. The drive lives on this machine because it is the one with the bulk of the storage (~150g), so it made sense to have the drive local to the biggest backup target. >From google, I've pieced together a few scraps for how I might schedule the tape to eject, but so far I've had no luck. I've set OfflineOnUnmount=yes in the storage daemon configuration, and when I issue the unmount command in the wx-console, the tape eventually ejects. So I've setup an admin job on the director, which has a RunScript directive in it, commanding bconsole with the unmount command. However, it's not working. I also don't receive any errors, just that the job completed without error. here's a snippet of my bacula-sd.conf Device { Name = LTO3 # Drive Index = 0 Media Type = LTO3 Device Type = Tape Archive Device = Tape0 AutomaticMount = yes # when device opened, read it Offline On Unmount = Yes AlwaysOpen = yes RemovableMedia = yes RandomAccess = no Changer Device = Tape0 Alert Command = "tapeinfo -f %c | findstr TapeAlert" } and here's the job in bacula-dir.conf Job { Name = "EjectTape" Type = Admin RunScript { Runs When = Before AbortJobOnError = No Command = "bconsole < c:\\eject" } Schedule = "EjectTape" Client = third-fd Messages = Standard Pool = "Tape" Storage = LTO3 Fileset = "Windows Full Set" } the file "c:\\eject" is a plain text file with the contents: unmount quit I have "C:\Program Files\Bacula\bin" in the system path, and if I run that script command on the command line, the tape ejects. Any suggestions??? Oh, on a side note, I'm having trouble with the tapealert feature: State: 0x1 (VSS_WS_STABLE) 27-Mar 21:00 third-sd: 3997 Bad alert command: tapeinfo -f Tape0 | findstr TapeAlert: ERR=Unknown error. when I run the command tapeinfo -f Tape0 | findstr TapeAlert on the command line, I get no output, which is to be expected. tapeinfo -f Tape0 by itself gives me all sorts of data on the drive and tape. Any thoughts about what it means "bad alert command"? Thanks a bunch! Gordon ------------------------------------------------------------------------- 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