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

Recovery Considerations for Exchange, Checksum Verification and Soft Recovery, Immediately

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 61 highlights

Recovery Considerations for Exchange • ASM/ME does not allow torn Smart Copies. A scheduled task fails when it results in a torn Exchange Smart Copy. See Torn Smart Copies for an explanation of torn Smart Copies. • ASM/ME prevents you from creating a multiple writer Smart Copy sets where the Exchange Writer and the SQL server are included in a Smart Copy set. This condition is detected whether you create the Smart Copy from a volume, an application, or a collection. ASM/ME also detects multiple writer Smart Copy sets when you attempt to create schedules for such objects. If a multiple writer schedule runs, a warning is included in the notification email. It is possible to create an invalid (multiple writer) configuration after a schedule was created. If you create an invalid configuration, the schedule fails when it runs. • When you create a Smart Copy set that contains multiple Exchange components from the same writer, ASM/ME displays a warning but allows the operation to proceed. Dell recommends that you always configure your mailbox databases (for Exchange 2013 and 2016) on separate volumes. This configuration ensures that if you do need to restore data, you will restore only the damaged component. If you configure multiple Exchange mailbox databases on a single volume, all databases are restored even if only one database was damaged. • When you use Exchange utilities to relocate mailbox database components, and you have a Smart Copy that predates the change, you cannot use that Smart Copy to recover data. Instead, use a Recovery mailbox database (for Exchange 2013 and 2016) created from that Smart Copy. Checksum Verification and Soft Recovery For Smart Copies of Exchange components, you should perform Checksum Verification to ensure data integrity. Checksum Verification verifies the integrity of all files in the Smart Copy by using page Checksum Verification. Soft Recovery configures the Smart Copy to replay the transaction logs to put the databases into a clean shutdown state. When you create a Smart Copy, you can run Checksum Verification and Soft Recovery as follows: • During Smart Copy creation-Run the operations while the Smart Copy is being created. • After Smart Copy creation-Run the operations after you have created a Smart Copy. If you are running on a cluster, the node must own the cluster resources. If the operation completes successfully, then this option is disabled the next time the window opens. • As part of a scheduled Global Verification task-If you are running on a cluster, the node must own cluster resources required at the time that it selects a Smart Copy targeted for global verification to be processed. • On a remote host-Run the operation as part of the Global Verification task on a remote verification server. When a scheduled Global Verification task operation executes, ASM/ME updates the Smart Copy node to show that Checksum Verification and Soft Recovery are in progress. A soon as the operation is complete, ASM/ME updates the Smart Copy node to show the result. If you notice I/O performance problems when running checksum verification, consider changing the eseutil.exe registry key value. This procedure is defined in Microsoft Exchange eseutil.exe Utility. If the Smart Copy is a replica of an Exchange component, rather than a snapshot or clone, the Checksum Verification and Soft Recovery procedure is different. Volume replication is a continuous process and ASM/ME provides options to perform Checksum Verification and Soft Recovery without disrupting replication. For Exchange replicas only, the option to perform Checksum Verification is not available immediately after you create a Smart Copy. See Checksum Verification and Soft Recovery for Replicas for more information. Run Checksum Verification and Soft Recovery Immediately You can run Checksum Verification as part of creating a Smart Copy of an Exchange component, by selecting the following options: • Perform Checksum Verification • Perform Soft Recovery In the Perform Task panel, select Immediately after Smart Copy creation. If you do not select Checksum Verification and Soft Recovery operations at the time you create a Smart Copy Set, you can select them from the Smart Copy node. See Checksum Verification and Soft Recovery for Replicas. This option is available only if you did not already run Checksum Verification and Soft Recovery, or if you ran it, but one of the operations failed. If the Smart Copy is already mounted, ASM/ME sets its access state to Read-Write (if the Smart Copy is not already set to Read-Write). Using ASM/ME with Exchange 61

  • 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
