Re: [Veritas-bu] Disaster Recovery Site
I've done something similar which is adopted as a DR method by the customer. Its perhaps not as fancy as below but carries the same important feature. The master server at DR site is the same hostname as the Production site. This was critical in getting the DR process to work. All i do is backup to disk each day the catalouges of Prod site ( also to tape ) and rsync them over to DR site backup server. The DR site backup server has its own catalogue for backing the DR site up during normal operation but in DR scenario i backup the DR catalogus (bpbackup -dpath etc ) and then recover the rsynced ones from production site ( bprecover) now my DR site knows about all the tapes used at production site ( where i also have an ITC and tapes sent offsite ) and so i can restore from production machines onto DR machines. Works a charm Dave Paul Keating wrote: Inline Tape Copy. It's a Netbackup feature where two tapes are written simultaneously. We've done several tests of our infrastructure, and it has worked well. We have a corporate test coming up soon.hope that goes as well. The procedures and everything will be the same, so it should go fine, there will just be 20 times more people involved in testing their stuff, so it will be much more hectic. Paul -- -Original Message- *From:* Sponsler, Michael [mailto:[EMAIL PROTECTED] *Sent:* July 31, 2006 1:26 PM *To:* Paul Keating; veritas-bu@mailman.eng.auburn.edu *Subject:* RE: [Veritas-bu] Disaster Recovery Site Paul, What is ITC? You say your tapes are replicated using ITC That sounds like a decent plan. Have you tested a DR event, and has it worked out alright? -- Mike Sponsler [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Northrop Grumman La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Disaster Recovery Site
Dave That sounds good! I sadly DON'T have a DR plan of sort, but I have a process where the Catalog tapes and ones to disk are replicated around a site - so in the event of the Master going pear-shaped (and assuming the robot is all ok!!), restore via bprecover same drive config / MP, ect and that has worked. But it would be nice to have another site solution similar to Paul, but adapting this to make the process to moving over as painless as possible, with minimal fuss. Thanks Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Dave Markham [mailto:[EMAIL PROTECTED] Sent: 01 August 2006 14:02 To: Paul Keating Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Disaster Recovery Site I've done something similar which is adopted as a DR method by the customer. Its perhaps not as fancy as below but carries the same important feature. The master server at DR site is the same hostname as the Production site. This was critical in getting the DR process to work. All i do is backup to disk each day the catalouges of Prod site ( also to tape ) and rsync them over to DR site backup server. The DR site backup server has its own catalogue for backing the DR site up during normal operation but in DR scenario i backup the DR catalogus (bpbackup -dpath etc ) and then recover the rsynced ones from production site ( bprecover) now my DR site knows about all the tapes used at production site ( where i also have an ITC and tapes sent offsite ) and so i can restore from production machines onto DR machines. Works a charm Dave Paul Keating wrote: Inline Tape Copy. It's a Netbackup feature where two tapes are written simultaneously. We've done several tests of our infrastructure, and it has worked well. We have a corporate test coming up soon.hope that goes as well. The procedures and everything will be the same, so it should go fine, there will just be 20 times more people involved in testing their stuff, so it will be much more hectic. Paul -- -Original Message- *From:* Sponsler, Michael [mailto:[EMAIL PROTECTED] *Sent:* July 31, 2006 1:26 PM *To:* Paul Keating; veritas-bu@mailman.eng.auburn.edu *Subject:* RE: [Veritas-bu] Disaster Recovery Site Paul, What is ITC? You say your tapes are replicated using ITC That sounds like a decent plan. Have you tested a DR event, and has it worked out alright? -- Mike Sponsler [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Northrop Grumman -- -- == == La version française suit le texte anglais. -- -- This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. -- -- Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. -- -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of Astrium Limited. Nothing in this email shall bind Astrium Limited in any contract or obligation. Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
[Veritas-bu] Disaster Recovery Site
Title: Disaster Recovery Site I'm working to get a Disaster Recovery Site setup and configured. I'm running my backups on my master server (netbackup 6.0) from City A, and that master server backs up information from Cities X, Y, and Z. The plan is to have another Master Server (netbackup 6.0), for disaster recover, setup at City B (it's 100 miles away, with a 10 meg fiber link to city A). I was wondering about a best practices approach. The catalog for the master server in City A sits on an external RAID device (Sun StoreEdge 9980). The catalog is to be replicated using Veritas Volume Replicator to a Sun StorEdge 9980 in City B, so that the Disaster Recovery site as a mirror to the catalog in City A. The idea is, is that if City A were for some reason to either Fall off the map, or be disconnected from the internet, City B's master server could pick up where City A left off. I know there are tape issues involved here, and what I'm trying to setup is basically a Netbackup Cluster. Now given the fact that City A and City B are at least 100 miles apart, is there anything anyone can recommend for my situation? Also, given that I'll have two master Servers (an active / passive thing), what would be the best way to approach hostnames? Does netbackup allow you to change the hostname? Are there any issues with changing a master server's hostname? Has anyone worked with the Netbackup Cluster software? Would they recommend it for a Disaster Recovery Site like I described? -- Mike Sponsler Northrop Grumman [EMAIL PROTECTED] (703) 968-1302 12900 Federal Systems Pkwy Fairfax, VA 22033 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Disaster Recovery Site
Title: Message I have a similar setup, except I'm using a GigE link over DWDM/leased fiber, as well as a pair of 2Gb/s FC connections. I have a master at two sites, each site has a tape library. the /opt/openv filesystem is replicated using VVR, and the tapes are replicated using ITC, so each backup writes simultaneously to a tape at each location. in the case of a DR event, the 2nd master would take over the replicated filesystem, daemons started, and the device configuration wizard would be run to reconfigure Netbackup to see whatever drives were available (probably only the 2nd site drives, rather than both sites' drive as the original master had seen.) All second copy tapes would be promoted to pirmary and we're off to the races. as far as the hostname thing. each of my masters has 2 NICs. the nic names have nothing to do with the "master" name. both systems are named "master", in /etc/nodename, etcnetbackup is installed with "master" as the name in all configs. at head office, the NIC names in DNS, and in the /etc/hosts files are master-ho1 and master-ho2 at the DR site, the NIC names in DNS, and in the /etc/hosts files are master-dr1 and master-dr2 at head office, there is a dns alias that points "master" to "master-ho1" in our DR plan, there is a note to change the alias to point to master-dr1, however that is only significant for launching the GUI from a host other than the master, as both masters have an entry in their hosts files that point "master" to the same IP as the primary NIC. works fine for us.alternating the catalog backups to2 tapes, one at HO and one at DR is a good idea, or if you don't have FC connectivity to the second site, make sure a copy ofyour catalog tape is sent to the DR site with your data tapes. Paul -- -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sponsler, MichaelSent: July 31, 2006 10:03 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Disaster Recovery Site I'm working to get a Disaster Recovery Site setup and configured. I'm running my backups on my master server (netbackup 6.0) from City A, and that master server backs up information from Cities X, Y, and Z. The plan is to have another Master Server (netbackup 6.0), for disaster recover, setup at City B (it's 100 miles away, with a 10 meg fiber link to city A). I was wondering about a "best practices" approach. The catalog for the master server in City A sits on an external RAID device (Sun StoreEdge 9980). The catalog is to be replicated using Veritas Volume Replicator to a Sun StorEdge 9980 in City B, so that the Disaster Recovery site as a mirror to the catalog in City A. The idea is, is that if City A were for some reason to either Fall off the map, or be disconnected from the internet, City B's master server could pick up where City A left off. I know there are tape issues involved here, and what I'm trying to setup is basically a Netbackup Cluster. Now given the fact that City A and City B are at least 100 miles apart, is there anything anyone can recommend for my situation? Also, given that I'll have two master Servers (an active / passive thing), what would be the best way to approach hostnames? Does netbackup allow you to change the hostname? Are there any issues with changing a master server's hostname? Has anyone worked with the Netbackup Cluster software? Would they recommend it for a Disaster Recovery Site like I described? La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu
Re: [Veritas-bu] Disaster Recovery Site
Title: Message Paul, What is ITC? You say your tapes are replicated using ITC That sounds like a decent plan. Have you tested a DR event, and has it worked out alright? -- Mike Sponsler [EMAIL PROTECTED] Northrop Grumman From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul KeatingSent: Monday, July 31, 2006 10:19 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Disaster Recovery Site I have a similar setup, except I'm using a GigE link over DWDM/leased fiber, as well as a pair of 2Gb/s FC connections. I have a master at two sites, each site has a tape library. the /opt/openv filesystem is replicated using VVR, and the tapes are replicated using ITC, so each backup writes simultaneously to a tape at each location. in the case of a DR event, the 2nd master would take over the replicated filesystem, daemons started, and the device configuration wizard would be run to reconfigure Netbackup to see whatever drives were available (probably only the 2nd site drives, rather than both sites' drive as the original master had seen.) All second copy tapes would be promoted to pirmary and we're off to the races. as far as the hostname thing. each of my masters has 2 NICs. the nic names have nothing to do with the "master" name. both systems are named "master", in /etc/nodename, etcnetbackup is installed with "master" as the name in all configs. at head office, the NIC names in DNS, and in the /etc/hosts files are master-ho1 and master-ho2 at the DR site, the NIC names in DNS, and in the /etc/hosts files are master-dr1 and master-dr2 at head office, there is a dns alias that points "master" to "master-ho1" in our DR plan, there is a note to change the alias to point to master-dr1, however that is only significant for launching the GUI from a host other than the master, as both masters have an entry in their hosts files that point "master" to the same IP as the primary NIC. works fine for us.alternating the catalog backups to2 tapes, one at HO and one at DR is a good idea, or if you don't have FC connectivity to the second site, make sure a copy ofyour catalog tape is sent to the DR site with your data tapes. Paul -- -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sponsler, MichaelSent: July 31, 2006 10:03 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Disaster Recovery Site I'm working to get a Disaster Recovery Site setup and configured. I'm running my backups on my master server (netbackup 6.0) from City A, and that master server backs up information from Cities X, Y, and Z. The plan is to have another Master Server (netbackup 6.0), for disaster recover, setup at City B (it's 100 miles away, with a 10 meg fiber link to city A). I was wondering about a "best practices" approach. The catalog for the master server in City A sits on an external RAID device (Sun StoreEdge 9980). The catalog is to be replicated using Veritas Volume Replicator to a Sun StorEdge 9980 in City B, so that the Disaster Recovery site as a mirror to the catalog in City A. The idea is, is that if City A were for some reason to either Fall off the map, or be disconnected from the internet, City B's master server could pick up where City A left off. I know there are tape issues involved here, and what I'm trying to setup is basically a Netbackup Cluster. Now given the fact that City A and City B are at least 100 miles apart, is there anything anyone can recommend for my situation? Also, given that I'll have two master Servers (an active / passive thing), what would be the best way to approach hostnames? Does netbackup allow you to change the hostname? Are there any issues with changing a master server's hostname? Has anyone worked with the Netbackup Cluster software? Would they recommend it for a Disaster Recovery Site like I described? ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Disaster Recovery Site
Title: Message Inline Tape Copy. It's a Netbackupfeature where two tapes are written simultaneously. We've done several tests of "our" infrastructure, and it has worked well. We have a corporate test coming up soon.hope that goes as well. The procedures and everything will be the same, so it should go fine, there will just be 20 times more people involved in testing their stuff, so it will be much more hectic. Paul -- -Original Message-From: Sponsler, Michael [mailto:[EMAIL PROTECTED] Sent: July 31, 2006 1:26 PMTo: Paul Keating; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Disaster Recovery Site Paul, What is ITC? You say your tapes are replicated using ITC That sounds like a decent plan. Have you tested a DR event, and has it worked out alright? -- Mike Sponsler [EMAIL PROTECTED] Northrop Grumman La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
