PowerProtect Data Manager 19.9 Microsoft Application Agent SQL Server User Guide

You can use the following optional parameters with the msagentrc.exe command.

-A "DM_USER=<PowerProtect_appliance_user>"

Specifies the username to use for the PowerProtect Data Manager connection.

This parameter is mandatory only for credential-based access to the PowerProtect Data Manager appliance. You are not required to specify this parameter when the Microsoft application agent is approved by PowerProtect Data Manager.

When you add a virtual machine to a protection policy, that virtual machine is approved with a certificate that expires after one day. The PowerProtect Data Manager administrator can approve the target Microsoft application agent on the PowerProtect Data Manager Infrastructure > Agents page.

-A "DM_LOG_LEVEL={WARNINGS | INFO | TRACE | DEBUG}"

Specifies the PowerProtect Data Manager log level, with WARNINGS providing the least amount of detail, and DEBUG providing the most amount of detail.

-A "DM_LOG_TAG=<PowerProtect_log_tag>"

Specifies the PowerProtect Data Manager log tag.

-A "ADDITIONAL_RESTORES={yes | no}"

Specifying yes disables the ability to roll back uncommitted transactions and uses the database to restore the latest or additional transaction logs. The default value is no.

-A "RENAME_TO=<new_database_name>"

Specifies the new name for the destination database. The selected database will be restored to the new database. The new name of the database must be a valid SQL database name. If the destination contains a database with the same name as the database that you have specified, the restore operation overwrites the existing database.

The database files that are data files (.mdf and .ndf) and log file (.ldf) will be restored to their source locations only. If the source database exists, its files can be in use. So, to avoid conflicts for using a new database name, use the -A RELOCATE_TO option along with the -A RENAME_TO option.

-A "INSTANCE_TO=<hostname>\<instance>"

Performs a redirected restore operation to a SQL Server instance that is different from the source instance where the backup was taken.

NOTE The target instance must reside on the same system where the restore operation is configured. You cannot restore the backup to an instance on a remote host.

-A "RELOCATE_TO='<source_file-1>'='destination_folder-1', '<source_file-2>'='destination_folder-2',[...]"

Performs redirected restores of the database files that are data files (.mdf and .ndf) and log file (.ldf). You can rename or change only the destination folders, but not the filenames.

Ensure that the destination paths are not root drives, for example, E:\.

-A "NSR_SQL_RECOVER_MODE=<alternate_location_path>"

Performs a redirected restore to the specified path.

-A "NSR_SQL_TARGET_DIR=<destination_folder_path>"

Specifies the destination path, to which you want to copy the restored files. You can then manually either move the files to the required folder or attach the files to a SQL Server instance.

Ensure that the destination path is not a root drive, for example, E:\.

-D <debug_level>

Generates detailed logs that you can use to troubleshoot the restore issues. The supported debug levels are 1 through 9.

-A "DELETE_DEBUG_LOG_DAYS=<number_of_days>"

Deletes debug log files that are older than the specified number of days. The valid range is between 1 and 32767. By default, debug logs are not deleted. Regularly deleting debug logs prevents the log folder on the installation drive from becoming too large.

NOTE This parameter only deletes debug logs named in the default format and located in the logs folder at <installation_path>\MSAPPAGENT\logs.