HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)

188 of 739
(because SQL on the target will not allow you to attach more than one copy of the
same-named database).
Note:
If you select and setup both servers’ default instances for protection and both
source servers fail, the “Accounting” database on the first source server to be
failed over will be attached. The second server to failover will not be able to
attach its “Accounting” database.
Case 2: If Source1 has a database named “Accounting1”, and Source2 has a
database named “Accounting2”, then you can protect and failover the database on
both servers without any issues.
Note:
All database filenames (*.mdf, *.ldf, and *.ndf) must either be:
● Uniquely named (for example, accounting1.mdf and accounting2.mdf),
or
● Uniquely located on the target (for example,
c:\Source1\accounting1\accounting.mdf and
c:\Source2\accounting2\accounting.mdf).
Example 2: If you have two SQL servers (Source3 and Source4) where each has a
named instance installed (for example, Source3\instance1 and Source4\instance2), you
can protect databases from both servers if the target has at least those two instances
installed (Target1\instance1 and Target1\instance2).
Case: Both source SQL servers have a database named “Accounting”
(Source3\instance1|Accounting and Source4\instance2|Accounting). You can
protect and failover each SQL server’s copy of the database without any issue.
Note:
All the database filenames (*.mdf, *.ldf, and *.ndf) must either be:
● Uniquely named (for example, accounting1.mdf and accounting2.mdf),
or
● Uniquely located on the target (for example,
c:\Source3\accounting1\accounting1.mdf and
c:\Source4\accounting2\accounting2.mdf)
Mirror type
The following options specify what files you want sent from the source to the target
during a mirror.
● Full—Copies all of the directories and files in the replication set to the target
machine. If a mirror has already been completed, another full mirror will overwrite
the data on the target.