Core Generates ‘Log Truncation Has Been Skipped’ Errors after Nightly Jobs Are Performed (4036142)

Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Core Generates ‘Log Truncation Has Been Skipped’ Errors after Nightly Jobs Are Performed
Description

After every nightly jobs, the Core generates the alert below:
“The log truncation for the protected machine “xxxxxx’ on volumes ‘(Volume Labeled ‘System Reserved’); C:\; D:\’ has been skipped, because there aren’t any Exchange or SQL databases in protection group”
Cause

CAUSE 1:
The drives, which contain the SQL/Exchange Databases and Logs files, are in separate protection schedule groups.

CAUSE 2:
The credentials have not been set for SQL/Exchange servers on the Core console yet.
Resolution
SOLUTION 1:
Configure one protection group for volumes which contain Exchange or SQL databases and logs files.
For more information regarding protection schedule groups, please refer to:
- Rapid Recovery 6 - Understanding Protection Schedule.
SOLUTION 2:
Set credentials for Exchange or SQL databases:
- Setting credentials for an Exchange server machine
In order to set login credentials, an Exchange server must be present on a protected volume. If Rapid Recovery does not detect the presence of an Exchange server, the Set Credentials function does not appear in the Core Console.
Once you protect data on a Microsoft Exchange server, you can set login credentials in the Rapid Recovery Core Console.
Complete the steps in this procedure to set credentials for each Exchange Server.
1. In the left navigation area of the Rapid Recovery Core Console, select the protected Exchange server machine for which you want to set credentials.
  The Summary page appears for the protected Exchange server.
2. On the Summary page, from the links at the top of the page, click the downward-facing arrow to the right of the Exchange menu, and then from the resulting drop-down menu, select Set Credentials.
  The Edit Exchange Credentials dialog box for the protected Exchange server appears.
3. In the Edit Exchange Credentials dialog box, enter your credentials as follows:
  In the User name text field, enter the user name for a user with permissions to the Exchange server; for example, Administrator (or, if the machine is in a domain, [domain name]\Administrator).
  In the Password text field, enter the password associated with user name you specified to connect to the Exchange server.
  Click OK to confirm the settings and close the dialog box.
- Setting credentials for a SQL Server machine
You can set login credentials for a single instance, or for all SQL Servers, in the Rapid Recovery Core Console. Complete the steps in this procedure to set credentials for each SQL Server.
1. In the left navigation area of the Rapid Recovery Core Console, select the protected SQL Server machine for which you want set credentials.
  The Summary page displays for the protected SQL Server.
2. On the Summary page, from the links at the top of the page, click the downward-facing arrow to the right of the SQL menu, and then from the resulting drop-down menu, do one of the following:
  If you want to set default credentials for all SQL Server database instances, click Set Default Credentials for All Instances, and in the Edit Default Credentials dialog box, do the following:
  In the User name text field, enter the user name for a user with permissions to all associated SQL servers; for example, Administrator (or, if the machine is in a domain, [domain name]\Administrator).
  In the Password text field, enter the password associated with the user name you specified to connect to the SQL server.
  Click OK to confirm the settings and close the dialog box.
  If you want to set credentials for a single SQL Server database instance, click the display name of the protected SQL Server machine, and then in the Edit Instance Credentials dialog box, do the following:
  Select the credential type (Default, Windows, or SQL)
  In the User name text field, enter the user name for a user with permissions to the SQL server; for example, Administrator (or, if the machine is in a domain, [domain name]\Administrator).
  In the Password text field, enter the password associated with the user name you specified to connect to the SQL server.
  Click OK to confirm the settings and close the dialog box.
VN:F [1.9.20_1166]

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Request a KB Article

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

Core Generates ‘Log Truncation Has Been Skipped’ Errors after Nightly Jobs Are Performed (4036142)

Title

Description

Cause

CAUSE 1:

CAUSE 2:

Resolution

SOLUTION 2:

Leave a Comment