Amanda-Users

Re: [HELP] amverify fails restoring

2003-03-19 09:50:29
Subject: Re: [HELP] amverify fails restoring
From: "Fabio Corazza" <corazza AT prosa DOT com>
To: <amanda-users AT amanda DOT org>
Date: Wed, 19 Mar 2003 14:01:13 +0100
Paul Bijnens wrote:
> Op ma 17-03-2003, om 16:46 schreef Fabio Corazza:
>
>> PROSADAILY04 (uranus.prosa.com.__notorius_EXCHANGE$.20030307.0):
>> amrestore: WARNING: not at start of tape, file numbers will be offset
>
> Did you fsf the tape to the correct position first? Or was it still
> at EOF from the last run?  You should rewind the tape, or position the
> tape with fsf commands manually, or if you are using amanda 2.4.4
> there
> is an option to amrecover to do this automatically for you.

I'm using Amanda 2.4.2p2 from debian woody packages, anyway this is the
crontab file for the backup user:

0 16    * * 1-5    /usr/sbin/amcheck -m ProsaDaily
45 0    * * 2-6    /usr/sbin/amdump ProsaDaily; /bin/mt -f /dev/tape
rewind; /usr/sbin/amverify ProsaDaily >/dev/null; /bin/mt -f /dev/tape
rewoffl

The tape is rewinded before starting amverify. Note that /dev/tape is a
symbolic link to /dev/nst0.

>> amrestore:   0: restoring
>> uranus.prosa.com.__notorius_EXCHANGE$.20030307.0
>
> It is a samba backup, I see. What version of smbclient did you
> use?  Some versions (I believe 2.2.3 and before) had a bug in the
> builtin tar command, that screwed up the backup images (it did output
> an informational message to stdout instead of stderr).

Here it goes with Samba 2.2.7a.

uranus:~# dpkg -l | grep samba
ii  samba          2.2.7a-0.1     A LanManager like file and printer
server fo
ii  samba-common   2.2.7a-0.1     Samba common files used by both the
server a

> The word "exchange" make me wonder if it is an Micrsoft Exchange
> datafile that you backed up.  I'm not a user of Exchange, but normally
> Microsoft Exchange keeps these files open, and you cannot make a
> backup of it, without shutting down Microsoft Exchange.
> Are you really sure the backup did not complain?

It doesn't complain because EXCHANGE$ is a directory shared on a remote
server which, through NTBACKUP.EXE, acts as backup client for Exchange
5.5 and stores all the backup data on a file called exchangeBackup.bkf
in the EXCHANGE$ directory.

I can go through this and show you this is not the problem:

uranus:~# smbclient //notorius/EXCHANGE$ -U backup
added interface ip=192.168.1.20 bcast=192.168.1.255 nmask=255.255.255.0
Password:
Domain=[PROSADOM] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
smb: \> ls
  .                                   D        0  Wed Mar 19 00:00:18
2003
  ..                                  D        0  Wed Mar 19 00:00:18
2003
  exchangeBackup.bkf                  A 3086029824  Wed Mar 19 00:23:07
2003

                38162 blocks of size 1048576. 17993 blocks available
smb: \> get exchangeBackup.bkf
getting file \exchangeBackup.bkf of size 3086029824 as
exchangeBackup.bkf (6366.0 kb/s) (average 6366.0 kb/s)
smb: \>


I can try to upgrade to the last Amanda release, but I think the problem
is elsewhere...


P.S.: I can give two hints to improve the mailing list usability,
      even if probably they have been already discussed:

1) Put a prefix before the subject, it would be more easy to
   filter and create appropriate rules to avoid shuffling ml's
   mail from others (work, friends..)
2) Set the reply-to to amanda-users AT amanda DOT org, or is it just
   a client issue?

Thank you,
Fabio


<Prev in Thread] Current Thread [Next in Thread>