Dell PowerVault LTO4-120HH Dell DR Series System Administrator's Guide - Page 19

Reverse Replication: Alternate Method, Supported File System Protocols, NFS

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

Page 19 highlights

5. Delete the replication relationship and re-create a replication relationship (restoring original source and target destinations). Under this scenario, a fraction of the data to be recovered is sent across the WAN link. This could speed up a remote restore significantly. However, there are some downsides to this type of scenario: • If step 1 is not followed correctly, any changes not fully replicated are lost. • During steps 2 and 3, any data that is written to the original DR Series system source container may be lost. • During step 4, if the data is not fully replicated back before the switch is made, it may be lost. Alternatively, you could still support this type of effort by completing the following: 1. Create a new container on the target DR Series system. 2. Set up replication from this container back to the source DR Series system container. 3. Set up a new disk storage unit in the DMA and make sure that the DMA is aware of any new images. 4. Import the old images back into the DMA from the target DR Series system (the original source location). 5. Use a new disk storage unit in the DMA, and then restore the data back to the original client. Reverse Replication: Alternate Method To support an alternate method of reverse replication, complete the following: 1. Create a new container on the target DR Series system. 2. Set up replication from this container back to the source DR Series system container. 3. Set up a new disk storage unit in the DMA and make sure that the DMA is aware of any new images. 4. Import the old images back into the DMA from the target DR Series system (the original source location). 5. Use a new disk storage unit in the DMA, and then restore the data back to the original client. Supported File System Protocols The DR Series system supports the following file system protocols: • Network File System (NFS) • Common Internet File System (CIFS) • OpenStorage Technology (OST) NOTE: The DR Series system supports three container connection types: NFS, CIFS, and OST. OST provides a logical disk interface that can be used with network storage devices to store data and support data storage operations. For more information on OST, see Understanding OST, Creating an OST Connection Type Container, and Creating an NSF or CIFS Connection Type Container. For more information on NFS and CIFS, see NFS, and CIFS. NFS The Network File System (NFS) is a file system protocol that is designated to be a file server standard, and its protocol uses the Remote Procedure Call (RPC) method of communication between computers. Clients can access files via the network similar to the way that local storage is accessed. NFS is a client-server application in which a client can view, store, and update files on a remote system just like they are working on a local system. System or Network Administrators can mount all or a portion of a file system, and the file 19

  • 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
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
5.
Delete the replication relationship and re-create a replication relationship (restoring original source and target
destinations).
Under this scenario, a fraction of the data to be recovered is sent across the WAN link. This could speed up a remote
restore significantly. However, there are some downsides to this type of scenario:
•
If step 1 is not followed correctly, any changes not fully replicated are lost.
•
During steps 2 and 3, any data that is written to the original DR Series system source container may be lost.
•
During step 4, if the data is not fully replicated back before the switch is made, it may be lost.
Alternatively, you could still support this type of effort by completing the following:
1. Create a new container on the target DR Series system.
2. Set up replication from this container back to the source DR Series system container.
3. Set up a new disk storage unit in the DMA and make sure that the DMA is aware of any new images.
4. Import the old images back into the DMA from the target DR Series system (the original source location).
5. Use a new disk storage unit in the DMA, and then restore the data back to the original client.
Reverse Replication: Alternate Method
To support an alternate method of reverse replication, complete the following:
1.
Create a new container on the target DR Series system.
2.
Set up replication from this container back to the source DR Series system container.
3.
Set up a new disk storage unit in the DMA and make sure that the DMA is aware of any new images.
4.
Import the old images back into the DMA from the target DR Series system (the original source location).
5.
Use a new disk storage unit in the DMA, and then restore the data back to the original client.
Supported File System Protocols
The DR Series system supports the following file system protocols:
•
Network File System (NFS)
•
Common Internet File System (CIFS)
•
OpenStorage Technology (OST)
NOTE:
The DR Series system supports three container connection types: NFS, CIFS, and OST. OST provides a
logical disk interface that can be used with network storage devices to store data and support data storage
operations.
For more information on OST, see
Understanding OST
,
Creating an OST Connection Type Container
, and
Creating an NSF
or CIFS Connection Type Container
.
For more information on NFS and CIFS, see
NFS
, and
CIFS
.
NFS
The Network File System (NFS) is a file system protocol that is designated to be a file server standard, and its protocol
uses the Remote Procedure Call (RPC) method of communication between computers. Clients can access files via the
network similar to the way that local storage is accessed.
NFS is a client-server application in which a client can view, store, and update files on a remote system just like they are
working on a local system. System or Network Administrators can mount all or a portion of a file system, and the file
19