inSync Private Cloud 5.2 - inSync Help - Druva

More documents

Recommendations

Info

inSync 5.2 Private Cloud – Administrator’s Guide Managing High Availability of a Storage In inSync, you can ensure high availability of a primary storage by assigning a secondary storage to it. The secondary storage takes over from the primary storage when the latter is unavailable for some reason. To the users, backups and restore continue seamlessly. This section describes the high availability functionality and the associated tasks. The topics described in this section are as follows. Tasks Concepts I Interface Descriptions Creating a High Availability Policy Viewing List of High Availability Policies Viewing the Details of a High Availability Policy Modifying a High Availability Policy About High Availability The High Availability Policy Details Page 172
inSync 5.2 Private Cloud – Administrator’s Guide About High Availability High Availability High availability is a feature of inSync that ensures that backups and restores from the user’s devices are not affected even when the primary storage is down. To use the HA functionality, you have to create a secondary storage that will act as a backup of your primary storage. This ensures that even when the primary storage is down, backups and restores continue seamlessly. Data from user’s devices are backed up independently to the primary and secondary storages. Backups to the primary storage follow the backup schedule defined in the user’s profile. Backup schedule to the secondary storage is defined when linking it to a primary storage. However, when the primary storage is down, backups to the secondary storage follow the backup schedule defined in the user’s profile. Seeding To reduce the bandwidth consumed for transferring data from the user’s devices to the secondary storage, you can utilize the seeding functionality of inSync. Under this functionality, modifications to data are replicated from the primary storage to the secondary storage at regular intervals. Backups to a secondary storage are not as frequent as a primary storage. Suppose, backup from a user's device to the primary storage happens every 4 hours but the backup to the secondary storage happens once every 24 hours. At the end of the day, the data that must be backed up from the user's device to the secondary storage can be quite large. However, most of these changes are already present in the primary storage. So, by seeding the changes from the primary to the secondary storage, you can reduce the amount of data that must be transferred from the user's device to the secondary storage. Note: If you are upgrading to inSync Private Cloud 5.2, the HA functionality will be available only for performance optimized storages. 173
Page 1 and 2:
inSync Private Cloud 5.2 Administra
Page 3 and 4:
inSync 5.2 Private Cloud - Administ
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122: inSync 5.2 Private Cloud - Administ
Page 171: inSync 5.2 Private Cloud - Administ
show all

inSync Private Cloud 5.2 - inSync Help - Druva

Create successful ePaper yourself

Delete template?

Save as template?