On Tue Oct 23, 2001 at 11:48:19PM +0200, Bernhard R. Erdmann wrote: > > I've got amanda serwer 2.4.2p2 on freebsd 4.4rc5 and amanda client > > on linux RH7.0 and freebsd 3.4 release. > > There isn't a lot of data to backup, only 2 GB from every host. > > Backup is done every night, starting from cron. > > Streamer is 40/80GB Tandberg DLT1, I've only one tape. > > Go buy some more tapes - if writing to this single tape fails you will > be lost with no backup
Ok that's right, but in amanda documentation, there was written that one backup (6GB) on one tape (80GB) is a waste of space, thats why amanda support multiple backup on one tape. > > > In my opinion amanda should write next backup on tape just after the > > previous, so on one tape 80 GB there is a lot of place for lets say > > 4 backups. > > But when I run amrecover and type setdate ---21 (today is 23 ) > > amrecover says: > > 200 Working date set to 2001-10-21. > > No index records for cwd on new date > > Setting cwd to mount point > > > > But in directory /usr/local/amanda/DailySet1/index/"hostname"/"partition" > > ther is a lot of files like: 20011023_2.gz 20011022_2.gz 20011021_2.gz > > all in mode 600. > > So why amrecover says that there is no indexes, > > and I can't recover from few days earlier? > > Did you type "sethost <hostname>" and "setdisk <partition>" in > amrecover? Yes I did. When I type history in amrecover, output is: 200- Dump history for config "DailySet1" host "ekoraid" disk "/export" 201- 2001-10-25 0 DailySet123 5 200 Dump history for config "DailySet1" host "ekoraid" disk "/export" Backup is done every day since last two weeks, so something is wrong. "ekoraid" is amanda client. Maybe this is client not server problem?
