Backup set name is different in Storage Center than in Replay Manager
|
Names are truncated to 31 characters in Storage Center.
For more information:
User-Defined Name in Summary of Backup Set Options
|
Connection to RMS fails
|
Configure the HTTP Proxy server using the
Bypass proxy server for local addresses option.
For more information:
Configure an HTTP Proxy Service
|
Queue stops accepting jobs
|
Replay Manager queues a maximum of 10 jobs at a time. Verify that this limit has not been exceeded by viewing the Queued Items.
For more information:
|
Connection to server fails
|
- Install the Replay Manager Service on all servers
- Open port 27444 on all servers
For more information:
|
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 prior to using
Restore or use
Expose (rather than
Restore) and manually merge the Exposed data with the existing data.
For more information:
|
Email notifications not working
|
- Verify SMTP settings
- Adjust spam settings on email server and/or client
|
Exchange generates errors
|
Expected behavior in Exchange 2007 Server if VSS full backup is not selected.
For more information:
VSS full backup in Summary of Backup Set Options
|
Hyper-V/VMware Replay fails
|
In a clustered server environment, make sure 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 new backup set with the new locations.
|
Paths are truncated/different in SQL Server
|
This is a known issue with SQL Server Management Studio (SSMS) data files. The full path is displayed for data and log files.
|
Replays fail
|
- 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:
|
Replays fail in a Microsoft VSS environment
|
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 restart MS Information Exchange services (requires an outage).
|
In VMware environment, Replays fail when VSS writers time out and/or cannot quiesce snapshot
|
In a VMware environment, Replays fail when VSS writers time out and/or cannot create a quiesced snapshot.
|
Scheduled backup occurs at an unexpected time
|
Verify
Current Server Time in the Modify Backup Schedule dialog box.
For more information:
Modify Schedules for an Existing Backup Set
|
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
|
Create an Exclude Time Range for the day hours (for example, 8:00 a.m. – 5:00 p.m.).
For more information:
Modify Settings for an Existing Backup Set
|