Dell PowerVault DL4000 Dell PowerVault DL4000 Backup To Disk Appliance - Power - Page 59

About Seeding, Hosted and Cloud

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

Page 59 highlights

Text Box Description Replication to a Local The target core is located in a local data center or on-site location, and replication is Location maintained at all times. In this configuration, the loss of the Core does not prevent a recovery. Replication to an Off- The target core is located at an off-site disaster recovery facility for recovery in the event of a site Location loss. Mutual Replication Two data centers in two different locations each contain a core and are protecting agents and serving as the off-site disaster recovery backup for each other. In this scenario, each core replicates the agents to the Core that is located in the other data center. Hosted and Cloud Replication AppAssure MSP partners maintain multiple target cores in a data center or a public cloud. On each of these cores, the MSP partner lets one or more of their customers replicate recovery points from a source core on the customer's site to the MSP's target core for a fee. NOTE: In this scenario, customers only have access to their own data. Possible replication configurations include: Point to Point Multi-Point to Point Replicates a single agent from a single source core to a single target core. Replicates multiple source cores to a single target core. About Seeding Replication begins with seeding: the initial transfer of deduplicated base images and incremental snapshots of the protected agents, which can add up to hundreds or thousands of gigabytes of data. Initial replication can be seeded to the target core using external media to transfer the initial data to the target core. This is typically useful for large sets of data or sites with slow links. NOTE: While it is possible to seed the base data over a network connection, it is not recommended. Initial seeding involves potentially very large amounts of data, which could overwhelm a typical WAN connection. For example, if the seed data measures 10 GB and the WAN link transfers 24 Mbps, the transfer could take more than 40 days to complete. The data in the seeding archive is compressed, encrypted, and deduplicated. If the total size of the archive is larger than the space available on the removable media, the archive can span across multiple devices based on the available space on the media. During the seeding process, the incremental recovery points are replicated to the target site. After the target core consumes the seeding archive, the newly replicated incremental recovery points automatically synchronize. Seeding is a two-part process (also known as copy-consume): • The first part involves copying, which is the writing of the initial replicated data to a removable media source. Copying duplicates all of the existing recovery points from the source core to a local removable storage device such as a USB drive. After copying is complete, you must then transport the drive from the source core location to the remote target core location. • The second part is consuming, which occurs when a target core receives the transported drive and copies the replicated data to the repository. The target core then consumes the recovery points and uses them to form replicated agents. NOTE: While replication of incremental snapshots can occur between the source and target cores before seeding is complete, the replicated snapshots transmitted from the source to the target remains "orphaned" until the initial data is consumed, and they are combined with the replicated base images. 59

  • 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
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
Text Box
Description
Replication to a Local
Location
The target core is located in a local data center or on-site location, and replication is
maintained at all times. In this configuration, the loss of the Core does not prevent a recovery.
Replication to an Off-
site Location
The target core is located at an off-site disaster recovery facility for recovery in the event of a
loss.
Mutual Replication
Two data centers in two different locations each contain a core and are protecting agents and
serving as the off-site disaster recovery backup for each other. In this scenario, each core
replicates the agents to the Core that is located in the other data center.
Hosted and Cloud
Replication
AppAssure MSP partners maintain multiple target cores in a data center or a public cloud. On
each of these cores, the MSP partner lets one or more of their customers replicate recovery
points from a source core on the customer’s site to the MSP’s target core for a fee.
NOTE:
In this scenario, customers only have access to their own data.
Possible replication configurations include:
Point to Point
Replicates a single agent from a single source core to a single target core.
Multi-Point to
Point
Replicates multiple source cores to a single target core.
About Seeding
Replication begins with seeding: the initial transfer of deduplicated base images and incremental snapshots of the
protected agents, which can add up to hundreds or thousands of gigabytes of data. Initial replication can be seeded to
the target core using external media to transfer the initial data to the target core. This is typically useful for large sets of
data or sites with slow links.
NOTE:
While it is possible to seed the base data over a network connection, it is not recommended. Initial seeding
involves potentially very large amounts of data, which could overwhelm a typical WAN connection. For example, if
the seed data measures 10 GB and the WAN link transfers 24 Mbps, the transfer could take more than 40 days to
complete.
The data in the seeding archive is compressed, encrypted, and deduplicated. If the total size of the archive is larger than
the space available on the removable media, the archive can span across multiple devices based on the available space
on the media. During the seeding process, the incremental recovery points are replicated to the target site. After the
target core consumes the seeding archive, the newly replicated incremental recovery points automatically synchronize.
Seeding is a two-part process (also known as copy-consume):
•
The first part involves copying, which is the writing of the initial replicated data to a removable media source.
Copying duplicates all of the existing recovery points from the source core to a local removable storage device
such as a USB drive. After copying is complete, you must then transport the drive from the source core location
to the remote target core location.
•
The second part is consuming, which occurs when a target core receives the transported drive and copies the
replicated data to the repository. The target core then consumes the recovery points and uses them to form
replicated agents.
NOTE:
While replication of incremental snapshots can occur between the source and target cores before seeding
is complete, the replicated snapshots transmitted from the source to the target remains “orphaned” until the initial
data is consumed, and they are combined with the replicated base images.
59