Is the order of values in the VERITAS/NetBackup/CurrentVersion/Config/Exclude registry key under Windows important? If so, in what way and is there a way to avoid reordering during (silent) upgrade from NBU Client 6.5 to 7.0?
Thanks.
Thanks for the comprehensive testing and thorough reply. I'll forward this on to the guys here. As soon as I have some response (it's taking Symantec some time...) I'll post back here. Thanks again.
Edit: It's the same thing I've been seeing - the d...
I don't have access to the GUI myself, but a collegue tells me that it is messes thing up there to.
Regarding prior updates, I'll withdraw the statement that it's been happening in prior version as I can't get a definite confirmation of that. At the...
Apparently this has been happening for version prior to 7 and is quite well know in our organisation. I've just completed another set tests and confirmed this is the case. The default values get moved to the bottom of the list.
We do have a case open...
This is regarding the EXCLUDE registry key. Say it has the following value:
C:\Program Files\Veritas\NetBackup\bin\*.lock
C:\Documents and Settings\somedir
*.ndf
CLASS:SOMECLASS
C:\Some other path
After the upgrade this now looks like this:
C:\Doc...
The reason I ask this question is that during an upgrade from 6.5 to 7.0 the exclude list registry key is getting reordered. This is resulting in items ending up in the wrong policy class. We're having to work aroudn this with a VB script in addition...
