![Dell PowerVault DL4000 User Manual Download Page 73](http://html.mh-extra.com/html/dell/powervault-dl4000/powervault-dl4000_user-manual_85600073.webp)
5.
Use the drop-down menus to select the instance of SQL Server installed on the Core from the
following options:
You can choose from:
•
SQL Server 2005
•
SQL Server 2008
•
SQL Server 2008 R2
•
SQL Server 2012
•
SQL Server 2014
6.
Select the credential type.
You can choose from:
•
Windows
•
SQL
7.
Specify the credentials with administrative privileges for the Windows or SQL Server instances,
described as follows:
Text Box
Description
Username
Enter a user name for logon permissions to the SQL server.
Password
Enter a password for SQL attachability. It is used to control logon activity.
8.
Click
Test Connection
.
NOTE: If you entered the credentials incorrectly, a message is displayed to alert you that the
credentials test failed. Correct the credential information and run the connection test again.
9.
Click
Save
.
Attachability checks are now available to be run on the protected SQL Server databases.
10.
In the Nightly Jobs window, click
OK
.
Attachability checks are now schedule to occur with the nightly jobs.
Configuring nightly SQL attachability checks and log truncation
To configure nightly SQL attachability checks and log truncation:
1.
In the left navigation area of the Core, select the machine for which you want to have nightly
attachability checks and log truncation, and click
SQL Server Settings
.
2.
Navigate to the Core Console.
3.
Click
Configuration
→
Settings
.
4.
In the
Nightly Jobs
section, click
Change
.
5.
Select or clear the following SQL Server settings based on the needs of your organization:
•
Attachability Check Job
•
Log Truncation Job (simple recovery model only)
6.
Click
OK
.
The attachability and log truncation settings take effect for the protected SQL Server.
Managing exchange database mountability checks and
log truncation
When using AppAssure to back up Microsoft Exchange Servers, mountability checks can be performed on
all Exchange databases after every snapshot. This corruption detection feature alerts administrators of
73