UNSOLVED

Aaron852

updated

15 years ago

A

Aaron852

1 Rookie

•

6 Posts

0

4715

October 6th, 2011 07:00

systemstate error code-10

Do you know why we keep getting the following error message:

avtar Error <8486>: Skipping post-processing on 'D:\Avamar\Var\SystemState.bkf' because of bad file size of 2048.0KB

avtar Error <6197>: Windows system State backup failed (code -10)

As a fix i have been performing an ntbackup of the systemstate file and if the backup runs to success i delete the systemstate file from the Avamar folder - This fix works for a couple of days and the issue occurs again, so i've started to move the backups to a different time window.

My questions is why do we receive this error message? It seems to be the cause of 80% of our failures?

I have checked the client by running the cmd - vssadmin list providers and writers with no errors found

Is this a known issue with Avamar backups? or maybe a performance related?

Please note, this is for VMs only.

  • Sameer_Khan

    121 Posts

    568

    1

    Posted October 30th, 2011 10:00

    Check the log for avamar initiated ntbackup system state backup in C:\Documents and Settings\Default User\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\Data and troublshoot ntbackup issues.

    You can also add --systemstate-timeout=7200 in avtar.cmd in var directory of target machine to allow 2 hours for ntbackup to finish.

  • Aaron852

    1 Rookie

    •

    6 Posts

    568

    0

    Posted November 3rd, 2011 03:00

    Thanks for the post above

    Sameer the systemstate timeout certainly sounds like a handy tip.

    I have recently noticed that the error occurs a lot when there is an issue with the writers (vssamin list writers)

    Does anyone know why the writers fail and is there anything i can do to proactively stop this happening?

  • Sameer_Khan

    121 Posts

    568

    0

    Posted November 16th, 2011 10:00

    Aaron,

    You can apply MS KB hotfix 940349 for windows 2003 SP2 and consult with Microsoft for VSS Failures on Windows 2008. Generally reboot clears up all VSS issues.

    Thanks

    Sameer K