Dell Appassure 5 User Guide

							Dell AppAssure User Guide
Version 5.4.3 Revision B69 Trace logs Trace log settings can be configured to record a significantly higher amount of events 
and states in the AppAssure Core than standard logs. This functionality is specifically 
intended to be used for problem resolution only. 
NOTE: Dell does not recommend changing these settings unless requested by Dell 
Support. Maintaining a high level of logging for a long period can significantly impact 
storage space and may impact performance.
Cloud configuration The Cloud Configuration settings let you specify configuration settings for various 
cloud storage accounts, including Microsoft Azure, Amazon S3, and managed cloud 
providers using OpenStack open source technology. These settings do not create cloud 
accounts. Instead, they associate your existing cloud accounts with your AppAssure 
Core to facilitate actions such as archiving AppAssure information.
For more information about managing cloud storage account information in the 
AppAssure Core, see Managing cloud accounts.
Licensing From the Core console, AppAssure lets you change the license associated with your 
Core, view license pool information, and contact the license server.
For more information about managing licenses from the Core, see Managing licenses.
For more information about managing licenses, see the Dell AppAssure License Portal 
Guide.
NOTE: The Dell AppAssure License Portal has a different release cycle than AppAssure 
software. For the latest product documentation, see the Dell Technical Documentation 
website.
Core settings backup 
and restoreAppAssure lets you back up Core configuration settings to an XML file. If you have a 
backup file, you can use it to restore or migrate Core settings.
For more information about backing up and restoring Core settings, see Backing up and 
restoring Core settings.
Jobs Core jobs are automatically created whenever you initiate operations such as 
replication. The Job Settings section of the Configuration tab lets you determine the 
settings for each job.
You can configure the number of jobs to execute at one time. In case network or other 
communication errors prevent any job from succeeding the first time, you can set how 
many times a job should be attempted.
For more information about Core jobs, which jobs are available, and how to configure 
them, see Configuring Core job settings.
Diagnostics (Core 
Logs)For diagnosing possible issues, you can download and view logs for your AppAssure 
Core, or you can upload logs for your Core an any protected machines. These features 
are available from the Tools menu.
For information about downloading or uploading logs, see Accessing diagnostics for the 
Core. Table 34. AppAssure Core configurable settings
Configuration Setting Description 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B70 Local database AppAssure displays information about Core tasks, events, and alerts on the 
Events tab. AppAssure stores this transactional information in a MongoDB service 
database that is installed locally on the same machine as the AppAssure Core.
You can configure credential information (username and password) for the local 
Mongo service database using the Local database settings.
SNMP configuration Simple Network Management Protocol (SNMP) is a protocol for managing devices 
on an IP network. SNMP is used primarily to monitor devices on a network for 
conditions that require attention. This protocol uses software components 
(agents) to report information to administrative computers (managers). An SNMP 
agent handles the managers requests to get or set certain parameters. The SNMP 
agent can also sends traps (notifications about specific events) to the manager). 
Data objects managed by SNMP agents are organized into a Management 
Information Base (MIB) that contains Object Identifiers (OIDs). Each OID 
identifies a variable that can be read or set using SNMP.
You can configure the AppAssure Core as an SNMP agent. The Core then can 
report information such as alerts, repository status, and protected machines. 
This information can be read by an SNMP host using a standalone application 
called an SNMP browser.
You can install the SNMP browser on any machine accessible over the network to 
the AppAssure Core. Use the SNMP settings to control communication between 
the Core and the SNMP browser.
You can also download a MIB file from the AppAssure Core. From the Tools tab, 
select Downloads and download the MIB from the Other Files pane. This file can 
be read by an SNMP browser in a more user-friendly fashion than data it receives 
directly from the Core.
Reports Report settings include a single configuration parameter that allows you to select 
the font used when a report is generated from the  
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B71
Understanding system information
AppAssure lets you view information about the AppAssure Core that includes system information, local and 
mounted volumes, and Replay engine connections.
In the System Info pane, you can see the information described in the following table.
The Volumes pane includes the following information about storage volumes for the Core machine: Name, 
device ID, file system, raw capacity, formatted capacity, used capacity, and mount points.
The Replay Engine Connections pane displays detailed information about currently mounted recovery points. 
You can view the ID, local end point, remote end point, mounted image agent ID, mounted image ID, and the 
mounted image display name. You can see if the mount is writable, view the authenticated user, bytes read, and 
bytes written.
You can dismount recovery points that are mounted locally on a core from the Mount option on the Tools tab. 
For more information about dismounting recovery points, see Dismounting recovery points.
Viewing system information
Complete the steps in this procedure to view system information.
To view system information
1 Navigate to the AppAssure Core, and then select the Tools tab.
2 From the Tools option, click System Info. Table 35. System information
UI Element Description
Host name The machine name of your AppAssure core.
OS version The version of the operating system installed on the AppAssure core.
OS architecture Lists the underlying structure and design of the machine hosting your AppAssure 
core. Potentially includes chipset and lists 64-bit system.
Memory (physical) Lists the amount of Random Access Memory installed on the Core machine.
Display name Shows the display name of the Core, which is configurable (see Understanding 
system information).
Fully qualified 
domain nameShows the fully qualified domain name for the Core machine.
Metadata cache 
locationShows the path of the metadata cache location. For more information, see 
Understanding deduplication cache size and storage locations.
Primary cache 
locationShows the path of the primary deduplication cache location. For more 
information, see Understanding deduplication cache size and storage locations.
Secondary cache 
locationShows the path of the secondary deduplication cache location. For more 
information, see Understanding deduplication cache size and storage locations. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B72
Configuring the Core general settings
Complete the steps in this procedure to update the general settings for the AppAssure Core, which include the 
Core display name, the web server port, service port, and the display language for the AppAssure Core.
To configure the Core general settings
1 Navigate to the AppAssure Core Console and click the Configuration tab, and then Settings.
The General Settings dialog box appears.
2 In the General pane, click Change.
The General Settings dialog box displays.
3 Enter the configuration information as described in the following table.
4Click OK.
5 If changing the languages, confirm the message indicating that the AppAssure Core service must restart 
before the updated language can display in the Core Console.
Configuring update settings
AppAssure includes the Automatic Update feature. When installing the AppAssure Core, you can choose whether 
to automatically update the AppAssure Core software when new updates are available, and how frequently the 
system should check for updates.
You can view and change the settings the system uses to check for updates at any time.
Complete the steps in this procedure to configure update settings.
To configure update settings
1 Navigate to the AppAssure Core Console and click the Configuration tab, and then Settings. Table 36. General Settings information
Te x t  B o x D e s c r i p t i o n
Display name Enter a new display name for the Core. This is the name that will 
display in the AppAssure Core Console. You can enter up to 64 
characters.
Web server port Enter a port number for the Web server. The default port is 8006.
Service port Enter a port number for the AppAssure Core service. The default 
port is 8006.
Language From the Language drop-down list, select the language you want to 
display.
International versions of AppAssure support English, French, 
German, Japanese, Korean, Portuguese, Simplified Chinese, and 
Spanish.
NOTE: For information on installing AppAssure Core software, see the Dell AppAssure Installation and 
Upgrade Guide.
CAUTION: When using replication, configuring your system to install updates automatically could 
result in upgrading the source core before the target core, which may result in replication failure or 
the inability to set up new replication between cores. For replication users, Dell recommends 
administrators apply automatic upgrades only to the target core, and then manually upgrade the 
source core, and lastly upgrade the protected machines. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B73 2 In the Updates pane, click Change.
The Update Settings dialog box displays.
3 In the Check for new updates text box, select how frequently AppAssure checks for and installs updates 
after the nightly jobs are complete. You may choose from the following options:
•Never
•Daily
•Weekl y
•Monthly
4 Specify the handling of available updates by choosing one of the following options:
• Install them automatically (recommended) or
• Notify me but do not install them
5Click OK.
Understanding nightly jobs
Nightly jobs are daily automated tasks that occur at a predetermined time outside of normal business hours. 
These jobs are memory-intensive, and include various integrity checks and data consolidation tasks that are 
best conducted when the AppAssure Core is less active.
Nightly jobs can be managed at the Core level, or for each protected machine. All of the nightly jobs, and the 
scope for which they can be applied, are described in the following table.
Table 37. Nightly jobs
Job Name Scope Description
Attachability check Protected 
MachineChecks the integrity of recovery points containing SQL databases. 
Pr oce s s:
•Mount the latest recovery point for protection groups 
containing databases.
•Connect to the database from SQL Server.
•Open the database.
•Close the database.
•Dismount the recovery point.
To enable this nightly check, specify a SQL Server instance to use 
to perform attachability checks for SQL Server databases on 
protected machines.
NOTE: This option does not appear if you are not protecting a SQL 
Server in your Core.
Check recovery 
points integrityCore or 
Pr ote ct ed  
MachineChecks the integrity of recovery points for each protected 
machine. By default, the Check recovery points integrity option is 
not enabled.
Pr oce s s:
•Mount the latest recovery point for every protection group.
•Enumerate the files and folders for each volume.
•Examines the recovery points to ensure that they are valid.
•Dismount the recovery point. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B74 The following procedures apply only to the Core-level nightly jobs. For more information about nightly jobs 
specific to protected machines, see Customizing nightly jobs for a protected machine.
Configuring nightly jobs for the Core
When any nightly job option is enabled on the AppAssure Core, the selected job executes once daily at the time 
specified for all machines that are protected by the Core. 
Conversely, if you disable any nightly job at the Core level, the specified job no longer executes for all machines 
protected by the Core.
Because nightly jobs are memory-intensive, Dell recommends configuring your Core to execute them during a 
time of low activity. The default schedule to run nightly jobs is 12:00 am. If another time is more suitable, 
change this setting in the Nightly Jobs Time field using this procedure.
To configure nightly jobs for the Core
1 Navigate to the AppAssure Core Console and click the Configuration tab, and then Settings.
2 In the Nightly Jobs pane, click Change.
The Nightly Jobs dialog box displays.
3 If you want to change the time nightly jobs execute, enter a new time in the Nightly Job Times text box. Checksum check Protected 
MachineChecks the integrity of recovery points containing Exchange 
Message Databases (MDBs).
NOTE: This option does not appear if you are not protecting an 
Exchange Server in your Core.
Deleting old events 
and jobsCore Maintains the scale of the events database by removing old events. 
The number of days is configurable, defaulting to 30 days.
Downloading the 
logs from the 
protected machinesCore Downloads logs for protected machines to the Core, so they can be 
sent to the logging server.
Log repository 
statisticsCore Sends repository statistics to the logging server.
Rollup Core Maintains the retention policy by combining backup images. The 
retention policy is defined on a per-Core basis, but can be 
overridden per protected machine. The rollup job is run for the 
whole Core.
Log truncation Protected 
MachineMaintains the size of SQL Server logs by truncating the database 
transaction log to match the last recovery point.
NOTE: This option does not appear if you are not protecting a SQL 
Server in your Core.
Tr u n c a t e  E x c h a n g e  
logsPr ote ct ed  
MachineMaintains the size of Exchange logs, by truncating the exchange 
database transaction log to match the last recovery point.
NOTE: This option does not appear if you are not protecting an 
Exchange Server in your Core.
NOTE: If the scope of a nightly job includes protected machines, you can apply that nightly job only for 
specific protected machines individually. The scope for each nightly job is described in the topic 
Understanding nightly jobs. For more information about applying nightly job settings specific to a 
protected machine, see Customizing nightly jobs for a protected machine.  Table 37. Nightly jobs
Job Name Scope Description 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B75 4 Select the nightly jobs option you want to set for the Core. You can choose to select all or individually 
select only those that apply.
5Click OK.
Modifying transfer queue settings
Transfer queue settings are core-level settings that establish the maximum number of concurrent transfers and 
the maximum number of retries for transferring data.
Complete the steps in this procedure to modify transfer queue settings.
To modify the transfer queue settings
1 Navigate to the AppAssure Core Console and click the Configuration tab, and then Settings.
2 In the Transfer Queue pane, click Change.
The Transfer Queue dialog box displays.
3 In the Maximum Concurrent Transfers text box, enter a value to update the number of concurrent 
transfers.
Set a number from 1 to 60. The smaller the number, the lesser the load on network and other system 
resources. As the number of agents that are processed increases, so does the load on the system.
4 In the Maximum Retries text box, enter a value to update the maximum number of retries.
5Click OK.
Adjusting client timeout settings
Client timeout settings control the length of time that various operations are attempted before the operation 
times out.
These settings let you configure the parameters described in the following table.
Complete the steps in this procedure to adjust client timeout settings.
NOTE: Dell recommends leaving default timeout settings unless you experience specific issues in your 
environment, and you are advised by a Dell Support representative to modify the settings.
Table 38. Timeout settings
Setting Description
Connection Timeout Controls the timeout for the connection between the Core and 
protected machines when sending data across the hypertext 
transfer protocol (http).
Read/Write Timeout Controls the timeout for the connection between the Core and 
protected machines when reading or writing stream data across 
http. An example is receiving changed data blocks from a protected 
machine to the Core for an incremental snapshot.
Connection UI Timeout Controls the timeout for the connection between the graphic user 
interface and the Core service across http.
Read/Write UI Timeout Controls the timeout for the connection for reading and writing 
data streams between the graphic user interface and the Core 
service across http. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B76
To adjust client timeout settings
1 Navigate to the AppAssure Core Console and click the Configuration tab, and then Settings.
2 In the Client Timeout Settings Configuration area, click Change.
The Client Timeout Settings dialog box displays.
3 In the Connection Timeout text box, enter the number of minutes and seconds before a connection time 
out occurs.
4 In the Connection UI Timeout text box, enter the number of minutes and seconds before a connection UI 
time out occurs.
5 In the Read/Write Timeout text box, enter the number of minutes and seconds you want to lapse before 
a time out occurs during a read/write event.
6 In the Read/Write UI Timeout text box, enter the number of minutes and seconds that will to lapse 
before a read/write UI time out occurs.
7Click OK.
Understanding deduplication cache size and 
storage locations
Global deduplication reduces the amount of disk storage space required for your backed up data. The AppAssure 
deduplication volume manager (DVM) combines a set of storage locations into a single repository. Each 
repository is deduplicated, storing each unique block once physically on disk, and using virtual references or 
pointers to those blocks in subsequent backups. To identify duplicate blocks, AppAssure includes a deduplication 
cache that holds references to unique blocks.
By default, this deduplication cache is 1.5 GB in size. This is a sufficient size for many repositories. Until this 
cache is exceeded, your data is deduplicated across the repository. Should the amount of redundant information 
be so large that the deduplication cache is full, your repository can no longer take full advantage of further 
deduplication across your repository for newly added data. The amount of data saved in your repository before 
the deduplication cache is full varies by the type of data being backed up and is different for every user. 
You can increase the size of the deduplication cache by changing the deduplication cache configuration in the 
AppAssure Core. For more information on how to accomplish this, see the topic Configuring deduplication cache 
settings.
When you increase the deduplication cache size, there are two factors to consider: disk space and RAM usage. 
Disk space. Two copies of the cache are stored on disk: a primary cache, and a secondary cache which is a 
parallel copy. So with a default cache size of 1.5 GB, 3 GB of disk storage is used in your system. As you increase 
the cache size, the amount of disk space used remains proportionally twice the size of the cache. To ensure 
proper and fault-resistent performance, the Core dynamically changes the priority of these caches. Both are 
required, the only difference being that the cache designated as primary is saved first.
RAM usage. When the AppAssure Core starts, it loads the deduplication cache to RAM. Memory usage for your 
system is therefore affected by the size of the cache. The total amount of RAM used by the Core depends on 
many factors including which operations are running, the number of users, the number of agents, as well as the 
size of the deduplication cache. Each operation performed by Core (transfer, replication, rollup, and so on) 
consumes more RAM. Once an operation is finished, memory consumption decreases accordingly. However, 
administrators should consider the highest RAM load requirement for efficient operations. 
Default settings for the AppAssure Core place the primary cache, secondary cache, and the metadata cache in 
the AppRecovery directory used by AppAssure. 
NOTE: Depending on your settings, the AppRecovery directory may not be visible on the AppAssure Core. 
To see this directory, you may need to change the Folder Options control panel to show hidden files, 
folders, and drives. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B77 Assuming the AppAssure Core is installed on the C drive, these locations are typically as follows:
You have the ability to change the storage location of these caches. For example, for increased fault tolerance, 
you can change location of your secondary cache to a different physical drive than the primary, assuming the 
AppAssure Core has access to the location. 
For more information on how to change storage locations for any of these settings, see the topic Configuring 
deduplication cache settings.
Configuring deduplication cache settings
Complete the steps in this procedure to configure deduplication cache settings.
To configure deduplication cache settings
1 Navigate to the AppAssure Core Console and click the Configuration tab, and then Settings.
2 In the Deduplication Cache Configuration pane, click Change.
The Deduplication Cache Configuration dialog box displays for you to specify the cache storage locations 
and cache size.
Since the primary and secondary cache are the same size, collective storage for these two caches 
requires twice the amount of space as the amount allocated for the deduplication cache size. For 
example, if you specify the default amount of 1.5 GB for the deduplication cache size, you will need to 
ensure that each of the two storage locations have at least 1.5 GB. In particular, if both locations belong 
to the same drive (for example, the C drive), there must be at least 3.0 GB of free disk space.
3 If you want to change the primary cache location, then in the Primary Cache Location text box, type the 
path for a storage location accessible to the Core.
4 If you want to change the secondary cache location, then in the Secondary Cache Location text box, type 
the path for a storage location accessible to the Core.
5 If you want to change the metadata cache location, then in the Metadata Cache Location text box, type 
the path for a storage location accessible to the Core.
6 If you want to change the deduplication cache size, then do the following:
a In the Dedupe Cache Size text box, enter a value corresponding to the amount of space you want 
to allocate for the deduplication cache.
For example, if you want to increase the deduplication cache size to 3 GB, enter 3 in this field.
b From the unit size drop-down field, select either GB (gigabytes) or TB (terabytes), as 
appropriate, to specify the unit of measurement for the value in the Dedupe Cache Size text box.
7Click OK. Table 39. Default storage locations for deduplication cache settings
Setting Default Storage Location
Primary Cache Location C:\ProgramData\AppRecovery\RepositoryMetaData\PrimaryCache
Secondary Cache Location C:\ProgramData\AppRecovery\RepositoryMetaData\SecondaryCache
Metadata Cache Location C:\ProgramData\AppRecovery\RepositoryMetaData\CacheMetadata
NOTE: The minimum cache size setting is 1.5 GB. Additionally, the cache size cannot exceed 50 
percent of the installed RAM.
NOTE: You must restart the AppAssure Core service for the changes to take effect. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B78
Configuring Replay engine settings
You can configure information regarding the Replay engine, which is the communication channel for AppAssure. 
These settings determine Core settings to provide effective communication.
In general, Dell recommends using default settings. In some cases, you may be directed by Dell Support to 
modify these settings to help adjust the performance specific to your network needs.
Complete the steps in this procedure to configure Replay engine settings.
To configure Replay engine settings
1 Navigate to the AppAssure Core Console and click the Configuration tab, and then Settings.
2 In the Replay Engine Configuration pane, click Change.
The Replay Engine Configuration dialog box displays.
3 Enter the configuration information as described in the following table.
4Click OK.
The Replay Engine Configuration dialog box closes, and your new job settings are applied. Table 40. Replay engine settings
Te x t  B o x D e s c r i p t i o n
IP Address Specify the IP address by choosing one of the following:
•Click Automatically Determined to use the preferred IP 
address from your TCP/IP.
•Or, click Use a specific address to manually enter an IP 
address.
Preferable Port Enter a port number or accept the default setting. The default port 
is 8007.
The port is used to specify the communication channel for the 
Replay engine.
 Port in use Represents the port that is in use for the Replay engine 
configuration.
Allow port auto-assigning Click for allow for automatic TCP port assignment.
Admin  Group Enter a new name for the administration group. The default name is 
BUILTIN\Administrators.
Minimum Async I/O Length Enter a value or choose the default setting. It describes the 
minimum asynchronous input/output length.
The default setting is 65536.
Receive Buffer Size Enter an inbound buffer size or accept the default setting. The 
default setting is 8192.
Send Buffer Size Enter an outbound buffer size or accept the default setting. The 
default setting is 8192.
Read Timeout Enter a read timeout value or choose the default setting. The 
default setting is 00:05:00.
Write Timeout Enter a write timeout value or choose the default setting. The 
default setting is 00:05:00.
No Delay It is recommended that you leave this check box unchecked as 
doing otherwise will impact network efficiency. If you determine 
that you need to modify this setting, contact Dell Support for 
guidance in doing so.