Dell EqualLogic PS6210XV EqualLogic Auto-Snapshot Manager/Microsoft Edition Ve - Page 49

Requirements for Creating Smart Copies

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

Page 49 highlights

Figure 8. Complete Smart Copy Consider the configuration shown in the following figure. In this example, two data sets span three volumes. Volume B contains data from two different data sets (Callouts 1 and 2). Figure 9. Torn Smart Copy You can use ASM/ME to copy Component1, indicated by Callout 1. However, ASM/ME performs its Smart Copy operations only on complete volumes. As a result, ASM/ME must include all the data on Volume B, even though some of it is part of a different data set (Component2, indicated by Callout 2). The resulting Smart Copy (containing A2 and B2) contains all of Component1, as indicated by Callout 1. It also contains the partial data set indicated by Callout 2. This partial data set is referred to as a torn data set because it does not contain all the files in the source data set. CAUTION: If you use this torn Smart Copy to restore Component1, you also partially overwrite Component2, potentially destroying live data on your production computer. When you have a torn Smart Copy, restore data only from those data sets that you know to be complete in the Smart Copy. This process can take longer, depending on the size of the files you restore from the Smart Copy. Because of the risk of data loss, and the more complicated recovery procedure, Dell recommends that you avoid spanning different data sets across common volumes. Requirements for Creating Smart Copies The following requirements must be met before you can create a Smart Copy: General ASM/ME Operations 49

  • 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
Figure 8. Complete Smart Copy
Consider the configuration shown in the following figure. In this example, two data sets span three volumes. Volume B contains data from
two different data sets (Callouts 1 and 2).
Figure 9. Torn Smart Copy
You can use ASM/ME to copy Component1, indicated by Callout 1. However, ASM/ME performs its Smart Copy operations only on
complete volumes. As a result, ASM/ME must include all the data on Volume B, even though some of it is part of a different data set
(Component2, indicated by Callout 2).
The resulting Smart Copy (containing A2 and B2) contains all of Component1, as indicated by Callout 1. It also contains the partial data set
indicated by Callout 2. This partial data set is referred to as a torn data set because it does not contain all the files in the source data set.
CAUTION:
If you use this torn Smart Copy to restore Component1, you also partially overwrite Component2, potentially
destroying live data on your production computer.
When you have a torn Smart Copy, restore data only from those data sets that you know to be complete in the Smart Copy. This process
can take longer, depending on the size of the files you restore from the Smart Copy. Because of the risk of data loss, and the more
complicated recovery procedure, Dell recommends that you avoid spanning different data sets across common volumes.
Requirements for Creating Smart Copies
The following requirements must be met before you can create a Smart Copy:
General ASM/ME Operations
49