Thank you for the pointers...
> >I'm having the same problem here, also running Amanda 2.4.2p2.
>
> Actually, you're having a different problem. But be that as it may ...
>
> >ERROR: /export/dumps/amanda: rewinding tape: Inappropriate ioctl for
device
> > (expecting a new tape)
> >...
> >I had set tapedev "/export/dumps/amanda" in amanda.conf with the
(obviously
> >mistaken) understanding that Amanda would just dump to that dir. ...
>
> The 2.4.2p2 version of Amanda only writes to tapes. If you want to store
> your images in a disk area, you need what's called the "tapeio" feature.
> You can get that either via the amanda-242-tapeio CVS branch (see the
> FAQ for details on how to check out and build from CVS), or it's also
> part of 2.4.3, which is now in beta.
>
> Are you planning on leaving the images in that disk area, i.e. treating it
> like a pseudo tape, or are you planning on flushing them to tape later on?
I plan to buy a tape setup, but the kind I want wont be available in Japan
until March, so I am trying to test the system by dumping to hard disk for
the time being. It will also make the boss feel better to be able to see
backed up data physically on another machine. :-)
> If you plan to eventually flush them, then you want to do things
> differently (and 2.4.2p2 support this). Just set "reserve" to zero in
> the holding disk declaration so Amanda will go ahead and do full dumps,
> then set tapedev to something like "/no/such/device". The tape writing
> portion of Amanda will fail, but the dumping to the holding disk part
> will work. Then change tapedev and run amflush as needed (and set
> tapedev back after the amflush).
>
> In fact, the above might do what you want even without the flushing.
> It depends on what the goal is.
I set tapedev to literally "/no/such/device" :-)
and set reserve to 0.
I then ran:
# su amanda -c "amcleanup daily"
# su amanda -c "amcheck daily"
# su amanda -c "amdump daily"
I then checked the dump directory to see what happened:
# ls -l /export/dumps/amanda/
total 1
drwx------ 2 amanda backup 512 Feb 5 11:21 20020205/
and saw that a new directory with today's date has been created.
I then looked in that directory for backed up data, but:
# ls -al /export/dumps/amanda/20020205/
total 2
drwx------ 2 amanda backup 512 Feb 5 11:21 ./
drwxrwxr-x 3 10000 backup 512 Feb 5 11:21 ../
hmm... nothing...
Any idea what I'm missing?
The error mail I get from Amanda follows.
Thanks,
Shawn
*** A TAPE ERROR OCCURRED: [no tape online].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
mydom.co. /usr lev 0 FAILED [disk /usr offline on mydom.co.jp?]
STATISTICS:
Total Full Daily
-------- -------- --------
Estimate Time (hrs:min) 0:00
Run Time (hrs:min) 0:00
Dump Time (hrs:min) 0:00 0:00 0:00
Output Size (meg) 0.0 0.0 0.0
Original Size (meg) 0.0 0.0 0.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped 0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min) 0:00 0:00 0:00
Tape Size (meg) 0.0 0.0 0.0
Tape Used (%) 0.0 0.0 0.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Adding new disk mydom.co.jp:/usr.
driver: WARNING: got empty schedule from planner
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-------------------------- --------------------------------- ------------
mydom.co /usr 0 FAILED ---------------------------------------
(brought to you by Amanda version 2.4.2p2)
