Unsolved
This post is more than 5 years old
8 Posts
0
7672
January 6th, 2013 21:00
How can I enable Persistent binding in my Backup server Tape Drives ?
We have a Networker Server at version 7.6.3 on Windows 2003 server.
We have two LTO-5 tape drives locally connected through SAN and twenty VTL drives connected from our Data Domain 670 Box.
I need to check whether we can configure Persistent binding or not also if yes then how.
I would be grateful if anyone can provide me a sure test as to see whether a particular LUN/SCSI device is persistently bound to a host or not.
No Events found!
masonb
445 Posts
0
January 7th, 2013 10:00
Peacerocks,
I don’t know of any command line test per say but if you have the Persistent Binding settings (also TUR etc) for Windows configured then your good. See Support Solution esg83905 - Potential tape drive issues in Windows - Persistent Naming-Binding, RSM, TUR and technical note available via the Web called Configuring Tape Devices for EMC NetWorker Technical Note .
If you are local to the server you could try switching off one of the physical drives and rebooting the server – all the remaining drives should be named the same with the drive missing. Test by comparing the inquire output before and after or similar software which allows you to compare serial numbers, WWN’s etc.
Bill Mason
Peacerocks
8 Posts
2
January 7th, 2013 22:00
Hi William,
Thanks for taking time and replying.
I have took reboot of theNetworker Server many times and the symbolic names of the drives have not changes also the WWN no and serial no and the OS paths give a perfect match every time system comes up.
Does that mean my drives are persistent binded, also I have heard that persistent binding can be done from windows registry also, correct me if I am wrong.. Is it possible ??
masonb
445 Posts
0
January 8th, 2013 00:00
Peacerocks,
Just rebooting the server without any change in the number of drives the server can see will prove nothing and you will see the results you report. What needs to happen to see if Persistent binding is in place is for at least one drive to be not available (i.e. cannot be seen over the san/SCSI connection) and then the names will change when reboot is done.
The Support solution I referenced has the links to the Microsoft Articles which detail the registry changes required to implement Persistent binding. It also references settings for Test Unit Ready (TUR) and Removable Storage Manager (RSM) which are also required to stop SCSI resets etc interfering with your drive functionality.
The Microsoft article numbers are 889330 and 933682 for Persistent binding and 842411 for TUR, but please look up the article via Powerlink or support.emc.com web pages for all details. It would also be helpful to you to look at the technical document I referenced also as this would assist you going forward.
Regards,
Bill Mason
ble1
4 Operator
•
14.3K Posts
0
January 8th, 2013 06:00
It depends on DDOS version, but most VTL implementations use IBM drives - meaning you can use IBM drivers on Windows box. Further, these drivers to supply support for persistant binding.
sarang_chadha
2 Posts
0
January 11th, 2013 03:00
Hi Peacerocks,
I have also faced somewhat similar issue. Below are the steps i used to resolve my problem.
Option 1:
You can edit the devices:
Go to devices tab
Go to all the devices
Right click of drive selet properties
Go to advanced tab
You will see CDI , select "Not Used"
You will also see Reserve/Release, select "Persistent"
Save & Exit
Option 2:
Disable TUR on windows server and update the Tape drive drivers.
First disable all the Tape drives on windows server, then take reboot, enable all the drives.
Check with inquire command that all the drives are visible.
Regards,
Sarang