01-16-2012 08:00 AM
I'm in the process of implementing a vls9000 into our backup environment.
We have multiple FC-hosts that will backup to this VLS.
With the autoconfigure devices wizard the devices are nicely created saving me alot of time.
However i run into a few very annoying issue's that need fixing:
1: Tape drives get a name i'm not happy with, but can live with that.
2: Same for TapeDrive description.
3: Each drive is assigned its own default media pool, and this pool is then also created !
-> now i need to modify every drive to use THE default media pool i created .. not some randomly generated empty media pool.
This modification needs to be done on every drive and most likely for every FC host that has access to the drives.
4: concurrency is set to 4. i need a different value for each drive.
5: Blocksize is default 64, i need 256KB for lto3.
6: the device lockname. again something i 'm not happy with but can live with that.
Who can help me out.
I need to create 48 Drives for 20FC hosts.
And i'd like to be able to add some options to each drive, like blocksize and default pool.
01-16-2012 09:48 AM
- omnidownload (for backing up current device information)
Possibly also nice for disaster recovery scenario's
- Omniupload, for inserting device/library information into DP
- Sanconf, most likely not what i need.
Will investigate the commands later on this week.
advice on this matter still welcome!
01-16-2012 10:24 AM
omnidownload/omniupload is the way how to do it. I usually use the autoconfiguration to get all required device paths on SAN hosts into the configuration, use omnidownload to write them to file, modify it as required and upload it back into the IDB using omniupload.
01-18-2012 02:34 AM
Thanks for the confirmation.
This method will however introduce 48 empty default media pools.
one for each newly autodiscovered tapedrive.
Not a big issue,
But those will need to be deleted.
Maybe i can discover the device path's with sanconf and use a template to create the 48 omniupload text file's to create the devices without poluting the media pools.
Also, i found a savedevice's tool for dataprotector based on a perl script.
see here for info and download.
I'll checkout sanconf and its options today.
01-18-2012 04:19 AM
Yes, this is expected. You can use omnimm -remove_pool to get rid of those pools after an autoconfiguration.
01-19-2012 05:45 AM
Since in the process its needed to modify textfiles anyway i did the creation a little bit different.
I Made a template for my vls drives with all the needed options.
I was able to retrieve the scsi addresses for all FC hosts & drives and device serial numbers in the summary of sanconf -list
But editing the text files and inserting the scsi addresses for all hosts is time consuming.
So i tried this in my template for all drives:
I set the scsi adress to an invalid scsi adres.
This results in a device discovery path first time you use the drive and this will fill in the correct adresses :)
Now in my template i only have to modify 4 entries beeing:
NAME "Drive name here"
and DEVSERIAL ""
Since the device serial number for the tape devices are all in sequence its just a matter of adding up the numbers.
The seperate device config files can be uploaded by omniupload.
this way its possible to create the library's and tape drives with your needed options without the default pools beeing created.
Still alot of files to edit. but only 4 entries to change.
01-20-2012 06:20 AM
tip for the future: when you install DP don't remove the "default" media pool for the tape type you will eventually configure - if the "Default LTO-Ultrium" media pool exists then this should have been set as the default media pool for the drives during the auto-configure
If my post was useful, please click on KUDOS! "White Star"