Error(s) backing up Sys State on 2008 R2 Servers

[ahall]

I'm having a problem backing up the system state on my 2008 R2 servers. One is currently a domain controller and the error it is receiving is as follows -

Final error: 0xe00084f8 - The network connection to the Backup Exec Remote Agent has been lost. Check for network errors.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-34040

For the non-domain controller, the job finishes but with exceptions. The following file was skipped "c:\windows\system32\cba\pds.exe".

I'm running Backup Exec 12.5, Service Pack 2
Hotfix 324012
Hotfix 324011
Hotfix 327135
Hotfix 331998

On the servers having problems Remote Agent 12.5 Rev. 2213.144, Remote Agent Utility 2214.0.

After checking what failed on both servers is was "System Files" within the system state.

Thanks!

[CraigV]

Hi,

If you updated the BEWS 12.5 installation, did you push out your remote agents to your servers?

[KJavheri]

Please verify the versions of files on the win2k8 R2 server as per document:

http://support.veritas.com/docs/331998

For the non domain controller backup, check if c:\windows\system32\cba\pds.exe exists or not. This generally caused if you uninstall a application or a driver to which the file pds.exe belonged and now after uninstall there is some orphan entry remaining on the server.

the only way to resolve this is, create a normal text file and rename it as pds.exe and copy it in the above location and then run the backup.

The exception is harmless and would not have any effect during system recovery. this is generally observed only with win2k8 server .
http://support.veritas.com/docs/303664

Second thought: if the file already exists then it is getting scanned by a AV software which is not unlocking the file. Contact the AV provider if thats the case.

[ahall]

I think the issue with the one DC (DC1) is that it running as a Hyper-V Guest (2008 R2) and on a clustered shared volume HA failover cluster. I just promoted the stand alone 2008 R2 server to a DC (DC3) and it haven't run into any problems backing up the state. DC3 is running on a Windows 2008 (non-R2) as a Hyper-V guest, none clustered shared volume.

Thanks for the info about creating a text file to get rid of the one error, that did the trick.

Is there anyway I can sign up for the Beta program? I have valid service/maintenance agreements.

[KJavheri]

You can register for the Backup Exec 2010 Beta here.

https://www-secure.symantec.com/connect/events/announcing-backup-exec-2010-public-beta-dedupe-ever...

Alos since you already have the valid service/maintenance agreements you can also contact on the symantec local support number get the information from pre-sales or sales team. :)

Thanks

[KJavheri]

https://www-secure.symantec.com/connect/groups/backup-exec-2010-deduplication-early-adopter-program

[KJavheri]

https://www-secure.symantec.com/connect/groups/backup-exec-2010-deduplication-early-adopter-program

[ahall]

Okay, I'm now running Backup Exec 2010 Beta on a Windows 2008 R2 VM in Hyper-v (none-HA) and I'm still having problems.

When trying to backup the system state I'm getting "e000ff15 - A communications failure has occurred with a System State resource." on the same 2008 R2 DC (again HA, on clustered shared volume). Ideas?

Also, I tried installing Backup Exec 2010 Beta on my local machine (Windows XP SP3 32bit) and got the same error message as above backing up same data.