Re: [Veritas-bu] Need help with FAILOVER_RESTORE_MEDIA_SERVERS
Netbackup does this if you have it configured to do so. You need to have entries on your clients to allow access from all of your media servers, else you'll end up with Status 59. then you create your STUs for each media server, create a STU-Group that contains all of those STUs, and configure your policies to use the STU-Group. works a treat. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sesar, Steven L. Sent: September 14, 2007 5:23 PM To: Justin Piszcz; Tim Hoke Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Need help with FAILOVER_RESTORE_MEDIA_SERVERS It makes a ton of sense! And, other data protection application vendors get it. I was performing a bake-off with another vendor and I inadvertently left 5 out of 6 media servers powered off. To my surprise, the next morning when I came in, backups had transparently failed over to the single, remaining media server! That's redundancy for you! This redundancy mechanism also applies with storage units. If one storage unit is for whatever reason unavailable, it'll fail over to a second, third, fourth.however many redundant paths you have a particular storage policy to use. --Steve 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
Re: [Veritas-bu] Need help with FAILOVER_RESTORE_MEDIA_SERVERS
Ah I was looking for the equivalent of FORCE_RESTORE_MEDIA_SERVER but only when the exsiting restore media server is busy. This would make a lot of sense, yes? It makes a ton of sense! And, other data protection application vendors get it. I was performing a bake-off with another vendor and I inadvertently left 5 out of 6 media servers powered off. To my surprise, the next morning when I came in, backups had transparently failed over to the single, remaining media server! That's redundancy for you! This redundancy mechanism also applies with storage units. If one storage unit is for whatever reason unavailable, it'll fail over to a second, third, fourth.however many redundant paths you have a particular storage policy to use. --Steve Justin. ___ 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] Need help with FAILOVER_RESTORE_MEDIA_SERVERS
On Fri, 14 Sep 2007, Tim Hoke wrote: > Justin, > > I think you are misinterpreting the parameter. It has nothing to do with > how busy a server is... It's if the server is totally not available > (offline). > >> From the SAG: > "Specifies automatic failover to another NetBackup server if a server is > temporarily inaccessible for a restore." > > The key word is "inaccessible". > > If you need a temporary solution, look at bpmedia -movedb... you can "move" > the server so that you can complete the restore, then move back. > > I though I heard at one point that this whole media "ownership" thing was > going to go away. I just don't know when. That way, if you kick off a > restore, it sounds like it would try to use the original host, else, find > one that is available so I can just get the restore done... In the short > term, bpmedia is your bet option. > > -Tim > Ah I was looking for the equivalent of FORCE_RESTORE_MEDIA_SERVER but only when the exsiting restore media server is busy. This would make a lot of sense, yes? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Need help with FAILOVER_RESTORE_MEDIA_SERVERS
Justin, I think you are misinterpreting the parameter. It has nothing to do with how busy a server is... It's if the server is totally not available (offline). >From the SAG: "Specifies automatic failover to another NetBackup server if a server is temporarily inaccessible for a restore." The key word is "inaccessible". If you need a temporary solution, look at bpmedia -movedb... you can "move" the server so that you can complete the restore, then move back. I though I heard at one point that this whole media "ownership" thing was going to go away. I just don't know when. That way, if you kick off a restore, it sounds like it would try to use the original host, else, find one that is available so I can just get the restore done... In the short term, bpmedia is your bet option. -Tim On 9/14/07, Justin Piszcz <[EMAIL PROTECTED]> wrote: > Anyone here use FAILOVER RESTORE media servers? > > Justin. > > On Fri, 14 Sep 2007, Justin Piszcz wrote: > > > I have a user-initiated restore in a library with > 20 tape drives. > > More than 15 of them are free, the one it is trying to use for the > > restore is completely utilized (all 4 drives are in use): > > > > 09/14/2007 01:21:11 - begin Restore > > 09/14/2007 01:21:19 - number of images required: 1 > > 09/14/2007 01:21:20 - media needed: C00498 > > 09/14/2007 01:21:57 - restoring from image the_client_hostname_1189167024 > > 09/14/2007 01:21:59 - connecting > > 09/14/2007 01:22:00 - connected; connect time: 0:00:00 > > 09/14/2007 01:21:59 - requesting resource C00498 > > 09/14/2007 01:22:00 - awaiting resource C00498. Waiting for resources. > > Reason: Drives are in use, Media server: media_server_2, > > Robot Type(Number): ACS(0), Media ID: N/A, Drive Name: N/A, > > Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A > > > > FAILOVER_RESTORE_MEDIA_SERVERS is NOT WORKING. > > > > If media_server_2 is busy, it should failover to one of the other media > > servers with free drives! > > > > media_server_2$ sudo /usr/openv/volmgr/bin/vmoprcmd -d ds > > > > DRIVE STATUS > > > > Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl . ReqId > > 0 hcart3 ACS Yes C00202 C00202 Yes Yes0 > > 1 hcart3 ACS Yes C00200 C00200 Yes Yes0 > > 2 hcart3 ACS Yes C02392 C02392 Yes Yes0 > > 3 hcart3 ACS Yes C00197 C00197 Yes Yes0 > > media_server_2$ logout > > > > media_server_3$ sudo /usr/openv/volmgr/bin/vmoprcmd -d ds > > > > DRIVE STATUS > > > > Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl . ReqId > > 0 hcart3 ACS Yes C00697 C00697 Yes Yes0 > > 1 hcart3 ACS- No - 0 > > 2 hcart3 ACS- No - 0 > > 3 hcart3 ACS- No - 0 > > media_server_3$ > > > > My bp.conf file: > > > > # new config > > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_1 media_server_2 media_server_3 > > media_server_4 media_server_5 media_server_6 media_server_7 media_server_8 > > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_2 media_server_3 media_server_4 > > media_server_5 media_server_6 media_server_7 media_server_8 media_server_1 > > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_3 media_server_4 media_server_5 > > media_server_6 media_server_7 media_server_8 media_server_1 media_server_2 > > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_4 media_server_5 media_server_6 > > media_server_7 media_server_8 media_server_1 media_server_2 media_server_3 > > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_5 media_server_6 media_server_7 > > media_server_8 media_server_1 media_server_2 media_server_3 media_server_4 > > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_6 media_server_7 media_server_8 > > media_server_1 media_server_2 media_server_3 media_server_4 media_server_5 > > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_7 media_server_8 media_server_1 > > media_server_2 media_server_3 media_server_4 media_server_5 media_server_6 > > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_8 media_server_1 media_server_2 > > media_server_3 media_server_4 media_server_5 media_server_6 media_server_7 > > > > # COMMENT: > > > > I used to use FORCE_RESTORE_MEDIA_SERVER but the problem with that is > > you can only force it to an alternate media server, I want to make the > > most use of the available capacity in the robot, how can I do this if > > failover restore media server does not work? > > > > Justin. > > > > > ___ > 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/ma
Re: [Veritas-bu] Need help with FAILOVER_RESTORE_MEDIA_SERVERS
Anyone here use FAILOVER RESTORE media servers? Justin. On Fri, 14 Sep 2007, Justin Piszcz wrote: > I have a user-initiated restore in a library with > 20 tape drives. > More than 15 of them are free, the one it is trying to use for the > restore is completely utilized (all 4 drives are in use): > > 09/14/2007 01:21:11 - begin Restore > 09/14/2007 01:21:19 - number of images required: 1 > 09/14/2007 01:21:20 - media needed: C00498 > 09/14/2007 01:21:57 - restoring from image the_client_hostname_1189167024 > 09/14/2007 01:21:59 - connecting > 09/14/2007 01:22:00 - connected; connect time: 0:00:00 > 09/14/2007 01:21:59 - requesting resource C00498 > 09/14/2007 01:22:00 - awaiting resource C00498. Waiting for resources. > Reason: Drives are in use, Media server: media_server_2, > Robot Type(Number): ACS(0), Media ID: N/A, Drive Name: N/A, > Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A > > FAILOVER_RESTORE_MEDIA_SERVERS is NOT WORKING. > > If media_server_2 is busy, it should failover to one of the other media > servers with free drives! > > media_server_2$ sudo /usr/openv/volmgr/bin/vmoprcmd -d ds > > DRIVE STATUS > > Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl. ReqId > 0 hcart3 ACS Yes C00202 C00202 Yes Yes0 > 1 hcart3 ACS Yes C00200 C00200 Yes Yes0 > 2 hcart3 ACS Yes C02392 C02392 Yes Yes0 > 3 hcart3 ACS Yes C00197 C00197 Yes Yes0 > media_server_2$ logout > > media_server_3$ sudo /usr/openv/volmgr/bin/vmoprcmd -d ds > > DRIVE STATUS > > Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl. ReqId > 0 hcart3 ACS Yes C00697 C00697 Yes Yes0 > 1 hcart3 ACS- No - 0 > 2 hcart3 ACS- No - 0 > 3 hcart3 ACS- No - 0 > media_server_3$ > > My bp.conf file: > > # new config > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_1 media_server_2 media_server_3 > media_server_4 media_server_5 media_server_6 media_server_7 media_server_8 > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_2 media_server_3 media_server_4 > media_server_5 media_server_6 media_server_7 media_server_8 media_server_1 > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_3 media_server_4 media_server_5 > media_server_6 media_server_7 media_server_8 media_server_1 media_server_2 > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_4 media_server_5 media_server_6 > media_server_7 media_server_8 media_server_1 media_server_2 media_server_3 > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_5 media_server_6 media_server_7 > media_server_8 media_server_1 media_server_2 media_server_3 media_server_4 > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_6 media_server_7 media_server_8 > media_server_1 media_server_2 media_server_3 media_server_4 media_server_5 > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_7 media_server_8 media_server_1 > media_server_2 media_server_3 media_server_4 media_server_5 media_server_6 > FAILOVER_RESTORE_MEDIA_SERVERS = media_server_8 media_server_1 media_server_2 > media_server_3 media_server_4 media_server_5 media_server_6 media_server_7 > > # COMMENT: > > I used to use FORCE_RESTORE_MEDIA_SERVER but the problem with that is > you can only force it to an alternate media server, I want to make the > most use of the available capacity in the robot, how can I do this if > failover restore media server does not work? > > Justin. > > ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Need help with FAILOVER_RESTORE_MEDIA_SERVERS
I have a user-initiated restore in a library with > 20 tape drives. More than 15 of them are free, the one it is trying to use for the restore is completely utilized (all 4 drives are in use): 09/14/2007 01:21:11 - begin Restore 09/14/2007 01:21:19 - number of images required: 1 09/14/2007 01:21:20 - media needed: C00498 09/14/2007 01:21:57 - restoring from image the_client_hostname_1189167024 09/14/2007 01:21:59 - connecting 09/14/2007 01:22:00 - connected; connect time: 0:00:00 09/14/2007 01:21:59 - requesting resource C00498 09/14/2007 01:22:00 - awaiting resource C00498. Waiting for resources. Reason: Drives are in use, Media server: media_server_2, Robot Type(Number): ACS(0), Media ID: N/A, Drive Name: N/A, Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A FAILOVER_RESTORE_MEDIA_SERVERS is NOT WORKING. If media_server_2 is busy, it should failover to one of the other media servers with free drives! media_server_2$ sudo /usr/openv/volmgr/bin/vmoprcmd -d ds DRIVE STATUS Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl. ReqId 0 hcart3 ACS Yes C00202 C00202 Yes Yes0 1 hcart3 ACS Yes C00200 C00200 Yes Yes0 2 hcart3 ACS Yes C02392 C02392 Yes Yes0 3 hcart3 ACS Yes C00197 C00197 Yes Yes0 media_server_2$ logout media_server_3$ sudo /usr/openv/volmgr/bin/vmoprcmd -d ds DRIVE STATUS Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl. ReqId 0 hcart3 ACS Yes C00697 C00697 Yes Yes0 1 hcart3 ACS- No - 0 2 hcart3 ACS- No - 0 3 hcart3 ACS- No - 0 media_server_3$ My bp.conf file: # new config FAILOVER_RESTORE_MEDIA_SERVERS = media_server_1 media_server_2 media_server_3 media_server_4 media_server_5 media_server_6 media_server_7 media_server_8 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_2 media_server_3 media_server_4 media_server_5 media_server_6 media_server_7 media_server_8 media_server_1 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_3 media_server_4 media_server_5 media_server_6 media_server_7 media_server_8 media_server_1 media_server_2 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_4 media_server_5 media_server_6 media_server_7 media_server_8 media_server_1 media_server_2 media_server_3 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_5 media_server_6 media_server_7 media_server_8 media_server_1 media_server_2 media_server_3 media_server_4 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_6 media_server_7 media_server_8 media_server_1 media_server_2 media_server_3 media_server_4 media_server_5 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_7 media_server_8 media_server_1 media_server_2 media_server_3 media_server_4 media_server_5 media_server_6 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_8 media_server_1 media_server_2 media_server_3 media_server_4 media_server_5 media_server_6 media_server_7 # COMMENT: I used to use FORCE_RESTORE_MEDIA_SERVER but the problem with that is you can only force it to an alternate media server, I want to make the most use of the available capacity in the robot, how can I do this if failover restore media server does not work? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
