Replay Manager Version 8.0 Administrator’s Guide

PDF

Troubleshooting Table

Use the following table to help troubleshoot issues with Replay Manager.

Table 1. Troubleshooting ProblemsTable of problems and solutions
Problem	Solution
Backup set name is different in Storage Center than in Replay Manager	Names are truncated to 31 characters in Storage Center. For more information, see User-Defined Name in Summary of Backup Set Options .
Connection failure	Check the firewall setting. This scenario is the most likely cause of the connection failure. Open port 27444. Configure the HTTP Proxy server using the Bypass proxy server for local addresses option. For more information, see: Configure an HTTP Proxy Service Inbound Ports in Replay Manager Ports
Connection failure that is related to installation of RMS	Install the Replay Manager Service on all servers. Open port 27444 on all servers. For more information, see Inbound Ports in Replay Manager Ports.
Scheduled backup did not run	Replay Manager queues a maximum of one scheduled job per backup set. Click Job Queue to ensure that the job is in the queue waiting to run. For more information, see: Guidelines for Backup Jobs View Queued Items
Connection to server fails	Install the Replay Manager Service on all servers. Open port 27444 on all servers. For more information, see: Install Replay Manager Service for Windows Inbound Ports in Replay Manager Ports
Data disappears after restoring a Replay	The Restore action restores data to its original location, overwriting the current data. To avoid losing current data, take a Replay immediately before using Restore or use Expose (rather than Restore) and manually merge the Exposed data with the existing data. For more information, see: Restore Data to Its Original Location Expose a Restore Point (Windows Extensions Only) Expose a Restore Point (VMware Only) Expose a Restore Point on an SMB File Share
Email notifications not working	Verify SMTP settings. Adjust spam settings on email server and/or client.
Hyper-V/VMware backup fails	In a clustered server environment, ensure that the VM owner and disk owner match.
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 Ensure that 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, see: 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 steps 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 ESXi is configured with default timeout values in some configurations or setup.	To decrease the time of the query operation, you can disable the file system liveness check. Log in to your host as root. 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. Add the checkLiveFSUnresolvedVolume parameter and set its value to FALSE. Use the following syntax: <checkLiveFSUnresolvedVolume>FALSE</checkLiveFSUnresolvedVolume> 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 time on the server . 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, see: 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, see 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, see 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, see Replay Manager Service for Windows.
Failed or missing VSS Writers	Restart the correct service for the missing VSS Writer. To view the current VSS Writers, open an elevated command prompt and run vssadmin list writers. These services might require an outage: For Exchange Server: Restart Microsoft Exchange Information Store (MSExchangeIS) For Hyper-V: Restart Hyper-V Virtual Machine Management (vmms) For SQL Server: Restart SQL Server VSS Writer (SQLWriter)
Dell Storage folder appears empty on Windows Server 2016	After installation of Replay Manager on Windows 2016, a Dell Storage folder is added to the list of Windows Apps. However, the folder might be empty, even though it should include all installed Replay Manager components. The installed Replay Manager components are shown in the Recently Added Apps list and can selected from there. There is no user workaround for this issue. Within one to two days, the Replay Manager components should be in the Dell Storage folder.