Job hangs after upgrading client to 6.5.5
Windows environment, 100's of clients running 6.5.5 with no problem, but every so often a newly updated client will not backup anything to tape after the upgrade to 6.5.5. The only way to get the job to run is to disable Volume Shadow Copy on the client. Disabling open file option on the Master Server under Client properties doesn't work. I have to go on the client and stop the Volume Shadow Copy and then disable it.
Has anyone run into this issue? I opened a ticket with Symantec 2 or 3 months ago thinking they were going to say, "Oh yeah, we know about the problem and here is the fix." Instead I spent a couple of weeks sending error logs but no resolution. I finally closed the call and rolled my clients back to 6.5.4 because I had to move on to another project. But now I need a fix. I'm going to open another ticket but thought I would first check with my fellow NetBackup Anonymous group.
Thanks,
Randy
Comments
Was the windows server rebooted after the upgrade
You don't mention it so I just thought I would ask, if after the upgrade to 6.5.5 did you reboot the windows servers.
I have had some where the VSC just will not 'reset' until I get the server rebooted.
I don't have to know how to spell....I work on Unix.
NetBackup 7.0.1 - AIX & Windows
Reboot Included...
I got excited because that made sense, it is Windows after all, and I didn't remember rebooting. But it just wasn't meant to be. Even after a reboot the backups wouldn't run. However, I think I made the same happen with 6.5.3 so I might be going down the wrong trail alltogether. I'll keep you posted in case anyone else runs into this.
What is the backup error code
What is the backup error code ?
check to make sure that you
check to make sure that you writers and providers are not in error
"vssadmin list writers"
"vssadmin list providers"
make sure that they all say 'no error' and 'stable'
if that is the case, in your list of providers, what entries are there? other writers might interfere with the the microsoft writer. i know for us this was the case with the storage foundation writer, and we had to unregister on all servers where we had similar issues
Would you like to reply?
Login or Register to post your comment.