AppAssure 5 User Guide Version 5.3.
Notes, Cautions and Warnings A NOTE indicates important information that helps you make better use of your computer. A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. A WARNING indicates a potential for property damage, personal injury, or death. Information in this publication is subject to change without notice. © 2013 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc.
Contents Chapter 1: What’s New in AppAssure 5 What’s New in AppAssure 5 User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Additional Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Chapter 2: Introduction to AppAssure 5 About AppAssure 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing AppAssure 5 Core Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Changing the Core Display Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Adjusting the Nightly Job Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Modifying the Transfer Queue Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Configuring Notification Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Configuring an Email Server and Email Notification Template . . . . . . . . . . . . . . . . . . . . . . . 70 Configuring Repetition Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing and Modifying Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Viewing System Information for a Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Configuring Notification Groups for System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Editing Notification Groups for System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Customizing Retention Policy Settings . . . .
Prerequisites for Performing a Bare Metal Restore for a Windows Machine . . . . . . . . . . . 158 Managing a Windows Boot Image . . . . . . . . . . . . . . . . . . . . . . . Creating a Boot CD ISO Image for Windows . . . . . . . . Defining Boot CD ISO Image Parameters . . . . . . . . . . . Transferring the Boot CD ISO Image to Media . . . . . . . Loading the Boot CD and Starting the Target Machine .. .. .. .. .. . . . . . . . . . . ... ... ... ... ... 159 159 160 163 163 ........................ .....
Modifying Cluster Transfer Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Converting a Protected Cluster Node to an Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Viewing Server Cluster Information . . . . . . . . Viewing Cluster System Information . Viewing Cluster Events and Alerts . . . Viewing Summary Information . . . . . . . . . . .. .. .. .. .. .. .. .. . . . . .. .. .. .. . . . . .. .. .. .. .. .. ..
PreExportScript.ps1 . . . . . . . . . . . . . . . . . . . . . . . . PostExportScript.ps1 . . . . . . . . . . . . . . . . . . . . . . . PreNightlyJobScript.ps1 . . . . . . . . . . . . . . . . . . . . PostNightlyJobScript.ps1 . . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. .. .. . . . . .. .. .. .. .. .. .. .. . . . . .. .. .. .. . . . . .. .. .. .. .. .. .. .. . . . . .. .. .. .. . . . . .. .. .. .. .. .. .. .. . . . . . . . . . . . . . . . . . . . . .. .. .. .. 229 230 .
| Contents
1 What’s New in AppAssure 5 This chapter lists new and changed features in this release of AppAssure 5. What’s New in AppAssure 5 User Guide The following table lists the changes that are described in this version of the documentation to support AppAssure 5. Topic Description Modifying AppAssure 5 Engine Settings on page 34 Modified topic. It describes how to configure the engine settings for AppAssure 5 to include parameters such as the preferable port.
Topic Description About the Local Mount Utility on page 75 Modified topic. It describes the Local Mount Utility (the LMU). Updated language in this topic and in each related subtopic for clarity. Dismounting a Recovery Point Using the Local Mount Utility on page 79 Modified topic. It describes how to dismount recovery points in the LMU.
Topic Understanding Bare Metal Restore on page 156 Description Modified topic. Formerly titled About Bare Metal Restore for Windows Machines, it describes conceptual information about performing a Bare Metal Restore (BMR) for Windows and Linux machines. It includes samples of similar and dissimilar restores, and indicates BMR functionality is used for both disaster recovery and server migration. Noted that BMR not supported for Windows 8.1 Storage Spaces.
Topic Description Mapping Volumes for a Bare Metal Restore on page 166 Modified topic. This topic, previously entitled “Mapping Volumes,” describes mapping volumes in the recovery point with those volumes on the destination machine. Injecting Drivers to Your Target Server on page 167 New topic. This topic describes the process of injecting additional drivers to the new hardware that may be required by the restored operating system to perform properly for dissimilar hardware.
Topic Description Transferring the Live DVD ISO Image to Media on New topic. It describes burning the Live DVD page 174 boot ISO image to media such as a CD or DVD, which is required for performing BMR on a physical machine. Loading the Live DVD and Starting the Target Machine on page 174 New topic. It describes loading the Live DVD boot disk and starting the destination machine from the boot image. Managing Linux Partitions on page 175 New topic.
Additional Changes This version of the AppAssure 5 User Guide also includes the following general changes: 16 | Editorial changes.
2 Introduction to AppAssure 5 This chapter provides an introduction and overview of AppAssure 5.
Today's legacy backup tools and first generation VM backup tools are inefficient and ineffective. The outdated backup tools lack the ability to handle large-scale data and do not offer the level of performance and reliability needed for protecting businesscritical applications. Combine this with complex and mixed IT environments and it presents an administrative challenge for IT professionals and vulnerability of system data.
Universal Recovery Universal Recovery technology gives you unlimited machine restoration flexibility. You can restore your backups from physical to virtual, virtual to virtual, virtual to physical, or physical to physical, and carry out bare metal restores to dissimilar hardware; for example, P2V, V2V, V2P, P2P, P2C, V2C, C2P, C2V. It also accelerates cross-platform moves among virtual machines; for instance, moving from VMware to Hyper-V or Hyper-V to VMware.
Repository The AppAssure repository uses deduplication volume manager (DVM) to implement a volume manager that provides support for multiple volumes, each of which could reside on different storage technologies such as Storage Area Network (SAN), Direct Attached Storage (DAS), Network Attached Storage (NAS), or cloud storage. Each volume consists of a scalable object store with deduplication.
The typical disk layout of a server consists of the operating system, application, and data. In most environments, the administrators often use a common flavor of the server and desktop operating system across multiple systems for effective deployment and management. When backup is performed at the block level across multiple machines at the same time, it provides a more granular view of what is in the backup and what is not, irrespective of the source.
Encryption AppAssure 5 provides integrated encryption to protect backups and data-at-rest from unauthorized access and use, ensuring data privacy. AppAssure 5 provides strong encryption. By doing so, backups of protected computers are inaccessible. Only the user with the encryption key can access and decrypt the data. There is no limit to the number of encryption keys that can be created and stored on a system. DVM uses AES 256-bit encryption in the Cipher Block Chaining (CBC) mode with 256-bit keys.
Replication Replication is the process of copying recovery points and transmitting them to a secondary location for the purpose of disaster recovery. The process requires a paired source-target relationship between two cores. Replication is managed on a per-protected-machine basis; meaning, backup snapshots of a protected machine are replicated to the target replica core. When replication is set up, the source core asynchronously and continuously transmits the incremental snapshot data to the target core.
Replication begins with seeding: the initial transfer of deduplicated base images and incremental snapshots of the protected agents, which can add up to hundreds or thousands of gigabytes of data. Initial replication can be seeded to the target core using external media. This is typically useful for large sets of data or sites with slow links. The data in the seeding archive is compressed, encrypted and deduplicated.
Retention policies enforce the periods of time in which backups are stored on shortterm (fast and expensive) media. Sometimes certain business and technical requirements mandate extended retention of these backups, but use of fast storage is cost prohibitive. Therefore, this requirement creates a need for long-term (slow and cheap) storage. Businesses often use long-term storage for archiving both compliance and non-compliance data.
Virtualization and Cloud The AppAssure 5 Core is cloud-ready, which allows you to leverage the compute capacity of the cloud for recovery. AppAssure 5 can export any protected or replicated machine to licensed versions of VMware or Hyper-V. Exports can be ad-hoc or continuous. With continuous exports, the virtual machine is incrementally updated after every snapshot. The incremental updates are very fast and provide standby-clones that are ready to be powered up with a click of a button.
Service Management APIs AppAssure 5 comes bundled with a set of service management APIs and provides programmatic access to all of the functionality available through the AppAssure 5 Central Management Console. The service management API is a REST API. All the API operations are performed over SSL and are mutually authenticated using X.509 v3 certificates.
This page is intentionally left blank.
3 Working with the AppAssure 5 Core This chapter describes the various aspects of working with, configuring, and managing the AppAssure 5 Core.
Accessing the AppAssure 5 Core Console Complete the following steps to access the AppAssure 5 Core Console. To access the AppAssure 5 Core Console 1. Perform one of the following to access the AppAssure 5 Core Console: a. Log on locally to your AppAssure 5 Core server, and then select the Core Console icon. b.
The Licensing page includes the following information: License type License status License pool size Number of machines protected Status of last response from the licensing server Time of last contact with the licensing server Next scheduled attempt of contact with the licensing server For more information, see the documentation, Managing AppAssure 5 Licenses, on the AppAssure 5 Technical Documentation page at: http://docs.appassure.
2. Click Licensing. The Licensing page appears. 3. From the License Server option, click Contact Now. Managing AppAssure 5 Core Settings The AppAssure 5 Core settings are used to define various settings for configuration and performance.
3. In the Start Time text box, enter a new start time. 4. Click OK. Modifying the 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 5 Core Console and click the Configuration tab, and then Settings. 2.
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 5 Core Console and click the Configuration tab, and then Settings. 2. In the Deduplication Cache Configuration area, click Change. The Deduplication Cache Configuration dialog box displays. 3. In the Primary Cache Location text box, enter an updated value to change the primary cache location. 4.
Text Box Description 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.
Text Box Description Password (optional) Enter a password for accessing and managing the database connection settings. Retain event and job history for, Enter the number of days to retain the event and job days history for the database connection. 4. Click Test Connection to verify your settings. 5. Click Save. About Repositories A repository is used to store the snapshots that are captured from your protected workstations and servers.
When you create a repository, the Core pre-allocates the space required for storing data and metadata in the specified location. You can create up to 255 independent repositories on a single core. To further increase the size of a single repository, you can add new storage locations or volumes. Managing a repository involves creating, configuring, and viewing a repository and includes the following operations: Access the Core Console.
4. Click Add Storage Location to define the specific storage location or volume for the repository. If the AppAssure repository that you are creating in this step is later removed, all files at the storage location of your repository will be deleted. If you do not define a dedicated folder to store the repository files, then those files will be stored in the root; deleting the repository will also delete the entire contents of the root, resulting in catastrophic data loss.
6. In the Details pane, click Show/Hide Details and enter the details for the storage location as described in the following table. Text Box Description Size Set the size or capacity for the storage location. The default is 250 MB. You can choose from the following: MB GB TB NOTE: The size that you specify cannot exceed the size of the volume. 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.
Viewing Details about a Repository Complete the following step to view the details for a repository. To view details about a repository In the AppAssure 5 Core Console, click the Configuration tab. The Repositories page displays. Click the right angle bracket > symbol next to the Status column of the repository for which you want to view the details.
2. Click the right angle bracket > symbol next to the Status column of the repository that you want to modify. 3. Next to Actions, click Settings. The Repository Settings dialog box displays. 4. Edit the repository information as described in the following table. Text Box Description Repository Name Represents the display name of the repository. By default, this text box consists of the word Repository and an index number, which corresponds to the number of the repository.
Select Add file on local disk to specify a local machine and then enter the information as described in the following table. Text Box Description Metadata Path Enter the location for storing the protected metadata. For example, type X:\Repository\Metadata. When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). The letters a to z are case-insensitive. Do not use spaces. No other symbols or punctuation characters are permitted.
4. In the Details pane, click Show/Hide Details and enter the details for the storage location as described in the following table. Text Box Description Size Set the size or capacity for the storage location.The default size is 250 MB. You can choose from the following: MB GB TB NOTE: The size that you specify cannot exceed the size of the volume. 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.
Checking a Repository AppAssure 5 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, and so on. 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. To check a repository 1.
Key security concepts and considerations include: Encryption is performed using 256 Bit AES in Cipher Block Chaining (CBC) mode that is compliant with SHA-3. Deduplication operates within an encryption domain to ensure privacy. Encryption is performed without impact on performance. You can add, remove, import, export, modify, and delete encryption keys that are configured on the AppAssure 5 Core. There is no limit to the number of encryption keys you can create on the Core.
To edit an encryption key 1. Navigate to the AppAssure 5 Core, and then click the Configuration tab. 2. From the Manage option, click Security. The Encryption Keys screen displays. 3. Click right angle bracket > symbol next to the name of the encryption key that you want to edit, and then click Edit. The Edit Encryption Key dialog box displays. 4. In the Edit Encryption Key dialog box, edit the name or modify the description for the encryption key. 5. Click OK.
3. Click the Actions drop-down menu, and then click Import. The Import Key dialog box displays. 4. In the Import Key dialog box, click Browse to locate the encryption key you want to import, and then click Open. 5. Click OK. Exporting an Encryption Key Complete the steps in this procedure to export an encryption key. To export an encryption key 1. Navigate to the AppAssure 5 Core, and then click the Configuration tab. 2. From the Manage option, click Security. 3.
Understanding Replication This section provides conceptual and procedural information to help you understand and configure replication in AppAssure 5. About Replication Replication is the process of copying recovery points and transmitting them to a secondary location for the purpose of disaster recovery. The process requires a paired source-target relationship between two cores.
Possible replication configurations include: Point to Point. Replicates a single agent from a single source core to a single target core. Figure 4. Point to point configuration Multi-Point to Point. Replicates multiple source cores to a single target core. Figure 5.
About Seeding Replication begins with seeding: the initial transfer of deduplicated base images and incremental snapshots of the protected agents, which can add up to hundreds or thousands of gigabytes of data. Initial replication can be seeded to the target core using external media to transfer the initial data to the target core. This is typically useful for large sets of data or sites with slow links. While it is possible to seed the base data over a network connection, it is not recommended.
About Failover and Failback in AppAssure 5 In the case of a severe outage in which your source core and agents fail, AppAssure 5 supports failover and failback in replicated environments. Failover refers to switching to a redundant or standby target AppAssure Core upon system failure or abnormal termination of a source core and associated agents. The main goal of failover is to launch a new agent identical to the failed agent that was protected by the failed source core.
Performance Considerations for Replicated Data Transfer If the bandwidth between the source core and the target core cannot accommodate the transfer of stored recovery points, replication begins with seeding the target core with base images and recovery points from the selected servers protected on the source core. The seeding process only has to be performed once, as it serves as the foundation that is required for regularly scheduled replication.
If a link fails during data transfer, replication resumes from the previous failure point of the transfer once link functionality is restored. Roadmap for Performing Replication To replicate data using AppAssure 5, you must configure the source and target cores for replication. After you configure replication, you can then replicate agent data, monitor and manage replication, and perform recovery.
Configuring the Source Core to Repl icate to a Self-Managed Target Core Complete the steps in the following procedure to configure your source core to replicate to a self-managed target core. To configure the source core to replicate to a self-managed target core 1. Navigate to the AppAssure 5 Core, and then click the Replication tab. 2. In the Actions drop-down menu, click Add Remote Core. The Select Replication Type dialog box appears. 3.
9. In the Copy to Seed Drive dialog box, enter the information described in the following table. Text Box Description Location Enter the path to the drive on which you want to save the initial data, such as a local USB drive. User Name Enter the user name for connecting to the drive. NOTE: This is required if the seed drive is located on a network share. Password Enter the password for connecting to the drive. NOTE: This is required if the seed drive is located on a network share.
Configuring Repl ication to a Target Core Managed by a Third Party Complete the steps in this procedure to configure replication for a core that is managed by a third party. To configure replication for a core managed by a third party 1. On the source core, navigate to the AppAssure 5 Core, and then click the Replication tab. 2. In the Actions drop-down menu, click Add Remote Core. 3.
8. In the Copy to Seed Drive dialog box, enter the information for the seed drive as described in the table below. Item Description Location Enter the path to the drive on which you want to save the initial data, such as a local USB drive. User Name Enter the user name for connecting to the drive. NOTE: This is required if the seed drive is located on a network share. Password Enter the password for connecting to the drive. NOTE: This is required if the seed drive is located on a network share.
To deny a request without reviewing it, see “Ignoring a Replication Request” on page 58. To review a replication request 1. On the target core, open the AppAssure 5 Core Console, and then click the Replication tab. 2. On the Replication tab, click Pending Requests (#). The Pending Replication Requests section appears. 3. Under Pending Replication Requests, click the drop-down menu next to the request you want to review, and then click Review. The Review Replication Request window appears.
3. Under Pending Replication Requests, click the drop-down menu next to the request you want to ignore, and then click Ignore. 4. Notification that the request has been ignored is sent to the source core. Consuming the Seed Drive on a Target Core Complete the follow procedure to consume the data from the seed drive on the target core.
Abandoning an Outstanding Seed Drive If you create a seed drive with the intent to consume it on the target core but choose not to send it to the remote location, a link for the Outstanding Seed Drive remains on the source core replication tab. In this case, you may want to abandon the outstanding seed drive in favor different or more current seed data. Complete the steps in the following procedure to abandon an outstanding seed drive.
2. On this tab, you can view information about and monitor the status of replication tasks as described in the following table. Section Description Available Actions Pending Replication Requests Lists your customer ID, email address, In the drop-down menu, click and host name when a replication Ignore to ignore or reject the request is submitted to a third-party request. service provider. It is listed here until the request is accepted by the MSP.
Pausing and Resuming Replication You can pause replication temporarily for the source (outgoing) or target (incoming) cores. To pause and resume replication 1. In the Core Console, click the Replication tab. 2. Under Outgoing Replication for a source core or Incoming Replication for a target core, click Pause to pause replication temporarily. 3. Click Resume to resume replication after it has been paused.
“Removing a Target Core from Replication” on page 63 “Removing a Source Core from Replication” on page 64 NOTE: Removing a source core results in the removal of all replicated agents protected by that core. Removing an Agent from Repl ication on the Source Core Complete the steps in this procedure to remove an agent from replication on the source core. To remove an agent from replication on the source core 1. From the source core, open the AppAssure 5 Core Console, and click the Replication tab.
To remove a target core from replication 1. On the source core, open the AppAssure 5 Core Console, and click to the Replication tab. 2. Under Outgoing Replication, click the drop-down menu next to the remote core that you want to delete, and click Delete. 3. In the Outgoing Replication dialog box, click Yes to confirm deletion. Removing a Source Core from Repl ication Complete the steps in this procedure to remove a source core from replication.
Perform a virtual machine (VM) export. For more information, see “Exporting Backup Information for your Windows Machine to a Virtual Machine” on page 144. Perform a bare metal restore (BMR). For more information, see “Roadmap for Performing a Bare Metal Restore for a Windows Machine” on page 157. Perform Failback (in the event you have a Failover/Failback replication environment set up). For more information, see “Performing Failback” on page 66.
Performing Failover on the Target Core When you encounter a disaster situation in which your source core and associated agents have failed, you can enable failover in AppAssure 5 to switch protection to your identical failover (target) core. The target core becomes the only core protecting the data in your environment, and you then launch a new agent to temporarily replace the failed agent. To perform failover on the target core 1.
3. On the Actions menu, click Failback. The Failback Warnings dialog box opens to describe the steps you need to follow before you click the Start Failback button. 4. Click Cancel. 5. If the failed-over machine is running Microsoft SQL Server or Microsoft Exchange Server, stop those services. 6. In the Core Console for the target core, click the Tools tab. 7. Create an archive of the failed-over agent and output it to disk or a network share location.
Managing Events Managing core events assists with the monitoring of the health and usage of the AppAssure 5 Core. The Core includes predefined sets of events, which can be used to notify administrators of critical issues on the Core or the backup jobs. From the Events tab, you can manage notification groups, email SMTP settings, repetition reduction, and event retention.
Enable Events Notification Options 4. In the description area, enter basic information for the notification group, as described in the following table. Text Box Description Name Enter a name for event notification group. It is used to identify the event notification group. Description Enter a description for the event notification group. It is used to describe the purpose of the event notification group. 5.
6. In the Notification Options tab, specify how to handle the notification process. The following table describes the notification options. Text Box Description Notify by email Designate the recipients of the email notification. You can choose to specify separate multiple email addresses as well as blind and carbon copies. You can choose: To: CC: BCC: Notify by Windows Event Log Select this option if you want alerts to be reported through the Windows Event Log.
3. In the Email SMTP Settings pane, click Change. The Edit Email Notification Configuration dialog box appears. Figure 6. Ed it Email Notification Configuration d ialog box 4. Select Enable Email Notifications, and then enter details for the email server as described in the following table. Text Box Description SMTP Server Enter the name of the email server to be used by the email notification template. The naming convention includes the host name, domain, and suffix; for example, smtp.gmail.com.
Text Box Description Timeout (seconds) Enter an integer value to specify how long to try to connect to the email server. It is used to establish the time in seconds before a timeout occurs. The default is 30 seconds. TLS Select this option if the mail server uses a secure connection such as Transport Layer Security (TLS) or Secure Sockets Layer (SSL). 5. Enter a subject for the email template.
4. In the Retain event and job history for: text box, enter the number of days that you want to retain information about events.; for example, 30 days (default). 5. Click Save. Managing Recovery The AppAssure 5 Core can instantly restore data or recover machines to physical or virtual machines from the recovery points. The recovery points contain agent volume snapshots captured at the block level.
About System Information AppAssure 5 lets you view information about the AppAssure 5 Core that includes system information, local and mounted volumes, and AppAssure engine connections. If you want to dismount individual or all recovery points that are mounted locally on a core, you can accomplish this from the Mount option on the Tools tab. For more information about dismounting recovery points, see “Dismounting Select Recovery Points” on page 137 and “Dismounting All Recovery Points” on page 137.
Downloading the Agent Installer You can download and deploy the AppAssure 5 Agent Installer on any machine that will be protected by the AppAssure 5 Core. Complete the steps in this procedure to download the web installer. To download the AppAssure 5 Agent installer 1. Download the AppAssure 5 Agent installer file from the AppAssure 5 License Portal or from the AppAssure 5 Core. For example: Agent-X64-5.2.1.xxxxx.exe 2. Click Save File.
5. From the Opening LocalMountUtility-Web.exe window, click Save File. The file saves to the local Downloads folder. In some browsers, the folder automatically opens. 6. From the Downloads folder, right-click the LocalMountUtility-Web executable and click Open. Depending on your machine’s configuration, the User Account Control window could appear. 7. If the User Account Control window appears, click Yes to let the program make changes to the machine.
3. In the upper-left corner of the AppAssure Local Mount Utility window, click Add Core. 4. In the Add Core dialog box, enter the requested credentials described in the following table. Option Description Host name The name of the Core from which you want to mount recovery points. NOTE: If installing the LMU on a core, the LMU automatically adds the localhost machine. Port The port number used to communicate with the Core. The default port number is 8006.
2. From the main AppAssure Local Mount Utility window, expand the Core in the navigation tree to reveal the protected agents. 3. From the navigation tree, select the agent from which you want to mount a recovery point. The recovery points displays in the main frame. 4. Expand the recovery point you want to mount to reveal individual disk volumes or databases. Figure 7. Local Mount Utility - recovery points 5.
ii. Click Mount. The LMU automatically opens the folder containing the mounted recovery point. NOTE: If you select a recovery point that is already mounted, the Mounting dialog will prompt whether to dismount the recovery point. Exploring a Mounted Recovery Point Using the Local Mount Utility Complete the following procedure to explore a recovery point that has remained mounted from a previous session.
5. To minimize the LMU application, click the X in the upper-right corner of the Local Mount Utility window. 6. To close the LMU application, right-click the AppAssure Local Mount Utility icon in the LMU tray menu, and select Exit. About the Local Mount Utility Tray Menu The LMU tray menu is located in your desktop task bar. Right-click the icon to reveal the options described in the following table: Option Description Browse Recovery Points Opens the LMU main window.
Accessing Remote Core Options Complete the steps in this procedure to access remote core options. To access remote core options Right-click the AppAssure 5 Core or agent and then select one of the remote core options as described in the following table. Option Description Reconnect to core Refreshes and updates information from the Core, such as recently added agents. Remove core Deletes the Core from the Local Mount Utility.
Creating an Archive Complete the steps in this procedure to create an archive. To create an archive 1. Navigate to the AppAssure 5 Core, and then click the Tools tab. 2. From the Archive option, click Create. The Create Archive dialog box displays. 3. In the Create Archive dialog box, enter the details for the archive as described in the following table. Text Box Description Date range Select the to and from dates to specify the date range. Location Enter the location for the output.
3. In the Import Archive dialog box, enter the details for importing the archive as described in the following table. Text Box Description Location Select the location for importing the archive. User Name Enter a user name. It is used to establish logon credentials for the network share. Password Enter a password for the network path. It is used to establish logon credentials for the network share. 4. Click Check File to validate the existence of the archive to import.
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. 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.
Configuring Nightly SQL Attachability Checks and Log Truncation Complete the steps in this procedure to have the system perform nightly attachability checks for the SQL Server recovery points. To configure nightly SQL attachability checks and log truncation 1. In the left navigation area of the AppAssure 5 Core, select the machine for which you want to configure nightly attachability checks and log truncation. The Summary tab for the selected machine displays. 2. Click SQL Server Settings. 3.
Managing Exchange Database Mountability Checks and Log Truncation When using AppAssure 5 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 potential failures and ensures that all data on the Exchange servers will be recovered successfully in the event of a failure. The mountability checks and log truncation features only apply to Microsoft Exchange 2007, 2010, and 2013.
Forcing a Mountability Check Complete the steps in this procedure to force the system to perform a mountability check for a specific Exchange server recovery point. To force a mountability check 1. In the left navigation area of the AppAssure Core Console, select the machine for which you want to force the mountability check, and then click the Recovery Points tab. 2. Click the right angle bracket > symbol next to a recovery point in the list to expand the view. 3. Click Force Mountability Check.
Forcing Log Truncation Complete the steps in this procedure to force log truncation. This option is only available for Exchange or SQL machines. To force log truncation 1. Navigate to the AppAssure 5 Core Console and then click the Machines tab. 2. From the Machines tab, perform one of the following: Click the hyperlink for the machine you want to truncate the log. Or, in the navigation pane, select the machine you want to truncate the log. 3.
Recovery Status Point Colors for Exchange Databases The following table lists the status indicators that display for Exchange databases. 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.
This page intentionally left blank.
4 Protecting Workstations and Servers This chapter describes how to protect, configure, and manage the agent machines in your AppAssure environment.
About Protecting Workstations and Servers To protect your data using AppAssure 5, you need to add the workstations and servers for protection in the AppAssure 5 Core Console; for example, your Exchange server, SQL Server, your Linux server, and so on. In this chapter, generally the word machine also refers to the AppAssure Agent software installed on that machine.
Select the Machines tab, and in the Actions drop-down menu, click Protect Machine. The Connect dialog box displays. 3. In the Connect dialog box, enter the information about the machine to which you want to connect as described in the following table. Text Box Description Host The host name or IP address of the machine that you want to protect. Port The port number on which the AppAssure 5 Core communicates with the Agent on the machine. The default port number is 8006.
Text Box Description Initially pause protection Once you add a machine for protection, AppAssure 5 automatically begins the process of taking a base snapshot of data. You can select this check box to pause protection initially. You then need to force a snapshot manually when you are ready to start protecting your data. For more information, see “Forcing a Snapshot” on page 141. Volume Groups Under Volume Groups, you can define which volumes you want to protect, and establish a protection schedule.
To deploy agents when protecting an agent. 1. From the Connect dialog box, after entering the appropriate connection settings, click Connect. The Deploy Agent dialog box appears. 2. Click Yes to deploy the Agent software remotely to the selected machine. The Deploy Agent dialog box appears. 3. In the Deploy Agent dialog box, enter logon and protection settings as defined in the following table. Text Box Description Host name The host name or IP address of the machine that you want to protect.
The Deploy Agent dialog box closes. There may be a slight delay before you see the selected agent appear in the list of protected machines as the Agent software is deployed. You must reboot the agent machine after installing the Agent software. This ensures that the drivers load properly, allowing the AppAssure 5 Core to monitor file activity on the agent and ensure successful backups.
Modifying Exchange Server Settings If you are protecting data from a Microsoft Exchange server, you need to configure additional settings in the AppAssure 5 Core Console. To modify Exchange server settings 1. Once you have added the Exchange Server machine for protection, navigate to the AppAssure 5 Core Console and select the machine in the Navigation pane. The Summary tab displays for the machine. 2. From the Summary tab, click the Exchange Server Settings link.
4. You can also modify the logon credentials for SQL Server. To do so, scroll down to the SQL Server Information table and then click Change Credentials. The Set SQL Server Credentials dialog box appears. 5. Enter your new credentials, and then click OK. Pausing and Resuming Protection When you pause protection, you temporarily stop all transfers of data from the current machine. To pause and resume protection 1. In the AppAssure 5 Core Console, click the Machines tab. 2.
3. Click Change to modify the machine settings as described in the following table. Text Box Description Display Name Enter a display name for the machine. A name for this machine to be displayed in the AppAssure 5 Core Console. By default, this is the host name of the machine. You can change this to something more user-friendly if needed. Host Name Enter a host name for the machine. Port Enter a port number for the machine. The port is used by the Core to communicate with this machine.
Memory (Physical) Display Name Fully Qualified Domain Name Detailed information about the volumes contained on this machine also displays and includes: Processors Type of Processors Network Adapters IP Addresses associated with this machine Figure 8. System information Configuring Notification Groups for System Events In AppAssure 5, you can configure how system events are reported for your machine by creating notification groups.
2. From the Machines tab, perform one of the following: Click the hyperlink for the machine you want to modify. Or, in the navigation pane, select the machine you want to modify. The Summary Tab appears. 3. Click the Configuration tab, and then click Events. The Notification Groups page displays. 4. Click Use custom alert settings and then click Apply. The Custom Notification Groups screen appears. 5. Click Add Group to add new notification groups for sending a list of system events.
Text Box Description Enable Events Select which events to share with this notification group.
7. Click OK to save your changes. 8. To edit an existing notification group, click Edit next to the notification group that you want to edit. The Edit Notification Group dialog box displays for you to edit the settings. Editing Notification Groups for System Events Complete the steps in the following procedure to edit notification groups for system events. To edit notification groups for system events 1. Navigate to the AppAssure 5 Core Console and then click the Machines tab. 2.
Text Box Description Enable Events Select which events to share with the notification group. You can select All or select a subset of events to include: BootCd LocalMount Metadata Clusters Notification PowerShellScripting PushInstall Attachability Jobs Licensing LogTruncation Archive CoreService Export Protection Replication Repository Rollback Rollup You can also choose to select by type, which are: Info, Warning, and Error.
Customizing Retention Policy Settings The retention policy for a machine specifies how long the recovery points for an agent machine are stored in the repository. Retention policies are used to retain backup snapshots for longer periods of time and to help manage these backup snapshots. The retention policy is enforced by a rollup process that helps with aging and deleting old backups. This task is also a step in the “Process of Modifying Cluster Node Settings” on page 193.
5. Select Enable Rollup, and specify the time intervals for retaining the backup data as needed. The retention policy options are described in the following table. Text Box Description Keep all Recovery Points for n [retention time period] Specifies the retention period for the recovery points. Enter a number to represent the retention period and then select the time period. The default is 3. You can choose from: Days Weeks Months Years ...
Text Box Description ...and then keep one Recovery Point Provides a more granular level of retention. It is used per month for n [retention time period] as a building block to further define how long recovery points are maintained. Enter a number to represent the retention period and then select the time period. The default is 2. You can choose from: Months Years ...
3. Click the Configuration tab, and then click Licensing. The Status screen appears and presents the details about the product licensing. Modifying Protection Schedules In AppAssure 5, you can modify the protection schedules for specific volumes on a machine. To modify protection schedules 1. Navigate to the AppAssure 5 Core Console and then click the Machines tab. 2. From the Machines tab, perform one of the following: Click the hyperlink for the machine you want to modify.
4. In the Edit Protection Settings dialog box, click the Edit link next to the volume for which you want to customize the protection schedule. The Protection Schedule dialog box displays. Figure 11.
5. In the Protection Schedule dialog box, edit the following schedule options as needed for protecting your data. The following table describes the options. Text Box Description Interval Weekday. To protect data on a specific time interval (for example, every 15 minutes), select the Interval, and then: To customize when to protect data during peak times, you can select a Start Time, End Time, and an Interval from the drop-down menus.
Virtual Machine Export. Creates a virtual machine (VM) from a recovery point, containing all of the data from the backup of the protected machine, as well the operating system and drivers and associated data to ensure the VM is bootable. Rollback. Restores backup information to a protected machine. NOTE: The entire volume is always rewritten during rollback of Windows systems using EFI system partitions.
To modify transfer settings 1. On the AppAssure 5 Core Console, do one of the following: Click the Machines tab, and then click the hyperlink for the machine you want to modify. Or, in the navigation pane, click the machine you want to modify. 2. Click the Configuration tab, and then click Transfer Settings. The current transfer settings are displayed. 3. On the Transfer Settings page, click Change. The Transfer Settings dialog box displays. Figure 12.
4. Enter the Transfer Settings options for the machine as described in the following table. Text Box Description Priority Sets the transfer priority between protected machines. Enables you to assign priority by comparison with other protected machines. Select a number from 1 to 10, with 1 being the highest priority. The default setting establishes a priority of 5. NOTE: Priority is applied to transfers that are in the queue.
Text Box Description Excluded Writers Select a writer if you want to exclude it. Since the writers that appear in the list are specific to the machine you are configuring, you will not see all writers in your list.
Viewing Machine Logs If you encounter any errors or issues with the machine, it may be useful to view the logs. To view machine logs 1. Navigate to the AppAssure 5 Core Console and then click the Machines tab. 2. From the Machines tab, perform one of the following: Click the hyperlink for the machine you want to view. Or, in the navigation pane, select the machine you want to view. 3. Click the Tools tab, and then click Diagnostics. 4. Click the View Log link.
4. Click Verify to validate the credentials you entered. The Deploy Agent dialog box displays a message to indicate that validation is being performed. Click Abort if you want to cancel the verification process. After the verification process is complete, a message indicating that verification has been completed displays. 5. Click Deploy. A message indicating that the deployment has started displays. You can view the progress in the Events tab.
Text Box Description Encryption Key Specify whether encryption should be applied to the data for every volume on this machine stored in the repository. NOTE: The encryption settings for a repository are defined under the Configuration tab in the AppAssure 5 Core Console. Remote Core Specify a target core to which you want to replicate the agent machine. Remote Repository The name of the repository on the target core in which to store the replicated data from this machine.
3. In the Actions drop-down menu, click Remove Machines, and then select one of the option described in the following table. Option Description Keep Recovery Points Keeps all currently stored recovery points for this machine. Remove Recovery Points Removes all currently stored recovery points for this machine from the repository.
Setting Replication Priority for an Agent Complete the steps below to set the priority for when an agent replicates. To set replication priority for an agent 1. From the AppAssure 5 Core Console, select the protected machine for which you want to set replication priority, and click the Configuration tab. 2.
Viewing Machine Status and Other Details Complete the step in this procedure to view the status as well as other details for a machine. To view machine status and other details Open the AppAssure 5 Core Console, and do one of the following: Click the Machines tab, and then click the hyperlink for the machine you want to view. Or, in the navigation pane, click the machine you want to view. The Summary tab appears. Figure 13.
Used Space Free space If SQL Server is installed on the machine, detailed information about the server also displays and includes: Name Install Path Version Version Number Database Name Online status If Exchange Server is installed on the machine, detailed information about the server and mail stores also displays and includes: Version Install Path Data Path Name Exchange Databases Path Log File Path Log Prefix System Path MailStore Type Managi
Deploying to Multiple Machines You can simplify the task of deploying the AppAssure Agent software to multiple Windows machines by using the Bulk Deploy feature of AppAssure 5. From within the Core Console, you can specifically bulk deploy to: Machines on an Active Directory domain Machines on a VMware vCenter/ESX(i) virtual host Machines on any other host The Bulk Deploy feature automatically detects machines on a host and allows you to select those to which you want to deploy.
5. On the Add Machines from Active Directory dialog box, select the machines to which you want to deploy the AppAssure 5 Agent, and then click Add. Figure 14. Add Machines from Active Directory d ialog box The machines you added appear on the Deploy Agent to Machines window. 6. To enter the password for the machine, select a repository, add an encryption key, or edit other settings for a machine, click the Edit link for that machine, and then do the following: a.
Text Box Description Automatic reboot after install Specify whether you want to automatically reboot the machine after deployment. NOTE: This option is mandatory and selected by default if you want to automatically protect the machine after deployment by selecting Protect machine after install. Protect machine after install Specify whether you want to automatically protect the machine after deployment. (This allows you to skip “Protecting Multiple Machines” on page 129.
Deploying to Machines on a VMware vCenter/ESX(i) Virtual Host Before starting this procedure, you must have the host location information and logon credentials for the VMware vCenter/ESX(i) virtual host. All virtual machines must have VM Tools installed; otherwise, AppAssure 5 cannot detect the host name of the virtual machine to which to deploy. In lieu of the host name, AppAssure 5 uses the virtual machine name, which may cause issues if the host name is different from the virtual machine name.
5. In the Deploy Agent on Machines window, you should see the machines that you added. If you want to select a repository, encryption key, or other settings for a machine, such as automatically rebooting the machine once the software is installed, select the machine and click Edit. For details on each setting, see “Deploying to Machines on an Active Directory Domain” on page 122. 6. Verify that AppAssure 5 can connect to each machine successfully.
2. On the Deploy Agent on Machines window, do one of the following: Click New to enter a new machine host, logon credentials, repository, encryption key, and other information. For details on each setting, see “Deploying to Machines on an Active Directory Domain” on page 122. After you enter this information, click OK to add it to the Deploy Agent on Machines list, or click OK & New to add another machine.
4. Verify that AppAssure 5 can connect to each machine successfully. To do this, select each machine in the Deploy Agent on Machines window, and click Verify. The Deploy Agent on Machines window shows an icon next to each machine that reflects its readiness for deployment, as follows: Green icon - AppAssure 5 is able to connect to the machine and it is ready to be deployed.
Protecting Multiple Machines After bulk deploying the AppAssure 5 Agent software to your Windows machines, you will need to protect the machines to protect the data. If you selected Protect Machine After Install when you deployed the Agent, you can skip this step. Agent machines must be configured with a security policy that makes remote installation possible. To protect multiple machines 1. Navigate to the AppAssure 5 Core Console, click the Tools tab, and then click Bulk Protect.
3. Once you have added the machines for protection, in the Protect Machines window, you should see the newly added machines. If you want to select a repository, encryption key, or other advanced settings for a machine, select the machine and click Edit. 4. Specify the settings as follows and click OK. Text Box Description User name The user name used to connect to this machine; for example, Administrator. Password The secure password used to connect to this machine.
Monitoring the Protection of Multiple Machines You can monitor the progress as AppAssure 5 applies the protection polices and schedules to the machines. To monitor the protection of multiple machines 1. Click the Machines tab to view the status and progress of the protection. The Protected Machines page displays. Figure 18.
2. Click the Events tab to view related tasks and alerts. The Events tab displays, showing Task and Alert events. As volumes are transferred, the status, start times, and end times display in the Tasks pane. As each protected machine is added, an alert is logged on the Events tab, which lists whether the operation was successful or if errors were logged. Figure 19. Events tab - Tasks and Alerts 3.
Progress Phase Failure Reason, if applicable 2. Click Open in New window to launch a new window to view the progress of the protection. Or, click Close to close the window; the task will process in the background. To view alert information In the Alerts pane, you will see an alert as each protected machine is added. This alert lists whether the operation was successful, any errors that occurred, the level of the alert, the transactional date, and the related message.
To view recovery points In the left navigation area of the AppAssure Core Console, select the machine for which you want to view recovery points, and then click the Recovery Points tab. Figure 20. Recovery Points tab You can view information about the recovery points for the machine as described in the following table. Info Description Status Indicates current status of the recovery point. Encrypted Indicates if the recovery point is encrypted.
To view a specific recovery point 1. In the left navigation area of the AppAssure Core Console, select the machine for which you want to view recovery points, and then click the Recovery Points tab. 2. Click the right angle bracket > symbol next to a recovery point in the list to expand the view. Figure 21.
3. Click the right angle bracket > symbol next to a volume in the selected recovery point to expand the view. You can view information about the selected volume in the expanded recovery point as described in the following table. Text Box Description Title Indicates the specific volume in the recovery point. Raw Capacity Indicates the amount of raw storage space on the entire volume.
2. In the Mount Recovery Point dialog box, edit the text boxes for mounting a recovery point as described in the following table. Option Description Mount Location: Local Folder Specify the path used to access the mounted recovery point.
2. From the Tools option, click System Info. 3. In the Local Mounts section, click Dismount All. Mounting a Recovery Point Volume on a Linux Machine In AppAssure you can remotely mount a restored volume to the local disk from a recovery point for a Linux machine. When performing this procedure, do not attempt to mount recovery points to the /tmp folder, which contains the aavdisk files. To mount a recovery point volume on a Linux machine 1.
8. Enter the following command to select and mount the specified recovery point at the specified mount point/path. m NOTE: You can also specify a line number in the command instead of the recovery point ID number to identify the recovery point.
To remove recovery points 1. In the left navigation area of the AppAssure 5 Core Console, select the machine for which you want to view recovery points, and then click the Recovery Points tab. 2. Click the Actions menu. Figure 22. Recovery Points tab - machine status and other information 3. Select one of the following options: To delete all currently stored recovery points, click Delete All. To delete a set of recovery points in a specific data range, click Delete Range.
For more information about forcing a base image, see “Forcing a Snapshot” on page 141. The ability to delete an orphaned recovery point chain is not available for replicated recovery points on a target core. To delete an orphaned recovery point chain 1. On the AppAssure 5 Core Console, click the protected machine for which you want to delete the orphaned recovery point chain. 2. Click the Recovery Points tab. 3. Under Recovery Points, expand the orphaned recovery point.
2. Click the Actions drop-down menu for that machine, click Force Snapshot, and then select one of the options described in the following table. Option Description Force Snapshot Takes an incremental snapshot of data updated since the last snapshot was taken. Force Base Image Takes a complete snapshot of all data on the volumes of the machine. 3. When notification appears in the Transfer Status dialog box that the snapshot has been queued, click OK.
The following diagram shows a typical deployment for exporting data to a virtual machine. Figure 23. Virtual standby deployment You create a virtual standby by continuously exporting protected data from your Windows machine to a virtual machine (VMware, ESXi, and Hyper-V). When you export to a virtual machine, all of the backup data from a recovery point as well as the parameters defined for the protection schedule for your machine will be exported.
Non-simple dynamic volumes have arbitrary disk geometries that cannot be fully interpreted and therefore AppAssure cannot export them. Neither Replay 4.x nor AppAssure 5.x has the ability to export complex or non-simple dynamic volumes. AppAssure does not support exporting non-simple or complex dynamic volumes. Notification appears in the user interface to alert you that exports are limited and restricted to simple dynamic volumes.
Performing a One-Time ESXi Export You can choose to perform a one-time export for ESXi. Complete the steps in this procedure to perform a one-time export. To perform a one-time ESXi export 1. In the AppAssure 5 Core Console, click the Machines tab. 2. In the list of protected machines, select the machine or cluster with the recovery point that you want to export. 3. In the Actions drop-down menu for that machine, click Export, and then select ESX(i) Export. The Select Export Type dialog box displays. 4.
2. In the list of protected machines, select the machine or cluster with the recovery point that you want to export. 3. In the Actions drop-down menu for that machine, click Export, and then select ESX(i) Export. The Select Export Type dialog box displays. 4. In the Select Export Type dialog box, click Continuous (Virtual Standby). 5. Click Next. The Virtual Standby Recovery Point to VMware vCenter Server/ESXi dialog box displays. 6.
Exporting Windows Data using VMware Workstation Export In AppAssure 5, you can choose to export data using VMware Workstation Export by performing a one-time or continuous export. Complete the steps in the following procedures to export using VMware Workstation Export for the appropriate type of export. Performing a One-Time VMware Workstation Export You can choose to perform a one-time export for VMware Workstation Export. Complete the steps in this procedure to perform a one-time export.
To define one-time settings for performing a VMware Workstation export 1. From the Virtual Standby Recovery Point to VMware Workstation/Server dialog box, enter the parameters for accessing the virtual machine as described in the following table. Option Description Target Path Specify the path of the local folder or network share on which to create the virtual machine.
Performing a Continuous (Virtual Standby) VMware Workstation Export You can choose to perform a continuous export for VMware Workstation Export. Complete the steps in this procedure to perform a continuous export. To perform a continuous (virtual standby) VMware Workstation export 1. In the AppAssure 5 Core Console, click the Machines tab. 2. In the list of protected machines, select the machine or cluster with the recovery point that you want to export. 3.
8. In the Options pane, enter the information for the virtual machine and memory usage as described in the following table. Text Box Option Virtual Machine Enter a name for the virtual machine being created; for example, VM0A1B2C3D4. NOTE: The default name is the name of the source machine. Memory Specify the memory for the virtual machine. Click Use the same amount of RAM as the source machine to specify that the RAM configuration is the same as the source machine.
Defining One-Time Settings for Performing a Hyper-V Export Complete the steps in this procedure to define the settings for performing a onetime Hyper-V export. To define one-time settings for performing a Hyper-V export 1. From the Hyper-V dialog box, click Use local machine to perform the Hyper-V export to a local machine with the Hyper-V role assigned. 2. Click the Remote host option to indicate that the Hyper-V server is located on a remote machine.
Performing a Continuous (Virtual Standby) Hyper-V Export You can choose to perform a continuous export for Hyper-V. Complete the steps in this procedure to perform a continuous export. To perform a one-time Hyper-V export 1. In the AppAssure 5 Core Console, click the Machines tab. 2. In the list of protected machines, select the machine or cluster with the recovery point that you want to export. 3. In the Actions drop-down menu for that machine, click Export, and then select Hyper-V Export.
9. Select the Options tab and then enter the name for the virtual machine in the Virtual Machine Name text box. The name you enter appears in the list of virtual machines in the Hyper-V Manager console. 10. Do one of the following: Click Use the same amount of RAM as the source machine to identify that the RAM use is identical between the virtual and source machines. Click Use a specific amount of RAM to specify how much memory the virtual machine should have after the export; for example, 4096 MB.
3. Click Load Volumes. The Volume Mapping dialog box displays. NOTE: The Core console does not automatically map Linux volumes. To locate a Linux volume, browse to the volume that you want to roll back. 4. Select the volumes that you want to roll back. 5. Using the Destination drop-down lists, select the destination volume to which the selected volume should roll back. 6. Select the options as described in the following table.
To perform a rollback for a volume on a Linux machine 1. Run the AppAssure aamount utility as root, for example: sudo aamount 2. At the AppAssure mount prompt, enter the following command to list the protected machines. lm 3. When prompted, enter the IP address or hostname of your AppAssure Core server. 4. Enter the logon credentials, that is, the user name and password, for this server. A list displays showing the machines protected by this AppAssure server.
7. When prompted to proceed, enter y for Yes. Once the rollback proceeds, a series of messages will display to notify you of the status. 8. Upon a successful rollback, the aamount utility will automatically mount and re- attach the kernel module to the rolled back volume if the target was previously protected and mounted. If not, you will need to mount the rollback volume to the local disk and then should verify that the files are restored.
Examples of performing a BMR for similar hardware include replacing the hard drive of the existing system, or swapping out the failed server with an identical machine. Examples of performing a BMR for dissimilar hardware include restoring a failed system with a server produced by a different manufacturer or with a different configuration.
In all cases, you will need to load the boot image into the destination server and start the server from the boot image. See “Loading the Boot CD and Starting the Target Machine” on page 163. Launch a Bare Metal Restore for Windows. Once the destination machine is started from the boot CD, you can launch the BMR. See “Launching a Bare Metal Restore for Windows” on page 164. You will need to initiate rollback from a recovery point on the Core.
Storage space and partitions, as appropriate. Ensure that there is enough space on the hard drive to create destination partitions on the target machine to contain the source volumes. Any destination partition should be at least as large as the original source partition. Compatible partitions. Windows 8 and Windows Server 2012 operating systems that are booted from FAT32 EFI partitions are not available for protection or recovery, nor are Resilient File System (ReFS) volumes.
The boot CD ISO image that you create is tailored to the machine being restored; therefore, it must contain the correct network and mass storage drivers. If you anticipate that you will be restoring to different hardware from the machine on which the recovery point originated, then you must include storage controller and other drivers in the boot CD. For information about injecting those drivers in the boot CD, see “Injecting Drivers in a Boot CD” on page 161.
Naming the Boot CD File and Setting the Path Complete the following step to name the boot CD file and set the path where the ISO image is stored. To name the boot CD file and set the path In the Create Boot CD dialog box, in Output Options, in the Output path text box, enter the path where you want to store the boot CD ISO image on the Core server. If the shared drive on which you want to store the image is low on disk space, you can set the path as needed; for example, D:\filename.iso.
Data restored from the recovery point includes drivers for the hardware previously in place. If performing a bare metal restore to dissimilar hardware, then you must also inject storage controller drivers into the operating system being restored using the URC after the data has been restored to the drive, This allows the restored operating system to boot using the new set of hardware.
Accessing the ISO Image Complete the following step to access the ISO image. To access the ISO image To access the ISO image, navigate to the output path you specified, or you can click the link to download the image to a location from which you can then load it on the new system; for example, network drive. Transferring the Boot CD ISO Image to Media When you create the boot CD file, it is stored as an ISO image in the path you specified.
AppAssure 5 Agent software The AppAssure Universal Recovery Console starts and displays the IP address and authentication password for the machine. NOTE: A new temporary password is generated each time the machine is started with the boot CD. Write down the IP address displayed in the Network Adapters Settings pane and the authentication password displayed in the Authentication pane. You will need this information later during the data recovery process to log back on to the console. 3.
Selecting a Recovery Point and Initiating Rollback for BMR Once the Universal Recovery Console is accessible on the machine on which you want to perform a BMR, you must select the recovery point that you want to restore. Navigate to the Core Console to select which recovery point you want to load, and designate the recovery console as the destination for the restored data. This step is required to perform BMR on all Windows machines and optional to perform BMR on Linux machines.
6. Enter the information about the machine to which you want to connect as described in the following table, and then click Load Volumes. Text Box Description Host The IP address of the machine to which you want to restore. This is identical to the IP address you wrote down from the URC Console. Password The specific password to connect to the selected server. This is identical to the Current Password shown in the URC Console.
To map volumes for a bare metal restore 1. If you want to map volumes automatically, do the following. If you want to map volumes manually, proceed to Step 2 a. In the RollbackURC dialog box, select the Automatically Map Volumes tab. b. In the Disk Mapping area, under Source Volume, verify that the source volume is selected, and that the appropriate volumes are listed beneath it and are selected.
If you are unsure which drivers are required by your target server, click the System Info tab in the Universal Recovery Console. This tab shows all system hardware and device types for the target server to which you want to restore. Your target server automatically contains some generic Windows 7 PE 32-bit drivers which will work for some systems. This task is a step in “Roadmap for Performing a Bare Metal Restore for a Windows Machine” on page 157.
Viewing the Recovery Progress Complete the steps in this procedure to view the recovery progress of a rollback initiated from the AppAssure 5 Core Console. This task is a step in “Roadmap for Performing a Bare Metal Restore for a Windows Machine” on page 157. It is part of the process for “Verifying a Bare Metal Restore” on page 168. To view the recovery progress 1. After you initiate the rollback process, the Active Task dialog box appears, showing that the rollback action initiated.
Troubleshooting Connections to the Universal Recovery Console The following are troubleshooting steps for connecting to the boot CD image as part of the process for “Selecting a Recovery Point and Initiating Rollback for BMR” on page 165. This task is a step in “Roadmap for Performing a Bare Metal Restore for a Windows Machine” on page 157. It is part of the process for “Verifying a Bare Metal Restore” on page 168.
Roadmap for Performing a Bare Metal Restore on Linux Machines In AppAssure 5 you can perform a Bare Metal Restore (BMR) for a Linux machine, including rollback of the system volume. When you restore a Linux machine, you will roll back to the boot volume recovery point. BMR functionality is supported using the command line aamount utility and from within the Core Console UI. To perform a bare metal restore for Linux machines, perform the following tasks. Manage a Linux boot image.
Verifying a Bare Metal Restore. After starting the bare metal restore, you can verify and monitor your progress. See “Verifying the Bare Metal Restore from the Command Line” on page 182. You can monitor the progress of your restore. See “Viewing the Recovery Progress” on page 169. Once completed, you can start the restored server. See “Starting a Restored Target Server” on page 169. Troubleshoot the BMR process.
Managing a Linux Boot Image A bare metal restore for Linux requires a Live DVD boot image, which you download from the license portal. You will use this image to start the destination Linux machine. Based on the specifics of your environment you may need to transfer this image to physical media such as a CD or DVD. You must then virtually or physically load the boot image, and start the Linux server from the boot image. The Live DVD was previously known as the Live CD.
This task is a step in “Roadmap for Performing a Bare Metal Restore for a Windows Machine” on page 157. It is part of the process for “Managing a Linux Boot Image” on page 173. Complete the steps in this procedure to download the Live DVD ISO image. To download a Boot ISO image for Linux 1. Log into the License Portal at https://licenseportal.com. 2. Access the Downloads area. 3. Scroll down to Linux Based Applications and, from the Linux Live CD section, click Download. 4. Save the Live DVD ISO image.
To load a Live DVD and start the target machine 1. Navigate to the new server and load the Live DVD image from the appropriate location. Specify that the server will start from the Live DVD image. 2. Start the machine. An AppAssure splash screen displays and a terminal window opens, displaying the IP address and authentication password for the machine. NOTE: A new temporary password is generated each time the machine is started with the Live DVD image. 3.
This task is a step in “Roadmap for Performing a Bare Metal Restore on Linux Machines” on page 171. It is part of the process for “Managing Linux Partitions” on page 175. To create partitions on the destination drive 1. Optionally, you can start the Screen utility. Once started, it remains active until you reboot the machine. NOTE: For more information, see “Starting the Screen Utility” on page 178. 2.
Mounting Partitions from the Command Line If performing a BMR using the AppAssure 5 Core Console, you must first mount the appropriate partitions on the destination machine. Perform this from the command line in the Universal Recovery Console. This task is a step in “Roadmap for Performing a Bare Metal Restore on Linux Machines” on page 171. It is part of the process for “Managing Linux Partitions” on page 175.
“Selecting a Recovery Point and Initiating Rollback for BMR” on page 165 “Mapping Volumes for a Bare Metal Restore” on page 166 “Selecting a Recovery Point and Initiating Rollback for BMR” on page 165 If restoring from the command line using the aamount utility, then you must first set appropriate privileges, mount volumes, execute aamount, obtain information about the Core from the list of machines, connect to the core, obtain a list of recovery points, select the recovery point you want to rol
Launching a Bare Metal Restore for a Linux Machine using the Command Line Once the Live DVD ISO image is accessible on the machine on which you want to perform a BMR, and the number and size of volumes matches between the target machine and the recovery point you want to restore to bare metal, then you can launch a restore from the command line using the aamount utility.
6. When prompted, enter the connection information for the AppAssure 5 Core as described in the following table, pressing Enter after each required command: Text Box Description Required AppAssure Core IP address or hostname The IP address or hostname of the AppAssure 5 Core. Yes Domain The domain of the AppAssure 5 Core. This is optional. No User The user name for an administrative user on the Core Yes Password The password used to connect the administrative user to the Core.
Size of the recovery point An ID number for the volume that includes a sequence number at the end, which identifies the recovery point Figure 25. List of recovery points 8. To select the recovery point for rollback, enter the following command and then press Enter: r You must ensure that the system volume is not mounted. If you started the machine from the Live DVD, then the system volume is not mounted.
You can also specify a line number in the command instead of the recovery point ID number to identify the recovery point. In that case, use the agent/machine line number (from the lm output), followed by the recovery point line number and volume letter (from the lettered list of volumes within the recovery point), followed by the path.
To perform a file system check on the restored volume 1. From the command line in the Universal Recovery Console of the Linux machine you have restored, to verify whether the appropriate partitions are mounted, type the following command and then press Enter: df 2. If the restored volume is not mounted, then skip to Step 3. If the restored volume is mounted, unmount it by typing the following command and then pressing Enter: umount 3.
To create bootable partitions on a Linux machine by using the command line 1.
5. Now you must delete the existing bitmap store by typing the following command and then press Enter: rm -rf /.blksnap/bitmap For example, if your restored volume was mounted to /mnt/sda1, then type the following command and then press Enter: rm -rf /mnt/sda1/.blksnap/bitmap 6.
13. Obtain the UUID of mount /etc/mtab and compare it to the UUIDs for the root (for Ubuntu and CentOS) and boot (for CentOS and RHEL) volumes by typing the following command and then press Enter: less /mnt/etc/mtab 14. If performing a BMR on a brand new disk on the destination machine, comment out the swap partition in fstab in your root volume. 15. Modifying fstab and mtab paths should occur on the restored volume, not the Live CD. There is no need to modify paths on the Live CD.
To view events for all machines managed by a core, in the Core Console, click the Events tab. To view events for a specific machine, in the AppAssure 5 Core Console, navigate to the machine for which you want to view events, and click the Events tab. The Events tab displays a log of all events. The contents of the Events tab is divided into two sections, Tasks and Alerts, for you to view details about task and alert events respectively. 2.
This page is intentionally left blank.
5 Protecting Server Clusters This chapter describes how to protect information on Microsoft SQL Server or Exchange Server clusters using AppAssure 5.
You can easily configure an AppAssure 5 Core to protect and manage a cluster. In the Core Console, a cluster is organized as a separate entity, which acts as a ‘container’ to include the related nodes. For example, in the left navigation area, the Core is listed at the top of the navigation tree, and then clusters are listed under the Core and contain the associated individual nodes (on which the AppAssure Agents are installed).
Protecting a Cluster This topic describes how to add a cluster for protection in AppAssure 5. When you add a cluster to protection, you need to specify the host name or IP address of the cluster, the cluster application, or one of the cluster nodes or machines that includes the AppAssure 5 Agent. A repository is used to store the snapshots of data that are captured from your protected nodes.
b. In the Volumes dialog box, select the volume(s) to protect, and then click Edit. c. In the Protection Schedule dialog box, select one of the schedule options for protecting your data as described in the following table. Text Box Description Interval You can choose from: Weekday. To protect data on a specific interval, select Interval, and then: To customize when to protect data during peak times, you can specify a start time, end time, and an interval.
3. In the Protect Cluster Node dialog box, select or enter as appropriate the following information, and then click Connect to add the machine or node. Text Box Description Host A drop-down list of nodes in the cluster available for protection. Port The port number on which the AppAssure 5 Core communicates with the Agent on the node. User name The user name of the domain administrator used to connect to this node; for example, example_domain\administrator or administrator@example_domain.com.
1. Do one of the following. Navigate to the cluster that contains the node you want to modify, click the Machines tab, and select the machine or node that you want to modify. Or, from the Navigation pane, under the Cluster heading, select the machine or node you want to modify. 2. To modify and view configuration settings, see “Viewing and Modifying Configuration Settings” on page 98. 3.
In the Core Console, click the Machines tab, and then select the cluster you wish to modify. Or, in the left navigation area, select the cluster you wish to modify. 2. Click the Configuration tab. The Settings page displays. 3. Click Edit to modify the settings on this page for the cluster as described in the following table. Text Box Description Display Name Enter a display name for the cluster. The name for this cluster displays in the AppAssure 5 Core Console.
4. If you selected Custom alert settings, do the following: a. Click Add Group to add a new notification group for sending a list of system events. The Add Notification Group dialog box opens. b. Add the notification options as described in the following table. Text Box Description Name Enter a name for the notification group. Description Enter a description for the notification group. Enable Events Select the events for notification, for example, Clusters.
In the Core Console, click the Machines tab, and then select the cluster you wish to modify. Or, in the left navigation area, select the cluster you wish to modify. 2. Click the Configuration tab, and then click Retention Policy. 3. Select one of the options in the following table. Option Description Use Core default retention policy This adopts the settings used by the associated core. Click Use Custom retention policy Apply. This lets you configure custom settings.
Rollback. Restores backup information for a protected cluster. To modify cluster transfer settings 1. Do one of the following: In the Core Console, click the Machines tab, and then select the cluster you wish to modify. Or, in the left navigation area, select the cluster you wish to modify. 2. Click the Configuration tab, and then click Transfer Settings. 3. Modify the protection settings as described in “Modifying Protection Schedules” on page 108, beginning with Step 2.
In the Core Console, click the Machines tab, and then select the cluster you wish to view. Or, in the left navigation area, select the cluster you wish to view. 2. Click the Tools tab. The system information page displays to show system details about the cluster such as name, included nodes with associated state and Windows versions, network interface information, and volume capacity information.
For information about viewing summary and status information for an individual machine or node in the cluster, see “Viewing Machine Status and Other Details” on page 120. Working with Cluster Recovery Points A recovery point, also referred to as a snapshot, is a point-in-time copy of the folders and files for the shared volumes in a cluster, which are stored in the repository. Recovery points are used to recover protected machines or to mount to a local file system.
Managing Snapshots for a Cluster In AppAssure 5, you can manage snapshots by forcing a snapshot or by pausing current snapshots. Forcing a snapshot lets you force a data transfer for the currently protected cluster. When you force a snapshot, the transfer starts immediately or will be added to the queue. Only the data that has changed from a previous recovery point transfers. If there is no previous recovery point, all data (the base image) on the protected volumes is transferred.
3. In the Pause Protection dialog box, select one of the options described in the following table. Option Description Pause until resumed Pauses the snapshot until you manually resume protection. To resume protection, click the Actions menu and then click Resume. Pause for Lets you specify an amount of time in days, hours, and minutes to pause snapshots. Dismounting Local Recovery Points Complete the steps in this procedure to dismount recovery points that are mounted locally.
2. Perform a rollback using the standard AppAssure procedure for the machine as described in “Performing a Rollback” on page 153 and “Performing a Rollback for a Linux Machine by Using the Command Line” on page 154. 3. When the rollback is finished, mount all databases for the cluster volumes. 4. Turn on all other nodes. 5. For Exchange, navigate to the Exchange Management Console, and, for each database, perform the Update Database Copy operation.
Removing a Cluster from Protection Complete the steps in the following procedure to remove a cluster from protection. To remove a cluster from protection 1. Do one of the following: In the Core Console, click the Machines tab, and then select the cluster you wish to remove. Or, in the left navigation area, select the cluster you wish to remove to view the Summary tab. 2. Click the Actions drop-down menu, and then click Remove Machine. 3. Select one of the following options.
Removing All Nodes in a Cluster from Protection Complete the steps in this procedure to remove all nodes in a cluster from protection. To remove all nodes in a cluster from protection 1. Do one of the following. In the Core Console, click the Machines tab, and select the cluster that contains the nodes you wish to remove. Then, click the Machines tab for the cluster. Or, from the left navigation area, select the cluster that contains the nodes you want to remove, and then click the Machines tab. 2.
3. In the Start Time drop-down calendar, select a start date, and then enter a start time for the report. NOTE: No data is available before the time the AppAssure 5 Core or Agent was deployed. 4. In the End Time drop-down calendar, select an end date, and then enter an end time for the report. 5. Click Generate Report. The report results appear in the page. If the report spans multiple pages, you can click the page numbers or the arrow buttons at the top of the report results to page through the results.
6 Reporting This chapter provides an overview of reporting available in AppAssure 5.
About the Reports Toolbar The toolbar available for all reports lets you print and save in two different ways. The following table describes the print and save options. Icon Description Print the report Print the current page Export a report and save it to the disk Export a report and show it in a new window Use this option to copy, paste, and email the URL for others to view the report with a Web browser.
Time Total Work For information about how to generate a report, see “Generating a Report for a Core or Agent” on page 210. About Errors Reports Errors Reports are subsets of the Compliance Reports and are available for AppAssure 5 Cores and AppAssure 5 Agents. Errors Reports include only the failed jobs listed in Compliance Reports and compile them into a single report that can be printed and exported.
Details about the repositories are presented in a column view with the following categories: Name Data Path Metadata Path Allocated Space Used Space Free Space Compression/Dedupe Ratio Agents Summary The Agents portion of the Core Summary Report includes data for all agents protected by the selected AppAssure 5 Core.
4. In the left navigation area, select the report you want to run. The reports available depend on the selection you made in Step 1 and are described in the following table. Machine Available Reports Core Compliance Report Summary Report Errors Report Agent Compliance Report Errors Report 5. In the Start Time drop-down calendar, select a start date, and then enter a start time for the report. NOTE: No data is available before the time the Core or the Agent was deployed. 6.
To generate a report from the Central Management Console 1. From the Central Management Console Welcome screen, click the drop-down menu in the upper-right corner. 2. From the drop-down menu, click Reports and then select one of the following options: Compliance Report Summary Report Errors Report 3. From the left navigation area, select the AppAssure 5 Core or Cores for which you want to run the report. 4.
A Scripting This appendix describes the scripts that can be used by administrators at designated occurrences in AppAssure 5 for Windows and Linux.
About PowerShell Scripting in AppAssure 5 Windows PowerShell is a Microsoft .NET Framework-connected environment designed for administrative automation. AppAssure 5 includes comprehensive client software development kits (SDKs) for PowerShell scripting that lets administrative users execute user-provided PowerShell scripts at designated occurrences; for example, before or after a snapshot, attachability and mountability checks, and so on.
Testing PowerShell Scripts If you want to test the scripts you plan to run, you can do so by using the PowerShell graphical editor, powershell_is. You also need to add the configuration file, powershell_ise.exe.config to the same folder the configuration file, powershell.exe.config. The configuration file, powershell_ise.exe.config must have the same content as that of the powershell.exe.config file. If the pre-PowerShell or post-PowerShell script fails, the job also fails.
AgentTransferConfiguration (namespace Replay.Common.Contracts.Transfer) The following table presents the available objects for the AgentTransferConfiguration parameter. Method Description public uint MaxConcurrentStreams { get; set; } Gets or sets the maximum number of concurrent TCP connections the Core establishes to the agent for transferring data.
Method Description public TimeSpan TransferTimeout { get; set; } Gets or sets the amount of time to wait for further contact from the Core before abandoning the snapshot. public TimeSpan NetworkReadTimeout { get; set; } Gets or sets the timeout for network read operations related to this transfer. public TimeSpan NetworkWriteTimeout { get; set; } Gets or sets the timeout for network write operations related to this transfer. BackgroundJobRequest (namespace Replay.Core.Contracts.
NightlyAttachabil ityJobRequest (namespace Replay.Core.Contracts.Sql) Inherits its values from the parameter, BackgroundJobRequest. RollupJobRequest (namespace Replay.Core.Contracts.Rollup) Inherits its values from the parameter, BackgroundJobRequest. TakeSnapshotResponse (namespace Replay.Agent.Contracts.Transfer) The following table presents the available objects for the TakeSnapshotResponse parameter.
Method Description public bool ForceBaseImage { get; set; } Gets or sets the value indicating whether the base image was forced or not. public bool IsLogTruncation { get; set; } Gets or sets the value indicating whether the job is log truncation or not. TransferPrescriptParameter (namespace Replay.Common.Contracts.PowerShellExecution) The following table presents the available objects for the TransferPrescript parameter.
Method Description public AgentTransferConfiguration TransferConfiguration { get; set; } Gets or sets the transfer configuration.
Method public AgentTransferConfiguration TransferConfiguration { get; set; } (cont.) Description ExcludedWriterIds - collection of VSS writer IDs which should be excluded from this snapshot. The writer ID is keyed by the name of the writer. This name is for documentation purposes only and does not have to exactly match the actual name of the writer.
TransferPostscriptParameter (namespace Replay.Common.Contracts.PowerShellExecution) The following table presents the available objects for the TransferPostscript parameter. Method Description public VolumeNameCollection VolumeNames (get; set; ) Gets or sets the collection of volume names for transfer. VolumeNames is a data structure that contains the following data: GuidName - The Guid associated with the volume, used as the name if a DisplayName is not set.
Method Description public AgentTransferConfiguration TransferConfiguration { get; set; } Gets or sets the transfer configuration.
Method Description public AgentTransferConfiguration TransferConfiguration { get; set; } (cont.) ExcludedWriterIds - collection of VSS writer IDs which should be excluded from this snapshot. The writer ID is keyed by the name of the writer. This name is for documentation purposes only and does not have to exactly match the actual name of the writer.
Method Description public uint LatestEpochSeenByCore { get; set; } Gets or sets latest epoch value. The LatestEpochSeenByCore method is the ordinal number of the most recent snapshot taken by the Core. This is the 'epoch number' assigned by the filter driver to this particular snapshot at the moment it was taken with VSS. public Guid SnapshotSetId { get; set; } Gets or sets the GUID assigned by VSS to this snapshot.
VolumeNameCollection (namespace Replay.Common.Contracts.Metadata.Storage) Inherits its values from the parameter, System.Collections.ObjectModel.Collection. The following table presents the available objects for the VolumeNameCollection parameter. Method Description public override bool Equals(object obj) Determines whether this instance and a specified object, which must also be a VolumeNameCollection object, have the same value. (Overrides Object.Equals(Object).
PreTransferScript.ps1 The PreTransferScript is executed on the agent side prior to transferring a snapshot. Sample PreTransferScript # receiving parameter from transfer job param([object]$TransferPrescriptParameter) # building path to Agent's Common.Contracts.dll and loading this assembly $regLM = [Microsoft.Win32.Registry]::LocalMachine $regLM = $regLM.OpenSubKey('SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ap pRecovery Agent 5') $regVal = $regLM.
Sample PostTransferScript # receiving parameter from transfer job param([object] $TransferPostscriptParameter) # building path to Agent's Common.Contracts.dll and loading this assembly $regLM = [Microsoft.Win32.Registry]::LocalMachine $regLM = $regLM.OpenSubKey('SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ap pRecovery Agent 5') $regVal = $regLM.GetValue('InstallLocation') $regVal = $regVal + 'Common.Contracts.dll' [System.Reflection.
PreExportScript.ps1 The PreExportScript is executed on the Core side prior to any export job. Sample PreExportScript # receiving parameter from export job param([object]$ExportJobRequest) # building path to Core's Common.Contracts.dll and loading this assembly $regLM = [Microsoft.Win32.Registry]::LocalMachine $regLM = $regLM.OpenSubKey('SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ap pRecovery Core 5') $regVal = $regLM.GetValue('InstallLocation') $regVal = $regVal + 'CoreService\Common.Contracts.
PostExportScript.ps1 The PostExportScript is executed on the Core side after any export job. NOTE: There are no input parameters for the PostExportScript when used to execute once on the exported agent after initial startup. The regular agent should contain this script in the PowerShell script folder as PostExportScript.ps1. Sample PostExportScript # receiving parameter from export job param([object]$ExportJobRequest) # building path to Core's Common.Contracts.
PreNightlyJobScript.ps1 The PreNightlyJobScript is executed before every nighty job on Core side. It has $JobClassName parameter, that helps to handle those child jobs separately. Sample PreNightlyJobScript # receiving parameters from Nightlyjob param([System.String]$JobClassMethod , [object]$NightlyAttachabilityJobRequest, [object]$RollupJobRequest, [object]$Agents, [object]$ChecksumCheckJobRequest, [object]$TransferJobRequest, [int]$LatestEpochSeenByCore) # building path to Core's Common.Contracts.
echo 'AgentId:' $NightlyAttachabilityJobRequestObject.AgentId; echo 'IsNightlyJob:' $NightlyAttachabilityJobRequestObject.IsNightlyJob; } break; } # working with Rollup Job RollupJob { $RollupJobRequestObject = $RollupJobRequest -as [Replay.Core.Contracts.Rollup.RollupJobRequest]; echo 'Rollup job results:'; if($RollupJobRequestObject -eq $null) { echo 'RollupJobRequestObject parameter is null'; } else { echo 'SimultaneousJobsCount:' $RollupJobRequestObject.
# working with Checksum Check Job ChecksumCheckJob { $ChecksumCheckJobRequestObject = $ChecksumCheckJobRequest -as [Replay.Core.Contracts.Exchange.ChecksumChecks.ChecksumCheckJobRequest]; echo 'Exchange checksumcheck job results:'; if($ChecksumCheckJobRequestObject -eq $null) { echo 'ChecksumCheckJobRequestObject parameter is null'; } else { echo 'RecoveryPointId:' $ChecksumCheckJobRequestObject.RecoveryPointId; echo 'AgentId:' $ChecksumCheckJobRequestObject.
} } PostNightlyJobScript.ps1 The PostNightlyJobScript is executed after every nighty job on Core side. It has $JobClassName parameter, that helps to handle those child jobs separately. Sample PostNightlyJobScript # receiving parameters from Nightlyjob param([System.
$NightlyAttachabilityJobRequestObject = $NightlyAttachabilityJobRequest -as [Replay.Core.Contracts.Sql.NightlyAttachabilityJobRequest]; echo 'Nightly Attachability job results:'; if($NightlyAttachabilityJobRequestObject -eq $null) { echo 'NightlyAttachabilityJobRequestObject parameter is null'; } else { echo 'AgentId:' $NightlyAttachabilityJobRequestObject.AgentId; echo 'IsNightlyJob:' $NightlyAttachabilityJobRequestObject.
echo 'Agents GUIDs:' foreach ($a in $AgentsCollection) { echo $a } } break; } # working with Checksum Check Job ChecksumCheckJob { $ChecksumCheckJobRequestObject = $ChecksumCheckJobRequest -as [Replay.Core.Contracts.Exchange.ChecksumChecks.ChecksumCheckJobRequest]; echo 'Exchange checksumcheck job results:'; if($ChecksumCheckJobRequestObject -eq $null) { echo 'ChecksumCheckJobRequestObject parameter is null'; } else { echo 'RecoveryPointId:' $ChecksumCheckJobRequestObject.
else { echo 'TransferConfiguration:' $TransferJobRequestObject.TransferConfiguration; echo 'StorageConfiguration:' $TransferJobRequestObject.StorageConfiguration; } echo 'LatestEpochSeenByCore:' $LatestEpochSeenByCore; $TakeSnapshotResponseObject = $TakeSnapshotResponse -as [Replay.Agent.Contracts.Transfer.TakeSnapshotResponse]; if($TakeSnapshotResponseObject -eq $null) { echo 'TakeSnapshotResponseObject parameter is null'; } else { echo 'ID of this transfer session:' $TakeSnapshotResponseObject.
You can add available objects from the TransferPrescript parameter or add your own commands to the PreTransferScript.sh and PostTransfer.sh scripts to customize them. Prerequisites for Bourne Shell Scripting All scripts must be named PreTransferScript.sh and PostTransfer.sh and have to reside in the /opt/appassure/scripts/ directory. Testing Bourne Shell Scripting You can test the scripts you want to run by using the editor for the script (.sh) files.
Method Description public string Key { get; set; } The Key method generates a pseudorandom (but not cryptographically secure) key, which can be used as a one-time password to authenticate transfer requests. public bool ForceBaseImage { get; set; } Gets or sets the value indicating whether the transfer was a forced base image capture. public bool IsLogTruncation { get; set; } Gets or sets the value indicating whether logging is being truncated.
Method Description public bool IsLogTruncation { get; set; } Gets or sets the value indicating whether logging is being truncated. public uint LatestEpochSeenByCore { get; set; } Gets or sets latest epoch value. The LatestEpochSeenByCore method is the ordinal number of the most recent snapshot taken by the Core. This is the 'epoch number' assigned by the filter driver to this particular snapshot at the moment it was taken with VSS.
TransferPrescriptParameter_ForceBaseImage=$TransferPrescriptParameter_For ceBaseImage TransferPrescriptParameter_IsLogTruncation=$TransferPrescriptParameter_Is LogTruncation TransferPrescriptParameter_LatestEpochSeenByCore=$TransferPrescriptParame ter_LatestEpochSeenByCore" > ~/PreTransferScriptResult.txt exit 0 PostTransferScript.sh The PostTransferScript is executed on the agent side after transferring a snapshot.
This page is intentionally left blank.
Glossary Agent An agent is a machine or server that is protected or to be protected by AppAssure 5. AppAssure 5 AppAssure 5 sets a new standard for unified data protection by combining backup, replication, and recovery in a single solution that is engineered to be the fastest and most reliable backup for protecting virtual machines (VM), as well as physical and cloud environments. Central Management Console The AppAssure 5 Central Management Console is a multi-core management portal.
Core The AppAssure 5 Core is the central component of the AppAssure architecture. The Core provides the essential services for backup, recovery, retention, replication, archival, and management. In the context of replication, the Core is also called a source core. The source core is the originating core, while the target core is the destination.
Machine A machine, sometimes referred to as an agent, is a physical or virtual machine or server that is protected by the AppAssure 5 Core. In the context of replication, a core may also be referred to as a source core. Management Roles The AppAssure 5 Central Management Console introduces a new concept of management roles which lets you divide administrative responsibility among trusted data and service administrators as well as access control to support secure and efficient delegation of administration.
Replication Replication is self-optimizing with a unique read-match-write (RMW) algorithm that is tightly coupled with deduplication. It represents the relationship between the target and source cores in the same site or across two sites with slow link in which the source core asynchronously transmits the data to the target or source core on a per agent basis.
Target Core The target core, which is sometimes referred to as replica core, is the AppAssure 5 Core receiving the replicated data from the source core. Target Replica Machine The instance of a protected machine on a target core is known as the target agent or replica agent. Transport Layer Security Transport Layer Security (TLS) is a modern cryptographic network protocol designed to ensure communication security over the Internet.
This page intentionally left blank.
Index A B about - 80, - 178 Active Directory deploying to multiple machines - 122 agent deploying when protecting an agent - 94 replicating - 116 reporting - 207 agent data replicating - 118 agents deploying (push install) - 115 alerts viewing - 186 AppAssure 5 about cluster protection - 189 core technologies - 18 license portal - 26 overview of - 17 product features - 19 What’s New - 11 AppAssure 5 Core archiving, about - 81 configuring - 30 recovery points, about - 133 security, managing - 44 settings,
Central Management Console Core Reports generating - 211 checksum checks forcing - 87 cloud about - 26 cluster snapshot, forcing - 201 snapshot, pausing - 201 snapshot, resuming - 201 clusters about cluster protection in AppAssure 5 - 189 configuring event notifications - 195 converting cluster machine to an agent - 198 dismounting recovery points - 202 modifying cluster machine settings - 193 modifying cluster protection schedules - 197 modifying cluster settings - 194 modifying cluster transfer settings -
L launching, from command line - 179 license information viewing - 107 license key changing - 31 licenses managing - 30 live cd loading - 174 Live DVD managing - 173 Local Mount Utility about - 75 adding a core - 76 downloading and installing - 75 mounted recovery point - 79 options, using - 80 recovery point - 77, - 79 Tray menu - 80 log truncation configuring - 85 forcing - 88 managing - 86 logs machine, viewing - 115 M machine agent data, replicating - 118 cluster machine settings - 193 converting clust
protection schedules modifying - 108 modifying for clusters - 197 R recovery managing - 73 recovery point mounting for Linux machines - 138 mounting for Windows machines - 136 orphaned, deleting - 140 removing - 139 snapshot, forcing - 141 Recovery Point Status - 88 recovery points dismounting, all - 137 dismounting, select - 137 for clusters - 200 specific points, viewing - 134 status indicators - 88 viewing - 133 Recovery-as-a-Service (RaaS) about - 24 replication about - 48 agent, removing - 63 and encr
input parameters - 215, - 238 NightlyAttachabilityJobRequest - 218 powershell.exe.
6 | Index
