Dell PowerVault NX3610 User Manual - Page 42

Replication Partners, Local Replication

Get Dell PowerVault NX3610 PDF manuals and user guides View all Dell PowerVault NX3610 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 42 highlights

Fast backup and restore Maintain full copies of data for protection against data loss, corruption, or user mistakes. Disaster recovery Mirror data to remote locations for failover. Remote data access Applications can access mirrored data in read-only or read-write mode. Online data migration Minimize downtime associated with data migration. Replication leverages the snapshot technology in the NAS cluster solution file system. After the first replication, only deltas are replicated. This allows for faster replication and efficient use of the CPU cycles. It also saves on storage space while keeping data consistent. Replication is volume based and can be used to replicate volumes on the same NAS appliance or a volume on another NAS appliance. When replicating a volume to another NAS appliance, the other NAS appliance must be setup as a replication partner. Replication Partners Once a partner relationship is established, replication is bi-directional. One system could hold target volumes for the other system as well as source volumes to replicate to that other system. Replication data flows through a secure ssh tunnel from system to system over the client network. A replication policy can be setup to run on various schedules as well as on demand. All system configurations (user quotas, snapshot policy, and so on) are stored on each volume. When a volume is replicated, the target volume holds identical information. When removing a replication policy, an option is provided for transferring the volume configuration. NOTE: Replication partners must have the same controller count. Do not, for example, attempt to replicate a 4 controller appliance to a 2 controller appliance. Figure 2. Local Replication 42

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
Fast backup and restore
Maintain full copies of data for protection against data loss, corruption, or user mistakes.
Disaster recovery
Mirror data to remote locations for failover.
Remote data access
Applications can access mirrored data in read-only or read-write mode.
Online data migration
Minimize downtime associated with data migration.
Replication leverages the snapshot technology in the NAS cluster solution file system. After the first replication, only
deltas are replicated. This allows for faster replication and efficient use of the CPU cycles. It also saves on storage
space while keeping data consistent.
Replication is volume based and can be used to replicate volumes on the same NAS appliance or a volume on another
NAS appliance. When replicating a volume to another NAS appliance, the other NAS appliance must be setup as a
replication partner.
Replication Partners
Once a partner relationship is established, replication is bi-directional. One system could hold target volumes for the
other system as well as source volumes to replicate to that other system. Replication data flows through a secure ssh
tunnel from system to system over the client network.
A replication policy can be setup to run on various schedules as well as on demand. All system configurations (user
quotas, snapshot policy, and so on) are stored on each volume. When a volume is replicated, the target volume holds
identical information. When removing a replication policy, an option is provided for transferring the volume
configuration.
NOTE:
Replication partners must have the same controller count. Do not, for example, attempt to replicate a 4
controller appliance to a 2 controller appliance.
Figure 2. Local Replication
42