2016-03-16 03:41 AM - last edited on 2016-03-16 08:03 AM by alissa
we are facing OSSV backup failure for only one drive F:\ expect C:\ and D:\
we geeting below errors...
Mon Mar 7 02:35:10 GMT [UKWKSTC1:replication.dst.waflErr:error]: SnapVault: destination transfer from 220.127.116.11:F:\ to /vol/OSSVHHGBKP_SATA/EHHGFILE001SPDRVF : could not read from socket:Resource temporarily unavailable.
Mon Mar 7 09:59:48 GMT [UKWKSTC1:replication.dst.waflErr:error]: SnapVault: destination transfer from 18.104.22.168:F:\ to /vol/OSSVHHGBKP_SATA/EHHGFILE001SPDRVF : could not read from socket:Resource temporarily unavailable.
dst Tue Mar 15 08:42:51 GMT 22.214.171.124:F:\ UKWKSTC1:/vol/OSSVHHGBKP_SATA/EHHGFILE001SPDRVF Start
dst Tue Mar 15 13:22:58 GMT 126.96.36.199:F:\ UKWKSTC1:/vol/OSSVHHGBKP_SATA/EHHGFILE001SPDRVF Abort (could not read from socket) (Resource temporarily unavailable)
dst Tue Mar 15 13:22:59 GMT 188.8.131.52:F:\ UKWKSTC1:/vol/OSSVHHGBKP_SATA/EHHGFILE001SPDRVF Rollback_start
if you gave update comment for snapvault ... the relatiship show trasfeering state but no data flow... after 4 -5 hours failing (without data transfer)...
184.108.40.206:F:\ UKWKSTC1:/vol/OSSVHHGBKP_SATA/EHHGFILE001SPDRVF Snapvaulted 275:13:14 Transferring
windows 2008/2003 both servers and ontap 8.2.3P3 version OSSV 3.0.1 version
2016-03-16 10:15 PM
There are two possible causes of this error:
1. The Windows server has run out of paged pool memory. This can be due to a registry hive which is too large for the API calls involved in the SystemState backup, or a general lack of memory resources on the Windows server. This issue is more likely to affect Windows Server 2003 systems and is described in Microsoft Support KB 304101.
2. There is a registry entry in the registry hive which is bad or otherwise cannot be read correctly. This issue is more common and typically affects Windows Server 2008 or newer systems.
1. To determine if the Windows server is running out of paged pool memory, follow the steps in Microsoft Support KB 304101.
Open Windows Task Manager and click the Performance tab.
Run an OSSV SystemState backup and note the Paged memory consumption in Task Manager.
On Windows Server 2003, if this value reaches 160 MegaBytes (MB) or larger, the server's paged pool memory is likely becoming exhausted. On Windows 2008, the maximum Paged memory is usually the same as the max Commit memory which can be seen from the Performance tab of Windows Task Manager.
2. To confirm a bad or unreadable registry entry, perform the following steps on the OSSV primary Windows server:
Click the Windows Start button and type "regedit" in the search field. Hit Enter.
Expand HKEY_LOCAL_MACHINE and right-click the registry hive on which the OSSV SystemState backup failed. For example, if the SystemState backup failed on \REGISTRY\MACHINE\SYSTEM, right-click SYSTEM.
Choose Registry Hive Files (*.*) in the Save as type drop-down menu and name the file using a .hiv extension such as "system.hiv".
If the registry hive has an issue with a particular registry entry, the export will most likely fail with the following Windows error:
Error writing to file. There may be a disk or file system error.