Re: Dealing with a dump too big

Hi, Stefan, Thanks for pointing out the option on amdump to just backup a single host or partition; I never used that, and overlooked what you were trying to tell me in my original response. I've been working since yesterday to implement your suggestions. I'll modify the slashes to

Re: Dealing with a dump too big

Hi, Kevin, on Dienstag, 22. Juni 2004 at 18:17 you wrote to amanda-users: KZ Hi, Stefan, KZ Thanks for pointing out the option on amdump to just backup a KZ single host or partition; I never used that, and overlooked what KZ you were trying to tell me in my original response. I've been KZ

Dealing with a dump too big

I'm trying to deal with a problem which I've just noticed. I've completely overwritten my level 0 backup of a disk called admin://db/f$. This is a SAMBA share from an NT server. I think I have complete level one backups: [EMAIL PROTECTED]:~ amadmin DailySet1 find admin //db/ |fgrep //db/f$

RE: Dealing with a dump too big

Title: RE: Dealing with a dump too big In the UK, we woudl flush a dump down the toilet, but not if it's too big ;-) -Original Message- From: [EMAIL PROTECTED] on behalf of KEVIN ZEMBOWER Sent: Mon 6/21/2004 4:46 PM To: [EMAIL PROTECTED] Cc: Subject: Dealing with a dump too big I'm

Re: Dealing with a dump too big

Hi, Kevin, on Montag, 21. Juni 2004 at 17:46 you wrote to amanda-users: KZ The disk F: on the NT server is indeed 13G in size, but I KZ didn't think that would be a problem, since I excluded KZ //db/f$/inetsrv, which is 9.1G. This filesystem, which I just KZ backup for the first time last run,

Re: Dealing with a dump too big

KEVIN ZEMBOWER wrote: The disk F: on the NT server is indeed 13G in size, but I didn't think that would be a problem, since I excluded //db/f$/inetsrv, which is 9.1G. This filesystem, which I just backup for the first time last run, backed up at level 0 just fine: There is a bug in the estimate

Re: Dealing with a dump too big

Stefan, hi, thanks for your suggestions. Here's the output before any changes are made: [EMAIL PROTECTED]:~ amadmin DailySet1 disklist admin //db/ snip of info for admin //db/c$ and admin //db/e$ line 100: host admin: interface default disk //db/f$: program GNUTAR

Re: Dealing with a dump too big

Hi, Kevin, on Montag, 21. Juni 2004 at 19:19 you wrote to amanda-users: KZ Stefan, hi, thanks for your suggestions. KZ Here's the output before any changes are made: [EMAIL PROTECTED]:~ amadmin DailySet1 disklist admin //db/ KZ snip of info for admin //db/c$ and admin //db/e$ KZ line 100: