Change the image database to be case insensitive.
Created: 28 Aug 2009 | 4 comments
When one has a master server running on a UNIX platform it's image database is made case sensitive as the file system it self is case sensitive. When client requests, such as bplist, or bpimagelist, or bprestore commands are issued, sometimes the master server won't find anything due to the case of the hostname sent in the request.
Can the database be changed to reflect the hostnames of all machines in lowercase, and then just also have bprd change the case of the hostnames sent in requests to lower case?
-Sean
idea Filed Under:
Comments
DNS isn't case sensitive.
DNS isn't case sensitive.
Case sensitivity is okay just
Case sensitivity is okay just as long as everything is made the same case. =) I'd much rather see NetBackup enforce all-lowercase client names in the policy configurations, and hence in the image catalog, for both Windows and UNIX deployments.
Besides Sean's issue (which certainly crops up enough), another issue with the cases is when you try and migrate images between the two platform types. For example, in UNIX someone sets up "SERVERABC" to back up and then after a few runs changes it to "serverabc". Later on, you need to move the image records to a Windows server - which will treat those as exactly the same folder name and overwrite whichever one you copied first.
- "Your backups are only as good as your restores."
From a support perspective
From a support perspective and the migration issues forcing this under the covers so a user or support does not need to worry abou it.
I have found that some
I have found that some NetBackup diagnostics will FAIL if your unix server is all caps. (NCVU)
This is something that should not happen.
NBU 7.0.1 on Solaris 10
writing to EMC 4206 VTL
duplicating to LTO2 in SL8500
(Soon to be LTO5)
using ACSLS 7.3.1
Would you like to reply?
Login or Register to post your comment.