Scenario 1
You have a customer with a large IBM Lotus Domino environment. The customer is in the process of migratingfrom a UNIX to a Microsoft Windows infrastructure. As part of this process, they are going to perform a refresh
of the hardware and software that Domino is running on. In addition, they will migrate all client backups to a
new EMC NetWorker environment. The new backup environment consists of a NetWorker server and two
storage nodes running on Windows 2008.
The Domino environment consists of a single server running two instances of Domino. The total amount of data
that needs to be backed up is approximately 900 GB. The Domino server will have connections to both the SAN
and the LAN. They would like to perform hot backups of the databases using the NMDA but are leaving specific
design decisions to you.
Additionally, the customer would like to send all data to disk for onsite backups and clone the first full backup of
the year to tape for long-term offsite retention. The backup target infrastructure consists of a single Quantum
i2000 tape library with six LTO-4 tape drives in addition to two EMC Data Domain 890s. One Data Domain will
be located at their primary site. The second Data Domain is at the disaster recovery (DR) site as a replication
target for the first.
One of the customer’s major concerns is the backup speed of the Domino environment. They are interested in
any best practices they can implement to improve backup performance at the Domino level. Furthermore, they
are looking for guidance in using NMDA to backup the data and leverage their backup infrastructure in the most
efficient way.
Refer to Scenario 1.
The customer has decided to implement DAOS on both Domino instances. What is a requirement to ensure
consistent recoverability of all data?
A.
DAOS directory and the Domino databases must be backed up at the same time.
B.
A level full backup must always be performed of the DAOS directory.
C.
A resync of the DAOS repository must be performed prior to backup.
D.
Domino index updates must be scheduled to occur immediately following the backup.