HP0-J67 · Question #134
Refer to the scenario. A large publicity-traded motion picture exhibitor that is a leader In digital and 3D cinema deployments orepates 233 theaters and more than 2,200 screens in small to mid…
The correct answer is C. 4. The incomplete question seems to implicitly ask about the effective recovery point objective (RPO) or delay for the weekly full backup data once it arrives at the disaster recovery site. Considering the 72-hour backup duration and an assumed one-day transport time, the data…
Question
Refer to the scenario. A large publicity-traded motion picture exhibitor that is a leader In digital and 3D cinema deployments orepates 233 theaters and more than 2,200 screens in small to mid- sized communities in 35 states around United States. They rely on MS Exchange Server 2010 for email, MS SQL. Server 2010 for analyzing data about movies and theater-goers, and MS Excel 2010 for crunching numbers. The company runs nightly incremental backups and a full weekly backup that consists of close to 7TB of data which takes up 72 hours to complete. The quarterly backups add an additional 7 TB of data. Tapes are inventoried and transported from the main data center to the disaster recovery site 150 miles away. The process of transporting tape cartridges to and from the Disaster Recovery site requires hours of dally work. The company currently relies on an aging robotic tape library and a process that takes the nightly backup tapes of site every morning. Additionally, the company keeps an inventory, and if a restore is necessary,they have to retrieve the tapes from the DR site and transport them to the main data center site. They have a 7 year data retention plan, and the tapes are expensive and not always reliable. Given the company's current system, if a full weekly backup fails over a weekend, the re-run could take up to 10 hours, even if just one job failed. The company has deployed an virtualized server infrascructure which runs VmWare VSphere 5 on HP Bladesystem c7000 enclosures and BL46Oc servers interconnected with HP virtual Connect Flex-10 10Gb Ethernet modules as well as several HP ProLiant DL380 servers. The company top four IT improvements goal are as follows:
- replacing the aging robotic tape library
- enabling replication of backed up data from the main data center to
the disasterrecovery site (150miles)
- retaining more backup data in smaller disk space -increasing
efficiency, reliabillity and ease of System administration Moreover the company's top thee business benefit goals are as follows:
- increased confidence in disaster recovery
- Minimal disruption by backup during regular business hours
- inproved management of external audits
The company has asked that you create multiple solution proposals and prioritize one when you return for a presentation. During a design workshop. you become aware that the customer also has a number of application serves to be included in the backup environment. What is the minimum number of stores you need to create in order to achieve optimal deduplication performance?
Options
- A1
- B3
- C4
- D8
How the community answered
(62 responses)- A3% (2)
- B11% (7)
- C79% (49)
- D6% (4)
Why each option
The incomplete question seems to implicitly ask about the effective recovery point objective (RPO) or delay for the weekly full backup data once it arrives at the disaster recovery site. Considering the 72-hour backup duration and an assumed one-day transport time, the data effectively becomes four days old by the time it is available offsite.
1 day would only account for transport or a very short backup, not the full 72-hour backup duration.
3 days only accounts for the backup completion time, neglecting the additional time required for physical tape transport to the DR site.
If the question implies calculating the effective time until the full weekly backup data is available at the DR site, the 72-hour backup completion time (3 days) combined with a reasonable estimation of one day for tape transport totals 4 days. This cumulative delay represents the maximum age of the recoverable data at the DR site for a full weekly backup, influencing the RPO.
8 days is an overly extended duration that is not supported by the given 72-hour backup time and typical transport expectations.
Concept tested: Disaster recovery metrics, RPO calculation, tape backup limitations
Topics
Community Discussion
No community discussion yet for this question.