Date: 09 Apr 2008
NV Version: All
OS Version: All
Plugin version: Snapvault Manager
Description:
This article talks about a problem restoring a OSSV snapshot. It was taken from the NetApp site.
NetApp Solution ID: kb28446
OSSV restore could not be started: cannot initialize an existing qtree
Symptoms
Snapvault release on OSSV primary fails with "Relationship not found"
Cannot release relationship from an OSSV restore
OSSV restore could not be started: cannot initialize an existing qtree
Whenever a file is restored using the Open Systems SnapVault (OSSV) command line, DFM or NetVault, a new snapvault relationship is created on the OSSV primary and Filer secondary. Once the restore completes, this relationship automatically enters a "Broken-off" state. It is necessary to remove this relationship if a restore to the same location is later needed.
For example, the following OSSV relationship has been created:
WIN2003-RTP:C:\tmp --> filer:/vol/restore/ossv_test
A file restore is needed from the destination. On the OSSV primary (WIN2003-RTP), the following command is used:
snapvault restore -S r200-rtp:/vol/restore/ossv_test/test.xls C:\test2
This restores file "test.xls" to the OSSV primary WIN2003-RTP in the C:\test2 folder. It also creates the new snapvault relationship.
On the OSSV primary:
Snapvault primary is ON
Source Destination State Lag Status
WIN2003:C:\tmp filer:/vol/vol1/ossv_qt Source 00:02:50 Idle
--> filer:/vol/vol1/ossv_qt/test.xls WIN2003:C:\test2 Broken-off - Idle
On the filer secondary:
Snapvault secondary is ON.
Source Destination State Lag Status
WIN2003:C:\tmp filer:/vol/vol1/ossv_qt Snapvaulted 00:01:43 Idle
--> filer:/vol/vol1/ossv_qt/test.xls WIN2003:C:\test2 Source 00:03:26 Idle
