SnapProtect - SnapProtect for Open Systems - Troubleshooting - NetApp

DFM Job Fails with Error "Unable to connect to source filer"

Check LREPTRansfer.log and if it contains the following error, resolve a possible conflict on port 10566 on the client computer.

LREPTransfer.log

i. 34216 8d54 08/08 16:00:34 1375992034 SnapProtect for Open SystemsControlThread() - Failed to bind:[Error code :-2147014848

If a client's IP address is changed, make sure that the file servers in the resourcepools, that is, the destination filers are notified of the name change. Use the Name Management application from SnapProtect to notify SnapProtect of the name change and kill SnapProtect for Open Systemstest.exe after you run the Name Management application.

VSS Snapshot Creation does not Finish Successfully on Windows 2003

If the snapshot creation fails and the system event or the specific log lines contain the errors below, remove pagefile.sys and hiberfil.sys from the files to be filtered, then re-run the job. Refer to Skipping Files for Backup for information about how to skip these two files.

System event:

[TYPE] Error [TIME] 2014/02/11 14:11:56 [SOURCE] VolSnap [COMPUTER] W2K3MS01 [DESCRIPTION] The shadow copies of volume C: were aborted because of a failure to ensure crash dump or hibernate consistency.

Log lines in the Windows Event logs:

[TYPE] Error [TIME] 2014/01/24 16:09:34 [SOURCE] VSS [COMPUTER] W2K3MS01 [DESCRIPTION] Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {a4b3467a-2462-442b-8699-bbad76968c76}. Routine details Error calling Query(). [0x800706ba] [hr = 0x800706ba].