You are The Exchange administrator for your company. The company hosts Exchange e-mail for other companies.
The service level agreement (SLA) for a customer named Trey Research states that failed Exchange mailbox stores must be online again in one hour or less.
The SLA also states that alI e-mail data must be retained tor one year.
Trey Research uses two mailbox stores named MBXO1 and MBX02. Both mailbox stores reside on a Storage Area Network. MBX01 is 25 GB in size and MBX02 is 22 GB in size.
There is 153 GB of available disk space on the Storage Area Network for Trey Research Data. You can back up or restore Trey Research mail at a rate of 12 GB per hour.
You need to ensure that you can meet the SLA requirements for the Trey Research mailbox stores.
What should you do?
A.
Every night, perform full backups to tape and archive them. Then perform a shadow copy backup to the Storage Area Network.
B.
Perform full backups to tape on Saturday night and archive them. Perform differential backups to tape every Sunday through Friday night.
C.
Perform full backups to tape on Saturday night and archive them. Perform incremental backups to tape every Sunday through Friday night,
D.
Enable circular logging for the Exchange storage groups. Every night, perform shadow copy backups to the Storage Area Network and copy the shadow copy backups to tape. Archive the tapes.
Explanation:
Explanation 1:
Every night, perform full backups to tape and archive them.
Then perform a shadow copy backup to the Storage Area Network.
Meets Requirement 1 (Shadow copy will be consistent and transaction files will be backed up to recover even deleted items (dumpster transactions.
We can point at the consistent Shadow Copy and replay the logs to be back online in under one hour – we can recover deleted items).
Meets Requirement 2
Explanation 2:
They tell us there is 153 GB of available disk space on the Storage Area Network for Trey Research data. By default, when you
perform a backup in Windows Server 2003, the volume shadow copy method is used to create the backup. Shadow Copies and full
backups made every night and archived would allow us to meet the SLA requirements. However, the Exchange 2003 Writer supports
only a Full backup at the storage group (SG) level. VSS performs Exchange Full backups at the SG level, even though the Exchange
Writer treats individual databases as separate components. VSS uses the AddComponent call to add each database component to
the Shadow Copy set, which in the case of a Full backup, is the entire SG (i.e., databases or log files). In a Full backup of a SG, VSS
creates a complete Shadow Copy of all volumes�the Shadow Copy contains database and transaction log files associated with that
SG. In addition, as is the case with non-VSS Full backups, VSS truncates the transaction log files after successfully creating and
backing up the Shadow Copy. To truncate the transaction log files, the Shadow Copy set must include all databases Although VSS
backup for Exchange 2003 is at the SG level, you can recover individual databases from the SG Shadow Copy set. VSS-based
restoration of an Exchange 2003 SG is useful when data in one or more databases in the SG is lost or corrupted, but the current log
files remain intact on disk; when the current log files on disk are lost or corrupted, but the databases remain intact; or when
databases and current log files within an SG are lost or corrupted.
Incorrect Answers:
B. Perform full backups to tape on Saturday night and archieve them.
Perform differential backups to tape every Sunday through Friday night.
Meets Requirement 2
(The data will be backed up but the logs wont be truncated meaning 2 hours or more to recover).
C. Perform full backups to tape on Saturday night and archive them.
Perform incremental backups to tape every Sunday through Friday night.
Meets Requirement 2
D. Enable circular logging for te Exchange storage groups.
Every night, perform shadow copy backups to the Storage Area Network and copy the shadow copy backups to tape.
Archive the tapes.
Meets Requirement 1
(Shadow copy will be consistent and no transaction files to recover.
We can point at the consistent Shadow Copy and replay the logs to be back online in under one hour).
Wont meet requirement 2 since all transactions are committed to the database (including people emptying the dumpster) – this means that all email data is *NOT* kept
References:
Overview of Dependencies and Requirements for Exchange Server 2003 Features 822178 Exchange Server 2003 Data Back
Up and Volume Shadow Copy Services 822896