Dell Appassure 5 User Guide

							Dell AppAssure User Guide
Version 5.4.3 Revision B59 The Repositories screen displays to include the newly added storage location.
5 Optionally, repeat Step 3 through Step 6 to add additional storage locations for the repository.
6Click OK.
Checking a repository
AppAssure provides the ability to perform a diagnostic check of a repository volume when errors occur. Core 
errors could be the result of it being improperly shut down, a hardware failure, or other environmental, lower 
IP stack factors that can be exposed in AppAssure functionality.
To check a repository
1 Click the Settings icon next to the Compression Ratio column below the Actions button, and then Check.
The Check Repository dialog box appears.
2 In the Check Repository dialog box, click Check.
Deleting a repository
Complete the steps in this procedure to delete a repository.
To delete a repository
1 Click the Settings icon next to the Compression Ratio column below the Actions button, and then Delete.
2 In the Delete Repository dialog box, click Delete.
A warning message appears to confirm deletion.
3Click Ye s to confirm the deletion of the repository.
About the repository Integrity Check job
In previous releases, replication included the process of copying recovery points from the source core to the 
target core on a regular basis. Rollup of aging recovery points occurred only at the source core. Combined older 
recovery points were synchronized daily when running the nightly job.
Starting with version 5.4.1, AppAssure includes the ability to set disparate retention policies between source 
and target cores, providing the source and target cores are the same version (5.4.1 or later).This allows 
AppAssure administrators to configure rollup on a target core at a different (presumably faster) rate than on the 
source core. Similarly, you can now define a custom retention policy for any replicated agent, rolling up 
recovery points at a faster rate and with less granularity in the target core than on the source core, saving 
space. For more information, see Customizing retention policy settings for a protected machine.
Some customers have experienced inconsistencies in recovery points that were replicated to a target core prior 
to AppAssure release 5.3.6. To address this issue, AppAssure release 5.4.1 and later includes a new Integrity 
NOTE: This procedure should only be performed for diagnostic purposes; for example, in the event of 
hardware failure, improper shutdown of the Core, failure when importing a repository, and so on.
NOTE: When you perform a check, all active tasks associated with this repository will be cancelled. 
Before you the check begins, a message asking you to acknowledge proceeding with the check will 
display. It is advised and encouraged to rebuild recovery points cache at this point to bring it up to 
date as the failure of a check will result in you having to restore the repository from an archive.
CAUTION: When a repository is deleted, the data contained in the repository is discarded and cannot 
be recovered. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B60 Check job that must be run on each repository before you can configure dissimilar retention policies between 
the source core and a target core, or configure a custom retention policy on a replicated agent.
When you run the Integrity Check job, the system verifies the integrity of all data stored in the specified 
repository, ensuring you can recover data from each snapshot or base image. If the integrity check discovers any 
issue with data in your repository, the job ceases immediately. The event details for that job on the core prompt 
you to contact Dell AppAssure Support, so you can schedule time to work with a Dell representative to perform 
additional procedures to identify and remediate data inconsistencies.
You can perform other operations in other repositories while the Integrity Check job is running.
This is an ad hoc job available to run on each repository. Dell recommends performing the Integrity Check job a 
single time on each repository on a replicated target core if upgrading from release 5.3.x.
Yo u  d o  not need to run this job:
•On a new repository on a target core created in release 5.4.1 or later.
•On a source core.
•If you have already run the Integrity Check Job on this repository.
•If you have not used replication.
For instructions on how to perform this check, see the procedure Running the Integrity Check job on a 
repository.
Running the Integrity Check job on a repository
Perform this procedure to check the integrity of the entire repository. This is recommended for replicated 
target cores when upgrading from AppAssure 5.3.x to release 5.4. During the execution of the integrity check, 
which can be lengthy, no other actions can be performed in the repository.
If you have multiple repositories for a target core, perform this process once for each repository.
To run the repository integrity check job
1 Navigate to the AppAssure Core Console, click the Configuration tab, and then click Repositories.
The Repositories page appears, displaying the list of repositories associated with this Core.
2 From the drop-down menu for the repository you want to check, select Integrity Check.
A confirmation message appears. 
3 From the Integrity Check Repository dialog box, to perform the integrity check, click Ye s.
The Check Repository dialog box closes, any jobs that were queued or that are in progress are canceled, 
and the integrity check job beings.
CAUTION: Running this job is expected to take an extended period of time based on the data in your 
repository, and the underlying storage system. While the job is running, no other transactions can be 
performed in that repository, including transfers (snapshot and base image backups, and replication), 
nightly jobs, and so on.
NOTE: This job checks the integrity of all of the contents within a repository. For information about the 
Repository Check job, which you can use to check to ensure a repository is mountable and usable, see 
Checking a repository.
NOTE: If you have another repository on the target core for which the Integrity Check job has already 
been completed, or if you create a new additional repository for this target core, you can perform 
operations in that secondary repository while the integrity check job is running on your primary repository.
CAUTION: Before you confirm that you want to perform the job, you should carefully consider the 
duration of time required. While the job is running, no other transactions can be performed in that 
repository, including transfers (snapshot and base image backups, and replication), nightly jobs, and 
so on. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B61 4 To monitor the progress of the Integrity Check job for a repository, including a determination of whether 
additional steps are required after the check, click the Events tab. 
5 From the Events tab, click Show details for the job to view more information about the job status.
•If you see an error in any child tasks for this job, note the error and provide the information to a 
Dell technical support representative.
•If the Integrity Check Job completes all child tasks successfully, you can then establish a custom 
retention policy for this repository.
Understanding custom groups
The AppAssure Core shows a Protected Machines menu in the left navigation area. This includes all machines 
added to protection on your AppAssure Core. If you have protected clusters, these also appear in the Protected 
Machines menu. Beneath this, if you have replicated machines, these appear in a replicated machines menu 
under the name of the replicated Core. You can perform group actions for all machines arranged under one of 
these menus, by selecting the arrow to the right of the menu name to access the drop-down menu.
In the same manner, you can create a custom group to display in the left navigation area, as described in 
Managing licenses.
The act of creating a group always adds one group member (a protected machine, server cluster, or replicated 
agent, based on how you initiated the group creation) to the new custom group. Ideally, you would then add 
additional members to the group. Thereafter, you can perform group actions that apply to all members of that 
custom group, as described in Performing group actions.
Custom groups can include protected agents, replicated agents, and server clusters. Server clusters behave the 
same as protected agents, with the exception that a server cluster and its nodes behave as a single entity. If you 
attempt to add a node from a server cluster to a group, the entire cluster is added.
A custom group may contain similar or dissimilar members. For groups of similar members, all group actions 
apply to all members of the group. For example, if you force a snapshot for a custom group of protected agents, 
each agent will be backed up. For groups with dissimilar members (for example, protected agents and 
replicated agents), if you apply a group action such as forcing replication, this will only apply to the replicated 
agents.
You can create one or more groups. A single agent or replicated machine can be included in one or more groups. 
This way, you can group machines on your core in any way you choose, and can perform actions on that specific 
group.
Each custom group appears in the left navigation area, with a label you designate. Groups with standard 
protected agents appear first in the custom group, and replicated agents appear below, as applicable.
Including a machine in a group does not remove it from its original location. For example, if you have three 
protected machines called Agent1, Agent2, and Agent3, and you add Agent1 to CustomGroup1, then Agent1 
appears in both locations.
For more information, see the following topics:
•Managing licenses
•Modifying custom group names
•Removing custom groups
•Performing group actions
•Viewing all machines in a custom group on one page 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B62
Creating custom groups
When you scroll your cursor over the name of any machine in the Protected Machines or replicated machines 
menu, you will see an arrow that opens a drop-down menu. From this menu, you can create a custom label.
Use the procedure below to create a custom group.
To create a custom group
1 Navigate to the AppAssure Core Console.
2 From the Protected Machines or replicated machines menu, do the following:
a Click on a machine in the menu.
b Click on the drop-down menu for that machine.
c Scroll down and select Label as, and then click New label.
A new menu appears, with a blank text box next to a label icon. The machine you selected is listed under 
the custom group.
3 Enter an appropriate label for your custom group.
Use a descriptive name that communicates the purpose of the group. For example, to group agent 
machines by department, type Accounting Department. You can rename a group later.
4 When you are satisfied with the label name, click the green check mark to save the name.
The page refreshes, showing your custom group in the navigation area.
5 Optionally, to add other agents to this group, navigate to the agent name in the appropriate menu, click 
to open the drop-down menu, scroll down and select Label as, and then click the name of the custom 
group.
You can now perform group actions on this group. For more information, see Performing group actions.
Modifying custom group names
When you modify the name of a custom group, only the label changes. The machine names remain the same.
Use the procedure below to modify a custom group name.
To modify a custom group name
1 Navigate to the AppAssure Core Console.
2 In the Protected Machines menu, scroll your cursor over the custom group you want to modify.
3 Click on the drop-down menu for that group, and then click Edit.
The name of the custom group becomes editable.
4 Enter a new label or your custom group. When you are satisfied with the label name, click the green 
check mark to save the name. You can edit this name later.
Use a descriptive name that communicates the purpose of the group. For example, to group agent 
machines by department, type Accounting Department.
5 Optionally, to add other agents to this group, navigate to the agent name in the appropriate menu, click 
to open the drop-down menu, scroll down and select Label as, and then click the name of the custom 
group.
NOTE: Labels must be 50 or fewer characters. You can include a single space between words. You 
must provide a label for your custom group.
NOTE: Labels must be 50 or fewer characters. You can include a single space between words. You 
must provide a label for your custom group. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B63
Removing custom groups
When you remove a custom group, you delete that group from the Protected Machines menu. The machines that 
were in the group are not removed, and can still be found in the appropriate standard menu.
Use the procedure below to remove a custom group.
To remove a custom group
1 Navigate to the AppAssure Core Console.
2 In the Protected Machines menu, scroll your cursor over the custom group you want to remove.
3 Click on the drop-down menu for that group, and then click Remove label.
You see a message asking to confirm the removal of the group. Confirm the action.
The page refreshes, and the custom group is removed from the navigation area.
Performing group actions
You can perform group actions on any group appearing in the left navigation area of the AppAssure Core 
Console. If the group contains dissimilar members (for example, standard agent machines and replicated 
agents), then the actions you request will only be performed on the relevant group members.
Use the procedure below to perform group actions on a custom group.
To perform group actions
1 Navigate to the AppAssure Core Console.
2 In the Protected Machines menu, scroll your cursor over the custom group for which you want to perform 
a group action.
3 Click on the drop-down menu for that group, and then select an action as follows:
•To force an incremental snapshot or base image for a protected agent, click Force Snapshot or 
Force Base Image, as appropriate. For more information, see Forcing a snapshot.
•To pause protection for a protected agent, click Pause  Prot ection and then specify resumption 
parameters. For more information, see Pausing and resuming replication.
•To resume protection for an agent for which protection has been paused, click Resume Protection 
and then confirm that you want to resume. For more information, see Pausing and resuming 
replication.
•To refresh the information displayed, click Refresh Metadata.
•To pause replication for a replicated agent on the target core, under Replication, click Pause. For 
more information, see Pausing and resuming replication.
•To resume replication for a replicated agent for which replication has been paused on the target 
core, under Replication, click Resume. For more information, see Pausing and resuming 
replication
•To force replication for a replicated agent machine, click Fo rc e. For more information, see 
Forcing replication.
•For custom groups only, to modify the label for the custom group, select Edit. For more 
information, see Modifying custom group names.
•For custom groups only, to remove the custom group, select Remove label. For more information, 
see Removing custom groups. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B64
Viewing all machines in a custom group on one page
Clicking the name of a custom group takes you to a Machines tab that lists all the machines in that custom 
group. You can then perform some functions on all machines from the Actions menu, or you can perform 
functions individually by selecting commands from each individual machine.
Backing up and restoring the Core 
configuration
When you configure an AppAssure Core, you can then back up all of the core settings that are stored in the 
Windows registry. If you perform this backup, these settings are then available in the future to restore to an 
AppAssure Core from the configuration file. This is useful in the case where you have restored or replaced a 
core machine due to upgrade or after a data loss.
Optionally, when restoring a backed-up configuration file, you can also choose to restore configuration 
information for the repositories. Finally, you can restore the path associated with data or metadata storage. 
This is useful if those settings have been inadvertently changed. 
This section includes the following topics:
•Backing up the Core configuration
•Restoring a backed-up Core configuration
Backing up the Core configuration
You can back up settings from your Core configuration, to be restored at a future time. Complete the steps in 
the following procedure to back up Core configuration information to an XML file.
To back up the Core configuration
1 Navigate to the AppAssure Core, click the Configuration tab, and then click Backup/Restore.
The Backup Core Configuration pane appears.
2 In the Backup Core Configuration pane, in the Local path text field, type the path of a local directory on 
the server with the AppAssure Core, and then click Backup.
For example, type C:\Users\administrator\Documents\Config and then click Backup.
The file is saved as AppRecoveryCoreConfigurationBackup.xml in the directory you specified.
NOTE: This process restores the configuration settings only, not the data.
Security information (such as authentication credentials) is not stored in the configuration file. There is 
no security risk to saving a Core configuration file.
CAUTION: If your Core configuration settings change, then you should back up this configuration 
information after those changes to maintain the latest configuration information.
Dell recommends you move the backup file to a known location on another machine, a network drive, 
or on storage media retained in an offsite storage location.
CAUTION: Dell recommends you move the backup file to a known location on another machine, a 
network drive, or on storage media retained in an offsite storage location. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B65
Restoring a backed-up Core configuration
If you have a Core configuration file backed up, you can restore this XML file to an AppAssure Core. This is useful 
in the case where you have restored or replaced a core machine due to upgrade or after a data loss. After you 
restore the backup file, then configuration settings in the backup file are restored to the AppAssure Core. This 
includes the names of protected machines, replication relationships, virtual standby information, and 
encryption keys, as applicable.
Complete the steps in the following procedures to restore a Core configuration file.
To restore a backed-up Core configuration
1 If restoring the backup file from a network drive or other location, copy the 
AppRecoveryCoreConfigurationBackup.xml file to a local drive on the Core machine and note the 
location.
2 Navigate to the AppAssure Core, click the Configuration tab, hover over Backup/Restore, and click 
Restore.
The Restore Core Configuration pane appears.
3 In the Restore Core Configuration pane, in the Local path text field, type the local path of the backup 
file.
4 Optionally, if you want to restore configuration information for any repositories backed up to the 
configuration file, select Restore Repositories.
5 Note the cautions indicated. If the restore process does not complete as expected, check each of these 
factors.
6 Then click Restore.
Your configuration is restored to the AppAssure Core.
NOTE: To restore, the configuration file must be stored locally on the Core machine. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B
4
66
 Managing AppAssure Core settings
