11.5 HP StoreVirtual Storage Release Notes

Snapshots
• An Active Directory user with read-only permissions can pass the Authentication Console credentials
test, but application-managed snapshots will fail
The Application Aware Snapshot Manager Authentication Console does not differentiate between
read-only users and those who have authorization to create snapshots. The LeftHand OS will deny
the Application Aware Snapshot Manager the right to create snapshots on behalf of a read-only
user; therefore, snapshots are not taken.
To resolve this issue, enter an Active Directory user with administrator capabilities into the
Authentication Console.
• Application-managed snapshots do not work on SMB file shares presented by a Windows Failover
Cluster
With Windows Server 2012, SQL Server is not quiesced when an application-managed snapshot
is taken on an SMB file share that is presented by a Windows Failover Cluster. The snapshot
appears as if it is a managed snapshot, but because SQL Server was not quiesced, it is not a true
managed snapshot.
SRA
• The Reprotect operation fails with an error message for cross-version management groups
An error prevents the Reprotect operation from creating remote schedules when running in a
mixed management group environment. This occurs when the remote group is running a later
version than the primary group and remote schedules have not been previously configured. In
this scenario, the Failover operation will fail with an error creating the remote schedule. To resolve
this issue, the following steps are provided to recover from the issue when it occurs and to prevent
the issue from occurring in the future.
To recover from this issue, 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 this 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.
3. Repeat these steps until all volumes have been evaluated.
4. After all volumes have been evaluated, rerun the Reprotect operation.
24 Workarounds