Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If I want users to restore from the local Snapshot, the user can just cd to volume "xyz" .snapshot directory and copy data from it. This can be done by users themself.
What if the user wants to restore data from SV on the remote filer, I need to export the volume "xyz_sv" on the secondary to the same client, and then mount "xyz_sv", and then copy data under "xyz_sv/.snapshot" to xyz on the host. Am I correct? In essence, the volume on the secondary has to be different than primary one
Appreicate your input!
4 REPLIES 4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You need a LIF and an export-policy (for NFS) or CIFS share (for cifs and joined the domain) then access the vaulted volume from the target export.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Understood. In addition to what you said, and then plus what I said will be the answer to my question. Correct?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
correct. 2 separate mount points. You can copy from snapvault/.snapshot back to the source volume.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Assuming this is for NFS I would suggest you use the automounter and then we've started placing a symlink in the primary volume (qtree in our case) that points to the autofs mount point of the snapvault volume. As long as you follow a standard naming convention on both sides of course..
--rdp
