Re: [Veritas-bu] sso question
You can load tapes from the master because it has the robot control and just loads the tape into a position in the library. You can't unload them, because the master server can't send the mt commands to the tape drive to unload the tape that the robot can then grab. Unless you know that you can feed 3 LTO-3 @ 80 MB/s per HBA, I don't think a little over- subscription is going to kill you. -- nick guys i have master server running sol8 connected to L700. L700 has 7 drives in it. Master can see 6 of them through fiber Med1 can see first 3 drives shared Med2 can see first 3 drives shared Med3 just added has access to drives 5,6,7 and can see them fine. I have just loaded a tape on the master server ( robot control ) and put a taper into drive 7. When i came to do an unload d7 so i could move the tape back (m d7 s6) it wouldn't do it. I then realized thats because it does unloads on rmt paths and i haven't added drive 7 to the master server. Didnt add for 2 reasons. 1. its recommended to have only 3 drives per 2gb HBA ( which is why it has 6 drives in total ). Plus if i added drive 7 i would need another shared license i guess. Question:- Is there something wrong with my setup then. Should the master have device paths set up for every drive in the robot. I know it can put tapes in but it cant take them out. What i was able to do was a mt -f /dev/rmt/2 offline from Med3 and then moved it using robtest from the master. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] sso question
On 10/9/07, Dave Markham <[EMAIL PROTECTED]> wrote: > > guys i have master server running sol8 connected to L700. > > L700 has 7 drives in it. > > Master can see 6 of them through fiber > > Med1 can see first 3 drives shared > Med2 can see first 3 drives shared > > Med3 just added has access to drives 5,6,7 and can see them fine. > > I have just loaded a tape on the master server ( robot control ) and put > a taper into drive 7. When i came to do an unload d7 so i could move the > tape back (m d7 s6) it wouldn't do it. I then realized thats because it > does unloads on rmt paths and i haven't added drive 7 to the master > server. > > Didnt add for 2 reasons. 1. its recommended to have only 3 drives per > 2gb HBA ( which is why it has 6 drives in total ). Plus if i added drive > 7 i would need another shared license i guess. You should probably only *write* to 3 drives per HBA at a time. Nothing says that you can't control more than that. Limit the number of drives per storage unit to limit how many you're actually using at any one time. You can configure every media server to see every drive and then limit how many they can actually use. Question:- Is there something wrong with my setup then. Should the > master have device paths set up for every drive in the robot. Not technically the master but actually the robot control host. After all, it's controlling the robot - if it can't talk to each drive, then there's no reason to expect that it should work. And yes, you'll need extra tape drive and SSO licenses. .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] sso question
This is a perfectly good configuration. You've just uncovered a limitation of using robtest where the robotic control host can't see the drives. In an L700, I'd be surprised if you actually needed to issue the unload command (lots of libraries can now accomplish the unload automagically while doing a move). Did you try a move without unload? If that doesn't work, then you've already found your appropriate solution. HTH -Tim On 10/9/07, Dave Markham <[EMAIL PROTECTED]> wrote: > > guys i have master server running sol8 connected to L700. > > L700 has 7 drives in it. > > Master can see 6 of them through fiber > > Med1 can see first 3 drives shared > Med2 can see first 3 drives shared > > Med3 just added has access to drives 5,6,7 and can see them fine. > > I have just loaded a tape on the master server ( robot control ) and put > a taper into drive 7. When i came to do an unload d7 so i could move the > tape back (m d7 s6) it wouldn't do it. I then realized thats because it > does unloads on rmt paths and i haven't added drive 7 to the master > server. > > Didnt add for 2 reasons. 1. its recommended to have only 3 drives per > 2gb HBA ( which is why it has 6 drives in total ). Plus if i added drive > 7 i would need another shared license i guess. > > Question:- Is there something wrong with my setup then. Should the > master have device paths set up for every drive in the robot. I know it > can put tapes in but it cant take them out. What i was able to do was a > mt -f /dev/rmt/2 offline from Med3 and then moved it using robtest from > the master. > > Cheers > ___ > 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
[Veritas-bu] sso question
guys i have master server running sol8 connected to L700. L700 has 7 drives in it. Master can see 6 of them through fiber Med1 can see first 3 drives shared Med2 can see first 3 drives shared Med3 just added has access to drives 5,6,7 and can see them fine. I have just loaded a tape on the master server ( robot control ) and put a taper into drive 7. When i came to do an unload d7 so i could move the tape back (m d7 s6) it wouldn't do it. I then realized thats because it does unloads on rmt paths and i haven't added drive 7 to the master server. Didnt add for 2 reasons. 1. its recommended to have only 3 drives per 2gb HBA ( which is why it has 6 drives in total ). Plus if i added drive 7 i would need another shared license i guess. Question:- Is there something wrong with my setup then. Should the master have device paths set up for every drive in the robot. I know it can put tapes in but it cant take them out. What i was able to do was a mt -f /dev/rmt/2 offline from Med3 and then moved it using robtest from the master. Cheers ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] SSO question
Title: Message No, the other jobs would just queue if a tape drive wasn't available. Once one of the other jobs finishes on any tape drive, the job would pick up and load a tape. Reneé Carlisle Sr. Systems Administrator675 Basket RoadWebster, NY 14580 Jer 29:11-13 585-216-0497 (w)585-472-2360 (c) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul KeatingSent: Tuesday, May 30, 2006 3:03 PMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] SSO question Assuming you have several tapes drives share among several media servers. ie, 10 drives and 3 servers. if you configure each server to see all 10 drives and then configure a STU on each server to use a max of 4 drives, you will encounter situations where there is demand for as many as 12 drives..In the instance where 2 of the media servers each reserve 4 drives and the third server has only 2 drives available to it, does this cause all the jobs queued on this third server to fail with status 134??? I'm thinking that CAN'T be the caseif so, SSO would be pointless as you would only be able to create STU's to use a total global max of the number of physical drive you have, in which case you may as well do fixed assignments, and not SSO. Sorry if this seems like a stupid questionI'm not using SSO at the moment, and don't have the resources to suss it out in the lab, and I'm expecting to be deploying two additional media servers in June. Paul The information contained in this message may be privileged, confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or any employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Paychex, Inc. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] SSO question
Title: Message Paul, we do use SSO, with one master and one media server, but we also throw ndmp in the mix. We do indeed limit the total count of our master and media servers to the drives actually available, 4 drives on the master and 6 on the media server. However, since the two servers can see all 10 drives they just choose whichever drive is available. As long as the policies are set to use "any available server" then the jobs will go to whichever one can grab a drive. If all the drives are busy the jobs go into the queue. Our point to doing it this way was to split the load over two separate gig-e pipes to the fiber where the the drives live in such a way that NBU took care of the details of how the data gets there. With NDMP we have it set to use paths available only on the master server, that's just to keep it from confusing the hell out of me. (Since we use 6mp2 ndmp allows us to use SSO) David Spearman County of Henrico,Va. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul KeatingSent: Tuesday, May 30, 2006 3:03 PMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] SSO question Assuming you have several tapes drives share among several media servers. ie, 10 drives and 3 servers. if you configure each server to see all 10 drives and then configure a STU on each server to use a max of 4 drives, you will encounter situations where there is demand for as many as 12 drives..In the instance where 2 of the media servers each reserve 4 drives and the third server has only 2 drives available to it, does this cause all the jobs queued on this third server to fail with status 134??? I'm thinking that CAN'T be the caseif so, SSO would be pointless as you would only be able to create STU's to use a total global max of the number of physical drive you have, in which case you may as well do fixed assignments, and not SSO. Sorry if this seems like a stupid questionI'm not using SSO at the moment, and don't have the resources to suss it out in the lab, and I'm expecting to be deploying two additional media servers in June. Paul ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] SSO question
Title: Message Assuming you have several tapes drives share among several media servers. ie, 10 drives and 3 servers. if you configure each server to see all 10 drives and then configure a STU on each server to use a max of 4 drives, you will encounter situations where there is demand for as many as 12 drives..In the instance where 2 of the media servers each reserve 4 drives and the third server has only 2 drives available to it, does this cause all the jobs queued on this third server to fail with status 134??? I'm thinking that CAN'T be the caseif so, SSO would be pointless as you would only be able to create STU's to use a total global max of the number of physical drive you have, in which case you may as well do fixed assignments, and not SSO. Sorry if this seems like a stupid questionI'm not using SSO at the moment, and don't have the resources to suss it out in the lab, and I'm expecting to be deploying two additional media servers in June. Paul 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
