Administrator Guide

Problem Solution
Partial Replays created—
Microsoft and VMware
environments
If components are moved after configuring a backup set, only the components in the original locations
get backed up. To correct, move components back to their original locations or create a backup set
with the new locations.
Paths are truncated/different in
SQL Server
This scenario is a known issue with SQL Server Management Studio (SSMS) data files. The full path is
displayed for data and log files.
Backup failure Storage Center Issues
• Make sure LUNs are available—transportable snapshots might not be expiring.
• Expected behavior with Microsoft Exchange if the component is not a Storage Center volume.
• For more information:
○ Add or Modify Storage Centers for a Server or Host
○ Run Exchange Verification in Summary of Backup Set Options
Extension-specific Issues
Sometimes when a Replay is taken during the time a primary controller fails over to the secondary
controller, the Replay fails. Furthermore, the Microsoft VSS writer may be left in a bad state causing
all future Replays to fail. In this case, bring the primary controller back online and follow the
troubleshooting step for failed or missing VSS Writers.
When you expose a Restore
point of a Datastore, the Restore
operations fail with the following
error:
Failed to locate VMFS volume
for snapshotThis issue may
occur when ESX is configured
with default timeout values in
some configurations or setup.
To decrease the time of the query operation, you can disable the filesystem liveness check.
1. Log in to your host as root.
2. Open the configuration file for hostd using a text editor.
The configuration file is located in /etc/vmware/hostd/config.xml under plugins/
hostsvc/storage node.
3. Add the checkLiveFSUnresolvedVolume parameter and set its value to FALSE. Use the
following syntax:
<checkLiveFSUnresolvedVolume>FALSE</checkLiveFSUnresolvedVolume>
4. As an alternative, you can set the ESXi Advanced option VMFS.UnresolvedVolumeLiveCheck to
FALSE in the vSphere Client.
Scheduled backup occurs at an
unexpected time
Verify Current Server Time in the Modify Backup Schedule dialog box. Replay Manager takes a
Replay by using the server's time. If Replay Manager Explorer is installed on a different computer, with
different time zone, it runs on server time.
Replay Manager can only run one backup job at a time. If there are many jobs waiting in the queue, the
scheduled backup is delayed.
For more information:
• Modify Schedules for an Existing Backup Set
• Guidelines for Backup Jobs
Exchange transaction logs are
truncated or missing
Expected behavior when VSS full backup is selected.
For more information:
VSS full backup on Summary of Backup Set Options
Unable to create an overnight
schedule
Use the Exclude Time Range option for the day hours—for example, 8:00 a.m. – 5:00 p.m..
For more information:
Modify Settings for an Existing Backup Set
Scheduled backup did not
happen after volume was failed
over
Confirm that the Replay Manager Service is installed on the owner node, and that the Replay
Manager Service is running as a user with proper privileges.
For more information:
Replay Manager Service for Windows
66 Troubleshooting