You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storsimple/storsimple-virtual-array-failover-dr.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ DR is modeled as a full device restore using the heat map–based tiering and tr
35
35
>
36
36
>
37
37
38
-
Disaster recovery is orchestrated via the device failover feature and is initiated from the **Devices** blade. This blade tabulates all the StorSimple devices connected to your StorSimple Device Manager service. For each device, you can see the friendly name, status, provisioned and maximum capacity, type, and model.
38
+
Disaster recovery is orchestrated through the device failover feature and is initiated from the **Devices** blade. This blade tabulates all the StorSimple devices connected to your StorSimple Device Manager service. For each device, you can see the friendly name, status, provisioned and maximum capacity, type, and model.
39
39
40
40
## Prerequisites for device failover
41
41
@@ -52,15 +52,15 @@ For a device failover, ensure that the following prerequisites are satisfied:
52
52
>
53
53
* The target device cannot have the same name as the source device.
54
54
* The source and target device have to be the same type. You can only fail over a virtual array configured as a file server to another file server. The same is true for an iSCSI server.
55
-
* For a file server DR, we recommend that you join the target device to the same domain as the source. This configuration ensures that the share permissions are automatically resolved. Only the failover to a target device in the same domain.
55
+
* For a file server DR, we recommend that you join the target device to the same domain as the source. This configuration ensures that the share permissions are automatically resolved. Only the failover to a target device in the same domain is supported.
56
56
* The available target devices for DR are devices that have the same or larger capacity compared to the source device. The devices that are connected to your service but do not meet the criteria of sufficient space are not available as target devices.
57
57
58
58
### Other considerations
59
59
60
-
* For a planned failover
60
+
* For a planned failover:
61
61
62
62
* We recommend that you take all the volumes or shares on the source device offline.
63
-
* We recommend that you take a backup of the device and then proceed with the failover to minimize data loss.
63
+
* We recommend that you take a backup of the device and then proceed with the failover to minimize data loss.
64
64
* For an unplanned failover, the device uses the most recent backup to restore the data.
0 commit comments