Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Backup Exec 2010 R2 fails on System State

Created: 01 Oct 2010 | 8 comments
Rosss's picture
0 0 Votes
Login to vote

Backup Exec 2010 R2 on a newly installed SBS 2008 server. Backup jobs are run onto a NAS device and they fail at the System State portion (the Remote Agent service crashes and everything goes belly up). I can read this in the log:

V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes.
V-79-57344-65301 - The System Sate resource is not responding. Backup set canceled.

The first portion of the job backup is fine.  The System State portion is the very last one and it just fails.

I also tried a local backup of just the System State component and it's terribly slow: it drops to 80 MB/min after a few minutes and then it almost freezes. Well, I read at http://www.symantec.com/business/support/index?pag... that this issue is still being investigated by Symantec but still... I'd like my full network backup to succeed.

Any suggestions? Thanks.

 

Comments

neo099's picture
02
Oct
2010
0 Votes 0
Login to vote

Hello, I have a similar

Hello, I have a similar problem with a MS Windows Small Business Server 2003Sp2. Deinstalled the old version BE v.10d totally, installed the 2010R2 60 days version and tried to backup to an QNap NAS. At the end of the protocol file it claims problems with the system state. There is a patch from microsoft for 2003 server and "system state problems" but it did not help. Backup on a tape was successfull. I am now trying to backup with Small Business server internal tool to the NAS. Maybe try this, i think the communication with the NAS is the problem.

 

Mahesh Roja's picture
03
Oct
2010
0 Votes 0
Login to vote

Hi

Here is its resolved follow the KB

http://www.symantec.com/business/support/index?page=content&id=TECH38338

If this Info helps to resolve the issue please Mark as Solution

Thanks

Mahesh Roja's picture
03
Oct
2010
0 Votes 0
Login to vote

And also

Refer this if above does't solved

http://www.symantec.com/business/support/index?page=content&id=TECH75076

If this Info helps to resolve the issue please Mark as Solution

Thanks

Mahesh Roja's picture
04
Oct
2010
0 Votes 0
Login to vote

HI Rosss

Any Update ?

If this Info helps to resolve the issue please Mark as Solution

Thanks

Rosss's picture
06
Oct
2010
0 Votes 0
Login to vote

No real improvements  And

No real improvements  frown

And we're not using AOFO at all. We even disabled the System State portion but the backup process stopped after a few minutes (we also tryed using a different network switch!) saying:

V-79-57344-65072 - The connection to target system has been lost

Our NAS system is a Synology DS410 (latest firmware).

 

Said@ccc.com.qa's picture
08
Feb
2011
0 Votes 0
Login to vote

Same Problem

My Backup didn't successful due to the same error , but the problem that i have on my list 5 system states the error appears only in one of them , mind you that i upgrade my version from d11 to 2010 R2 on windows 2003.

pkh's picture
08
Feb
2011
0 Votes 0
Login to vote

This is an old discussion. 

This is an old discussion.  You should start a new one for your problem and give the OS of the media server and the problem server.

navar holmes's picture
09
Mar
2011
0 Votes 0
Login to vote

Had the same type issue on my

Had the same type issue on my Server 2003 file server.  Using BE 2011 R2.

At first backups ran at about 1300 to 1500 MB/Min.  Then they dropped to 500 to 300.  Between these two we had a power outage.  Backups on this server started failing on Full and Diff jobs.

What I did.

Added the Anti-virus scanning exclusion for real time scanning and *.vsp

Per each drive letter: c:\Backup Exec AOFO Store\*.*

Change how big my event logs are.  I had them each at 16MB changed to 8MB.  Then I saved and cleared each event log.

As soon as i did this the current running job jumped to 1500MB/Min.