Dell Appassure 5 User Guide

							Dell AppAssure User Guide
Version 5.4.3 Revision B119 cIn the Location field, enter a directory path for the repository. For example, on a local computer, 
type C:\Repository. This location must be unique for this core. If storing your repository on a 
shared drive, enter in format \\servername\sharename.
d If storing the repository on a shared volume, in the User Name field, enter the user name with 
privileges to access the shared drive, and in the Password field, enter the password for this user.
eIn the Metadata path field, enter the path where you want metadata to be stored. This should be 
a subdirectory of the storage location. For example, if the storage location is C:\Repository, type 
C:\Repository\Metadata. This must be a unique path for this core.
15 When you have entered all required data for the Repository page, click Next.
The Repository Configuration page appears.
16 Specify the size of the repository.
17 To specify bytes per sector, bytes per record, or control the write caching policy, select Show advanced 
options, and then enter details for the storage location as described in the following table.
18 When you are satisfied with the repository configuration information you entered, click Next.
The Encryption page appears.
CAUTION: If you delete your repository in the future, the Installer program will remove the entire 
contents of the repository path. For this reason, do not create the storage location at the root (for 
example, c:\), which could result in losing all data stored on that volume.
NOTE: If the storage location is a New Technology File System (NTFS) volume using Windows XP or 
Windows 7, the file size limit is 16 TB.

If the storage location is a NTFS volume using Windows 8, 8.1 or Windows Server 2012, 2012 R2, the 
file size limit is 256 TB.

