Thanks for asking. Lots of drama but it didn't take anywhere as long as
they "guessed". In fact it took me longer to reconfigure 7-TSM servers and
then figure out various nuances then the physical deinstall/install.
The library was completely emptied and ready for them to shutdown by 10am
Friday. They showed up around 1pm and had the 3494 dismantled by 4pm,
eventhough they did a proper disasembly (took it apart carefully vs using
hacksaws and chainsaws. Originally IBM was going to 'deinstall for
purposes of disposal' but then they came up with a "recycle" program and
didn't charge us.
They originally said they were going to quit by 6:30pm and come back
Saturday. I get a phone call at 8:30pm saying the TS3500 was installed and
ready to have our tapes manually loaded but it wasn't powered-up or tested,
We agreed to start at 8am Saturday. They arrived and powered things up and
tested, oiled (it was squeaking) and upgraded the library firmware. Turned
it over to us by 1pm.
Had to restart most of my TSM servers but they still couldn't see the tape
drives. Nobody told us the WWN of the drives would be changed/managed by
the library so my SAN guy had to reconfigure the switch/ports/fabric.
After that it was TSM reconfiguration and wrestling with the
assignment/checkin process (what fun manually reassigning 1400 cartridges).
IMHO, the 3494 was sooo much easier to manage.
We went home around 6pm Saturday.
Still had some TSM issues to deal with Sunday morning, mostly things like
vaulting, training operators how to checkin/checkout tapes, etc.
On Tue, May 28, 2013 at 9:33 AM, Richard Rhodes <rrhodes AT firstenergycorp DOT
> I can't help with your question, but I'm really curious how the swap out
> went. Did it take as long as IBM thought it would?
> From: Zoltan Forray <zforray AT VCU DOT EDU>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 05/28/2013 09:16 AM
> Subject: Now that I have a TS3500 - I have questions
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> Our new TS3500 was installed this weekend (replacing our 17-year old 3494)
> and I have lots of questions about how things should be done/configured
> why it is doing what it is doing.
> First off, the library is configured as 2-virtual librarys, each side with
> fixed drive assignments and each side managed by a separate TSM server.
> 1. Per other discussions, I configured 255 "Virtual IO". We also
> configured/enabled "Insert Notification". However, some tapes keep being
> inserted "unassigned" while most are properly assigned to the right
> library?. Why?
> 2. What is the proper CHECKIN command options for doing mass checkins
> the IO/VIO slots? SEARCH=BULK or SEARCH=YES - CHECKLABEL=YES or
> CHECKLABEL=BARCODE? The book says for a SCSI library you can't specify
> SEARCH=YES and CHECKLABEL=NO....
> *Zoltan Forray*
> TSM Software & Hardware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html
> The information contained in this message is intended only for the
> personal and confidential use of the recipient(s) named above. If
> the reader of this message is not the intended recipient or an
> agent responsible for delivering it to the intended recipient, you
> are hereby notified that you have received this document in error
> and that any review, dissemination, distribution, or copying of
> this message is strictly prohibited. If you have received this
> communication in error, please notify us immediately, and delete
> the original message.
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details