Hello, friend!
Do you want to clone a LUN?
If yes, please see the following steps:
1. Log in to DeviceManager.
2. Click
vStore, select the desired vStore, and click Details to go to the vStore view. Choose Data Protection > Clone > LUN.
3. Click Create.
The Create Clone Wizard dialog box is displayed.
4. Set Name and Description of the clone, and click Next.
5. Optional: Select Immediately Available
6. Select a primary LUN for the clone.
a. Select the desired primary LUN.
b. Click Next.
7. Select secondary LUNs for the clone.
a. In the Available Secondary LUNs area, select the desired secondary LUN.
If no secondary LUN is available, click Create Secondary LUN and create a secondary LUN.
b. Click
.
c. The secondary LUN is moved to the Selected Secondary LUNs area.
Click Next.
8. Set properties for the clone
a. Set pair properties for the clone.
Parameter | Description | Value |
|---|
Copy Speed | Speed of data synchronization between the primary and secondary LUNs. Possible values are as follows: Low: When the speed is set to low, the data synchronization will take a long time. This value is applicable to scenarios where the service load is heavy. The speed is normally from 0 to 5 MB/s. Medium: When the speed is set to medium, the data synchronization will take a relatively short period. This value is applicable to scenarios where the service load is relatively heavy. The speed is normally from 10 to 20 MB/s. High: When the speed is set to high, the data synchronization will take a short period. This value is applicable to scenarios where the service load is relatively light. The speed is normally from 50 to 70 MB/s. Highest: When the speed is set to highest, the data synchronization will take the shortest period. This value is applicable to scenarios where the service load is light. The speed is normally above 100 MB/s.
| [Example] Medium |
Recovery Policy | In the event of a system problem such as a disk array fault or a LUN failure, all the pairs in a clone are interrupted. For synchronization or reverse synchronization tasks that are ongoing when a system problem occurs: If Recovery Policy is Automatic, suspended tasks automatically resume once the problem is resolved. If Recovery Policy is Manual, the value of Pair Running Status changes to To be recovered once the system problem is resolved. In this case, you can check the system before deciding whether to manually resume the suspended tasks.
| [Example] Automatic |
Enable initial synchronization | Indicates whether to implement an initial synchronization of data from the primary LUN to the secondary LUN. NOTE: If data on the primary LUN is inconsistent with that on the secondary LUN, you must select initial synchronization. Otherwise, data stays inconsistent. For example, if the primary LUN is for production services but the secondary LUN is a new one, initial synchronization is required. If the data on the primary LUN is consistent with that on the secondary LUN, you do not need to perform initial synchronization. If you are not sure about data consistency between the primary and secondary LUNs, perform initial synchronization.
| [Example] Enable |
b. Click Next.
9. Confirm that information about the clone is complete.
a. Check the clone's parameters.
b. Click Finish.
The Execution Result dialog box is displayed, indicating that the operation succeeded.
c. Click Close.
You have finished creating the clone.
Hope this helps!