Re: Backing up autofs/NFS shares
Hello, Jon,
Thanks for going through my long email. And thanks a lot for the suggestions.
Regards,
Yogesh
Jon LaBadie <[EMAIL PROTECTED]> wrote: On Thu, Nov 20, 2008 at 03:37:41AM
-0800, Yogesh Hasabnis wrote:
> Hi All,
>
> I referred the doc at
> http://wiki.zmanda.com/index.php/How_To:Backup_Partitions_Mounted_via_NFS
>
> I just need to confirm whether whatever I have understood from this doc is
> correct. What I understand is that I need to mount these nfs shares from 2
> different servers on some Linux host on the network and modify the disklist
> of my amanda full backup configuration to include the new amanda client. For
> eg my disklist file would look like
>
> /vol/vol1/home {
> root-tar
> estimate calcsize
> }
> ## Above is the original config. Given below is the additonal config
> ## for backing up the nfs shares mounted on an nfs client
>
> /nfs/project1 {
>root-tar
>estimate calcsize
>}
> /nfs/project2 {
>root-tar
>estimate calcsize
>}
>
> ## end of disklist
>
> Would like to know whether my understanding is correct,whetehr this will work
> and whether all these DLEs can be backed up on a single tape media.
As far as I remember, that is it. I call them
"indirect" clients vs. "direct" clients that
have amanda software.
For about 2 years I had a diverse set of unix boxes to
backup, Solaris x86 & sparc, HP-UX, Tru-64, plus linux
systems. Not wanting to bother compiling all those
client amanda's, I NFS mounted them all on my x86
server and backed up /net//.
You can also do similar backups of smb/cifs mounts.
Two notes, you don't need to use a different direct
clients than your amanda server. And it might be
more network efficient to use the amanda server.
If a different direct client is used, the data
from the indirect client must travel twice over
the network, once to the direct client and then
to the server.
Anytime I start using the same definitions more
than once, I tend to make a new definition.
define dumptype calc-tar {
root-tar
estimate calcsize
}
define dumptype calc-nfs {
calc-tar
}
/vol/vol1/home calc-tar
/nfs/project1 nfs-tar
/nfs/project2 nfs-tar
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)
Re: only one slot recognized
On Thu, Nov 20, 2008 at 03:32:55PM -0500, Nicholas Brockner wrote: > Hi All, > > I have been banging my head against this all day: > > I have a superloader3 16 slot LTO3 unit I am trying to set up. For some > reason, the glue script only sees one slot (slot 1): > > -sh-3.2$ /usr/libexec/amanda/chg-zd-mtx -info > 1 1 1 1 > > -sh-3.2$ amtape dailyfull show > amtape: scanning all 1 slots in tape-changer rack: > slot 1: time X label week1tape1 > > I am using 2.6.0p2 on Centos 5.2. > > any ideas? Same glimmer I always suggest. Amanda uses system utilities to do its work. So you should confirm that you can operate your changer and its drives with mtx and mt. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Re: only one slot recognized
What's in your changer config file? What's the output of : mtx -f /dev/sg? status What's in the debug file? Jean-Louis Nicholas Brockner wrote: Hi All, I have been banging my head against this all day: I have a superloader3 16 slot LTO3 unit I am trying to set up. For some reason, the glue script only sees one slot (slot 1): -sh-3.2$ /usr/libexec/amanda/chg-zd-mtx -info 1 1 1 1 -sh-3.2$ amtape dailyfull show amtape: scanning all 1 slots in tape-changer rack: slot 1: time X label week1tape1 I am using 2.6.0p2 on Centos 5.2. any ideas? -Nick
Re: Backing up virtual machines
--On November 20, 2008 4:40:28 PM -0500 Jon LaBadie <[EMAIL PROTECTED]> wrote: On Thu, Nov 20, 2008 at 01:04:33PM -0700, Michael Loftis wrote: --On November 20, 2008 2:51:24 PM -0500 Jon LaBadie <[EMAIL PROTECTED]> wrote: > Just dipping my toe into virtual machines and > wondering how others are doing backups of them. > > I'm using VirtualBox with a host of Fedora 9. > My guest is WinXP Pro. The objective is to > no longer need to dual-boot this machine. > > The virtual guest does appear on my network as > a separate host and static IP when it is up. > > I can see two ways to backup it up; > > - backup the VBox files (*.vdi and others) on > the host Fedora file system > > - consider the virtual machine a separate host > and amanda client > > How have others dealt with this situation? > Or maybe both forms are used simultaneously? Both have problems. Backing up the vdi's requires the machine be down. Why is this a requirement Michael? Is it because the VDI is changing while being backed up? Currently the VDI is not on a FS that can be snapshot'ted. If it was, for example an LVM file system on Linux, would the VDI of a running virtual machine be suitable for backup if taken from a snapshot (snapshot from the FS, not VBox). To my thinking, another major problem is the lack of access to individual files within the VDI file. Yeah live filesystem live device live everything. Restores would be complicated to say the least. I've also had problems with VMWare disk images if you back them up/copy them live they ended up completely corrupted and unusable on restore - the VMWare tool being unable to repair the disk image. I'd imagine there's the same problem with vbox. Backing up inside each VM requires you be careful not to overload the VM host during backup windows. For me, backing up inside each VM (each VM as an amanda client) was/is the only way to go, despite the pitfall. That is what I expect to do. I just hate windows backups with all the hassle over "can't backup system and any in-use files". Yeah I know. Backing up windows is worse than herding cats. You've got files, then you've got the hidden registry component to backup too...and even with all that you might not be able to restore a windows box. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax) -- "Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds." -- Samuel Butler
Re: Installing 2.6.0p2 on Ubuntu
On Wed, Nov 19, 2008 at 3:00 PM, Matt Burkhardt <[EMAIL PROTECTED]> wrote: > AMRECOVER Version 2.6.0p2. Contacting server on ubuntu ... > [request failed: timeout waiting for ACK] > > Is there another configure directive to find the original files? This can be because amrecover is using the wrong auth mechanism to find the server (look for "auth" in /etc/amanda/amanda-client.conf), or because something is wrong with your xinetd configuration -- is the executable that's pointing to still at that location? Dustin -- Storage Software Engineer http://www.zmanda.com
Re: Backing up virtual machines - Off topic question about LVM snapshots
Jon LaBadie schrieb: >> Backing up the vdi's requires the machine be down. > > Why is this a requirement Michael? Is it because the > VDI is changing while being backed up? Currently the > VDI is not on a FS that can be snapshot'ted. If it was, > for example an LVM file system on Linux, would the VDI > of a running virtual machine be suitable for backup if > taken from a snapshot (snapshot from the FS, not VBox). It's a off-topic question, but I just ask out of curiosity (don't know much about LVM snapshots yet): If I do a LVM snapshot of a running VM (or e.g. databases, too) and backup it, what happens if I restore it later? The VDI was open while the backup was done (and the information inside the VDI show this too, I guess). If I start the VM after the restore, doesn't cause this problems? I guess applications expect files with finalized written data (from the previous shutdown) on startup. Regards Marc -- Marc Muehlfeld (Leitung IT) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Re: Backing up virtual machines
On Thu, Nov 20, 2008 at 01:04:33PM -0700, Michael Loftis wrote: > > > --On November 20, 2008 2:51:24 PM -0500 Jon LaBadie <[EMAIL PROTECTED]> wrote: > > >Just dipping my toe into virtual machines and > >wondering how others are doing backups of them. > > > >I'm using VirtualBox with a host of Fedora 9. > >My guest is WinXP Pro. The objective is to > >no longer need to dual-boot this machine. > > > >The virtual guest does appear on my network as > >a separate host and static IP when it is up. > > > >I can see two ways to backup it up; > > > > - backup the VBox files (*.vdi and others) on > > the host Fedora file system > > > > - consider the virtual machine a separate host > > and amanda client > > > >How have others dealt with this situation? > >Or maybe both forms are used simultaneously? > > Both have problems. > Backing up the vdi's requires the machine be down. Why is this a requirement Michael? Is it because the VDI is changing while being backed up? Currently the VDI is not on a FS that can be snapshot'ted. If it was, for example an LVM file system on Linux, would the VDI of a running virtual machine be suitable for backup if taken from a snapshot (snapshot from the FS, not VBox). To my thinking, another major problem is the lack of access to individual files within the VDI file. > Backing up inside each VM requires you be careful not to overload the VM > host during backup windows. For me, backing up inside each VM (each VM as > an amanda client) was/is the only way to go, despite the pitfall. > That is what I expect to do. I just hate windows backups with all the hassle over "can't backup system and any in-use files". jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Re: Backing up virtual machines
I've been backing up virtual hosts on Solaris. There are a couple of ways... If the virtual, er, lets use the proper vendor terms because they connote specific non-transferable things. In some cases I can backup my non-global zones from the global zone amanda client. This is fine if the whole of the non-global zone file system is visable from the global zone. For those systems where there are file systems within the non-global zone that are not visable from the global zone, for instance, ZFS file systems that are not-mounted by the global zone, then I do run an amanda-client within both the global and the non-global zones. I realize this is essentially what Jon said, but I had accomplished on another platform and wanted to say that "yes, this does work". On Thu, Nov 20, 2008 at 02:51:24PM -0500, Jon LaBadie wrote: > Just dipping my toe into virtual machines and > wondering how others are doing backups of them. > > I'm using VirtualBox with a host of Fedora 9. > My guest is WinXP Pro. The objective is to > no longer need to dual-boot this machine. > > The virtual guest does appear on my network as > a separate host and static IP when it is up. > > I can see two ways to backup it up; > > - backup the VBox files (*.vdi and others) on >the host Fedora file system > > - consider the virtual machine a separate host >and amanda client > > How have others dealt with this situation? > Or maybe both forms are used simultaneously? > > jl > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 12027 Creekbend Drive(703) 787-0884 > Reston, VA 20194(703) 787-0922 (fax) --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: Backing up virtual machines
--On November 20, 2008 2:51:24 PM -0500 Jon LaBadie <[EMAIL PROTECTED]> wrote: Just dipping my toe into virtual machines and wondering how others are doing backups of them. I'm using VirtualBox with a host of Fedora 9. My guest is WinXP Pro. The objective is to no longer need to dual-boot this machine. The virtual guest does appear on my network as a separate host and static IP when it is up. I can see two ways to backup it up; - backup the VBox files (*.vdi and others) on the host Fedora file system - consider the virtual machine a separate host and amanda client How have others dealt with this situation? Or maybe both forms are used simultaneously? Both have problems. Backing up the vdi's requires the machine be down. Backing up inside each VM requires you be careful not to overload the VM host during backup windows. For me, backing up inside each VM (each VM as an amanda client) was/is the only way to go, despite the pitfall. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax) -- "Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds." -- Samuel Butler
Backing up virtual machines
Just dipping my toe into virtual machines and wondering how others are doing backups of them. I'm using VirtualBox with a host of Fedora 9. My guest is WinXP Pro. The objective is to no longer need to dual-boot this machine. The virtual guest does appear on my network as a separate host and static IP when it is up. I can see two ways to backup it up; - backup the VBox files (*.vdi and others) on the host Fedora file system - consider the virtual machine a separate host and amanda client How have others dealt with this situation? Or maybe both forms are used simultaneously? jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Re: Backing up autofs/NFS shares
On Thu, Nov 20, 2008 at 03:37:41AM -0800, Yogesh Hasabnis wrote:
> Hi All,
>
> I referred the doc at
> http://wiki.zmanda.com/index.php/How_To:Backup_Partitions_Mounted_via_NFS
>
> I just need to confirm whether whatever I have understood from this doc is
> correct. What I understand is that I need to mount these nfs shares from 2
> different servers on some Linux host on the network and modify the disklist
> of my amanda full backup configuration to include the new amanda client. For
> eg my disklist file would look like
>
> /vol/vol1/home {
> root-tar
> estimate calcsize
> }
> ## Above is the original config. Given below is the additonal config
> ## for backing up the nfs shares mounted on an nfs client
>
> /nfs/project1 {
>root-tar
>estimate calcsize
>}
> /nfs/project2 {
>root-tar
>estimate calcsize
>}
>
> ## end of disklist
>
> Would like to know whether my understanding is correct,whetehr this will
> work and whether all these DLEs can be backed up on a single tape media.
As far as I remember, that is it. I call them
"indirect" clients vs. "direct" clients that
have amanda software.
For about 2 years I had a diverse set of unix boxes to
backup, Solaris x86 & sparc, HP-UX, Tru-64, plus linux
systems. Not wanting to bother compiling all those
client amanda's, I NFS mounted them all on my x86
server and backed up /net//.
You can also do similar backups of smb/cifs mounts.
Two notes, you don't need to use a different direct
clients than your amanda server. And it might be
more network efficient to use the amanda server.
If a different direct client is used, the data
from the indirect client must travel twice over
the network, once to the direct client and then
to the server.
Anytime I start using the same definitions more
than once, I tend to make a new definition.
define dumptype calc-tar {
root-tar
estimate calcsize
}
define dumptype calc-nfs {
calc-tar
}
/vol/vol1/home calc-tar
/nfs/project1 nfs-tar
/nfs/project2 nfs-tar
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)
Re: Quantum SuperLoader 3
Hi Marc, it is this one: EC-L2DAA-YF LTO-3 16 Slots/2 Magazine Thanks! -Nick Marc Muehlfeld wrote: Nick Brockner schrieb: Is anyone here using a Quantum Superloader 3 (I know at least one person is) and care to share your config details with me? Specifically, how did you set up amanda.conf to use it. What kind of drive is in it? I take a look at the specification, but it seems that is autoloader is available with different kind of drives (e. g. DLT, LTO-2/3/4): ER-SL1AA-YF DLT VS160, 8 Slots /1 Magazin ER-S21AA-YF DLT VS160, 16 Slots/2 Magazine EC-SL6AA-YF DLT-V4, 8 Slots/1 Magazin EC-S26AA-YF DLT-V4, 16 Slots/2 Magazine ER-SL2AA-YF SDLT 600, 8 Slots/1 Magazin ER-S22AA-YF SDLT 600, 16 Slots/2 Magazine ER-LL4AA-YF LTO-2 HH, 8 Slots/1 Magazin ER-L24AA-YF LTO-2 HH, 16 Slots/2 Magazine EC-L2DAA-YF LTO-3 16 Slots/2 Magazine EC-LLDAA-YF LTO-3 8 Slots/1 Magazin EC-SL3AA-YF DLT-S4, 8 Slots/1 Magazin EC-S23AA-YF DLT-S4, 16 Slots/2 Magazine EC-SL3AC-YF DLT-S4 nFC, 8 Slots/1 Magazin EC-S23AC-YF DLT-S4 nFC, 16 Slots/2 Magazine EC-LL8AC-YF LTO-3 nFC, 8 Slots/1 Magazin EC-L28AC-YF LTO-3 nFC, 16 Slots/ 2 Magazine EC-LLEAA-YF LTO-4 SCSI, 8 Slots/1 Magazin EC-L2EAA-YF LTO-4 SCSI, 16 Slots/2 Magazine Regards Marc
Re: Quantum SuperLoader 3
Nick Brockner schrieb: it is this one: EC-L2DAA-YF LTO-3 16 Slots/2 Magazine The tapetype definition from my StorageLoader LTO3 I added to the wiki some time ago http://wiki.zmanda.com/index.php/Tapetype_definitions#Tandberg_StorageLoader_LTO3_.2820_Slot.29 I think this could work for you, too. Regards Marc -- Marc Muehlfeld (Leitung IT) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Backing up autofs/NFS shares
Hi All,
I use amanda 2.5.0p2 for our backup requirements with RHEL3 Linux being the OS
of the amanda server. Till now we have been backing up only one directory on
our fileserver which contains the home directories- say /vol/vol1/home. More
importantly, the backup client and the backup server are the same machine ie
the amanda server backs up a directory on itself. We have been using daily
incremental backups and monthly full backups using 2 different backup
configurations - say backdaily and fullback respectively. Now I need to change
the backup configuration of the monthly full backups such that it not only
backs up /vol/vol1/home on this original amanda server/client machine but also
the nfs shares of a netapp network storage device and one other autofs/nfs
Linux server.
I referred the doc at
http://wiki.zmanda.com/index.php/How_To:Backup_Partitions_Mounted_via_NFS
I just need to confirm whether whatever I have understood from this doc is
correct. What I understand is that I need to mount these nfs shares from 2
different servers on some Linux host on the network and modify the disklist of
my amanda full backup configuration to include the new amanda client. For eg my
disklist file would look like
/vol/vol1/home {
root-tar
estimate calcsize
}
## Above is the original config. Given below is the additonal config
## for backing up the nfs shares mounted on an nfs client
/nfs/project1 {
root-tar
estimate calcsize
}
/nfs/project2 {
root-tar
estimate calcsize
}
## end of disklist
Would like to know whether my understanding is correct,whetehr this will work
and whether all these DLEs can be backed up on a single tape media.
Hope I have described my query clearly. Kindly advise.
Thanks in advance.
Yogesh
Re: how large must the data volume be...
On Thu, 20 Nov 2008, Olivier Nicole wrote:
> > ...so that tape drives become more cost-effective than storing
> > everything on HD's?
>
> >From my past experience, 50GB SLR100 tape costs $100 while for that
> price I can have a 500GB disk...
Recently I asked our sysadmin at work how much an LTO tape (800 GB, i.e. 400 GB
native) costs, and I was quite surprised. I had expected O(100 EUR), but it was
much less.
But now let's start talking about the price of an autoloader... IIRC that's
something like 3000 EUR.
If you're a SOHO-user, you can probably get away with a few removable hard
drivers (and bring some of them offsite).
Pricewise, I guess you can get to the point were a bunch of HDs is still
cheaper than an autoloader with tapes, but it becomes more of a hassle to
manage your hard drives.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
