Getting Amanda to production
hello, I have a few question in mind so I'll be able to better configure it. 1) So far I tested Amanda and backed up data on a hard drive and am quit happy with the results. Recently we got a new tape drive and I need to start backing up our data into taps. I am going to use the same Amanda server and clients. Should and if so how do I initialize Amanda so it won't care about previous backups? Additionally I'll probably have to do some more testing in order to see how much time/bandwidth Amanda uses when it backup to our tape drive. But after doing those tests - can I delete those files from the tape? 2) I understand that Amanda has its algorithm that decides when do to a full backup, or an incremental one. But I am a little confused with labeling tapes. (amlabel) When I used the hard-disk I define each hard-drive 'partition' as 4GB and then amlabel each disk e.g. #/usr/sbin/amlabel DailySet1 HISS01 slot 1 #/usr/sbin/amlabel DailySet1 HISS02 slot 2 ... However, I have tapes that each can store 400 compress data, and we have to store about 30GB - am I domed to use each tape for one backup - or can I 'partition' those tapes? Do I have to put each tape in the tape drive and run amlabel? 3) We have a local and remote sites that we have to backup any thoughts, comments on what should I keep in mine before doing so. Additionally any recommendation for what to use to secure our data when backing up remotely? I read that I can use TCP wrappers but how do I implement it with Amanda? 4) Finally, we have one tape drive and about 20 servers that we need to backup from. Some of those servers run on Solaris, some on Windows. Can I back all servers on the same tape, or do I need to set separate tapes for Win machines? Many thanks, gil
Re: Getting Amanda to production
On Fri, Feb 04, 2005 at 02:43:55PM -0500, Gil Naveh wrote: hello, I have a few question in mind so I'll be able to better configure it. 1) So far I tested Amanda and backed up data on a hard drive and am quit happy with the results. Recently we got a new tape drive and I need to start backing up our data into taps. I am going to use the same Amanda server and clients. Should and if so how do I initialize Amanda so it won't care about previous backups? Additionally I'll probably have to do some more testing in order to see how much time/bandwidth Amanda uses when it backup to our tape drive. But after doing those tests - can I delete those files from the tape? I'd start a different config for the tape. Currently you probably do a cronjob with amdump vtapeconfig, simply comment that out entry and add an amdump realtapeconfig. That way, if you ever need to do vtape backups again, you can just uncomment it. 2) I understand that Amanda has its algorithm that decides when do to a full backup, or an incremental one. But I am a little confused with labeling tapes. (amlabel) When I used the hard-disk I define each hard-drive 'partition' as 4GB and then amlabel each disk e.g. #/usr/sbin/amlabel DailySet1 HISS01 slot 1 #/usr/sbin/amlabel DailySet1 HISS02 slot 2 ... However, I have tapes that each can store 400 compress data, and we have to store about 30GB - am I domed to use each tape for one backup yes - or can I 'partition' those tapes? no What some who have a large holding disk(s) space is to let several dump runs collect on the holding disk(s) by not putting a tape in the drive. Amrecover, I'm pretty sure, works with the taped or holding disk dumps. Then insert a tape and amflush them to tape. Do I have to put each tape in the tape drive and run amlabel? yes 3) We have a local and remote sites that we have to backup any thoughts, comments on what should I keep in mine before doing so. Additionally any recommendation for what to use to secure our data when backing up remotely? I read that I can use TCP wrappers but how do I implement it with Amanda? Don't bring them all on line at the same time. Make all your disklist entries but put a # sign to comment them out. Uncomment a couple each dump. Run amcheck with several from each client uncommented BEFORE even thinking about a dump. Maybe use your vtape config to test drive a client before moving them to the big show. 4) Finally, we have one tape drive and about 20 servers that we need to backup from. Some of those servers run on Solaris, some on Windows. Can I back all servers on the same tape, or do I need to set separate tapes for Win machines? Both can share a config. Lots of ways to do the M$ machines, none fully satisfactory. Samba clients to one or several of your unix hosts, nfs shares if your M$ boxes are nfs servers (possibly from M$'s free Services For Unix product - SFU), some windows backup program that writes to a file and backup that single file/directory with amanda, install cygwin on each box and install amanda so it looks like a unix host. Many limitations to backing up M$ boxes, set your expectations low and you won't be unhappy. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Getting Amanda to production
On Friday 04 Feb 2005 19:43, you wrote: hello, I have a few question in mind so I'll be able to better configure it. 1) So far I tested Amanda and backed up data on a hard drive and am quit happy with the results. Recently we got a new tape drive and I need to start backing up our data into taps. I am going to use the same Amanda server and clients. Should and if so how do I initialize Amanda so it won't care about previous backups? Just modify your disklist entries etc. If you don't care, Amanda won't care. As long as you use amlabel the new tapes. Additionally I'll probably have to do some more testing in order to see how much time/bandwidth Amanda uses when it backup to our tape drive. But after doing those tests - can I delete those files from the tape? Just over write them or remove them with amadmin 2) I understand that Amanda has its algorithm that decides when do to a full backup, or an incremental one. But I am a little confused with labeling tapes. (amlabel) When I used the hard-disk I define each hard-drive 'partition' as 4GB and then amlabel each disk e.g. #/usr/sbin/amlabel DailySet1 HISS01 slot 1 #/usr/sbin/amlabel DailySet1 HISS02 slot 2 ... However, I have tapes that each can store 400 compress data, and we have to store about 30GB - am I domed to use each tape for one backup - or can I 'partition' those tapes? Yes, one tape for one backup and you can't partition the tapes, but one backup can be many clients. Do I have to put each tape in the tape drive and run amlabel? Of course, how would Amanda know what tapes to use? 3) We have a local and remote sites that we have to backup any thoughts, comments on what should I keep in mine before doing so. Additionally any recommendation for what to use to secure our data when backing up remotely? I would use rsync to get the remote files if they are across the internet and then backup the machine they go to. I read that I can use TCP wrappers but how do I implement it with Amanda? This is in the docs. 4) Finally, we have one tape drive and about 20 servers that we need to backup from. Some of those servers run on Solaris, some on Windows. Can I back all servers on the same tape, or do I need to set separate tapes for Win machines? All one tape, just get teh right clients installed. Many thanks, gil -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1467 624141 M +44 (0) 7930 323266 F +44 (0) 1224 742001 E [EMAIL PROTECTED] Open Source. Open Solutions(tm). http://www.suretecsystems.com/
RE: Getting Amanda to production
Thanks Gavin and Jon, Wow that was great help. Regarding my first question, what should I do with the 'old' labels (the hard disk) can I delete them? if not how Amanda knows to write on the new tape drive and not on the hard disk. Sincerely, gil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jon LaBadie Sent: Friday, February 04, 2005 3:46 PM To: Amanda-Users Subject: Re: Getting Amanda to production On Fri, Feb 04, 2005 at 02:43:55PM -0500, Gil Naveh wrote: hello, I have a few question in mind so I'll be able to better configure it. 1) So far I tested Amanda and backed up data on a hard drive and am quit happy with the results. Recently we got a new tape drive and I need to start backing up our data into taps. I am going to use the same Amanda server and clients. Should and if so how do I initialize Amanda so it won't care about previous backups? Additionally I'll probably have to do some more testing in order to see how much time/bandwidth Amanda uses when it backup to our tape drive. But after doing those tests - can I delete those files from the tape? I'd start a different config for the tape. Currently you probably do a cronjob with amdump vtapeconfig, simply comment that out entry and add an amdump realtapeconfig. That way, if you ever need to do vtape backups again, you can just uncomment it. 2) I understand that Amanda has its algorithm that decides when do to a full backup, or an incremental one. But I am a little confused with labeling tapes. (amlabel) When I used the hard-disk I define each hard-drive 'partition' as 4GB and then amlabel each disk e.g. #/usr/sbin/amlabel DailySet1 HISS01 slot 1 #/usr/sbin/amlabel DailySet1 HISS02 slot 2 ... However, I have tapes that each can store 400 compress data, and we have to store about 30GB - am I domed to use each tape for one backup yes - or can I 'partition' those tapes? no What some who have a large holding disk(s) space is to let several dump runs collect on the holding disk(s) by not putting a tape in the drive. Amrecover, I'm pretty sure, works with the taped or holding disk dumps. Then insert a tape and amflush them to tape. Do I have to put each tape in the tape drive and run amlabel? yes 3) We have a local and remote sites that we have to backup any thoughts, comments on what should I keep in mine before doing so. Additionally any recommendation for what to use to secure our data when backing up remotely? I read that I can use TCP wrappers but how do I implement it with Amanda? Don't bring them all on line at the same time. Make all your disklist entries but put a # sign to comment them out. Uncomment a couple each dump. Run amcheck with several from each client uncommented BEFORE even thinking about a dump. Maybe use your vtape config to test drive a client before moving them to the big show. 4) Finally, we have one tape drive and about 20 servers that we need to backup from. Some of those servers run on Solaris, some on Windows. Can I back all servers on the same tape, or do I need to set separate tapes for Win machines? Both can share a config. Lots of ways to do the M$ machines, none fully satisfactory. Samba clients to one or several of your unix hosts, nfs shares if your M$ boxes are nfs servers (possibly from M$'s free Services For Unix product - SFU), some windows backup program that writes to a file and backup that single file/directory with amanda, install cygwin on each box and install amanda so it looks like a unix host. Many limitations to backing up M$ boxes, set your expectations low and you won't be unhappy. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Getting Amanda to production
On Fri, Feb 04, 2005 at 05:02:59PM -0500, Gil Naveh wrote: Thanks Gavin and Jon, Wow that was great help. Regarding my first question, what should I do with the 'old' labels (the hard disk) can I delete them? Are they important to you? if not how Amanda knows to write on the new tape drive and not on the hard disk. How did it know to write to the vtapes? You told it where to write. How will it know where to write to the real tapes? You will tell it. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: Getting Amanda to production
ok you can laugh at me :) but I don't understand something with amlabel: how does it knows which tape drive I am referring to? since the command looks like: #amlabel DailySet1 labelname thx, gil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jon LaBadie Sent: Friday, February 04, 2005 5:13 PM To: amanda-users@amanda.org Subject: Re: Getting Amanda to production On Fri, Feb 04, 2005 at 05:02:59PM -0500, Gil Naveh wrote: Thanks Gavin and Jon, Wow that was great help. Regarding my first question, what should I do with the 'old' labels (the hard disk) can I delete them? Are they important to you? if not how Amanda knows to write on the new tape drive and not on the hard disk. How did it know to write to the vtapes? You told it where to write. How will it know where to write to the real tapes? You will tell it. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: Getting Amanda to production
On Fri, 4 Feb 2005 at 5:40pm, Gil Naveh wrote ok you can laugh at me :) but I don't understand something with amlabel: how does it knows which tape drive I am referring to? since the command looks like: #amlabel DailySet1 labelname It uses the drive specified in DailySet1's amanda.conf. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Getting Amanda to production
On Friday 04 February 2005 14:43, Gil Naveh wrote: hello, I have a few question in mind so I'll be able to better configure it. 1) So far I tested Amanda and backed up data on a hard drive and am quit happy with the results. Recently we got a new tape drive and I need to start backing up our data into taps. I am going to use the same Amanda server and clients. Should and if so how do I initialize Amanda so it won't care about previous backups? Additionally I'll probably have to do some more testing in order to see how much time/bandwidth Amanda uses when it backup to our tape drive. But after doing those tests - can I delete those files from the tape? 2) I understand that Amanda has its algorithm that decides when do to a full backup, or an incremental one. But I am a little confused with labeling tapes. (amlabel) When I used the hard-disk I define each hard-drive 'partition' as 4GB and then amlabel each disk e.g. #/usr/sbin/amlabel DailySet1 HISS01 slot 1 #/usr/sbin/amlabel DailySet1 HISS02 slot 2 ... However, I have tapes that each can store 400 compress data, You meant 400MB, or 400GB? and we have to store about 30GB - am I domed to use each tape for one backup - or can I 'partition' those tapes? Amanda does not to my knowledge, support partitioned tapes. I think it would be going against the basic premise amanda has of having the data safest at all times. Therefore amanda uses a different tape each run, and only re-uses that tape when its time to re-use it. It will not let you 'accidently' overwrite last nights backup with tonights unless _you_ force it to. The usual practice is to setup the schedule which amanda uses only as a guide, for a dumpcycle of say 7 days. You'll want at least 14 tapes in order to have a complete backup image available at all times, and possibly even backup up a few days if something wrong isn't promptly discovered. So you have 14 tapes, the tapecycle then is 14 days. Then you tell amanda how many runs in that dumpcycle days, like maybe you only do tuesday morning to saturday morning, 5 times a week, so the runspercycle then would be set to 5. Amanda then looks at what she has to do in that time frame, and will adjust the schedule of who gets a level 0 and who gets incrementals in order to satisfy the schedule you have given amanda as a target schedule AND to try and use about the same amount of the media each night. This 'balance' adjustment is an ongoing process, and you'll get emails after every run describing what was done during the run just completed. With anything sane for the target numbers, I've never seen amanda put off a level 0 that was needed by more than 1 day. Do I have to put each tape in the tape drive and run amlabel? Yes, thats the required method. 3) We have a local and remote sites that we have to backup any thoughts, comments on what should I keep in mine before doing so. Yes. It would be advisable to stay away from anything on a samba share. It doesn't support ctime, so the data always looks new and gets a level 0 every night even if the level has advanced to 4. Install an amanda client setup on each of the machines and use that instead. Or use rsync which I mention below. Additionally any recommendation for what to use to secure our data when backing up remotely? I read that I can use TCP wrappers but how do I implement it with Amanda? Tcpwrappers is a security control tool, and wouldn't hurt anything once setup to pass the amanda traffic. I use it on my firewall box, watching the internet side of things, along with portsentry and iptables. Call me paranoid... But as far as security of the data is concerned, one would want to wrap the amanda functions in an ssh or sftp in order to scramble it enough to be secure while in transit if thats a concern. I have not done that, so I'll defer to others here who may have and let them give the 'howto' advice. I'd point out that rsync, once the initial images in the holding area have been made, does a 64k block checksum on the src and target files, and only exchanges the real data if the checksums are different. This checksum traffic would help the security issue by drowning out the real data with the checksum traffic, once its in place and running. Bear in mind of course that this, along with gzip compression does require some horsepower to be expended in the client machines, but, a gzipped file also takes up less network bandwidth so a multimachine environment won't be bringing the network to it knees quite so fast. And the potential to speed up the backups by offloading the jobs to the clients so that many of them can be doing their thing all at the same time can save you several hours in a larger, 20 machine system. The secret is to give each machine/drive, a different, unique spindle number in the disklist entry as amanda will not run more than one operation on the same spindle at the same time.
