HP P6000 Replication Solutions Manager User Guide (T3680-96089, October 2012)

Scheduled job event run times are wrong (AM/PM)
Problem
Symptoms that can indicate this problem:
• When using the Schedule a Job wizard, a time of day entered as PM appears as AM on the
final page.
• A scheduled job runs at an unexpected time.
Explanation / resolution
This can occur due to a non-English setting on a Windows-based storage management server. A
non-English setting changes the time entered in the Schedule a Job wizard to an AM time. For
example, a time entered in the wizard as 2:00 PM is saved as 2:00 AM. For more information
on jobs, see the HP P6000 Replication Solutions Manager Job Command Reference.
To correct this problem, perform the following procedure. You must be a member of the server's
Administrators group.
CAUTION: Performing this procedure requires a reboot.
1. Coordinate reboot activities to avoid disruption of services to others. Ensure that no replication
manager jobs are running or are scheduled to run during the reboot.
2. On the Window-based storage management server, select Start > Control Panel > Regional
and Language Options > Advanced tab.
3. On the Advanced tab, under Standards and formats, select English (United States).
4. Click OK and follow the Windows on-screen instructions.
5. When prompted, reboot the computer. Click Yes to complete the change to Windows.
6. In the replication manager, edit any scheduled job events that had incorrect run times.
7. If you have previously exported the replication manager database (that included incorrect
times), HP recommends that you perform a new export.
Second snapclone of the same storage volume or host volume fails
Problem
The second snapclone of the same storage volume or host volume fails and the replication manager
logs a message such as:
Copy type CLONE not available or no resource bundle
Explanation / resolution
You can make multiple snapclones of a source volume. However, only one snapclone can be in
the normalization (unsharing) phase at one time. If the second snapclone action is started too soon,
the action can fail.
This issue can occur when:
• You run and then quickly rerun the same job.
• The replication manager database was not refreshed after the first snapclone was completed.
When the second snapclone is requested, the replication manager encounters the out-of-date
normalization status in the database and fails the requested snapclone action.
To resolve this issue:
• Allow sufficient time after between snapclones to allow the unsharing process to complete.
• Allow sufficient time between snapclones to allow the replication manager database to be
refreshed.
Troubleshooting 37