Thanks, Stephen, for sharing your experience with amanda with me. I'll add the eject to my crontab; that's a good idea.
I suspect that what's confusing amanda in making my initial backup is the fact that I've still got running another, homebrew, backup system that's also writing to /etc/dumpdates. On the other hand, the report does say that the size of the backup of the two machines that worked is 3.5G, which might be close to a level 0 backup on these two machines. I'm still left with one question. Is it permissible to run more than one amdump in a day, even if tapes are changed between runs? Would this do anything positive, like push forward a more extensive dump that might be normally scheduled for the next day? Or, would amanda just see that not much has changed in the hour or two since the last dump, and not do much of anything? Thanks for your thoughts. -Kevin Zembower >>> Stephen Walton <[EMAIL PROTECTED]> 12/12/01 12:44AM >>> Hi, > /tmp/amanda/sendsize.*.debug file, and this showed that I had a > directory named /etc/amandates, instead of a file. I mad the same mistake. > However, when my backup finished, the report noted that the tape was > only 10% full, and it didn't eject. The 10% full number depends on timing of full dumps and so on. If you've set everything up right, then either amanda should have done a full dump of everything the first time out, or postponed some of them for later. I see everything from 10% to 99% full on my regular backups depending on how the mix of full & incrementals works out. amdump does not eject a tape. In my crontab I have something like: 5 12 * * * /opt/amanda/sbin/amdump daily && /bin/mt -t /dev/rmt/0m offl to get a tape eject when the backup is done. -- Stephen Walton, Professor of Physics and Astronomy, California State University, Northridge [EMAIL PROTECTED]