This chapter describes how to manage and change the settings for your AppAssure Core from the Configuration 
tab or icon. It includes the following sections:
•Understanding system information
•Configuring update settings
•Understanding nightly jobs
•Modifying transfer queue settings
•Modifying transfer queue settings
•Adjusting client timeout settings
•Understanding deduplication cache size and storage locations
•Configuring Replay engine settings
•Configuring deployment settings
•Accessing diagnostics for the Core
•Configuring database connection settings
•Changing a license
•Backing up and restoring Core settings
•Configuring Core job settings
The AppAssure Core settings are configured by default for optimum performance for most users. These settings 
affect the performance of the AppAssure Core, or in some cases the display of information in the AppAssure 
Core Console. You can access most Core settings from the Configuration tab by clicking Settings. From the same 
tab, you can also access Licensing, Backup/Restore, or Job Settings, as appropriate. The comprehensive set of 
AppAssure Core settings that you can configure is described in the following table. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B67 Table 34. AppAssure Core configurable settings
Configuration Setting Description
System Information System information includes data about the AppAssure Core server. You can see the 
host name, OS, architecture and memory for the Core. You can see or change the 
name displayed on the Core Console. You can also view the fully qualified domain 
name of the Core on your network, and the path for your cache metadata and 
deduplication caches. System information is available from the Tools menu.
For more information about changing the display name, see Understanding system 
information. For more information about deduplication cache, see Understanding 
deduplication cache size and storage locations. For information on adjusting the 
settings, see Configuring deduplication cache settings.
General General settings include configuration options that apply generally to the AppAssure 
Core, including display options and ports for the web server and for the AppAssure 
service. You access general settings by selecting General settings include:
•Display name
•We b s e rve r p or t
•Service port
•Language
For more information about the general settings for AppAssure Core, including how to 
configure these settings, see Understanding system information.
Updates Update settings controls aspects of the Automatic Update feature, which checks for 
updated versions of AppAssure software.
Update settings include:
•Check for new updates
•Install updates
•Status
•Last check
For more information about settings for updating the AppAssure Core, including how to 
configure these settings, see Configuring update settings.
Nightly jobs Nightly jobs settings are automated tasks which the Core performs on a daily basis. 
You can configure the time the jobs begin and which jobs are performed. Dell 
recommends scheduling the jobs outside of normal business hours to reduce load on 
the system when demand is high.
For more information about nightly jobs, see Understanding nightly jobs. For more 
information about how to configure these settings for the Core, see Configuring nightly 
jobs for the Core. For more information about configuring nightly jobs for specific 
protected machines, see Customizing nightly jobs for a protected machine.
Transfer queue Transfer queue settings apply to the number of times transfer operations are 
attempted if jobs fail due to unavailability of resources. You can establish the 
maximum number of concurrent transfers and the maximum number of retries for 
transferring data.
For more information about transfer queue settings, see Modifying transfer queue 
settings.
Client timeout Client timeout settings determine the length of time before that specific connection 
requests or read and write operations should be attempted before timing out. 
For more information about client timeout settings, see Adjusting client timeout 
settings. 
						

							Dell AppAssure User Guide
