Amanda-Users

Re: Partial backup

2006-07-14 12:02:20
Subject: Re: Partial backup
From: Jon LaBadie <jon AT jgcomp DOT com>
To: amanda-users AT amanda DOT org
Date: Fri, 14 Jul 2006 11:55:41 -0400
On Fri, Jul 14, 2006 at 08:13:40AM -0500, James Wilson wrote:
> <body bgcolor="#ffffff" text="#000000">
> What I meant before the backup is that I ran amdump manually waited for
> about a minute because it does the estimated size, then I ran amstatus.
> Then I ran amstatus again when it finished I do have the email after
> the backup if you want to see that. But there should be at least 2 gigs
> of data if not more that it should be backing up from that host. I am
> using an SMB share to back this host up. And I get a lot of timeout
> errors maybe you have seen this before? I'll paste the output from the
> email below.<br>
> <br>
> <pre wrap="">FAILED AND STRANGE DUMP DETAILS:
> 
> /--  amanda.transolutions.net //192.168.1.133/ifxsessions lev 1 STRANGE
> sendbackup: start [amanda.transolutions.net://192.168.1.133/ifxsessions level 
> 1]
> sendbackup: info BACKUP=/usr/bin/smbclient
> sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/bin/smbclient -f... -
> sendbackup: info COMPRESS_SUFFIX=.gz
> sendbackup: info end
> | Domain=[IFX-SE-02] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
> ? Call timed out: server did not respond after 20000 milliseconds listing 
> \Apex_SPFLD_ADT\Input\Archive\20060501\*
> ? Call timed out: server did not respond after 20000 milliseconds listing 
> \Apex_SPFLD_ADT\Input\Archive\2\*
> ? Call timed out: server did not respond after 20000 milliseconds listing 
> \Apex_SPFLD_ADT\Input\Archive\2\*
> ? Call timed out: server did not respond after 20000 milliseconds listing 
> \Apex_SPFLD_ADT\Input\Archive\2\*

As the first status was early in the same run as the second status,
I'll change my thoughts.  The two reports clearly said different
size estimates, 1231m vs 171m.  But the first said "partial estimate
done".  Amanda typically does estimates for a full dump and one or
more incremental levels.  After that the decision as to what level
backup to actually perform is done.

My guess is that your first status report caught amanda after the
level 0 estimate (1231m) and its decision to do an incremental
dump (171m).  Amanda appears to have chosen to do the smaller
incremental dump.  Your amreport would allow you to confirm this:

  HOSTNAME     DISK        L ORIG-MB OUT-MB ...
  -------------------------- -------------- ...
  bigcow       HOME        1     227     12 ...
  bigcow       LOCAL       1     125    122 ...
  bigcow       LastChanceC 0      32     17 ...

The "L" column is the level.

As to why you got only 5m out of 171m expected, well ... it is a PC ;(

Note my last line above.  "LastChance" is my wife's PC and the trailing
'C' in the disk name refers of course to the C drive.  Only 32 MB were
dumped on a level 0.  This is from an old run, I now dump over 7 GB on
a level 0.  I too was, and to a lesser degree still am getting those
"timed out" messages.  I've not seen them mentioned on the list, but
I have basically said - 'thats samba backups of a PC for yah'.  You
can more easily do that in a home rather than in a business environment.
Particularly if it is not your data ;)

But I did go from 32 MB to 7 GB with permission changes.  When I tried
to make changes from a normal boot up, I was unable to accomplish much.
Then I read in some Micro$oft note that somethings can only be done by
the actual administrator account, not by some other user with adminis-
trator privilege.  So I rebooted the PC into safe-mode (the only way to
get to the actual administrator account I read).  Then, on each drive,
I set the user amanda accesses to have full control, not just read, and
clicked the button to propogate the change down to all files and folders.

Suddenly I was backing up much more data and incrementals were smaller
than full dumps.

I don't recommend the changes I did.  Not being a PC person I don't know
all the consequences.  And it might be a policy violation in a business.
But it made a big difference for me.  There are still lots of files that
I get errors about not being able to be backed up.  And I still get those
"timed out" messages.  But now I'm getting the bulk of the data and it
appears to include most (all?) of what I'm looking to backup.


-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)

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