Search results matching tag 'Backup Exec'

The BackupExec backup analysis fails

Sergey Vartanov — Mon, 16 Nov 2009 10:02:47 GMT

Issue

The BackupExec backup analysis fails.

Cause

The invalid Media Server SQL Instance name is specified in the Settings.py file located in the INSTALLDIR\BackupExec folder.
This results into errors like "An error occured while establishing connection..."

Resolution

Specify valid Media Server SQL Instance in the configuration.

Cause

The recovery job fails with Error message: "Restore job failed. For more information see restore job details". The job details on the BackupExec server contain the following description: "Access denied to Remote Agent". The job fails despite the fact that the service account has been added to the local administrators group on the machine where the database is restored.

This happens because "System Logon Account" is used by the BackupExec recovery job. This account may not have required permissions to complete this operation.

Resolution

The are two possible solutions here:

Grant "System Logon Account" required permissions (local administrator on the server where the database is being restored)
Provide the RM service account (or any other account that is granted required permissions) to the recovery job. To complete this task:

run the bemcmd command line utility from the Recovery Manager installation directory with the following arguments: bemcmd.exe -v -c:BackupExecServerName -o211 where BackupExecServerName is a actual name of the BackupExec server.
Browse the output and copy the ACCOUNT ID of the required account.
Update the ScriptFile.py file located in the INSTALLDIR\BackupExec by replacing SQL_REDIRECT_SERVER_ACCOUNT and SQL_REDIRECT_ACCOUNT values with the identifier collected on the previous step.

The Backup Exec backups are not discovered

Sergey Vartanov — Mon, 09 Nov 2009 09:16:58 GMT

Issue

The Backup Exec backups are not discovered when the whole SQL Server is backed up.

Reason

Recovery Manager 3.1.2 does not support full SQL Server backup jobs (the selection list has *.* selection): content databases have to be explicitly specified in the backup job selection list.

The backup list is obtained using BackupExec command line API. The object filtering was done by comparing the object name with the content database name, while the SQL Server backup object name equals to '*.*', thus the comparison failed.

Resolution

Selection lists in the resource selection dialog can be created without any limitations in Recovery Manager 3.2. The full SQL server backup (with database excludes if needed) or individual content databases backups are supported.

The Backup Exec backups are not discovered.

Sergey Vartanov — Mon, 26 Oct 2009 09:21:02 GMT

Issue

The Backup Exec backups are not discovered. It can result from two issues:

Reason

Microsoft SharePoint server farm agent is used to protect SharePoint content databases.

Resolution

Recovery Manager 3.1 does not support it for a while. It is recommend to use the Backup Exec SQL backup.

Reason

Content databases are not explicitly specified in the backup job selection list. Recovery Manager 3.1 does not support full SQL Server backup jobs (the selection list has *.* selection)

Resolution

Modify the selection list by selecting the required content databases in the resource selection dialog.