Re: dumpcycle / runspercycle / tapecycle best practices?
Hi, as i'm using chg-scsi with some changers under linux let's check a few things : 1.) remove all comments from chg-scsi.conf, sometimes i had problems with chg-scsi which went away after removing them all. 2.) set lastslot to 4 or your cleaningtape will be loaded in every search cycle through the magazin. (probably not what you want) 3.) your changer and your tapedrive are recognized at bootup by the kernel, correct? ( do you see both when you do a cat /proc/scsi/scsi ?) Christoph Erik Anderson schrieb: On Wed, 3 Nov 2004 17:46:19 -0500, Jon LaBadie [EMAIL PROTECTED] wrote: I've not used the scsi chg script/program. Have you read and done what it says in the documentation and example files to set up config files for chg-scsi ... Yes, indeed I have. Here's my chg-scsi.conf: number_configs 1 eject 1 # Tapedrives need an eject command sleep 5 # Seconds to wait until the tape gets ready cleanmax10 # How many times could a cleaning tape get used changerdev /dev/sg1 # # Next comes the data for drive 0 # config 0 drivenum0 dev /dev/nst0 # the device that is used for the tapedrive 0 startuse0 # The slots associated with the drive 0 enduse 5 # statfile/etc/amanda/tape-slot # The file where the actual slot is stored cleancart 5 # the slot where the cleaningcartridge for drive 0 is located cleanfile /etc/amanda/tape-clean # The file where the cleanings are recorded usagecount /etc/amanda/backup/totaltime
Re: dumpcycle / runspercycle / tapecycle best practices?
On Thu, 04 Nov 2004 09:23:10 +0100, Christoph Scheeder [EMAIL PROTECTED] wrote: Hi, as i'm using chg-scsi with some changers under linux let's check a few things : 1.) remove all comments from chg-scsi.conf, sometimes i had problems with chg-scsi which went away after removing them all. 2.) set lastslot to 4 or your cleaningtape will be loaded in every search cycle through the magazin. (probably not what you want) 3.) your changer and your tapedrive are recognized at bootup by the kernel, correct? ( do you see both when you do a cat /proc/scsi/scsi ?) Hello Christoph - I have removed all of the comments from my chg-scsi.conf, and I have noticed no change in behavior. And yes, my changer and tape drive are surely recognized by the kernel. I am able to load/read/write/unload tapes using the mt and mtx commands. Thanks! -Erik
Re: dumpcycle / runspercycle / tapecycle best practices?
On Thu, Nov 04, 2004 at 08:31:31AM -0600, Erik Anderson enlightened us: On Thu, 04 Nov 2004 09:23:10 +0100, Christoph Scheeder [EMAIL PROTECTED] wrote: Hi, as i'm using chg-scsi with some changers under linux let's check a few things : 1.) remove all comments from chg-scsi.conf, sometimes i had problems with chg-scsi which went away after removing them all. 2.) set lastslot to 4 or your cleaningtape will be loaded in every search cycle through the magazin. (probably not what you want) 3.) your changer and your tapedrive are recognized at bootup by the kernel, correct? ( do you see both when you do a cat /proc/scsi/scsi ?) Hello Christoph - I have removed all of the comments from my chg-scsi.conf, and I have noticed no change in behavior. And yes, my changer and tape drive are surely recognized by the kernel. I am able to load/read/write/unload tapes using the mt and mtx commands. Then why not use chg-zd-mtx? :-) -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 pgpYZq8e1K2Eg.pgp Description: PGP signature
Re: dumpcycle / runspercycle / tapecycle best practices?
On Wed, Nov 03, 2004 at 10:53:59PM +0100, Jukka Salmi wrote:
Hmm, when setting dumpcycle to zero, to what value should runspercycle
be set if amdump runs once a day? Zero (same as dumpcycle) or one?
Both settings are equivalent. From planner.c:
if (runs_per_cycle = 0) {
runs_per_cycle = 1;
}
So pick the one that looks nicer :-)
--
| | /\
|-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
The animal that coils in a circle is the serpent; that's why so
many cults and myths of the serpent exist, because it's hard to
represent the return of the sun by the coiling of a hippopotamus.
- Umberto Eco, Foucault's Pendulum
Re: dumpcycle / runspercycle / tapecycle best practices?
Eric Siegerman -- amanda-users (2004-11-04 14:02:13 -0500):
On Wed, Nov 03, 2004 at 10:53:59PM +0100, Jukka Salmi wrote:
Hmm, when setting dumpcycle to zero, to what value should runspercycle
be set if amdump runs once a day? Zero (same as dumpcycle) or one?
Both settings are equivalent. From planner.c:
if (runs_per_cycle = 0) {
runs_per_cycle = 1;
}
So pick the one that looks nicer :-)
Fine, thanks!
Jukka
--
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~
dumpcycle / runspercycle / tapecycle best practices?
Greetings - I'm just starting to get Amanda set up. I have a 5-tape DLT7000 changer. I've been going back and forth about how to structure my backup policies. The amount of data that will be being backed up is around 10 gigs. The DLTIV tapes I'm using should hold around 30 gigs, according to amtapetype. I have a ton of tapes to work with - approximately 80 tapes. Because of the relatively small amount of data I'm working with and the large number of tapes, I figure that I might as well do a full backup every night. Would this make sense? That's my first question. My second question is how to implement this in my amanda.conf. I believe the following should be correct, but I wanted to run it by the list to see if there are any improvements: ... dumpcycle 1 day runspercycle 1 day tapecycle 28 days ... If I'm thinking correctly, this will force Amanda to do a full backup every night, and I'll have 28 days worth of full backups in the cycle. Correct? Any suggestions? Thanks!
Re: dumpcycle / runspercycle / tapecycle best practices?
--On Wednesday, November 03, 2004 14:44:55 -0600 Erik Anderson [EMAIL PROTECTED] wrote: Greetings - I'm just starting to get Amanda set up. I have a 5-tape DLT7000 changer. I've been going back and forth about how to structure my backup policies. The amount of data that will be being backed up is around 10 gigs. The DLTIV tapes I'm using should hold around 30 gigs, according to amtapetype. I have a ton of tapes to work with - approximately 80 tapes. Because of the relatively small amount of data I'm working with and the large number of tapes, I figure that I might as well do a full backup every night. Would this make sense? It wil make restores simpler. The only reason I can think of to consider not doing it would be if you had a very short backup window or very slow network link between clients and server. Otherwise I'd go for the fulls every day. That's my first question. My second question is how to implement this in my amanda.conf. I believe the following should be correct, but I wanted to run it by the list to see if there are any improvements: ... dumpcycle 1 day runspercycle 1 day runspercycle has no units, it just the number of runs per dumpcycle, so just make it 1. tapecycle 28 days ... If I'm thinking correctly, this will force Amanda to do a full backup every night, and I'll have 28 days worth of full backups in the cycle. Correct? To make doubly sure, you could define allways-full in your dumptype. Frank Any suggestions? Thanks! -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: dumpcycle / runspercycle / tapecycle best practices?
On Wed, 3 Nov 2004 16:20:18 -0500, Jon LaBadie [EMAIL PROTECTED] wrote: Not quite. The tapecycle means amanda will not overwrite a tape until 27 others in the tapelist have been used. You could actually cycle 40 or 80 tapes and leave the tapecycle at 28 or reduce it to 7. Tape- cycle is how soon can a tape be reused. That makes tapecycle much easier to understand. Thanks! Yeah I know that I could cycle a bunch more tapes, but frankly, I don't really want (nor have the need) for that much retention. And, get that day and days off of the runspercycle and tapecycle lines. They are unit-less integers. One run per day. Twenty eight tapes minimum in the cycle. Same with runspercycle. Yeah - that was a typo on my part...thanks for pointing it out, though.
Re: dumpcycle / runspercycle / tapecycle best practices?
On Wed, 03 Nov 2004 15:24:43 -0600, Frank Smith [EMAIL PROTECTED] wrote: It wil make restores simpler. The only reason I can think of to consider not doing it would be if you had a very short backup window or very slow network link between clients and server. Otherwise I'd go for the fulls every day. Sounds like fulls are the way to go...my backup window is not a problem, and the systems are all connected via switched 10/100 ethernet, so that shouldn't be an issue either. runspercycle has no units, it just the number of runs per dumpcycle, so just make it 1. Sweet - thanks. To make doubly sure, you could define allways-full in your dumptype. That's good to know - I'll put that into my dumptype.
Re: dumpcycle / runspercycle / tapecycle best practices?
Hi, Erik Anderson -- amanda-users (2004-11-03 14:44:55 -0600): [...] full backup every night. [...] dumpcycle 1 day According to the amanda man page you should set dumpcycle to zero to get full dumps each run. Hmm, when setting dumpcycle to zero, to what value should runspercycle be set if amdump runs once a day? Zero (same as dumpcycle) or one? Does it matter at all? TIA, Jukka -- bashian roulette: $ ((RANDOM%6)) || rm -rf ~
Re: dumpcycle / runspercycle / tapecycle best practices?
On Wed, Nov 03, 2004 at 10:53:59PM +0100, Jukka Salmi wrote: Hi, Erik Anderson -- amanda-users (2004-11-03 14:44:55 -0600): [...] full backup every night. [...] dumpcycle 1 day According to the amanda man page you should set dumpcycle to zero to get full dumps each run. Hmm, when setting dumpcycle to zero, to what value should runspercycle be set if amdump runs once a day? Zero (same as dumpcycle) or one? Does it matter at all? Good point, one advantage the minor situation that you run a second amdump in the same day. With dumpcycle 0 days you are certain to be due for full dumps again. BTW on the tapecycle, an advantage of having more tapes in cycle than the number listed in amanda.conf is the occasional need to take a tape out of rotation. Bad or damaged tape, temporary or permanent archiving, or whatever. Having more tapes in rotation than the tapecycle count means you do not have to amlabel a new tape right then and there. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: dumpcycle / runspercycle / tapecycle best practices?
On Wed, 3 Nov 2004 17:02:02 -0500, Jon LaBadie [EMAIL PROTECTED] wrote: BTW on the tapecycle, an advantage of having more tapes in cycle than the number listed in amanda.conf is the occasional need to take a tape out of rotation. Bad or damaged tape, temporary or permanent archiving, or whatever. Having more tapes in rotation than the tapecycle count means you do not have to amlabel a new tape right then and there. That's a great idea. On a different note, I just attempted to do my first amlabel operation, and this is what I got: [EMAIL PROTECTED] amanda $ amlabel LPD LPD000 slot 0 amlabel: could not load slot 0: could not read result from /usr/libexec/chg-scsi Ideas? Google didn't seem to have any suggestions.
Re: dumpcycle / runspercycle / tapecycle best practices?
On Wed, Nov 03, 2004 at 04:05:56PM -0600, Erik Anderson wrote: On a different note, I just attempted to do my first amlabel operation, and this is what I got: [EMAIL PROTECTED] amanda $ amlabel LPD LPD000 slot 0 amlabel: could not load slot 0: could not read result from /usr/libexec/chg-scsi Ideas? Google didn't seem to have any suggestions. Don't amlabel until you can use amtape and amcheck. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: dumpcycle / runspercycle / tapecycle best practices?
On Wed, 3 Nov 2004 17:22:14 -0500, Jon LaBadie [EMAIL PROTECTED] wrote: Don't amlabel until you can use amtape and amcheck. I get a similar result from amtape: [EMAIL PROTECTED] amanda $ amtape LPD show amtape: could not get changer info: could not read result from /usr/libexec/chg-scsi
Re: dumpcycle / runspercycle / tapecycle best practices?
On Wed, Nov 03, 2004 at 04:25:37PM -0600, Erik Anderson wrote: On Wed, 3 Nov 2004 17:22:14 -0500, Jon LaBadie [EMAIL PROTECTED] wrote: Don't amlabel until you can use amtape and amcheck. I get a similar result from amtape: [EMAIL PROTECTED] amanda $ amtape LPD show amtape: could not get changer info: could not read result from /usr/libexec/chg-scsi I've not used the scsi chg script/program. Have you read and done what it says in the documentation and example files to set up config files for chg-scsi ... -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: dumpcycle / runspercycle / tapecycle best practices?
On Wed, 3 Nov 2004 17:46:19 -0500, Jon LaBadie [EMAIL PROTECTED] wrote: I've not used the scsi chg script/program. Have you read and done what it says in the documentation and example files to set up config files for chg-scsi ... Yes, indeed I have. Here's my chg-scsi.conf: number_configs 1 eject 1 # Tapedrives need an eject command sleep 5 # Seconds to wait until the tape gets ready cleanmax10 # How many times could a cleaning tape get used changerdev /dev/sg1 # # Next comes the data for drive 0 # config 0 drivenum0 dev /dev/nst0 # the device that is used for the tapedrive 0 startuse0 # The slots associated with the drive 0 enduse 5 # statfile/etc/amanda/tape-slot # The file where the actual slot is stored cleancart 5 # the slot where the cleaningcartridge for drive 0 is located cleanfile /etc/amanda/tape-clean # The file where the cleanings are recorded usagecount /etc/amanda/backup/totaltime
Re: dumpcycle / runspercycle / tapecycle best practices?
On Wed, 3 Nov 2004 17:46:19 -0500, Jon LaBadie [EMAIL PROTECTED] wrote: I've not used the scsi chg script/program. Have you read and done what it says in the documentation and example files to set up config files for chg-scsi ... I'm assumming that chg-scsi is the correct glue script for my environment...I have a 6-tape changer with one drive.
Re: dumpcycle / runspercycle / tapecycle best practices?
On Wed, Nov 03, 2004 at 05:14:35PM -0600, Erik Anderson wrote: On Wed, 3 Nov 2004 17:46:19 -0500, Jon LaBadie [EMAIL PROTECTED] wrote: I've not used the scsi chg script/program. Have you read and done what it says in the documentation and example files to set up config files for chg-scsi ... I'm assumming that chg-scsi is the correct glue script for my environment...I have a 6-tape changer with one drive. No, that is just one of several possibilities. Tape drives have traditionally been scsi. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
