High Availability Review (T/F)

(answers at bottom)

 

  1. If mirrored, a failover will occur if principal database is corrupt
  2. With the use of mount points one can have up to 50 instances in a cluster
  3. Mirroring is synchronized Log Shipping
  4. In place upgrade is supported from 32-bit to 64-bit
  5. Snapshot database can be restored on top of principal database
  6. Endpoints are a must for mirroring to work
  7. Forced service failover guarantees no data loss
  1. If database is set in single user mode then mirroring will be suspended
  2. Mirroring uses similar concepts as ‘looks alive’ and ‘is alive’ in clustering
  3. In mirroring, a failover will occur if database is corrupt
  4. ‘Full safety’ in mirroring means possible data loss
  5. Mount points are supported in mirroring
  6. Snapshot databases are designed primarily for turning a mirrored database in to a reporting database
  7. Synchronous mode is optimal for mirroring as it guarantees no data loss and has no impact on application performance though log writes to mirror are delayed
  1. Snapshot database creation requires same amount of disk space as the primary database
  2. One bit map manages all snapshots on a single instance
  3. Snapshot created on a mirrored database will need to be recreated if mirror assumes principal role
  4. Multiple snapshots can be created on a single database
  5. Snapshot databases are still functional even though principal is suspect
  6. You can perform regular TLog backups on a snapshot database

 

Answer Key:  1.T, 2.F, 3.F, 4.F. 5.T, 6.T, 7.F, 8.F, 9.T, 10.T, 11.F, 12.T, 13.F, 14.F, 15.F, 16.F, 17.F, 18.T, 19.T, 20.F