I've decided to turn this over to our Windows system admins. I'll also be
recommending them to open a call with Microsoft support (instead of using TSM
support). The crash isn't isolated to just the TSM backup window, and I can
prove it with event logs from previous crashes. Therefore, I
Sergio,
The particular system I am experiencing the trouble with right now is
vendor controlled. They are working with microsoft on the issue. One
other thing about this system is that it is using ms/sql replication for
the database and crashes are occuring during that replication as well.
I'll
I haven't done much experimenting with Windows 2008 yet but if you can't
even run the ntbackup utility to completion then IBM will classify this
issue as a Microsoft issue and as such they will ask you to contact
Microsoft. Sergio stated the system recovered from crash; my first
thought will be to
Sergio,
What specific error messages pertaining to TSM do you see in the
dsmerror.log file? While running vssadmin list writers, are there any
writers that show state of failure?
Thanks.
BERTAUT TCHUISE
TSM/NetApp Storage Administrator
Legg Mason Technology Services
*410-580-7032
The only indication that it's a VSS issue is the fact that the crash or hang
happens during or immediately after the System state backup. There's nothing
in the logs because the crash occurs abruptly. Even Window event logs don't
show any sort of error message or STOP event. The hotfixes I
Sergio,
Let me know how you make out with this. We are experiencing similar
problems which my gut kept telling me had to do with the vss. We have an
open ticket with IBM, but no real answers yet. One thing we did find was
that if you add -systemstate to the opt file thei system doesn't hang or
