IBM System Storage requirements

If you use IBM System Storage DS8000® series, SAN Volume Controller, or Storwize® V7000 storage systems, be aware of database, log, file, and LUN settings.

Follow these guidelines when you plan for IBM® System Storage®:
  • Place database files for each database or group of databases that are going to be backed up and restored together as a unit on a separate and dedicated logical volume.
  • Place logs for each database or group of databases that are going to be backed up and restored together as a unit on a separate logical volume.
  • Do not place non-SQL data on storage volumes that are dedicated to SQL.
  • When you use hardware snapshot providers, ensure that the database LUNs are dedicated to only one database or application.
  • If you delete a local snapshot that is stored on a IBM SAN Volume Controller or IBM Storwize V7000 space-efficient volume (SEV) that has multiple dependent targets, delete the snapshots in the same order in which you created the snapshots. You must delete the oldest one first, followed by the second oldest.
  • In a IBM SAN Volume Controller or IBM Storwize V7000 environment, if you use multiple target FlashCopy® mappings, a mapping might stay in the copying state after all the source data is copied to the target. This situation can occur if mappings that started earlier and use the same source disk are not yet fully copied. In this instance, schedule local backups for IBM SAN Volume Controller and IBM Storwize V7000 storage systems at intervals that are greater than the time required for the background copy process to complete.