|
You need to uninstall the maintenance pak, then uninstall the client, then reboot. If you're not unlucky and found yourself with an unbootable system, you can then re-install the client, using the custom installation option to not install VSP. Once you've done this, you can then upgrade the clients in the future without reboots.
There are cases where the uninstall will render your system unbootable - Veritas has technotes on this on how to recover. Even though the technotes describe a very small set of cases where this can happen, we've found other cases that don't fit their description that suffered the same fate - from a blue screen on boot to a continuous reboot cycle.
VSP is evil on Windows 2003. I am shocked that it is still installed by default when it's not required and when Veritas knows that uninstalling it could render the system unbootable.
.../Ed
On Feb 7, 2008 5:51 AM, amure1 < netbackup-forum AT backupcentral DOT com> wrote:
Hi I have searched this forum for help with locked VSP files and am a little bit more confused that when I started..
I'm using 2003 Servers with no 2000 servers in the domain and from what you guys are saying i should have VSS files not VSP?!?
The servers were not upgraded from 2000 and were a clean install to 2003 & I'm using NB 6.0MP5.
Well the question I got is how do I change these files to VSS as from what I gathered from the posts these don't fill up the drives and if they do what other options do I have..
Thanks
Marcus :D
--
Ed Wilts, Mounds View, MN, USA
mailto:ewilts AT ewilts DOT org
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
| 