vSphere Storage - ESXi 5.0 - Documentation - VMware
vSphere Storage - ESXi 5.0 - Documentation - VMware
vSphere Storage - ESXi 5.0 - Documentation - VMware
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>vSphere</strong> <strong>Storage</strong><br />
Third-Party Management Applications<br />
You can use third-party management applications in conjunction with your <strong>ESXi</strong> host.<br />
Most SAN hardware is packaged with storage management software. In many cases, this software is a web<br />
application that can be used with any web browser connected to your network. In other cases, this software<br />
typically runs on the storage system or on a single server, independent of the servers that use the SAN for<br />
storage.<br />
Use this third-party management software for the following tasks:<br />
n <strong>Storage</strong> array management, including LUN creation, array cache management, LUN mapping, and LUN<br />
security.<br />
n Setting up replication, check points, snapshots, or mirroring.<br />
If you decide to run the SAN management software on a virtual machine, you gain the benefits of running a<br />
virtual machine, including failover using vMotion and <strong>VMware</strong> HA. Because of the additional level of<br />
indirection, however, the management software might not be able to see the SAN. In this case, you can use an<br />
RDM.<br />
NOTE Whether a virtual machine can run management software successfully depends on the particular storage<br />
system.<br />
SAN <strong>Storage</strong> Backup Considerations<br />
Having a proper backup strategy is one of the most important aspects of SAN management. In the SAN<br />
environment, backups have two goals. The first goal is to archive online data to offline media. This process is<br />
repeated periodically for all online data on a time schedule. The second goal is to provide access to offline data<br />
for recovery from a problem. For example, database recovery often requires retrieval of archived log files that<br />
are not currently online.<br />
Scheduling a backup depends on a number of factors:<br />
n Identification of critical applications that require more frequent backup cycles within a given period of<br />
time.<br />
n Recovery point and recovery time goals. Consider how precise your recovery point needs to be, and how<br />
long you are willing to wait for it.<br />
n The rate of change (RoC) associated with the data. For example, if you are using<br />
synchronous/asynchronous replication, the RoC affects the amount of bandwidth required between the<br />
primary and secondary storage devices.<br />
n Overall impact on SAN environment, storage performance (while backing up), and other applications.<br />
n Identification of peak traffic periods on the SAN (backups scheduled during those peak periods can slow<br />
the applications and the backup process).<br />
n Time to schedule all backups within the datacenter.<br />
n Time it takes to back up an individual application.<br />
n Resource availability for archiving data; usually offline media access (tape).<br />
Include a recovery-time objective for each application when you design your backup strategy. That is, consider<br />
the time and resources necessary to perform a backup. For example, if a scheduled backup stores so much data<br />
that recovery requires a considerable amount of time, examine the scheduled backup. Perform the backup<br />
more frequently, so that less data is backed up at a time and the recovery time decreases.<br />
28 <strong>VMware</strong>, Inc.