Skip to main content

ONTAP SVM root volume Load Sharing Mirror(LSM)

 ONTAP root volume Load Sharing Mirror(LSM)

A load-sharing mirror reduces the network traffic to a FlexVol volume by providing additional read-only access to clients.A load-sharing mirror is mounted in the same area of the SVM namespace as its source volume. This is useful for frequently read, but infrequently updated data, such as shared binary files


Steps:

1. Create destination Volume:

C1_SVM1::> volume create -vserver vs0 -volume root_dest -aggregate sti8_vsim_ucs571x_aggr1 -size 2GB -type DP

[Job 241] Job succeeded: Successful

2)Create the Mirror relation

C1_SVM1::> snapmirror create -source-path vs0:root_vs0 -destination-path vs0:root_dest -type LS

[Job 243] Job succeeded: SnapMirror: done

3)Initialize the mirror

C1_SVM1::> snapmirror initialize-ls-set -source-path vs0:root_vs0

[Job 245] Job is queued: snapmirror initialize-ls-set for source "C1_SVM1://vs0/root_vs0".

4)Verify the relationship

snapmirror show -destination-path vs0:root_dest



Comments

Popular posts from this blog

Deploy OVF fails Issues detected with selected template. Details: VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19].

 Error: While deploy using OVF file ,getting error as : Issues detected with selected template. Details: - -1:-1:VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19]. Solution: Open .OVF file and edit       <Info>Virtual hardware requirements for a virtual machine</Info>       <System>         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>         <vssd:InstanceID>0</vssd:InstanceID>         <vssd:VirtualSystemIdentifier>zabbix_appliance-6.2.7</vssd:VirtualSystemIdentifier>         <vssd:VirtualSystemType> virtualbox-2.2 </vssd:VirtualSystemType>       </System> to  vmx-19       <Info>Virtual hardware requireme...

Change ESXi acceptane level of VIBs to community Supported

-When you install VIB bundles you may see issue like:               'Could not find a trusted signer: self signed certificate  For resolving this issue, we have to convert the ESXi to community supported acceptance level. -To do that: if  ESXI is a VM :      Edit settings ->boot option ->disable secure boot. if Physical ESXi:      Edit  UEFI Now ssh to ESXi: - Move the ESX machine to community-support esxcli software acceptance set --level=CommunitySupported - Install the bundle with no-sign-check esxcli software vib install -d  VMware_bootbank_vmware-fdm_7.0.1-16478307.vib --no-sig-check -  Set back PartnerSupported esxcli software acceptance set --level=PartnerSupported