SHIFT

--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools


srmclone
Differences

This shows you the differences between two versions of the page.

Link to this comparison view

srmclone [2013/07/01 22:06] (current)
sjoerd created
Line 1: Line 1:
 += SRM 5.1: Where is RW Clone Located =
  
 +During implementation of SRM we had the question where the RW clone that gets created during a SRM test is located. It should be in the aggregate containing the volume, because that's also where the snapshot is located. However, we decided to check.
 +
 +> Note: This is with the NetApp SRA, other storage vendors might use different replication techniques resulting in different architecture.
 +
 +After performing a SRM test we could see the following information.
 +
 += Volume Information =
 +With the command {{{vol status}}} you can check the various volumes involved:
 +
 +Source volume:
 +<​code>​
 +filer01b>​ vol status R_FC_PRD_01
 +         ​Volume State           ​Status ​           Options
 +R_FC_PRD_01 online ​         raid4, flex       ​nosnap=on,​ no_atime_update=on,​
 +                                mirrored ​         snapmirrored=on,​ create_ucode=on,​
 +                                snapmirrored ​     fs_size_fixed=on,​
 +                                read-only ​        ​fractional_reserve=0
 +                                64-bit
 +                Volume has clones: testfailoverClone_nss_v10745371_R_FC_PRD_01
 +                         ​Volume UUID: d1797cc3-744b-11e2-b103-123478563412
 +                Containing aggregate: '​aggr0'​
 +</​code>​
 +
 +Cloned volume:
 +<​code>​
 +filer01b>​ vol status testfailoverClone_nss_v10745371_R_FC_PRD_01
 +         ​Volume State           ​Status ​           Options
 +testfailoverClone_nss_v10745371_R_FC_PRD_01 online ​         raid4, flex       ​nosnap=on,​ no_atime_update=on,​
 +                                mirrored ​         create_ucode=on,​ guarantee=none,​
 +                                64-bit ​           fractional_reserve=0
 +                Clone, backed by volume '​R_FC_PRD_01',​ snapshot '​filer01b(0151702703)_R_FC_PRD_01.3682'​
 +                         ​Volume UUID: 6560861a-7691-11e2-b103-123478563412
 +                Containing aggregate: '​aggr0'​
 +</​code>​
 +As you can see is the clone located in aggregate aggr0. Also, you can see that although the source volume has a space guarantee, the clone does not.
 +
 +== OnCommand ==
 +If you prefer OnCommand to view this information you can: \\
 +{{srmclone01.jpg}} \\
 +{{srmclone02.jpg}} \\
 +
 += LUN Information =
 +With the command {{{lun show}}} you can also check the LUN which is connected to the ESX servers:
 +<​code>​
 +filer01b>​ lun show -v /​vol/​testfailoverClone_nss_v10745371_R_FC_PRD_01/​R_FC_PRD_SRM
 +        /​vol/​testfailoverClone_nss_v10745371_R_FC_PRD_01/​R_FC_PRD_SRM ​    25g (26843545600) ​  (r/w, online, mapped)
 +                Comment: "​Tijdelijk lun for SRM testing"​
 +                Serial#: 2FfBf]BKxrzZ
 +                Share: none
 +                Space Reservation:​ disabled
 +                Multiprotocol Type: vmware
 +                Maps: srmtest_v10745371_domain-c36_fcp=0
 +                Occupied Size:   13.9g (14894223360)
 +                Creation Time: Mon Feb 11 15:10:11 CET 2013
 +                Cluster Shared Volume Information:​ 0x0
 +
 +filer01b>​ lun show -m /​vol/​testfailoverClone_nss_v10745371_R_FC_PRD_01/​R_FC_PRD_SRM
 +/​vol/​testfailoverClone_nss_v10745371_R_FC_PRD_01/​R_FC_PRD_SRM srmtest_v10745371_domain-c36_fcp ​       0       FCP
 +</​code>​
 +
 +== OnCommand ==
 +If you prefer OnCommand to view this information you can: \\
 +{{srmclone03.jpg}} \\
 +
 +{{tag>​srm vmware storage}}
srmclone.txt ยท Last modified: 2013/07/01 22:06 by sjoerd