11.5 HP StoreVirtual Storage Release Notes

To prevent this issue from occurring, do the following:
1. Identify all the volumes that are included in this recovery plan. For each of these volumes:
a. Verify that the remote schedule is missing from the "new primary" group to the "new
remote" group. If this remote schedule exists, continue with step 2.
b. Find the paused remote schedule that is from the "old primary" group to the "old remote"
group.
If this schedule exists, note the following items:
◦ Retention count
◦ Occurrence rate
◦ Start time
If this schedule does not exist, find out the above information for the volume from the
customer.
2. Using the CMC, set up a remote schedule for this volume from the "new primary" group to
the "new remote" group.
◦ Choose a start time that matches the existing schedule start time but is in the future (for
example, tomorrow at 2:00:00 AM).
◦ Use the proper occurrence rate and retention count.
◦ Verify that the schedule did not run since the start time was set for the future.
◦ Create a snapshot for the "new remote volume" (must create snapshot due to volume
changing from primary to remote).
3. Change the "new remote volume" back to primary from remote.
4. Delete the snapshot that was created.
5. Repeat steps 1–4 until all volumes have been evaluated.
6. After all volumes have been evaluated, rerun the Reprotect operation.
The Reprotect operation will:
◦ Change the remote volumes from primary to remote.
◦ Identify the newly set up remote schedules.
◦ Perform a data sync from the "new primary" group to the "new remote" group.
The Reprotect operation should complete successfully.
VSA
• Upgrading ProLiant servers using the HP Customized ESXi image causes StoreVirtual VSA RDMs
to disappear
When upgrading an HP ProLiant server from vSphere 5.1 Update 1 (U1) to 5.1 Update 2 (U2)
using the HP Customized ESXi image, the upgrade process installs a new version of the hpsa
driver. The new driver enumerates LUNs differently than the previous driver, so the vmdk no longer
points to the correct raw device (RDM). This prevents the StoreVirtual VSA’s virtual machine (VM)
from starting, and an error message from ESXi displays, indicating that the VM could not start. If
all the VSAs in a cluster were hosted on the same server, then they would all be offline. This issue
will be fixed in a future version of the hpsa driver.
To resolve this issue, delete the existing RDMs and add them back in ESXi, as follows:
1. Using vSphere Client (or web client), select the ESX host’s Configuration tab and select
Advanced Settings in the Software section.
Workarounds 25