Showing results for 
Search instead for 
Did you mean: 

Upgrade BESR from 6.5 to 7.0 - any issues?

Level 4
I'm planning on upgrading BESR from 6.5 to 7.0 on a Dell Poweredge 2950, PERC 5i, USB RD1000, and Windows Server 2003 R2 (standard).
If anyone has any suggestions as to things I should look at before/after this upgrade I'd appreciate it - the Symantec info regarding an upgrade seems a bit sparse - perhaps because it's such a simple, troublefree  process?
I read about the RD1000 eject issue with Win2003 SBS, and assume that it probably exists with Win2003 Standard as well.
I also assume that recovery points created with BESR 6.5 are completely useable by BESR 7.0 (otherwise no one would ever upgrade!)
Regardless, I appreciate any comments!
Thanks - Joe

Level 6
Employee Accredited Certified
BESR 7.0 does install "over the top" of BESR 6.5 installations.
BESR 7.0 does indeed fully support restoring recovery points created with earlier versions of the product.

Level 3
My recent experience is that there are many problems you can encounter updating from earlier versions to 7.0. My strong recommendation is to remove the earlier version first. Obtain the registry clean scripts from Symantec Support and use those as well. When installing 7.0 on domain controllers you might run into problems with the Microsoft Volume Snapshot Services. As far as I can tell those services need to be running when you do the install.
I get a different experience with each server (Mostly Dell 2650s). I've had to manually copy the .drivers to %systemdrive%/system32/drivers; I've had to run the fixinstall.bat script to re-register the DLLs when the setup failed to do that. I had to figure out how to make the setup finish when it hangs part way through.
If you install successfully and your backups don't run:
Check Start>Programs>Accessories>System Tools>System Information
Look for sysnap.sys and check it is loaded. If not then look for missing drivers and run fixinstall.bat
Hopefully Symantec will make a service release available soon that fixes these issues, or at least a decent KB article.
Cheers, Anthony Murfet.