Scenario: Backup using BRMS

Sharon's backup plan for JKL took into account each server's purpose, workload, and availability requirements.

She also planned carefully for how the media used for each backup would be moved to and from offsite locations. Her strategy is reflected in the following diagram of JKL's network. Click on a server to see Sharon's backup strategy for it:

Once Sharon established the backup strategy for each server (JKLPROD, JKLDEV, and JKLINT), she needed to decide how often the media from those backups would be rotated and moved to an offsite location for safekeeping.

• JKLDEV backup strategy
  JKLDEV is JKL's development system and does not require continuous availability. It is used primarily during the week and during the day, although there is some development activity into the evening hours and on weekends.
• JKLPROD backup strategy
  JKLPROD is the system that JKL uses for all of their customer orders and where their business applications are installed (inventory control, customer orders, contracts and pricing, accounts receivable).
• JKLINT backup strategy
  JKLINT is the system that JKL uses for their website and e-mail. While this data is critical to their business, it is fairly static-- they don't make a lot of changes to the user profiles or configuration data on the system.