Recovery Considerations for Exchange
•
ASM/ME does not allow torn Smart Copies. A scheduled task fails when it results in a torn Exchange Smart Copy. See
Torn Smart
Copies
for an explanation of torn Smart Copies.
•
ASM/ME prevents you from creating a multiple writer Smart Copy sets where the Exchange Writer and the SQL server are included in
a Smart Copy set. This condition is detected whether you create the Smart Copy from a volume, an application, or a collection.
ASM/ME also detects multiple writer Smart Copy sets when you attempt to create schedules for such objects. If a multiple writer
schedule runs, a warning is included in the notification email. It is possible to create an invalid (multiple writer) configuration after a
schedule was created. If you create an invalid configuration, the schedule fails when it runs.
•
When you create a Smart Copy set that contains multiple Exchange components from the same writer, ASM/ME displays a warning
but allows the operation to proceed. Dell recommends that you always configure your mailbox databases (for Exchange 2013 and
2016) on separate volumes. This configuration ensures that if you do need to restore data, you will restore only the damaged
component. If you configure multiple Exchange mailbox databases on a single volume, all databases are restored even if only one
database was damaged.
•
When you use Exchange utilities to relocate mailbox database components, and you have a Smart Copy that predates the change, you
cannot use that Smart Copy to recover data. Instead, use a Recovery mailbox database (for Exchange 2013 and 2016) created from
that Smart Copy.
Checksum Verification and Soft Recovery
For Smart Copies of Exchange components, you should perform Checksum Verification to ensure data integrity.
Checksum Verification verifies the integrity of all files in the Smart Copy by using page Checksum Verification. Soft Recovery configures
the Smart Copy to replay the transaction logs to put the databases into a clean shutdown state.
When you create a Smart Copy, you can run Checksum Verification and Soft Recovery as follows:
•
During Smart Copy creation—Run the operations while the Smart Copy is being created.
•
After Smart Copy creation—Run the operations after you have created a Smart Copy. If you are running on a cluster, the node must
own the cluster resources. If the operation completes successfully, then this option is disabled the next time the window opens.
•
As part of a scheduled Global Verification task—If you are running on a cluster, the node must own cluster resources required at the
time that it selects a Smart Copy targeted for global verification to be processed.
•
On a remote host—Run the operation as part of the Global Verification task on a remote verification server.
When a scheduled Global Verification task operation executes, ASM/ME updates the Smart Copy node to show that Checksum
Verification and Soft Recovery are in progress. A soon as the operation is complete, ASM/ME updates the Smart Copy node to show the
result.
If you notice I/O performance problems when running checksum verification, consider changing the
eseutil.exe
registry key value.
This procedure is defined in
Microsoft Exchange eseutil.exe Utility
.
If the Smart Copy is a replica of an Exchange component, rather than a snapshot or clone, the Checksum Verification and Soft Recovery
procedure is different. Volume replication is a continuous process and ASM/ME provides options to perform Checksum Verification and
Soft Recovery without disrupting replication.
For Exchange replicas only, the option to perform Checksum Verification is not available immediately after you create a Smart Copy. See
Checksum Verification and Soft Recovery for Replicas
for more information.
Run Checksum Verification and Soft Recovery
Immediately
You can run Checksum Verification as part of creating a Smart Copy of an Exchange component, by selecting the following options:
•
Perform Checksum Verification
•
Perform Soft Recovery
In the
Perform Task
panel, select
Immediately after Smart Copy creation
.
If you do not select Checksum Verification and Soft Recovery operations at the time you create a Smart Copy Set, you can select them
from the Smart Copy node. See
Checksum Verification and Soft Recovery for Replicas
.
This option is available only if you did not already run Checksum Verification and Soft Recovery, or if you ran it, but one of the operations
failed. If the Smart Copy is already mounted, ASM/ME sets its access state to
Read-Write
(if the Smart Copy is not already set to
Read-Write
).
Using ASM/ME with Exchange
61