Dell EqualLogic PS6210S EqualLogic Auto-Snapshot Manager/Microsoft Edition Ver - Page 21

Backup Document Directories for Standalone (Non-Clustered) Hosts

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

Page 21 highlights

moved. Untagged collections (those for which the original host cannot be determined) are copied to the new location, but also left in the original location. Backup Document Directories for Standalone (Non-Clustered) Hosts A host that is not part of a cluster or a SharePoint farm should have its own backup document directory for storing backup documents. The hosts should use different directories for storing their backup documents. If you use a shared Windows directory for a standalone host, you must use a subdirectory within the shared directory. If host A and host B (both standalone hosts) store their backup documents on a shared directory, they should each store them in their own subdirectories. For example, Host A would store them on \\server\share\subdirectory1, and Host B would store them on \\server\share \subdirectory2. Backup Document Directories for Clusters and SharePoint Farms With the exception of Exchange Data Availability Group (DAG) clusters, cluster nodes and hosts in a SharePoint farm must always share the same backup document directory path. For example, if Node 1 stores backup documents on \\server\share\subdirectory1, then Node 2 must also store backup documents on \\server\share\subdirectory1. In a cluster, you can specify a directory as a non-clustered or clustered resource. You must first use Windows cluster utilities to create the folder and make it available to the cluster nodes. If you specify a shared folder located on a clustered iSCSI volume, you can create Smart Copies of that volume, but cannot restore data from the volume (otherwise the folder might be overwritten). Set the Backup Document Directory 1. In the navigation area, click Settings. 2. Click the General Settings tab. If you are managing multiple hosts and want to make the same changes to multiple hosts, multiselect the hosts in the middle panel. The changes will affect all selected hosts. 3. Specify a directory for backup documents. a) For a single-system configuration, you can change the location of Auto-Snapshot Manager Document Directory. Do not change the location of Smart Copy documents if you have configured remote verification. See Run Checksum Verification and Soft Recovery on a Remote Host. b) If you have a cluster, backup documents should use a network shared folder. ASM/ME expects you to enter the UNC-format name of this network shared folder, in a format such as \\ClustersystemFS\H$\VSS Requestor\ The network shared folder is accessed from all cluster nodes. 4. Specify all other options listed and click Save. To restore settings to their current saved state, click Discard. Managing the ASM Services You can choose to run the ASM Services on a local system or as a specified user of a domain. You must add the host running ASM/ME to the domain and enter a user name and password. If you plan to use single sign-on (SSO), the ASM Services must be configured to use accounts with domain access. See Edit ASM/ME Settings on Hosts in a HIT Group. Notification Settings The Notification Settings panel allows you to configure email settings so that you can send or receive email alerts when certain operations complete or fail. This page also allows you to specify whether or not to receive email alerts at all. • In a cluster environment, set up email notification for every node in the cluster. Jobs run on the node that currently owns the cluster resource, and the node that owns the cluster resource can change. • To view the list of available alerts, or to enable or disable specific alerts, click Alert Settings. For more information about the alerts list, see Alert Settings. The following table describes the email notification settings. Configure ASM/ME 21

  • 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
moved. Untagged collections (those for which the original host cannot be determined) are copied to the new location, but also left in the
original location.
Backup Document Directories for Standalone (Non-Clustered) Hosts
A host that is not part of a cluster or a SharePoint farm should have its own backup document directory for storing backup documents.
The hosts should use different directories for storing their backup documents. If you use a shared Windows directory for a standalone
host, you must use a subdirectory within the shared directory. If host A and host B (both standalone hosts) store their backup documents
on a shared directory, they should each store them in their own subdirectories.
For example, Host A would store them on
\\server\share\subdirectory1
, and Host B would store them on
\\server\share
\subdirectory2
.
Backup Document Directories for Clusters and SharePoint Farms
With the exception of Exchange Data Availability Group (DAG) clusters, cluster nodes and hosts in a SharePoint farm must always share
the same backup document directory path. For example, if Node 1 stores backup documents on
\\server\share\subdirectory1
,
then Node 2 must also store backup documents on
\\server\share\subdirectory1
.
In a cluster, you can specify a directory as a non-clustered or clustered resource. You must first use Windows cluster utilities to create the
folder and make it available to the cluster nodes.
If you specify a shared folder located on a clustered iSCSI volume, you can create Smart Copies of that volume, but cannot restore data
from the volume (otherwise the folder might be overwritten).
Set the Backup Document Directory
1.
In the navigation area, click
Settings
.
2.
Click the
General Settings
tab.
If you are managing multiple hosts and want to make the same changes to multiple hosts, multiselect the hosts in the middle panel.
The changes will affect all selected hosts.
3.
Specify a directory for backup documents.
a)
For a single-system configuration, you can change the location of Auto-Snapshot Manager Document Directory. Do not change
the location of Smart Copy documents if you have configured remote verification.
See
Run Checksum Verification and Soft Recovery on a Remote Host
.
b)
If you have a cluster, backup documents should use a network shared folder. ASM/ME expects you to enter the UNC-format
name of this network shared folder, in a format such as
\\ClustersystemFS\H$\VSS Requestor\
The network shared folder is accessed from all cluster nodes.
4.
Specify all other options listed and click
Save
.
To restore settings to their current saved state, click
Discard
.
Managing the ASM Services
You can choose to run the ASM Services on a local system or as a specified user of a domain. You must add the host running ASM/ME to
the domain and enter a user name and password.
If you plan to use single sign-on (SSO), the ASM Services must be configured to use accounts with domain access. See
Edit ASM/ME
Settings on Hosts in a HIT Group
.
Notification Settings
The
Notification Settings
panel allows you to configure email settings so that you can send or receive email alerts when certain operations
complete or fail. This page also allows you to specify whether or not to receive email alerts at all.
•
In a cluster environment, set up email notification for every node in the cluster. Jobs run on the node that currently owns the cluster
resource, and the node that owns the cluster resource can change.
•
To view the list of available alerts, or to enable or disable specific alerts, click
Alert Settings
. For more information about the alerts
list, see
Alert Settings
.
The following table describes the email notification settings.
Configure ASM/ME
21