Re: Full dump not running in dumpcycle days (FIXED and a question)
On Mon, 10 Dec 2001 at 9:53am, [EMAIL PROTECTED] wrote I figured out what my issue was late last week so please forgive in the delay in reporting my findings. What I am doing is not putting a tape in the drive, so that forces amanda to write my incrementals to disk. What appears to be happening is amanda will not run a full dump if there is no tape in the drive. It will fall back on an incremental though. Is this the desired behavior? My fulls only require about 15G's currently. My holding disk is 35G. Why will amanda not write a level 0 if the holding disk has enough space? Look for a parameter in amanda.conf called 'reserve'. The default is 100. That is the percentage of holding disk space that amanda reserves for incremental backups when running in degraded mode (i.e. no tape in the drive). If you want to get full backups in degraded mode, you need to set the reserve to something 100 (enough less than 100, obviously, to fit your full backups). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Full dump not running in dumpcycle days (FIXED and a question)
Check out the RESERVE parameter in amanda.conf. It specifies how much of the holding disk can be used for degraded mode (no tape) dumps to the holding disk. IIRC, it defaults to 30%. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, December 10, 2001 9:54 AM To: [EMAIL PROTECTED] Subject: Full dump not running in dumpcycle days (FIXED and a question) Hello all, I figured out what my issue was late last week so please forgive in the delay in reporting my findings. What I am doing is not putting a tape in the drive, so that forces amanda to write my incrementals to disk. What appears to be happening is amanda will not run a full dump if there is no tape in the drive. It will fall back on an incremental though. Is this the desired behavior? My fulls only require about 15G's currently. My holding disk is 35G. Why will amanda not write a level 0 if the holding disk has enough space? As always thanks for any insight. Andrew
Re: Full dump not running in dumpcycle days
The only message in the FAILED AND STRANGE is that a file changed while reading it. amadmin CONFIG due tells me that each is overdue. I am going to do a little more looking into it today and will report my results tomorrow. Andrew On Tue, 4 Dec 2001, Joshua Baker-LePain wrote: On Tue, 4 Dec 2001 at 2:42pm, [EMAIL PROTECTED] wrote I do not have anything defined for runspercycle. What messages are your refering to? I have the mails for each day. OK, runspercycle defaults to be the same as dumpcycle. Are you running amdump every night? Are there any messages in the FAILED AND STRANGE DUMP SUMMARY or under NOTES? What does 'amadmin CONFIG due' say? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Full dump not running in dumpcycle days
Hello, I am seeing some strang behavior with my amanda setup. I have an dump that has a dumpcycle of 7 days, yet seven days has passed and I have not see a full dump. In fact my last full dump was on Nov 20. I have had a successful incremental dump every day since, but no full. Below are the line I believe are relavent from my amanda.conf. dumpcycle 7 days# the number of days in the normal dump cycle tapecycle 10 tapes # the number of tapes in rotation bumpsize 20 MB # minimum savings (threshold) to bump level 1 - 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * (level-1)**bumpmult diskdir /holdingdisk # where the holding disk is disksize 25 GB # how much space can we use on it Any ideas? Thanks in Advance. Andrew
Re: Full dump not running in dumpcycle days
On Tue, 4 Dec 2001 at 10:51am, [EMAIL PROTECTED] wrote I am seeing some strang behavior with my amanda setup. I have an dump that has a dumpcycle of 7 days, yet seven days has passed and I have not see a full dump. In fact my last full dump was on Nov 20. I have had a successful incremental dump every day since, but no full. Below are the line I believe are relavent from my amanda.conf. dumpcycle 7 days# the number of days in the normal dump cycle tapecycle 10 tapes # the number of tapes in rotation bumpsize 20 MB # minimum savings (threshold) to bump level 1 - 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * (level-1)**bumpmult diskdir /holdingdisk # where the holding disk is disksize 25 GB # how much space can we use on it What's runspercycle? Are you getting any messages in your nightly reports from amanda? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Full dump not running in dumpcycle days
I do not have anything defined for runspercycle. What messages are your refering to? I have the mails for each day. Andrew On Tue, 4 Dec 2001, Joshua Baker-LePain wrote: On Tue, 4 Dec 2001 at 10:51am, [EMAIL PROTECTED] wrote I am seeing some strang behavior with my amanda setup. I have an dump that has a dumpcycle of 7 days, yet seven days has passed and I have not see a full dump. In fact my last full dump was on Nov 20. I have had a successful incremental dump every day since, but no full. Below are the line I believe are relavent from my amanda.conf. dumpcycle 7 days# the number of days in the normal dump cycle tapecycle 10 tapes # the number of tapes in rotation bumpsize 20 MB # minimum savings (threshold) to bump level 1 - 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * (level-1)**bumpmult diskdir /holdingdisk # where the holding disk is disksize 25 GB # how much space can we use on it What's runspercycle? Are you getting any messages in your nightly reports from amanda? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Full dump not running in dumpcycle days
On Tue, 4 Dec 2001 at 2:42pm, [EMAIL PROTECTED] wrote I do not have anything defined for runspercycle. What messages are your refering to? I have the mails for each day. OK, runspercycle defaults to be the same as dumpcycle. Are you running amdump every night? Are there any messages in the FAILED AND STRANGE DUMP SUMMARY or under NOTES? What does 'amadmin CONFIG due' say? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Dump not running
I will give chg-manual a go.. however here are the system details. Tape Drive - Sony DDS TLS-S9000 ( it has an auto changer built in, which uses an 8 tape holder stacker type layout ) OS - Redhat Linux 6.2 Amanda Version - Amanda-2.4.1p1 If you would like any more information I should be able to provide it... but as I said I'll give the manual changer a try too. Nathan -Original Message- From: Bort, Paul [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 17 January 2001 2:29 To: 'Nathan Bird'; '[EMAIL PROTECTED]' Subject: RE: Dump not running Does it behave better if you change your changer to 'chg-manual'? It looks kind of like it's trying to talk to a non-existent changer. If you provide more information about your hardware (drive type, changer type) and software (OS and AMANDA Version), that would help too. -Original Message- From: Nathan Bird [mailto:[EMAIL PROTECTED]] Sent: Monday, January 15, 2001 10:18 PM To: '[EMAIL PROTECTED]' Subject: Dump not running Hi, Whenever I run 'amcheck' I get [root@paperbark sbin]# ./amcheck hlink-data2 Amanda Tape Server Host Check - /usr/local/amanda/dumps: 1900471 KB disk space available, that's plenty. amcheck-server: slot 8: date 20010112 label hlink-data12 (first labelstr match) NOTE: skipping tape-writable test. Tape hlink-data12 label ok. Server check took 6.004 seconds. Amanda Backup Client Hosts Check Client check: 1 host checked in 0.565 seconds, 0 problems found. (brought to you by Amanda 2.4.1p1) which to me would appear as though the dump is going to run correctly, however the cronjob that I have set up for amdump never actually runs. I have tried changing my disklist to only backup the /tmp directory and this appears to run fine, but if I try to backup my /user directory 'amdump' never appears to finish. so i tried to run amverify and it just does this [root@paperbark sbin]# ./amverify hlink-data2 Tape changer is chg-multi... 1 slot... Verify summary to root Defects file is /tmp/amverify.24428/defects amverify hlink-data2 Tue Jan 16 14:14:28 EST 2001 Loading current slot... Using device aborted!for device to go ready... cat: /tmp/amverify.24428/tapelist: No such file or directory and I eventually have to push ctrl-c to stop it, it nevers becomes 'ready' what should I be looking at to try and work out what is happening cheers Nathan
Dump not running
Hi, Whenever I run 'amcheck' I get [root@paperbark sbin]# ./amcheck hlink-data2 Amanda Tape Server Host Check - /usr/local/amanda/dumps: 1900471 KB disk space available, that's plenty. amcheck-server: slot 8: date 20010112 label hlink-data12 (first labelstr match) NOTE: skipping tape-writable test. Tape hlink-data12 label ok. Server check took 6.004 seconds. Amanda Backup Client Hosts Check Client check: 1 host checked in 0.565 seconds, 0 problems found. (brought to you by Amanda 2.4.1p1) which to me would appear as though the dump is going to run correctly, however the cronjob that I have set up for amdump never actually runs. I have tried changing my disklist to only backup the /tmp directory and this appears to run fine, but if I try to backup my /user directory 'amdump' never appears to finish. so i tried to run amverify and it just does this [root@paperbark sbin]# ./amverify hlink-data2 Tape changer is chg-multi... 1 slot... Verify summary to root Defects file is /tmp/amverify.24428/defects amverify hlink-data2 Tue Jan 16 14:14:28 EST 2001 Loading current slot... Using device aborted!for device to go ready... cat: /tmp/amverify.24428/tapelist: No such file or directory and I eventually have to push ctrl-c to stop it, it nevers becomes 'ready' what should I be looking at to try and work out what is happening cheers Nathan
