HP Storage Mirroring Software - Manual (Page 238)

Workload protection Page 237 of 677
*.ldf, and so on). Any attempts to manually attach the database may fail
if the user account does not yet have NTFS permissions to access the
physical files. To change the permissions on an individual file, perform
these steps on each file that is part of the database's file list.
a. In Windows Explorer, right-click the folder that contains the
physical files for the database that needs to be manually
attached.
b. Select Properties.
c. On the Security tab, determine if the user account has NTFS
permissions for that folder.
d. If the user account does not have specific or inherited
permissions, click the Add button.
e. Enter the user account name (such as domain\administrator).
f. After the user account has been added, give the account Full
Control permissions.
g. Make sure that the subfolders and files are set to inherit these
rights, then click OK.
l
If you are working in a many-to-one scenario, and you have two SQL
servers and each has only the default instance installed, you can
protect databases from both servers' default instances provided that the
database names are unique. For example, if both servers' default
instances have a database named Accounting, you can only protect
and failover one server's copy of the database because SQL on the
target will not allow you to attach more than one copy of the same-
named database. The first server to failover will attach its Accounting
database, while the second server to failover will not attach its
Accounting database.
If your two SQL servers have unique instances installed, you can
protect databases from both servers if the target has at least those two
instances installed.
Keep in mind, if the database names (accounting1.mdf and
accounting2.mdf) or locations on the target
(\source1\accounting1\accounting.mdf and
\source2\accounting2\accounting.mdf) are unique, you can protect and
failover both databases to the same target.
3. If you selected Database Only, you can highlight a non-system database and then
identify a unique Target Path. Keep in mind that if you are protecting multiple
databases, specifying a unique target path will impact the location of any
databases in the same or lower directory structure. For example, if you specify a