SQL

You are backing up an entire machine with the Application-aware backup option enabled. You have selected SQL, Exchange, or both.

After some time, you change the password for the user that has been specified during activation of the feature.

The backup starts failing with the following error message:

Logging on with the specified credentials is impossible, probably because the account does not exist or the password is invalid.

Symptoms

The issue reproduces in the following conditions:

  1. Customer is using MS SQL for their Management Server instead of built-in SQLite,
  2. MS SQL is in any language besides English,
  3. Customer is using the same encryption password for multiple plans or the same location for multiple plans,

Protection plan cannot be saved, with an error similar to:

Symptoms

 

  1. You try to back up SQL databases: either by selecting databases directly or using disk-level backup with enabled Microsoft SQL Server application backup
  2. Backup fails with the following error:

    Backup failed.
    Failed to get additional information about file 'D:\MSSQL\03\Database1.mdf'.

After you have disabled SSL 3.0, TLS 1.0, TLS 1.1 and left only TLS 1.2 running on the machine, application-aware backup of an SQL server finishes with a warning:

Error code: 4358
Module: 87
LineInfo: 0xEC865955C73BB27A
Fields: {"$module":"aavb_mssql_backuper_vsa64_11010"}
Message: Failed to collect the metadata of the SQL Server databases selected for backup. The databases will not be backed up.

If you try to edit of specify credentials for an SQL server user, you get these errors:

Cannot collect the metadata of Microsoft SQL Server
The specified user is not a member of the sysadmin role in SQL Server instance 'Instance_name'.
Cannot collect the metadata of Microsoft SQL Server
Cannot back up the SQL Server instances due to environment issues.

Symptoms

  • You are backing up a Hyper-V virtual machine in agentless mode,
  • Backup fails with the following error:

    Unexpected call result. Error code 32768

  1. Acronis Backup 12.5 または Acronis Cyber Cloud を使用しています。
  2. Microsoft SQL データベースのバックアップを実行します。
  3. 以下のエラーが表示され、バックアップに失敗します:

 

「Problems detected that may cause a VSS snapshot failure. Trailing spaces in the path. To remove the trailing spaces, run the T-SQL command: ALTER DATABASE MODIFY FILE」

  1. You use Acronis Backup 12.5 or Acronis Cyber Cloud
  2. You run a backup of a Microsoft SQL database
  3. Backup fails with the following error:

Problems detected that may cause a VSS snapshot failure. Trailing spaces in the path. To remove the trailing spaces, run the T-SQL command: ALTER DATABASE MODIFY FILE

Table of trial limitations of Acronis products

Symptoms

The SQL database transaction logs are not decreasing in size after being truncated via Application-Aware backup, even though MMS logs show truncation was performed:

2021-10-10T18:54:18:107-05:00 16136 I00000000: service_process(14868): TruncateLogOf: Local881 start

2021-10-10T18:54:18:248-05:00 16136 I00000000: service_process(14868): TruncateLogOf: Local881 done

Cause

The transaction logs do not reduce in size during truncation, as the truncated space is not deallocated.

Acronis Recovery for MS SQL Server のインストール方法

この資料は、以下の製品に該当します。

  • Acronis Recovery for MS SQL Server

はじめに

Acronis Recovery for MS SQL Server エージェントはローカルでもリモートでもインストールできます。Acronis Recovery for MS SQL Server エージェントをデータベースサーバーにリモートでインストールするには、最初に、Acronis Recovery for MS SQL Server 管理コンソールをローカルのコンピュータにインストールする必要があります。

解決法

最初に、Acronis Recovery for MS SQL Server 管理コンソールをインストールします。このコンポーネントでは、リモートの SQL サーバーにあるデータのバックアップ管理および復元を一元的に実行できます。

ページ