For AppAssure to validate the operating system, Windows Management Instrumentation (WMI) must 
be installed on the intended storage location.
Table 55. Advanced options for storage
Te x t  B o x D e s c r i p t i o n
Bytes per Sector Specify the number of bytes you want each sector to include. The 
default value is 512.
Bytes per Record Specify the average number of bytes per record. The default value is 
8192.
Write Caching Policy The write caching policy controls how the Windows Cache Manager is 
used in the repository and helps to tune the repository for optimal 
performance on different configurations.
Set the value to one of the following:
•On
•Off
•Sync
If set to On, which is the default, Windows controls the caching.
NOTE: Setting the write caching policy to On could result in faster 
performance. If you are using a version of Windows Server prior to Server 
2012, the recommended setting is Off.
If set to Off, AppAssure controls the caching.
If set to Sync, Windows controls the caching as well as the synchronous 
input/output. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B120 19 Optionally, to enable encryption, on the Encryption page, select Enable Encryption.
Encryption key fields appear on the Encryption page.
20 If you want to encrypt these protected machines using an encryption key that is already defined on this 
AppAssure Core, select Encrypt data using an existing Encryption key, and select the appropriate key 
from the drop-down menu.
Proceed to Step 22.
21 If you want to add a new encryption key to the Core and apply that key to these protected machines, 
then enter the information as described in the following table.
22 Click Finish to save and apply your settings.
The wizard closes. The AppAssure Agent software is deployed to the specified machines, if necessary, 
and the machines are added to protection on the Core.
Monitoring the protection of multiple machines
You can monitor the progress as AppAssure applies the protection polices and schedules to the machines.
To monitor the protection of multiple machines
•In the AppAssure Core Console, navigate to the AppAssure Home tab and then click the Events tab.
The Events tab displays, broken down by Tasks, Alerts, and Events. As volumes are transferred, the 
status, start times, and end times display in the Tasks pane.
NOTE: If you enable encryption, it will be applied to data for all protected volumes for the 
machines you have specified for protection. You can change the settings later from the 
Configuration tab in the AppAssure Core Console. For more information about encryption see, 
Understanding encryption keys.
CAUTION: AppAssure uses AES 256-bit encryption in the Cipher Block Chaining (CBC) mode with 256-
bit keys. While using encryption is optional, Dell highly recommends that you establish an encryption 
key, and that you protect the passphrase you define. Store the passphrase in a secure location as it is 
critical for data recovery. Without a passphrase, data recovery is not possible.
Table 56. Encryption key settings
Te x t  B o x D e s c r i p t i o n
Name Enter a name for the encryption key.
Encryption key names must contain between 1 and 130 alphanumeric 
characters. You may not include special characters such as the back slash, 
forward slash, pipe, colon, asterisk, quotation mark, question mark, open or 
close brackets, ampersand or hash.
Description Enter a comment for the encryption key.
This information appears in the Description field when viewing encryption 
keys from the Core Console.
Passphrase Enter the passphrase used to control access.
Best practice is to avoid special characters listed above.
Record the passphrase in a secure location. Dell Support cannot recover a 
passphrase. Once you create an encryption key and apply it to one or more 
protected machines, you cannot recover data if you lose the passphrase.
Confirm Passphrase Re-enter the passphrase you just entered. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B121 You can also filter tasks by status (active, waiting, completed and failed). For more information, see 
Viewing tasks.
As each protected machine is added, an alert is logged, which lists whether the operation was successful 
or if errors were logged. For more information, see Viewing alerts.
For information on viewing all events, see Viewing all events.
NOTE: To only see tasks that are waiting to be performed, make sure that you select the Waiting 
Ta s k s  i c o n . 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B
7
122
Managing Microsoft Exchange and SQL 
Servers
This chapter describes how to configure, and manage the protection of Microsoft Exchange and SQL Servers in 
your AppAssure environment. It includes the following sections:
•Configuring Exchange and SQL Server settings
•Managing SQL attachability and log truncation
•Managing Exchange database mountability checks and log truncation
Options specific to Exchange Server and SQL Server appear in the AppAssure Core Console when an instance of 
the software and associated databases are detected on protected servers. This section includes the following 
topics specific to managing protected machines that use Exchange Server or SQL Server:
This section includes the following topics:
•Modifying Exchange Server settings
•Forcing a mountability check of an Exchange database
•Forcing a checksum check of Exchange Server recovery points
•Modifying SQL Server settings
•Forcing a SQL Server attachability check
•Forcing log truncation for a SQL machine
When you protect SQL Servers and Exchange Servers, there are functions specific to these server types that you 
can perform. These include:
• Forcing server log truncation. Both SQL Servers and Exchange Servers include server logs. The process 
for truncating SQL logs identifies available space on the server. When you truncate Exchange server logs, 
in addition to identifying the available space, the process frees up more space on the server. For 
information on forcing log truncation, see Forcing log truncation for a SQL machine.
• Setting credentials for the relevant server. Exchange servers allow you to set credentials for the 
protected machine in the Summary tab for the protected server. SQL Servers allow you to set credentials 
for a single protected SQL server machine, or to set default credentials for all protected SQL Servers.
•For information on setting credentials for Exchange servers, see Setting credentials for an 
Exchange Server machine.
•For information on setting credentials for SQL servers, see Setting credentials for a SQL Server 
machine.
•For information on performing other actions accessible to all protected agents from the agent 
Summary tab, see Viewing the Summary tab. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B123
Configuring Exchange and SQL Server 
settings
If you protect data on Exchange servers or SQL servers on your AppAssure Core, you can establish credentials so 
the Core can authenticate to those machines. Navigate to the protected server in the AppAssure Core console to 
configure these server settings, as described in the following topics.
Setting credentials for an Exchange Server machine
Once you protect data on a Microsoft Exchange server, you can set login credentials in the AppAssure Core 
Console.
To set credentials for an Exchange Server machine
1 Once you have added the Exchange Server machine for protection, navigate to the AppAssure Core 
Console and select the machine in the Navigation pane.
The Summary tab displays for the machine.
2 From the Summary tab, in the Actions drop-down menu, click Exchange, and from the context-sensitive 
drop-down menu, select the action you want to perform.
3 To set credentials for a single Exchange server, click Set Credentials, and in the Edit Exchange 
Credentials dialog box, do the following:
a 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).
b In the Password text field, enter the password associated with user name you specified to 
connect to the Exchange server.
cClick OK to confirm the settings and close the dialog box.
Setting credentials for a SQL Server machine
Once you protect data on a SQL Exchange server, you can set login credentials in the AppAssure Core Console.
To set credentials for a SQL server machine
1 Once you have added the SQL Server machine for protection, from the AppAssure Core Console, select 
the machine in the Navigation pane.
The Summary tab displays for the machine.
2 From the Summary tab, in the Actions drop-down menu, click, and from the context-sensitive drop-
down menu, select the action you want to perform.
•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:
a 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).
b In the Password text field, enter the password associated with user name you specified to 
connect to the SQL server.
cClick OK to confirm the settings and close the dialog box. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B124 •If you want to set credentials for a single SQL Server database instance, click Set Instance 
Credentials, and in the Edit Instance Credentials dialog box, do the following:
a Select the credential type (Default, Windows, or SQL)
b 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).
c In the Password text field, enter the password associated with user name you specified to 
connect to the SQL server.
dClick OK to confirm the settings and close the dialog box.
Understanding recovery point status indicators
Once a recovery point is created on a protected SQL or Exchange server, the application displays a 
corresponding color status indicator in the Recovery Points table. The color that displays is based on the check 
settings for the protected machine and the success or failure of those checks, as described in the following 
Recovery Status Point Colors for SQL Databases and Recovery Status Point colors for Exchange Database tables.
Recovery status point colors for SQL databases
The following table lists the status indicators that display for SQL databases.
Recovery status point colors for Exchange databases
The following table lists the status indicators that display for Exchange databases.
NOTE: For more information on viewing Recovery Points, see Viewing recovery points.
Table 57. SQL database status indicators
Status Color Description
White Indicates that one of the following conditions exist:
•An SQL database did not exist,
•Attachability checks were not enabled, or
•Attachability checks have not yet been run.
Yellow Indicates that the SQL database was offline and a check was not possible.
Red Indicates that the attachability check failed.
Green Indicates that the attachability check passed.
Table 58. Exchange database status indicators
Status Color Description
White Indicates that one of the following conditions exist:
•An Exchange database did not exist, or
•Mountability checks were not enabled.
NOTE: This can apply to certain volumes within a recovery point.
Yellow Indicates that the Exchange database mountability checks are enabled, but the 
checks have not yet been run.
Red Indicates that either the mountability or checksum checks failed on at least one 
database.
Green Indicates that the mountability check passed or that the checksum check passed.  
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B125
Modifying Exchange Server settings
If you are protecting data from a Microsoft Exchange server, you need to configure additional settings in the 
AppAssure Core Console.
To modify Exchange Server settings
1 Once you have added the Exchange Server machine for protection, navigate to the AppAssure Core 
Console and select the machine in the Navigation pane.
The Summary tab displays for the machine.
2 From the Summary tab, in the Actions drop-down menu, click Exchange, and from the context-sensitive 
drop-down menu, select the action you want to perform.
•If you want to truncate Exchange server logs, click Force Log Truncation.
•If you want to set credentials for a single Exchange server, click Set Credentials, and in the Edit 
Exchange Credentials dialog box, do the following:
a 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).
b In the Password text field, enter the password associated with user name you specified to 
connect to the Exchange server.
cClick OK to confirm the settings and close the dialog box.
Modifying SQL Server settings
If you are protecting data from Microsoft SQL Server, there are additional settings you need to configure in the 
AppAssure Core Console.
To modify SQL Server settings
1 Once you have added the SQL Server machine for protection, from the AppAssure Core Console, select 
the machine in the Navigation pane.
The Summary tab displays for the machine.
2 From the Summary tab, in the Actions drop-down menu, click, and from the context-sensitive drop-
down menu, select the action you want to perform.
•If you want to truncate SQL or Exchange server logs, click Force Log Truncation.
•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:
a 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).
b In the Password text field, enter the password associated with user name you specified to 
connect to the SQL server.ke as described in the following table.
cClick OK to confirm the settings and close the dialog box.
•If you want to set credentials for a single SQL Server database instance, click Set Instance 
Credentials, and in the Edit Instance Credentials dialog box, do the following:
NOTE: Recovery points that do not have an Exchange or SQL database associated with it will appear with 
a white status indicator. In situations where both an Exchange and SQL database exists for the recovery 
point, the most severe status indicator displays for the recovery point. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B126 a Select the credential type (Default, Windows, or SQL)
b 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).
c In the Password text field, enter the password associated with user name you specified to 
connect to the SQL server.
dClick OK to confirm the settings and close the dialog box.
Managing SQL attachability and log 
truncation
The SQL attachability configuration enables the AppAssure Core to attach SQL database and log files in a 
snapshot of a SQL server using a local instance of Microsoft SQL Server. The attachability test lets the Core 
check for the consistency of the SQL databases and ensures that all data files (MDF and LDF files) are available 
in the backup snapshot. Attachability checks can be run on demand for specific recovery points or as part of a 
nightly job.
Attachability requires a local instance of Microsoft SQL Server on the AppAssure Core machine. This instance 
must be a fully licensed version of SQL Server procured from Microsoft or through a licensed reseller. Microsoft 
does not allow the use of passive SQL licenses.
Attachability supports SQL Server 2005, 2008, 2008 R2, 2012, and 2014. The account used to perform the test 
must be granted the sysadmin role on the SQL Server instance.
The SQL Server on-disk storage format is the same in both 64-bit and 32-bit environments and attachability 
works across both versions. A database that is detached from a server instance that is running in one 
environment can be attached on a server instance that runs in another environment.
Log truncation identifies the free space available in the SQL database logs, but does not minimize them. You 
can schedule log truncation to occur with the nightly jobs, or you can force it on demand. To force log 
truncation, see Forcing log truncation for a SQL machine.
This section includes the following topics:
•Configuring SQL attachability settings
•Configuring nightly SQL attachability checks and log truncation for all protected machines
For more information about managing protected machines that use SQL Server, see Modifying SQL Server 
settings or Customizing nightly jobs for a protected machine.
Configuring SQL attachability settings
Prior to running attachability checks on protected SQL databases, you must first select a local instance of SQL 
Server on the Core machine that will be used to perform the checks against the agent machine.
Complete the steps in this procedure to configure SQL attachability settings.
To configure SQL attachability settings
1 Navigate to the AppAssure Core, and then click the Configuration tab.
NOTE: The version of SQL Server on the Core must be equal to or newer than the SQL Server version on all 
of the agent machines with SQL Server installed.
NOTE: Attachability requires a local instance of Microsoft SQL Server on the AppAssure Core machine. This 
instance must be a fully licensed version of SQL Server procured from Microsoft or through a licensed 
reseller. Microsoft does not allow the use of passive SQL licenses. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B127 2Click Settings.
3 In the Nightly Jobs pane, click change.
The Nightly Jobs dialog box appears.
4Select Attachability Check Job and then click Settings.
The Configuration dialog box appears, letting you choose the local SQL Server instance to use for 
performing attachability checks for the protected SQL Server databases.
5 Use the drop-down menus to select the instance of SQL Server installed on the Core from the following 
options:
•SQL Server 2005
•SQL Server 2008
•SQL Server 2008 R2
•SQL Server 2012
•SQL Server 2014
6 Select the credential type. You can select from:
•Windows, or
•SQL
7 Specify the credentials with administrative privileges for the Windows or SQL Server instances, as 
described in the following table.
8Click Test Connection.
9Click 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 for all protected machines
You can view, enable, or disable SQL database server settings, including attachability check and nightly log 
truncation from the Nightly Jobs dialog box accessed from the Core. Changes made here apply to all SQL 
machines protected by the Core.
Complete the steps in this procedure to have the system perform nightly attachability checks for the SQL Server 
recovery points.
NOTE: The options that appear in this drop-down list are populated based on the local SQL 
Server instances in your environment. 
Table 59. SQL Server administrator credentials
Te x t  B o x D e s c r i p t i o n
User Name 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.
NOTE: If you entered the credentials incorrectly, a message displays to alert you that the 
credentials test failed. Correct the credential information and run the connection test again. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B128
To configure nightly SQL attachability checks and log truncation
1 Navigate to the AppAssure Core, and then click the Configuration tab.
2Click Settings.
3 In the Nightly Jobs section, click Change.
4 Select or clear the SQL Server settings based on the needs of your organization:
•Attachability Check Job
•Log Truncation Job (simple recovery model only)
5Click OK.
The attachability and log truncation settings take effect for the protected SQL Server.
Forcing a SQL Server attachability check
Complete the steps in this procedure to force the system to perform an attachability check for a specific SQL 
server recovery point.
To force a SQL Server attachability check
1 In the left navigation area of the AppAssure Core, select the machine for which you want to force the 
attachability check and click the Recovery Points tab.
2 Click the right angle bracket > symbol next to a recovery point in the list to expand the view.
3Click Check, and then click Force Attachability Check.
The Force Attachability Check window appears for you to indicate that you want to force an 
attachability check.
4Click Ye s.
The system performs the attachability check.
Forcing log truncation for a SQL machine
Log truncation is available for machines that use SQL Server. Complete the steps in this procedure to force log 
truncation.
To force log truncation for a SQL machine
1 On the AppAssure Core Console, navigate to the protected machine for which you want to force log 
truncation.
•From the Summary tab of the protected machine, click the Actions drop-down menu, select SQL, 
and then click Fo rc e L o g Tru nc a ti on.
2Click Ye s to confirm that you want to force log truncation.
NOTE: To have the ability to force an attachability check, a SQL database must be present on a protected 
volume. If AppAssure does not detect the presence of a database, the attachability check function does 
not appear in the Core Console.
NOTE: For information on how to view the status of the attachability checks, see Viewing tasks, 
alerts, and events.
NOTE: When conducted for a SQL machine, truncation identifies the free space on a disk, but does not 
reduce the size of the logs.