09-06-2013 03:59 AM
Dear Forum,
I m trying to backup W2K12 Standard OS server Roles configured:- File and storage services , Hyper-V through NBU 7.5.0.6 but the server reboots in between.
This issue has started only after the backup was provisioned for the server.
Master server OS is Sol. 10.
Your suggestions/solutions are welcomed.
Solved! Go to Solution.
02-17-2014 10:13 PM
Sorry for the delayed response, When the problem was refered to symantec technical team in co-ordination with Microsoft team it was found that 1 HP storage controller file (HPCISSS2.sys - ) was creating the issue and that was degraded.
After that the issue was not faced.
09-06-2013 05:30 AM
Hi NBU2010,
That's not good. If the reboots itself during backup, better open a case with NetBackup support asap. I would upload the following logs as well to speed up analysis.
1. Memory dump (memory.dmp) as mentioned in:
http://blogs.technet.com/b/askcore/archive/2012/09/12/windows-8-and-windows-server-2012-automatic-memory-dump.aspx
2. NetBackup bpbkar log
<install dir>\Veritas\NetBackup\logs\bpbkar\
3. NetBackup bpfis log
<install dir>\Veritas\NetBackup\logs\bpfis\
4. NetBackup NBSU output. To obtain this item, open command line and go to:
<install dir>\Veritas\NetBackup\bin\support\
Run nbsu -c -t <enter>, the output will be in <install dir>\Veritas\NetBackup\bin\support\output\nbsu\...\
(in .cab format).
The only problem is you may or may not already have the bpbkar and bpfis log folders created. If you don't have them, just log the case first.
All the best!
02-16-2014 10:38 PM
There was the issue with the OS itself which was referred to Microsoft and then as per the procedure informed, the issue has been resolved.
02-17-2014 09:51 PM
Please share with the forum the details of the OS problem?
And how it was resolved?
This is why all of us visit this forum - not to only receive assistance, but also to share experience that will help other users experiencing similar issues...
02-17-2014 10:13 PM
Sorry for the delayed response, When the problem was refered to symantec technical team in co-ordination with Microsoft team it was found that 1 HP storage controller file (HPCISSS2.sys - ) was creating the issue and that was degraded.
After that the issue was not faced.