HP 4400 HP StorageWorks 4400 Enterprise Virtual Array getting started guide (5 - Page 20

Q: How do I schedule and perform nightly backups? A: The EVA is supported by numerous backup applications. Through these applications, schedule regular backups and be sure to test the restore process twice a year. For additional information, see the HP StorageWorks Enterprise Backup Solutions (EBS) website: http://h18006.www1.hp.com/products/storageworks/ebs/index.html. Q: Should I save my array configuration? How often should I save my configuration? How? A: Yes. Along data backups, be sure to save a copy of EVA confi guration files. Configuration file backups should made whenever changes are made to the configuration (new hosts, new virtual disks, hardware changes) and should be stored on media not associated with the array. Configuration file backups aid in diagnosing any EVA issues that occur, and is usually requested when an escalation to HP services results. HP Command View EVA includes HP Storage System Scripting Utility software (SSSU), a powerful scripting utility. You can use the capture configuration command to save your array configuration. For additional information, see the HP StorageWorks Storage System Scripting Utility reference. Q: What is the difference between a snapclone and snapshot? A: Snapclones and snapshots complement a backup strategy that includes full copies to offline or near-line storage. Using HP Business Copy EVA and HP Replication Solutions Manager functionality, snapclones and snapshots provide alternatives for reducing recovery time by providing the first option for recovery in case of a disk write error, corrupted file, or program malfunction. Snapclones and snapshots are easy to use and integrate well into typical data center processes. A snapclone is an independent, point-in-time copy of a virtual disk. It is independent because all of the data from the source virtual disk is copied to the snapclone. Use snapclones when you need independent and durable copies; for example, for data mining, data warehousing, or preproduction testing. A snapshot is a dependent, point-in-time copy of a virtual disk. It is dependent because data is copied to the snapshot only when it is entered or overwritten on the source. Use snapshots when you need temporary copies; for example, to create a copy of a database that you then store on tape. For additional information, see the HP StorageWorks Business Copy EVA administrator guide. Q: What should (or shouldn't) FATA drives be used for? A: Fibre Attached Technology Adapted (FATA) disks are low-cost, low-performance disks supported for use in the EVA. Because of the design of these disks, HP recommends using FATA drives for low-duty cycle workloads and are not meant for continuous access or where random access performance is required. Do not use these drives as a replacement for EVA's high performance, standard-duty cycle, Fibre Channel drives. The best application for FATA disks is to augment near-line storage usage for the online part of your backup and recovery solution. Snapclones assigned to FATA disk groups provide the lowest cost solution for zero-downtime backup and fast recovery storage. (FATA disks and snap copies are not a replacement for offline backup.) Please note that EVA requires that FATA disks be organized in separate disk groups. Q: What are the best practices for zoning between hosts and the arrays? A: Zoning by operating system, HBA, application, or port are all supported zoning methods. The following zoning rules apply to heterogeneous SANs with EVA storage systems: • Each operating system type must be in a separate zone or virtual SAN (VSAN). • The HP Command View EVA management server should be zoned to include only the EVA systems that it is intended to manage. • EVA storage systems can be in multiple operating system zones. 20 Frequently asked questions