Filter
Top Products
Troubleshooting
Troubleshooting Backup and Restore Sessions
Chapter 12586
reset by peer. It is possible that some parallel restore sessions are
completed without errors, while other restore sessions are not even
started.
Action A workaround for this problem is to set the SmMaxAgentStartupRetries
global variable in the Data Protector global options file (located in
/etc/opt/omni/options/global) to 2 or more (max. 50). This variable
specifies the maximum number of retries for the session manager to
restart the failed agent before it fails. Refer to “Global Options File” on
page 523 for more information about the Data Protector global options
file.
Backup Protection Expiration
When scheduling backups, you have set the same protection period for
full and incremental backups, which means that incremental backups
are protected for the same duration as the relevant full backup. The
consequence of this is that your data will actually only be protected until
the full backup expires. You cannot restore incremental backups that
have been based on expired full backups.
Action Configure the protection for your full backups so that they are protected
for longer than your incremental backups.
The time difference between the protection for the full backup and the
incremental backup should be the amount of time between the full
backup and the last incremental backup before the next full backup. For
example, if you run incremental backups Monday through Friday and
full backups on Saturday, you should set the protection of the full backup
to at least 6 days more than for the incremental backups. This will keep
your full backup protected and available until your last incremental
backup expires.
Troubleshooting Application Database Restores
A poorly-configured DNS environment could cause problems with
database applications. If you try to restore a database and it fails with
the message Cannot connect to target database or Cannot create
restore set, the problem is as follows:
When backing up the database on a system, the agent that starts on the
system logs the system’s name to the database as
<system.company.com>. The Restore Session Manager wants to restore