When creating a flex clone with Qtree SnapMirror (QSM)
(SnapVault destination volume) based on a snapshot newer than the base snapshot
for the QSM/SnapVault relationship;the qtree will be cloned in RO mode.
Below is an example of what was encountered:
filer1*> snapvault status /vol/HSQLdst/data
Snapvault secondary is ON.
Source
Destination
State Lag
Status
filer2:/vol/HSQL/data
filer1:/vol/HSQLdst/data Snapvaulted
00:23:23 Idle
filer1*> snap list HSQLdst
Volume HSQLdst
working...
%/used %/total
date name
---------- ---------- ------------
--------
0% ( 0%) 0% ( 0%) Sep 12
07:31 newer_than_snapvault_base_snapshot
0% ( 0%) 0% ( 0%) Sep 12
07:06 filer1(0050420116)_HSQLdst-base.264 (busy,snapvault)
0% ( 0%) 0% ( 0%) Sep 12
07:05 sv_hourly.0
0% ( 0%) 0% ( 0%) Sep 12
06:05 sv_hourly.1
1% ( 0%) 0% ( 0%) Sep 12
05:05 sv_hourly.2
1% ( 0%) 0% ( 0%) Sep 12
04:05 sv_hourly.3
filer1*> vol clone create HSQLdst_c -b HSQLdst
newer_thansnapvault_base_snapshot
filer1*> snap list HSQLdst_c
Volume HSQLdst_c
working...
%/used
%/total date name
---------- ---------- ------------
--------
0% ( 0%) 0% ( 0%) Sep 12 07:31
newer_than__snapvault_base_snapshot
0% ( 0%) 0% ( 0%) Sep 12
07:06 filer1(0050420116)_HSQLdst-base.264 (busy,snapvault)
the cloned qtree is created with the snapvaulted flag
causing the lun within it to be R/O.
filer1*> qtree status HSQLdst_c
Volume Tree Style
Oplocks Status
-------- -------- ----- -------- ---------
HSQLdst_c
ntfs enabled normal
HSQLdst_c data ntfs
enabled snapvaulted
filer1*> lun show /vol/HSQLdst_c/data/data.lun
/vol/HSQLdst_c/data/data.lun 4.0g
(4301821440) (r/o, online)
When using snapshot older than the base snapshot for the
clone:
filer1*> vol clone create HSQLdst_c2 -b HSQLdst
sv_hourly.0
filer1*> qtree status HSQLdst_c2
Volume
Tree Style Oplocks Status
--------
-------- ----- -------- ---------
HSQLdst_c2
ntfs
enabled normal
HSQLdst_c2
data
ntfs enabled normal
filer1*> lun show /vol/HSQLdst_c2/data/data.lun
/vol/HSQLdst_c2/data/data.lun 4.0g
(4301821440) (r/w, offline)
Cause
This is by design. The clone operation inherits the
SnapVault/QSM base snapshot as busy, therefore,making the SnapVault property
clone as RO for the specified qtrees.
Solution
To resolve this issue, use the older snapshot as the base
snapshot for the clone. In this way the clone will not inherit the base
snapshot for that relationship. Then the clone will be created as Read/Write
(RW).
Source= Netapp Supoort
No comments:
Post a Comment