Re: VSS writers problems backing up



Hi,

Sorry about the delay in responding I had to wait for them to reboot the
server after the patches you mentioned in the last post were installed.

The error I get in the event viewer is this :

Volsnap Event ID 25

The shadow copies of volume C: were deleted because the shadow copy storage
could not grow in time. Consider reducing the IO load on the system or
choose a shadow copy storage volume that is not being shadow copied.

I also get this message:

Volsnap Event ID 33

The oldest shadow copy of volume D: was deleted to keep disk space usage for
shadow copies of volume D: below the user defined limit.

I have applied Service Pack 5 for Veritas on the server and had before this
installed all the patches I could find, now unfortunately the update client
has stopped working so I cannot easily check for more.

As for Windows patches I have basically been led by you on which ones I need
to apply and have put all the ones on that you have mentioned.

The backup works for a couple of days after a reboot but then starts failing
again.

Thanks

Anthony

"Thee Chicago Wolf" wrote:

Sorry to be back again but this has started happening again, we have tried
another reboot but the problem is not going away again.

Any new ideas come to the fore of late?

Thanks

Anthony

Anthony,

That's ok. How about a breakdown of what version / patches related to
Backup Exec do you have? What patches related to VSS do you have
installed? How about any event viewer logs and Event IDs associated
with the failed backups? All this info would help greatly. You've
already re-registered the EXE's and DLLs per
http://support.microsoft.com/kb/940032, correct?

The only other post-VSS roll-up patches and articles I've come across
are these:

Hotfixes:
http://support.microsoft.com/kb/949391
http://support.microsoft.com/kb/951568

Articles:
http://support.microsoft.com/kb/945058
http://support.microsoft.com/kb/941956
http://support.microsoft.com/kb/940184
http://support.microsoft.com/kb/953617
http://support.microsoft.com/kb/950141

Did you also happen to see these articles:
http://seer.entsupport.symantec.com/docs/264862.htm
http://seer.support.veritas.com/docs/263771.htm

I know you're not specifically experiencing these issues explicitly
(even after the roll-up was applied) but perhaps installing the
hotfixes from the two KBs listed above will at the very least bring
all VSS related files fully up to date and fix a couple bugs along the
way. Give it a shot.

- Thee Chicago Wolf

.



Relevant Pages

  • a1000 problem
    ... After installing the latest recommended ... patches, the 6.221 raid manager and some small patches and, ... reboot the machine and A1000 because the tools no longer ... There are no devices (controllers) in the system; ...
    (SunManagers)
  • Re: Any issues with this months patches?
    ... >reboot after installing the patches my desktop goes into a perpetual reboot. ... >Fortunately it booted into safe mode and I was able to do a restore. ...
    (microsoft.public.windowsxp.general)
  • Any issues with this months patches?
    ... I installed this month's patches on my desktop running XP Pro SP2. ... reboot after installing the patches my desktop goes into a perpetual reboot. ... On my laptop, XP Pro SP2, I installed the patches and saw the same issue. ...
    (microsoft.public.windowsxp.general)
  • Re: Any issues with this months patches?
    ... > I installed this month's patches on my desktop running XP Pro SP2. ... > Upon reboot after installing the patches my desktop goes into a ... > perpetual reboot. ...
    (microsoft.public.windowsxp.general)
  • Re: Patches that require a reboot
    ... I do that when deciding whether I can install single patches on ... a reboot). ... > rebooting after each patch saying this would be very time consuming. ... > installing a patch, even if the next thing you wish to do is install ...
    (comp.sys.sun.admin)