Unsolved
This post is more than 5 years old
8 Posts
0
318
June 27th, 2019 21:00
Is there a way to use tapes with different client ID to a new EBS networker without the need of relabeling them ?
We have received tapes with different client ID and is need to be used among 2 different networker servers with different Client IDs.
Tapes are need to be used for a period of 80 days in 1 networker and after that on another networker without resulting in the loss of data from the tapes.
I have created 2 different client ID's on both the networker and added the tapes in the pools. When i add volumes to tapes they are added in read only mode. After changing the read only status i did the backup on the tapes.
I ran scanner to see backup data on the tapes. But next day i am not able to see any data on the tapes.
Will doing backups of 2 different client Id's on tapes will corrupt the index and data on tapes. ?
bingo.1
2.4K Posts
0
June 27th, 2019 23:00
Let me start to explain a few details here:
- the client ID belongs to the client. Consequently it is stored with the save set, but it is not tight to a volume.
If this would be tha case, only one client could be saved on that media.
- The client ID is an additional 'parameter' to ensure that each save set ID (SSID) will be unique.
It was introduced with NW 6.0 because at that point in time NW just increased the SSID with each new save set. Consequently, if you wanted to read a tape with another NW server, it happened that the SSID already existed there.
'Merging' the client ID to the 'old' save set ID will ensure that the new SSID will be unique. - As a consequence, the same client must be created with the same client ID on both sites.
- scanner will tell you the client ID of the save set. - If you add a media to another NW server, it will be automatically set to 'read-only' (as a precaution).
The retention time is an attribute of the save set. Once it has been set, it will not change any more. This means, if you add a written volume to another NW server, the retention time may have passed already. In this case, NW will cleanup/delete the save sets when it is time (once a day or even more often). To prevent this, you have to verify and extend the retention time after the scanner command:
mminfo -q "volume=volname" -r "client,name,level,savetime,ssid,ssretent"
nsrmm -e "01/01/2020" -S ssid
mminfo -q "ssid=ssid" -r "client,name,level,savetime,ssid,ssretent" (for verification)