Version 5.4.3 Revision B68 Deduplication cache AppAssure deduplicates your data globally across a repository. Deduplication ensures 
that unique blocks of information are stored only once in your repository, creating 
references to repeated data blocks. The references are stored in a deduplication 
cache. If encryption keys are used, then deduplication occurs within each encryption 
domain.
The deduplication cache settings let you configure the size and specify the locations 
for the primary and secondary cache as well as the location for the metadata cache.
For more information about deduplication cache, see Understanding deduplication 
cache size and storage locations. For information on adjusting the settings, see 
Configuring deduplication cache settings.
Replay Engine Replay engine settings control information regarding the communication channel for 
the Replay engine. Settings include IP addresses, port numbers, automatic port 
assignment, buffer sizes for sending and receiving information, and timeout settings to 
help adjust the performance specific to your network needs.
For more information about engine settings for AppAssure, see Configuring Replay 
engine settings.
Deploy Deploy settings let you set options for deploying the AppAssure Agent software from 
your Core to the machines you want to protect. AppAssure lets you specify the name 
of the installer file, Core address, timeout settings, and limit the number of 
concurrent installations (to prevent overload of your network). You can also specify 
whether protected machines reboot, and whether machines are automatically 
protected after the AppAssure Agent software is deployed.
For more information about configuring deployment settings, see Configuring 
deployment settings.
Database connection 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 by default on the Core machine. You can configure these settings to 
change how long information is retained in the database, or to change the connection 
pool size to allow for more or fewer connections concurrently.
If using a second AppAssure Core, you can configure the database connection settings 
on the first Core to point to the second Core machine. In this way, the event data for 
both Cores will be stored in the MongoDB on the second Core.
Alternatively, you can configure the database connection settings on the Core to point 
to another machine that has a separately installed MongoDB which is accessible over 
the network to the AppAssure Core. The event transaction data for your Core is then 
saved to that service database, not locally. For more information about establishing or 
modifying database connection settings for the service database, see Configuring 
database connection settings.
SMTP server The AppAssure Core monitors tasks, events and alerts. This information is visible on 
the Events tab. If you configure simple mail transfer protocol (SMTP) server settings 
for the Core, you can also send this information by email. These settings include the 
SMTP server name, originating email address (“From” address), login credentials, 
port, timeout and security settings for that email server.
For more information about configuring an SMTP email server, see Configuring an email 
server.
NOTE: To send event information by email, you must also configure notification group 
settings. For more information on specifying events to receive email alerts, see 
Configuring notification groups. Table 34. AppAssure Core configurable settings
Configuration Setting Description