Steven,
In my test I was able to successfully run a backup. I
tried to simulate your scenario as close as possible with the information
given. The backup was written to a disk STU rather than tape but that shouldn’t
make any difference. The client happened to be at version 6.5.1. What client version
is in use in your situation?
Regards.
From: Haskins, Steve
Sent: Monday, January 12, 2009 1:59 PM
To: 'Green, Steven'; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] NB 6.5.3 event log restore hangs subsequent
backup
Steven,
This is very interesting and I am glad you shared. I just
updated my Windows Netbackup environment to 6.5.3 (from 6.5.1).
I’ll test this out.
I have an issue with the automated Image Cleanup job ending with
status 20.
Regards,
Steve
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Green,
Steven
Sent: Monday, January 12, 2009 1:37 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] NB 6.5.3 event log restore hangs subsequent backup
I
have run into an issue during testing of NB 6.5.3 that I wanted to share with
the group. Perhaps someone else running 6.5.3 can try and duplicate the problem
and help determine whether this is a furreal problem, or something peculiar
about our environment. Here is the scenario:
- Backup a run-o-the-mill Windows
2003 server
- Restore the event logs from that
backup - redirect to a new folder (eg C:\MyLogs), and be sure to select
the Overwrite checkbox in the restore dialog
- Submit another backup (full or
incr) to same server – it hangs
The
problem comes in on the second backup, following the restore of the event logs
- the backup job hangs endlessly, never writing data. The client will have the
bpbkar32 process “running”, but doing nothing, and nothing useful
is logged either. Killing and restarting the backup make no difference. In
fact, killing the backup from the NB admin console does not make the
client bpbkar32 process go away. If you explicitly kill the client bpbkar32 PID
and restart the backup you get the same behavior – no backup. Even
restarting the NB service makes no difference. It takes a reboot of the server
to clear up the condition. Not very nice. I suspect this same behavior would occur
in restoring any other component of the System State information, but my focus
has been on the event logs as we occasionally get requests from our security
people to do this.
I
have an open case to Symantec on this issue but have not received any useful
feedback as yet. I thought I’d share with group and see if anyone else
has noticed this behavior. Aside from this anomaly, 6.5.3 seems to be a good
release (it must be snowing in Hell).
When/if
I ever get feedback from Symantec I’ll post the resolution.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#!/usr/local/man/steve green
TDS Storage Administration
Ph:
608.664.8210 Cel: 608.219.2106
What can be asserted
without evidence may be dismissed without evidence.
