Dell DL4300 Appliance User's Guide
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2016 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Introduction to Dell DL4300 Appliance......................................................... 10 Core technologies...............................................................................................................................10 Live Recovery................................................................................................................................. 11 Verified Recovery.............................................................................................
Adjusting the nightly job time ......................................................................................................26 Modifying the transfer queue settings .........................................................................................26 Adjusting the client time-out settings ......................................................................................... 27 Configuring deduplication cache settings .........................................................................
Removing a protected machine from replication on the source Core...................................... 55 Removing a protected machine on the target Core................................................................... 56 Removing a target Core from replication.................................................................................... 56 Removing a source Core from replication...................................................................................56 Recovering replicated data .........
Forcing checksum checks ............................................................................................................75 Forcing log truncation ..................................................................................................................75 Recovery point status indicators ..................................................................................................76 3 Managing Your Appliance.............................................................................
Protecting multiple machines ....................................................................................................106 Monitoring the protection of multiple machines ..................................................................... 108 Managing snapshots and recovery points ...................................................................................... 108 Viewing recovery points ........................................................................................................
Supported applications and cluster types ..................................................................................141 Protecting a cluster .......................................................................................................................... 142 Protecting nodes in a cluster ...........................................................................................................143 Process of modifying cluster node settings .....................................................
Installing the operating system.........................................................................................................159 Running the recovery and update utility.......................................................................................... 159 8 Changing the host name manually............................................................... 161 Stopping the Core service...............................................................................................................
Introduction to Dell DL4300 Appliance 1 This chapter provides an introduction and overview of DL4300.
Live Recovery Live Recovery is instant recovery technology for VMs or servers. It gives you near-continuous access to data volumes on virtual or physical servers. You can recover an entire volume with near-zero RTO and an RPO of minutes. The backup and replication technology records concurrent snapshots of multiple VMs or servers, providing near instantaneous data and system protection.
object and a volume manager with integrated global deduplication, compression, encryption, replication, and retention. The following diagram describes the AppAssure True Scale architecture. Figure 1. AppAssure True Scale architecture The AppAssure Volume Manager and Scalable Object Store serve as the foundation of the AppAssure True Scale architecture. The scalable object store stores block-level snapshots that are captured from virtual and physical servers.
volumes with dependency for comprehensive protection and effective recovery. This ensures that you never have incomplete backups when you are performing recoveries. Backups are performed by using application-aware block-level snapshots. Your appliance can also perform log truncation of the protected Microsoft Exchange and SQL servers. The following diagram depicts a simple deployment.
Smart Agent Smart Agent tracks the changed blocks on the disk volume and then snaps an image of the changed blocks at a predefined interval of protection. The incremental forever block-level snapshots approach prevents repeated copying of the same data from the protected machine to the Core. The Smart Agent is installed on the machines that is protected by the Core.
AppAssure uses Microsoft VSS because it has built-in support for all Windows internal technologies such as NTFS, Registry, Active Directory, to flush data to disk before the snapshot. Additionally, other enterprise applications, such as Microsoft Exchange and SQL, use VSS Writer plug-ins to get notified when a snapshot is being prepared and when they have to flush their used database pages to disk to bring the database to a consistent transactional state.
Repository The 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.
Figure 4. Diagram of deduplication Your appliance performs target-based inline data deduplication, where the snapshot data is transmitted to the Core before it is deduplicated. Inline data deduplication simply means the data is deduplicated before it is committed to disk.
In replication scenarios, your appliance uses SSL 3.0 to secure the connections between the two cores in a replication topology to prevent eavesdropping and tampering. Replication Replication is the process of copying recovery points from an AppAssure core and transmitting them to another AppAssure core in a separate location for the purpose of disaster recovery. The process requires a paired source-target relationship between two or more cores.
replicate to the target site. After data has been transferred to the target core, the newly replicated incremental recovery points automatically synchronize. Recovery-as-a-Service (RaaS) Managed service providers (MSPs) can fully leverage the appliance as a platform for delivering recovery as a service (RaaS).
appliance solves the big data problem by managing the retention of large amounts of data with complex retention policies and performing rollup operations for aging data using efficient metadata operations. Backups can be performed with an interval of a few minutes. As these backups age over days, months, and years, retention policies manage the aging and deletion of old backups. A simple waterfall method defines the aging process.
organize the managed cores in hierarchical organizational units. These organizational units can represent business units, locations, or customers for MSPs with role-based access. The central console can also run reports across managed cores. Service management APIs Your appliance comes bundled with a service management API and provides programmatic access to all of the functionality available through the Central Management Console. The service management API is a REST API.
Working with the DL4300 Core 2 Accessing the DL4300 Core Console To access the Core Console: 1. Update trusted sites in your browser. See Updating Trusted Sites In Internet Explorer. 2. Configure your browsers to remotely access the Core Console. See Configuring Browsers To Remotely Access The Core Console. 3. Perform one of the following to access the Core Console: • Log on locally to your DL4300 core server, and then double-click the Core Console icon.
NOTE: Ensure that the Internet Explorer Enhanced Security Configuration is turned on when you access the Core Web Console either locally or remotely. To turn on the Internet Explorer Enhanced Security Configuration: 1. Open Server Manager. 2. Select Local Server IE Enhanced Security Configuration displayed on the right. Ensure that it is On. Configuring browser settings in Internet Explorer and Chrome To modify browser settings in Internet Explorer and Chrome: 1. Open Internet Explorer. 2.
Configuring the Core involves understanding certain concepts and performing the following initial operations: • Create a repository • Configure encryption keys • Configure event notification • Configure retention policy • Configure SQL attachability NOTE: If you are using this Appliance, it is recommended that you use the Appliance tab to configure the Core. For more information about configuring the Core after initial installation, see the Dell DL4300 Appliance Deployment Guide at dell.
Changing the AppAssure language manually AppAssure allows you to change the language that you had selected while running AppAssure Appliance Configuration Wizard to any of the supported languages. To change the AppAssure language to the desired language: 1. Launch the registry Editor using regdit command. 2. Navigate to HKEY_LOCAL_MACHINE → SOFTWARE → AppRecovery → Core → Localization. 3. Open Lcid. 4. Select decimal. 5.
8. To make this language your display language, move it to the top of your language list. 9. Log out and log in again to Windows for the change to take effect. Managing Core settings The Core settings are used to define various settings for configuration and performance.
To modify the transfer queue settings: 1. Navigate to the Core Console. 2. Click Configuration → Settings. 3. In the Transfer Queue pane, click Change. The Transfer Queue dialog box appears. 4. In the Maximum Concurrent Transfers text box, enter a value to update the number of concurrent transfers. Set a number from 1 to 60. The smaller the number, the lesser the load is on network and other system resources. As the capacity that is processed increases, so does the load on the system. 5.
8. Click OK. NOTE: You must restart the Core service for the changes to take effect. Modifying engine settings To modify the engine settings: 1. Navigate to the Core Console. 2. Click Configuration → Settings 3. In the Replay Engine Configuration pane, click Change. The Replay Engine Configuration dialog box appears. 4. 5.
Modifying database connection settings To modify database connection settings: 1. Navigate to the Core Console. 2. Click Configuration → Settings 3. In the Database Connection Settings area, choose one of the following: • Click Apply Default. • Click Change. The Database Connection Settings dialog box appears. 4. Enter the settings for modifying the database connection described as follows: Text Box Description Host Name Enter a host name for the database connection.
• All data stored within a repository is globally deduplicated. • The Scalable Object File System can deliver scalable I/O performance in tandem with global data deduplication, encryption, and retention management. NOTE: DL4300 repositories are stored on primary storage devices. Archival storage devices such as Data Domain are not supported due to performance limitations.
5. Text Box Description Repository Name Enter the display name of the repository. By default, this text box consists of the word Repository and an index number which sequentially adds a number to the new repository starting with 1. You can change the name as needed. You can enter up to 150 characters. Concurrent Operations Define the number of concurrent requests that you want the repository to support. By default the value is 64. Comments Optionally, enter a descriptive note about this repository.
Text Box Description If this location is at the root, define a dedicated folder name (for example, Repository). The path must begin with \\. 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. 7. User Name Specify a user name for accessing the network share location.
8. Text Box Description Bytes per Sector Specify the number of bytes you want each sector to include. The default value is 512. Average Bytes per Record Specify the average number of bytes per record. The default value is 8192. Click Save. The Repositories screen is displayed to include the newly added storage location. 9. Repeat step 4 through step 7 to add more storage locations for the repository. 10. Click Create to create the repository.
Field 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. NOTE: You cannot edit the repository name. Description Optionally, enter a descriptive note about the repository. Maximum Concurrent Operations Define the number of concurrent requests that you want the repository to support.
3. Specify how to add the file for the storage location. You can choose to add the file on the local disk or on a CIFS share. • • 4. To specify a local machine, click Add file on local disk, enter the information as follows: Text Box Description Metadata Path Enter the location for storing the protected metadata. Data Path Enter the location for storing the protected data.
Text Box Description If set to Sync, Windows controls the caching as well as the synchronous input/ output. 5. Bytes per Sector Specify the number of bytes you want each sector to include. The default value is 512. Average Bytes per Record Specify the average number of bytes per record. The default value is 8192. Click Save. The Repositories screen is displayed to include the newly added storage location. 6. Repeat Step 4 through Step 7 to add more storage locations for the repository. 7.
The Volumes remount. Resolving foreign volumes If a provisioned MD1400 is powered off or disconnected and then later powered back on, an event appears on the Core Console reporting that the MD1400 is connected. However, no task appears on the Appliance tab Tasks screen that permits you to recover it. The Enclosures screen reports the MD1400 as being in a foreign state and the repositories on the foreign virtual disks as off-line. To resolve foreign volumes: 1.
md "" NOTE: Ensure that you remove the \File_x portion of the metadata path, and enclose the metadata path in quotes. 9. From Computer Management → Storage Management → Disk Management, add the mount path to the volume. NOTE: Ensure that you remove the \File_x portion of the metadata path. 10. Remove the drive letter. 11. Add drive letters to all DL_VMRSRV_x volumes. 12. From the AppAssure Core Console → Configuration → Restore screen, click fix path, and then click Save.
5. Text Box Description Description Enter a description of the encryption key. It is used to provide more details for the encryption key. Passphrase Enter a passphrase. It is used to control access. Confirm Passphrase Re-enter the passphrase. It is used to confirm the passphrase entry. Click OK. CAUTION: It is recommended that you protect the passphrase. If you lose the passphrase, you cannot access the data. Editing an encryption key To edit an encryption key: 1. Navigate to the Core Console.
5. Click OK. Exporting an encryption key To export an encryption key: 1. Navigate to the Core Console. 2. Click Configuration → Security. 3. Click > next to the name of the encryption key that you want to export, and then click Export. The Export Key dialog box appears. 4. In the Export Key dialog box, click Download Key to save and store the encryption keys in a secure location. 5. Click OK. Removing an encryption key To remove an encryption key: 1. Navigate to Core Console. 2.
5. Enter the details described in the following table based on the cloud type selected in Step 4. Table 1. Adding a cloud account Cloud Type Text Box Description Microsoft Azure Storage Account Name Enter the name of your Windows Azure storage account. Access Key Enter the access key for your account. Display Name Create a display name for this account in AppAssure; for example, Windows Azure 1. Access Key Enter the access key for your Amazon cloud account.
Editing a cloud account Perform the following steps to edit a cloud account: 1. In the Core Console, click the Tools tab. 2. In the left menu, click Clouds. 3. Next to the cloud account you want to edit, click the drop-down menu, and then click Edit. The Edit Account window opens. 4. Edit the details as necessary, and then click Save. NOTE: You cannot edit the cloud type.
4. In the Delete Account window, click Yes to confirm that you want to remove the account. 5. If the cloud account is currently in use, a second window asks you if you still want to remove it. Click Yes to confirm. NOTE: Removing an account that is currently in use causes all archive jobs scheduled for this account to fail.
• Point to Point. Replicates a single protected machine from a single source core to a single target core. Figure 7. Basic Replication Architecture Diagram • Multi-Point to Point. Replicates multiple source cores to a single target core. Figure 8. Multi-Point Replication Architecture Diagram About seeding Replication begins with seeding: the initial transfer of deduplicated base images and incremental snapshots of the protected machines, which can add up to hundreds or thousands of gigabytes of data.
NOTE: While it is possible to seed the base data over a network connection, it is not recommended. Initial seeding involves potentially very large amounts of data, which could overwhelm a typical WAN connection. For example, if the seed data measures 10 GB and the WAN link transfers 24 Mbps, the transfer could take more than 40 days to complete. The data in the seeding archive is compressed, encrypted, and deduplicated.
About retention policies for replication The retention policy on the source core determines the retention policy for the data replicated to the target core, because the replication task transmits the merged recovery points that result from a rollup or ad-hoc deletion. NOTE: The target core is not capable of rollup or of ad-hoc deletion of recovery points. These actions can only be performed by the source core.
Maximum change rate for wan connection types Table 2. Maximum change rate for wan connection types Broadband Bandwidth Max Change Rate DSL 768 Kbps and up 330 MB per hour Cable 1 Mbps and up 429 MB per hour T1 1.5 Mbps and up 644 MB per hour Fiber 20 Mbps and up 838 GB per hour If a link fails during data transfer, replication resumes from the previous failure point of the transfer after link functionality is restored.
Configuring the source core to replicate to a self-managed target core To configure the source core to replicate to a self-managed target core: 1. In the Core, click the Replication tab. 2. Click Add Target Core. The Replication wizard appears. 3. Select I have my own Target Core, and then enter the information as described in the following table. Text Box Description Host Name Enter the host name or IP address of the Core machine to which you are replicating.
the Container associated with your account. Select the Folder Name to which the archived data is to be saved. d. Click Next. ntainer 9. In the Seed Drive Option dialog box, enter the information described as follows: Text Box Description Maximum Size Large archives of data can be divided into multiple segments.
The pairing of the source core to the target core is complete. Replication begins, but produces orphaned recovery points on the target core until the seed drive is consumed and provides the necessary base images. Consuming the seed drive on a target core This procedure is only necessary if you created a seed drive while Configuring Replication For A SelfManaged Core. To consume the seed drive on a target core: 1.
NOTE: This procedure removes the link to the outstanding seed drive from the Core Console on the source core. It does not remove the drive from the storage location on which it is saved. To abandon an outstanding seed drive: 1. From the Core Console on the source core, select the Replication tab. 2. Click Outstanding Seed Drive (#). The Outstanding seed drives section appears.
6. If you plan to perform the seeding process for the transfer of base data, select Use a seed drive to perform initial transfer. 7. Click Submit Request. NOTE: If you select Use a seed drive to perform initial transfer, the Copy to Seed Drive dialog box displays. 8. In the Copy to Seed Drive dialog box, enter the information for the seed drive as described in the following table.
Reviewing a replication request A replication request is sent from the source core to the third-party target core. As the third party, you can review the request, and then approve it to begin replication for your customer, or you can deny it to prevent replication from occurring. To review a replication request on a third-party target core: 1. Open the Core Console on the target core and select the Replication tab. 2. Click Pending Requests (#). The Pending Replication Requests section appears. 3.
To monitor replication: 1. In the Core Console, click the Replication tab. 2. On this tab, you can view information about and monitor the status of replication tasks described as follows: Table 3. Monitoring replication Section Description Available Actions Pending Replication Requests Lists your customer ID, email In the drop-down menu, click address, and host name when a Ignore to ignore or reject the replication request is submitted request. to a third-party service provider.
Managing replication settings You can adjust a number of settings for how replication executes on the source and target cores. To manage replication settings: 1. In the Core Console, click the Replication tab. 2. In the Actions drop-down menu, click Settings. 3. In the Replication Settings window, edit the replication settings described as follows: 4. Option Description Cache lifetime Specify the amount of time between each target-core status request performed by the source core.
Removing a protected machine on the target Core To remove a protected machine on the target core: 1. On the target core, open the Core Console, and click the Replication tab. 2. Expand the Incoming Replication section. 3. In the drop-down menu for the protected machine that you want to remove from replication, click Delete, and then select one of the following options. Option Description Relationship Only Removes the protected machine from replication but retains the replicated recovery points.
• Mount recovery points. • Roll back to recovery points. • Perform a virtual machine (VM) export. • Perform a bare metal restore (BMR). • Perform Failback (in the event you have a Failover/Failback replication environment set up).
4. Click the Machines tab, and then select the machine that has the associated AppAssure agent with recovery points. 5. Export the backup recovery point information on that agent to a virtual machine. 6. Shut down the machine that has the AppAssure agent. 7. Start the virtual machine that now includes the exported backup information. 8. Reboot the virtual machine and wait for the agent service to start. 9.
19. In the Core Console of the source core, set up replication again between the source and target by clicking the Replication tab, and then adding the target core for replication. Managing events Managing core events assists with the monitoring of the health and usage of the 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.
4. 5. • Notification Options In the General panel, enter basic information for the notification group described as follows: Text Box Description Name Enter a name for event notification group, used to identify the event notification group. Description Enter a description for the event notification group, used to describe the purpose of the event notification group. In the Enable Events panel, select the conditions for which event logs (alerts) to create and report.
Text Box Description • 7. BCC: Notify by Windows Event Log Select this option if you want alerts to be reported through the Windows Event Log. It is used to specify whether the notification of alerts must be reported through the Windows Event Log. Notify by sys logd Select this option if you want alerts to be reported through sys logd. Specify the details for the sys logd in the following text boxes: • Hostname: • Port:1 Click OK.
Text Box Description Password Enter a password for accessing the email server. From Enter a return email address. It is used to specify the return email address for the email notification template; for example, noreply@localhost.com. Email Subject Enter a subject for the email template. It is used to define the subject of the email notification template; for example, - .
• Recovery of data volumes, using Live Recovery • Recovery of data volumes for Microsoft Exchange Server and Microsoft SQL Server, using Live Recovery • Bare metal restore, using Universal Recovery • Bare metal restore to dissimilar hardware, using Universal Recovery • Ad-hoc and continuous export to virtual machines About system information AppAssure lets you view information about the Core that includes system information, local and mounted volumes, and AppAssure engine connections.
For more information about installing the agents, see the Dell DL4300 Appliance Deployment Guide available at Dell.com/support/home. About the local mount utility The Local Mount Utility (LMU) is a downloadable application that lets you mount a recovery point on a remote Core from any machine. The light-weight utility includes the aavdisk and aavstor drivers, but it does not run as a service. When you install the utility, by default, it is installed in the directory C: \Program Files\AppRecovery\Local Moun
Adding a core to the local mount utility To mount a recovery point, you must add the Core to the LMU. There is no limit as to how many cores you can add. To add a core to the Local Mount Utility: 1. From the machine on which the LMU is installed, launch LMU by double-clicking the desktop icon. 2. If the User Account Control window displays, click Yes to let the program to make changes to the machine. 3. In the upper-left corner of the AppAssure Local Mount Utility window, click Add core. 4.
Mounting a recovery point by using the local mount utility Before mounting a recovery point, the LMU must connect to the Core on which the recovery point is stored. As described in Adding A Core To The Local Mount Utility, the number of cores that can be added to the LMU is unlimited; however, the application can connect to only one core at a time.
Option Description Dismount Dismounts only the adjacent recovery point. Dismount all a. Click Dismount beside the chosen recovery point. b. Close the window. Dismounts all mounted recovery points. a. Click Dismount all. b. In the Dismount All window, click Yes to confirm. c. Close the window. About the local mount utility tray menu The LMU tray menu is located in your desktop taskbar. Right-click the icon to reveal the following options: Browse Recovery Points Opens the LMU main screen.
Option Description Edit core Opens the Edit Core window, where you can change the host name, port, and credentials. Accessing agent options To access agent options, right-click the Core or agent and then click Refresh recovery points. The list of recovery points for the selected agent updates. Managing retention policies Periodic backup snapshots of all the protected servers accumulate on the Core over time.
Text Box Description Date range To specify the date range, select the to and from dates. Archive password Enter a password for the archive, which is used to establish log in credentials to secure the archive. Confirm Re-enter the password to secure the archive, which is used to provide validation of the information that you entered in the Archive Password text box. Output Location Enter the location for the output, used to define the location path where you want the archive to reside.
– User Name: Enter a user name. It establishes logon credentials for the network share. – Password: Enter a password for the network path. It establishes logon credentials for the network share. • Cloud – Account : Select an account from the drop-down list. To select a cloud account, you must first have added it in the Core Console. – Container: Select a container associated with your account from the drop-down menu. 5. – Folder Name: Enter a name for the folder in which the archived data is to be saved.
– Pause – Resume The status of the archive displays in the Schedule column. Editing a scheduled archive 1. In the Core Console, click the Tools tab. 2. From the Archive option, click Scheduled. 3. On the Scheduled Archive page, click the drop-down menu next to the archive you want to change, and then click Edit. The Add Archive Wizard dialog box appears. 4.
Checking an archive You can scan an archive for structural integrity by performing an archive check. This check verifies the presence of all necessary files within the archive. To perform an archive check, complete the steps in the following procedure: 1. In the Core Console, click the Tools tab. 2. From the Archive option, click Check Archive. The Check Archive dialog box appears. 3.
Managing SQL attachability The SQL attachability configuration enables the Core to attach SQL database and log files in a snapshot of a SQL server using a local instance of Microsoft SQL Server. The attachability test lets the Core check for the consistency of the SQL databases and ensures that all data files (MDF and LDF files) are available in the backup snapshot. Attachability checks can be run on demand for specific recovery points or as part of a nightly job.
7. 8. • SQL Specify the credentials with administrative privileges for the Windows or SQL Server instances, described as follows: Text Box Description Username Enter a user name for logon permissions to the SQL server. Password Enter a password for SQL attachability. It is used to control logon activity. Click Test Connection. NOTE: If you entered the credentials incorrectly, a message is displayed to alert you that the credentials test failed.
To configure Exchange database mountability and log truncation: 1. In the left navigation area of the Core Console, select the machine for which you want to configure mountability checks and log truncation. The Summary tab for the selected machine is displayed. 2. Click Exchange Server Settings. The Exchange Server Settings dialog box displays. 3. 4.
To force log truncation: 1. Navigate to the 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. 3. • Or, in the navigation pane, select the machine you want to truncate the log. In the Actions drop-down menu for that machine, click Force Log Truncation. 4. Confirm whether to proceed with forcing log truncation.
Term heading Description heading Green Indicates that the mountability check passed or that the checksum check passed. NOTE: Recovery points that do not have an Exchange or SQL database associated with it is displayed with a white status indicator. In situations where both an Exchange and SQL database exists for the recovery point, the most severe status indicator is displayed for the recovery point.
Managing Your Appliance 3 The Core Console includes an Appliance tab, which you can use to provision space, monitor the health of the appliance, and access management tools. Monitoring the status of the Appliance You can monitor the status of the Appliance subsystems by using the Appliance tab Overall Status page. The Overall Status page displays a status light next to each subsystem, along with a status description indicating the health of the subsystem.
Based on a medium-sized environment that does not need standby virtual machines, you can use all of the storage to back up a significant number of agents. However, if you need more resources for standby virtual machines and back up a smaller number of agent machines, you can allocate more resources for larger VMs.
4. Click Provision. The disk provisioning begins and the status of the AppAssure repository creation is displayed in the Status area of the Tasks screen. The State displays Provisioned. 5. To view the details after disk provisioning completes, click > next to the status light. The Tasks page expands and displays status, repository, and virtual disk details (if allocated). Deleting space allocation for a virtual disk Before you begin this procedure, determine which virtual disk you want to delete.
The Core Console launches. Repairing your Appliance To repair your appliance: 1. Download the Recovery and Update Utility from dell.com/support to your Appliance. 2. Copy the utility to the appliance desktop and extract the files. 3. Double-click the launchRUU icon. 4. When prompted, click Yes to acknowledge that you are not running any of the listed processes. 5. When the Recovery and Update Utility screen displays, click Start. 6. When prompted to reboot, click OK.
Protecting workstations and servers 4 About protecting workstations and servers To protect your data add the workstations and servers you want to protect in the Core Console; for example, your Exchange server, SQL Server, or your Linux server. NOTE: In this section, generally the word machine also refers to the AppAssure Agent software installed on that machine.
Text Box Description Host Name Enter a host name for the machine. Port Enter a port number for the machine. The Core uses the port to communicate with this machine. Repository Select a repository for the recovery points. Displays the repository on the Core in which to store the data from this machine. NOTE: This setting can only be changed if there are no recovery points or the previous repository is missing. Encryption Key Edit the encryption key if necessary.
To configure notification groups for system events: 1. In the Core Console, click the Machines tab. 2. From the Machines tab, perform one of the following: • Click the hyperlink for the machine that you want to modify. • In the navigation pane, select the machine that you want to modify. The Summary tab appears. 3. Click the Configuration tab, and then click Events. The Notification Groups page appears. 4. Click Use custom alert settings and then click Apply. 5.
Text Box Description • Warning • Error NOTE: When you choose to select by type, by default, the appropriate events are automatically enabled. For example, if you choose Warning, the Attachability, Jobs, Licensing, Archive, CoreService, Export, Protection, Replication, and Rollback events are enabled. Notification Options Select the method to specify how to handle notifications.
Text Box Description Description Enter a description for the notification group. Enable Events Select which events to share with the notification group.
Text Box Description – Port — Enter a port number for communicating with the server. 7. Click OK. 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. A rollup process enforces the retention policy, and helps with aging and deleting old backups.
Text Box ...and then keep one Recovery Point per day for n [retention time period] Description • Weeks • Months • Years Provides a more refined level of retention. It is used as a building block to further define how long recovery points are maintained. Enter a number that represents the retention period and then select the time period. The default is 4. You can choose from: ...
...and then keep one recovery point per hour for 3 days ...and then keep one recovery point per day for 4 days ...and then keep one recovery point per week for 3 weeks ...and then keep one recovery point per month for 2 months ...and then keep one recovery point per month for 1 year Newest Recovery Point is set to the current day, month, and year. In this example, the oldest recovery point can be one year, four months, and six days old. 6. Click Apply to save your changes. 7.
Option 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. • To protect data during off-peak times, select the Protection interval during off-peak times check box, and then select an interval for protection from the drop-down menu.
• Amount of data change on disk • Available network bandwidth • Repository disk subsystem performance • Amount of memory available for data buffering You can adjust the performance options to best support your business needs and fine-tune the performance based on your environment. To modify transfer settings: 1. In the Core Console, do one of the following: • 2. • In the navigation pane, click the machine that you want to modify. From the Machines tab, perform one of the following: • 3.
Text Box Description CAUTION: Do not change this option from the default setting. Maximum Transfer Specifies the number of commands that can be sent concurrently. You can Queue Depth adjust this option to a higher number if your system as a high number of concurrent input/output operations. Outstanding Reads per Stream Specifies how many queued read operations will be stored on the back end. This setting helps to control the queuing of agents. NOTE: Dell recommends setting this value to 24.
• Click the hyperlink for the machine that you want to restart. 3. • In the Navigation pane, select the machine that you want to restart. Click the Tools tab, and then click Diagnostics. 4. Select the Restart Service option, and then click the Restart Service button. Viewing machine logs If you encounter any errors or issues with the machine, view the logs to troubleshoot. To view machine logs: 1. In the Core Console, click the Machines tab. 2.
4. Text Box Description Password The password used to connect to this machine. Click Connect to connect to this machine. NOTE: If the Agent software is not yet installed on the machine that you designated, follow the procedure Deploying The Agent Software When Protecting An Agent. Restart the agent machine after deploying the Agent software, and then resume with the next step. 5. In the Protect dialog box, edit the settings as needed as described in the following table.
The first time protection is added for a machine, a base image (which is a snapshot of all the data in the protected volumes) immediately begins to transfer to the repository on the Core, unless you specified to initially pause protection. CAUTION: If you protected a Linux machine, you must not unmount a protected volume manually. In the event you need to do this, you must execute the following command before unmounting the volume: bsctl -d [path_to_volume].
Creating custom schedules for volumes To create custom schedules for volumes: 1. In the Protect Machine dialog box (for information about accessing this dialog box, see Protecting A Machine, under Volume Groups, select a volume for protection, and then click Edit. The Protection Schedule dialog box appears. 2.
4. – Truncate log before checksum check completes You can also modify the logon credentials for your Exchange Server. To do so, scroll down to the Exchange Server Information section and then click Change Credentials. The Set Exchange Credentials dialog box appears. 5. Enter the new credentials and then click OK. Modifying SQL server settings If you are protecting data from Microsoft SQL Server, there are additional settings that you need to configure in the Core Console.
4. Text Box Description Automatic reboot after install Select to specify whether the Core starts upon the completion of the deployment and installation of the AppAssure Agent Installer. Click Verify to validate the credentials you entered. The Deploy Agent dialog box displays a message indicating that validation is being performed. 5. Click Abort if you want to cancel the verification process. After the verification process completes, a message indicating that verification has been completed appears.
Text Box Description Remote Core Specify the target core to which you want to replicate the agent. Remote Repository The name of the desired repository on the target core in which to store the replicated data from this machine. Pause Select this check box if you want to pause replication; for example, to pause it until after AppAssure takes a base image of the new agent.
Outbound replication can be configured to a Managed Service Provider providing off-site backup and disaster recovery service or to a self-managed core. To replicate agent data on a machine: 1. From the Core Console, click the Machines tab. 2. Select the machine that you want to replicate. 3. In the Actions drop-down menu, click Replication, and then complete one of the following options: • If you are setting up replication, click Enable.
Text Box Description All Operations Cancels all active operations for that machine. Snapshot Cancels the snapshot currently in progress. Viewing machine status and other details To view machine status and other details: 1. In the navigation pane of the Core Console, do one of the following: • Select the Machines tab, and then click the hyperlink for the machine that you want to view. • In the navigation pane, click the machine that you want to view. The Summary tab is displayed.
• Log File Path • Log Prefix • System Path • MailStore Type Managing multiple machines This topic describes the tasks that administrators perform to deploy Agent software simultaneously to multiple Windows machines. To deploy and protect multiple agents, perform the following tasks: 1. Deploy AppAssure to multiple machines. See Deploying To Multiple Machines. 2. Monitor the activity of the batch deployment. See Monitoring The Deployment Of Multiple Machines. 3. Protect multiple machines.
To push the agent installation program from the Core machine: 1. From the Core machine, copy the agent installation file Agent-X64–5.x.x.xxxxx.exe to the C: \Program Files\apprecovery\core\installers directory. 2. From the Core Console, select the Configuration tab, and then click Settings. 3. In the Deploy Settings section, edit the Agent Installer Name.
Text Box Description Repository Use the drop-down list to select the repository on the Core where the data from the machines should be stored. The repository that you select is used for all of the machines that are being protected. NOTE: This option is only available when you select Protect machine after install. Encryption Key (Optional) Use the drop-down list to specify whether encryption should be applied to the data on the machine that should be stored in the repository.
Text Box Description Host Enter the name or IP address of the VMware vCenter Server/ESX(i) virtual host. User Name Enter the user name used to connect to the virtual host; for example, administrator. Password Enter the secure password used to connect to this virtual host. 4. On the Add Machines from VMware vCenter Server/ESXi dialog box, check the box next to the machines to which you want to deploy the AppAssure Agent, and then click Add. 5.
3. On the Deploy Agent on Machines window, you can see the machines that you added. If you want to select a repository, encryption key, or other settings for a machine, select the check box next to the machine and click Edit Settings. For details on each setting, see Deploying To Machines On An Active Directory Domain. 4. Verify that AppAssure can connect to each machine successfully. Select each machine on the Deploy Agent on Machines window, and then click Verify.
To protect multiple machines: 1. From the Core Console, click the Tools tab, and then click Bulk Protect. The Protect Machines window appears. 2. Add the machines that you want to protect by clicking one of the following options. For details on completing each option, see Deploying To Multiple Machines. • Click Active Directory to specify machines on an Active Directory domain. • Click vCenter/ESXi to specify virtual machines on a vCenter/ESXi virtual host.
7. Icon Description Yellow icon AppAssure is able to connect to the machine; however, the agent is already paired with a core machine. Red icon AppAssure cannot connect to the machine. This may be because the logon credentials are incorrect, the machine is shut down, the firewall is blocking traffic, or another problem. To correct, click Edit Settings on the toolbar or the Edit link next to the machine.
Viewing recovery points To view recovery points: 1. In the left navigation area of the Core Console, select the machine for which you want to view recovery points, and then click the 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. Contents Lists the volumes included in the recovery point.
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. Formatted Capacity Indicates the amount of storage space on the volume that is available for data after the volume is formatted. Used Capacity Indicates the amount of storage space currently used on the volume.
Text Box Description Create a Windows Optionally, select the check box to specify whether the mounted recovery share for this point can be shared, and then set access rights to it including the Share name Mount and access groups. 3. Click Mount to mount the recovery point. Dismounting select recovery points You can dismount select recovery points that are mounted locally on the Core. To dismount select recovery points: 1. From the Core Console, select the Tools tab. 2.
number for the volume that includes a sequence number at the end (for example, 293cc667-44b4-48ab-91d8-44bc74252a4f:2), which identifies the recovery point. 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.
NOTE: The ability to delete an orphaned recovery chain is not available for replicated recovery points on a target core. To delete an orphaned recovery point chain: 1. On the Core Console, select 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. This recovery point is labeled in the Type column as Incremental Orphaned. 4. Next to Actions, click Delete.
Restoring data You can instantly recover or restore data to your physical machines (for Windows or Linux machines) or to virtual machines from stored recovery points for Windows machines. The topics in this section describe how you can export a specific recovery point for Windows machines to a virtual machine or to roll back a machine to a previous recovery point.
If a backup is running, information regarding Current Backup Progress and Start Time is displayed. Windows Backup Policy To configure a Windows backup policy, perform the following steps: 1. In the Core Console, navigate to Appliance → Backup. 2. Click the Configure Policy button. The Windows Backup Policy window is displayed. 3.
with a high availability copy of the data. If a protected machine goes down, you can boot up the virtual machine to then perform recovery. The following diagram shows a typical deployment for exporting data to a virtual machine. Figure 9. Exporting data to a virtual machine You create a virtual standby by continuously exporting protected data from your Windows machine to a virtual machine.
Exporting backup information from your Microsoft Windows machine to a virtual machine In AppAssure you can export data from your Microsoft Windows machines to a virtual machine (VMware, ESXi, Hyper-V, and Oracle VirtualBox) by exporting all of the backup information from a recovery point as well as the parameters defined for the protection schedule for your machine. To export Windows backup information to a virtual machine: 1. In the Core Console, click the Machines tab. 2.
Performing a continuous (virtual standby) ESXi export To perform a continuous (virtual standby) ESXi export: 1. In the Select Export Type dialog box, click Continuous (Virtual Standby). 2. Click Next. The Virtual Standby Recovery Point to VMware vCenter Server/ESXi dialog box is displayed. 3. Enter the parameters for accessing the virtual machine as described below. Text Box Description Host name Enter a name for the host machine. Port Enter the port for the host machine. The default port is 443.
Exporting Windows data using VMware workstation export In AppAssure, you can choose to export data using VMware Workstation Export by performing a onetime 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 To perform a one-time VMware Workstation export: 1. In the Select Export Type dialog box, click One-time export. 2. Click Next.
Text Box Description NOTE: It is recommended to use a name that is derived from the agent name or one that matches the agent name. You can also create a name derived from the hypervisor type, IP address or DNS name. Memory 4. 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. • Click Use a specific amount of RAM to specify how much RAM to use. For example, 4096 MB.
Text Box Description Virtual Machine Enter a name for the virtual machine being created. For example, VM-0A1B2C3D4. NOTE: It is recommended to use a name that is derived from the agent name or one that matches the agent name. You can also create a name derived from the hypervisor type, IP address or DNS name. 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.
Performing a one-time Hyper-V export To perform a one-time Hyper-V export: 1. In the Core Console, navigate to the machine you want to export. 2. On the Summary tab, click Actions → Export → One-time. The Export Wizard displays on the Protected Machines page. 3. Select a machine for export, and then click Next. 4. On the Recovery Points page, select the recovery point that you want to export, and then click Next.
8. On the Volumes page, select the volume(s) to export. For the virtual machine to be an effective backup of the protected machine include the protected machine’s boot drive. Example. C:\. Your selected volumes should be no larger than 2040 GB for VHD. If the selected volumes are larger than 2040 GB, and the VHD format is selected, you will receive an error. 9. On the Summary page, click Finish to complete the wizard and to start the export.
• VHD NOTE: Hyper-V Export supports VHDX disk formats if the target machine is running Windows 8 (Windows Server 2012) or higher. If the VHDX is not supported for your environment, the option is disabled. On the Network Adapters page, select the virtual adapter to be connected to a switch. 11. On the Volumes page, select the volume(s) to export. For the virtual machine to be an effective backup of the protected machine include the protected machine’s boot drive. Example, C:\.
Option Description Target Path Specify a local or remote target path to create the virtual machine. NOTE: The target path should not be a root directory. If you specify a network share path, you will need to enter valid logon credentials (user name and password) for an account that is registered on the target machine. The account must have read and write permissions to the network share. Memory 6.
4. Enter the parameters for accessing the virtual machine as described in the following table. Option Description Virtual Machine Name Enter a name for the virtual machine being created. Target Path Specify a local or remote target path to create the virtual machine. NOTE: It is recommended to use a name that is derived from the agent name or one that matches the agent name. You can also create a name derived from the hypervisor type, IP address or DNS name.
VM Management for Hyper-V and ESXi virtual standby(s) Field Description Agent / VM Information Agent Name: Indicates the name of the protected machine for which you have created virtual standby. VM Name: Indicates the name of the VM. NOTE: It is recommended to use a name that is derived from the agent name or one that matches the agent name. You can also create a name derived from the hypervisor type, IP address or DNS name. Status: Indicates the status of the virtual machine.
Field Description • 2. Not Performed If an export is currently in progress, percentage of export is displayed. Last Export: Indicates the time of last export. Hypervisor Information Name: Indicates the name of the Hypervisor on which VM is created. Status: Indicates the status of connection to the Hyper-V and ESXi hypervisors. • Online • Offline • Unknown (temporary status) NOTE: The status is displayed only for Hyper-V and ESXi hypervisors.
The maximum number of VNAs per VM depends on the type of hypervisor. For Hyper-V you can add up to 8 adapters for every virtual machine. To create a virtual network adapter: 1. Navigate to the VM Management page. 2. Click the Add Network Adapter button associated with the VM to add a VNA. NOTE: Do not add adapters to a VM for a Virtual Standby that is still running backups or exports of protected machines. The additional VNAs can cause future export operations to fail.
Stopping a VM operation To stop a VM operation: 1. Navigate to the VM Management window. 2. Click the Stop button associated with the VM to stop. NOTE: The Stop button is enabled only if the virtual machine is currently running and is available within a 30 second (approximately) refresh after starting the VM. NOTE: The Start button is enabled within 30 seconds (approximately) after stopping the VM.
6. Select from the following options: • Live Recovery. When selected, the rollback for Windows volumes happens immediately. Selected by default. NOTE: The Live Recovery option is not available for Linux volumes. • 7. Force Dismount. When selected, it forces the dismount of any mounted recovery point prior to performing the rollback. Selected by default. Click Rollback. The system begins the process of rolling back to the selected recovery point.
NOTE: To identify the recovery point, you can also specify a line number in the command instead of the recovery point ID number. In that case, use the agent/machine line number (from the lm output), followed by the recovery point line number and volume letter, followed by the path, such as, r [machine_line_item_number] [recovery_point_line_number] [volume_letter] [path]. In this command, [path] is the file descriptor for the actual volume.
• Hardware to restore (new or old, similar or dissimilar) • Blank CD and CD burning software • VNC viewer (optional) • Windows 7 PE (32-bit) Compatible Drivers Storage and Network adapter drivers for the target machine • Storage Controller, RAID, AHCI, and chipset drivers for the target operating system NOTE: The Storage Controller Drivers are only needed if the restore being performed is to dissimilar hardware.
Naming the boot cd file and setting the path To name the boot CD file and set the path: In the Create Boot CD dialog box, enter the ISO path where to store the boot image on the Core server. If the share 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. NOTE: The file extension must be .iso. When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains).
Viewing the iso image creation progress To view the ISO image creation progress, select the Events tab, and then under Tasks, you can monitor the progress for building the ISO image. NOTE: You can also view the progress of the creation of the ISO image in the Monitor Active Task dialog box. When the creation of the ISO image is complete, it is available on the Boot CDs page, accessible from the Tools menu.
3. In the Universal Recovery Console, click Driver Injection. 4. To locate the compressed driver file, navigate through the filing system and select the file. 5. If you clicked Driver Injection in step 3, click Add Driver. If you clicked Load driver in step 3, click Open. The selected drivers are injected and will be loaded to the operating system after you reboot the target server. Launching a restore from the Core To launch a restore from the Core: 1.
c. Under Destination, from the drop-down menu, select the appropriate destination that is the target volume to perform the bare metal restore of the selected recovery point, and then click Rollback. 3. In the RollbackURC confirmation dialog box, review the mapping of the source of the recovery point and the destination volume for the rollback. To perform the rollback, click Begin Rollback.
Performing a bare metal restore for a Linux machine You can perform a Bare Metal Restore (BMR) for a Linux machine including rollback of the system volume. Using the AppAssure command line utility aamount, roll back to the boot volume base image. Before you can perform a BMR for a Linux machine, you first must do the following: • Obtain a BMR Live CD file from AppAssure support, which includes a bootable version of Linux.
This command rolls back the volume image specified by the ID from the Core to the specified path. The path for the rollback is the path for the device file descriptor and is not the directory to which it is mounted. NOTE: You can also specify a line number in the command instead of the recovery point ID number to identify the recovery point.
4. Verify that the Universally Unique Identifier (UUID) contains the new volumes by using either the blkid command or the ll /dev/disk/by-uuid command. 5. Verify that /etc/fstab contains the correct UUIDs for the root and boot volumes. 6. Install Grand Unified Bootloader (GRUB) by using the following commands: mount --bind /dev/ /mnt/dev mount --bind /proc/ /mnt/proc chroot/mnt/bin/bash grub-install/dev/sda 7. Verify that the /boot/grub/grub.
5 Protecting server clusters About server cluster protection In AppAssure, server cluster protection is associated with the AppAssure agents installed on individual cluster nodes (that is, individual machines in the cluster) and the Core, which protects those agents, all as if they were one composite machine. You can easily configure an 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.
• Basic disks The supported mount types include: • Shared drives that are connected as drive letters (for example, D:) • Simple dynamic volumes on a single physical disk (not striped, mirrored, or spanned volumes) • Shared drives that are connected as mount points Protecting a cluster This topic describes how to add a cluster for protection in AppAssure.
b. In the Volumes dialog box, select the volume(s) to protect, and 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.
4. Click Protect to start protecting this machine with default protection settings. NOTE: The default settings ensure that all volumes on the machine are protected with a schedule of every 60 minutes. 5. To enter custom settings for this machine, (for example, to change the Display name, add encryption, or customize the protection schedule), click Show Advanced Options. 6. Edit the following settings as needed, as described below.
• Modifying Cluster Settings • Configuring Cluster Event Notifications • Modifying the Cluster Retention Policy • Modifying Cluster Protection Schedules • Modifying Cluster Transfer Settings Modifying cluster settings After adding a cluster, you can easily modify basic settings (for example, display name), protection settings (for example, protection schedules, adding or removing volumes, and pausing protection), and more. To modify cluster settings: 1. Do one of the following: • 2.
3. Select one of the options described in the following table. Text Box Description Use Core alert settings This adopts the settings used by the associated core: Use Custom alert settings 4. a. Click Apply. b. Complete Step 5. This lets you configure custom settings. Proceed to Step 4. If you select Custom alert settings, click Add Group to add a new notification group for sending a list of system events. The Add Notification Group dialog box opens. 5.
periods of time and to help with management of these backup snapshots. The retention policy is enforced by a rollup process that helps in aging and deleting old backups. 1. Do one of the following: • In the Core Console, click the Machines tab, and then select the cluster that you want to modify. 2. • In the left navigation area, select the cluster that you want to modify. Click the Configuration tab, and then click Retention Policy. 3.
3. Modify the protection settings as described in Modifying Protection Schedules, beginning with Step 2. Converting a protected cluster node to an agent In AppAssure, you can convert a protected cluster node to an AppAssure agent so that it is still managed by the Core, but it is no longer part of the cluster. This is helpful, for example, if you want to remove the cluster node from the cluster but still keep it protected. To convert a protected cluster node to an agent: 1.
Viewing summary information To view summary information: 1. 2. Do one of the following: • In the Core Console, click the Machines tab, and then select the cluster that you want to view. • In the left Navigation area, under Clusters, select the cluster that you want to view. On the Summary tab, you can view such information as the cluster name, cluster type, quorum type (if applicable), and the quorum path (if applicable).
point transfers. If there is no previous recovery point, all data (the base image) on the protected volumes is transferred. When you pause a snapshot, you temporarily stop all transfers of data from the current machine. For information about forcing snapshots for the individual machines in a cluster, see Forcing A Snapshot. For information about pausing and resuming snapshots for the individual machines in a cluster, see Pausing And Resuming Protection.
Performing a rollback for clusters and cluster nodes A rollback is the process of restoring the volumes on a machine from recovery points. For a server cluster, you perform a rollback at the node, or machine, level. This section provides guidelines for performing a rollback for cluster volumes. Performing a rollback for CCR (Exchange) and DAG clusters To perform a rollback for SCC (Exchange, SQL) clusters: 1. Turn off all nodes except one. 2.
Option Description Keep Recovery Points To keep all currently stored recovery points for this cluster. Remove Recovery Points To remove all currently stored recovery points for this cluster from the repository. Removing cluster nodes from protection Complete the steps in the following procedures to remove cluster nodes from protection. If you just want to remove a node from the cluster, see Converting A Protected Cluster Node To An Agent. To remove a cluster node from protection. 1.
Viewing a cluster or node report You can create and view compliance and errors reports about AppAssure activities for your cluster and individual nodes. The reports include AppAssure activity information about the cluster, node, and shared volumes. For more information about AppAssure reporting, see About Reports. For more information about the exporting and printing options located in the reports toolbar, see About The Reports Toolbar. To view a cluster or node report: 1. Do one of the following: • 2.
Reporting 6 About reports Your DL Appliance lets you generate and view compliance, error, and summary information for multiple core and agent machines. You can choose to view reports online, print reports, or export and save them in one of several supported formats. The formats from which you can choose are: • PDF • XLS • XLSX • RTF • MHT • HTML • TXT • CSV • Image About the reports toolbar The toolbar available for all reports lets you print and save in two different ways.
• Core • Protected Agent • Type • Summary • Status • Error • Start Time • End Time • Time • Total Work About errors reports Errors Reports are subsets of the Compliance Reports and are available for Cores and AppAssure 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.
• Compression/Dedupe Ratio Agents summary The Agents portion of the Core Summary Report includes data for all agents protected by the selected core. Details about the agents are presented in a column view with the following categories: • Name • Protected Volumes • Total protected space • Current protected space • Change rate per day (Average, Median) • Jobs Statistic (Passed, Failed, Canceled) Generating a report for a Core or agent To generate a report for a core or agent: 1.
About the Central Management Console Core reports Your DL Appliance lets you generate and view compliance, error, and summary information for multiple Cores. Details about the Cores are presented in column views with the same categories described in this section. Generating a report from the Central Management Console To generate a report from the Central Management Console: 1. From the Central Management Console Welcome screen, click on the drop-down menu in the upper-right corner. 2.
7 Completing a full recovery of the DL4300 Appliance The data drives on the DL4300 Backup To Disk appliance are located in slots 0–11 and 14–17 and in RAID 6 format, they can sustain up to two drive failures without data loss. The operating system resides on drives 12 and 13, which are formatted as a RAID 1 virtual disk. If both of these disks fail, you must replace the drives and reinstall the necessary software for the appliance to function again.
The capacity of this disk is approximately 278 GB. 11. Select Apply and press . 12. Exit the PERC BIOS Configuration utility and press to reboot the system. Installing the operating system Use the Unified Server Configurator - Lifecycle Controller Enabled (USC-LCE) utility on your appliance to recover the operating system: 1. Locate the operating system installation media. 2. Ensure you have a drive from which to run the media.
The Windows Server Roles and Features, ASP .NET MVC3, LSI Provider, DL Applications, OpenManage Server Administrator and AppAssure Core Software are installed as part of the Recovery and Update Utility. 7. Reboot your system if prompted again. 8. After all services and applications are installed, click Proceed. The AppAssure Appliance Recovery wizard starts. 9. Complete the steps in the Collecting Information and Configuring phase of the AppAssure Appliance Recovery Wizard and then click Next.
Changing the host name manually 8 It is recommended that you select a host name during the initial configuration of the DL4300 Backup to Disk Appliance. If you change the hostname at a later time using Windows System Properties, you must perform the following steps manually to ensure that the new host name takes effect and the appliance functions properly: 1. Stop AppAssure Core service 2. Delete AppAssure server certificates 3. Delete Core server and registry keys 4.
Launching the Core with the new host name To launch the Core using the new host name that you created manually: 1. Start AppAssure Core services. 2. Right-click the AppAssure 5 Core icon on the desktop, and then click Properties. 3. Replace the old server name with the new . For example, https://:8006/apprecovery/admin/Core. 4. Click OK, and then launch the AppAssure Core Console by using the AppAssure 5 Core icon.
Appendix A— scripting 9 About powershell scripting Windows PowerShell is a Microsoft .NET Framework-connected environment designed for administrative automation. AppAssure includes comprehensive client software development kits (SDKs) for PowerShell scripting that enables administrators to automate the administration and management of AppAssure resources by the execution of commands through scripts. It lets administrative users execute user-provided PowerShell scripts at designated occurrences.
NOTE: The configuration file, powershell_ise.exe.config must have the same content as that of the powershell.exe.config file. CAUTION: If the pre-PowerShell or post-PowerShell script fails, the job also fails. Input parameters All available input parameters are used in sample scripts. The parameters are described in the following tables. NOTE: Script files must possess the same name as the sample script files. Table 5. AgentTransferConfiguration (namespace Replay.Common.Contracts.
Method Description public ushort TransferDataServerPort { get; set; } Gets or sets a value containing the TCP port upon which to accept connections from the Core for the actual transfer of data from the agent to the Core. The agent attempts to listen on this port, but if the port is in use, the agent can use a different port instead. The Core uses the port number specified in the BlockHashesUri and BlockDataUri properties of the VolumeSnapshotInfo object for each snapped volume.
Method Description public VolumeImageIdsCollection VolumeImageIds { get; private set; } Gets or sets the volume images to include in the VM export. public ExportJobPriority Priority { get; set; } Gets or sets the priority for export request. NightlyAttachabilityJobRequest (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.
Table 7. TransferPostscriptParameter (namespace Replay.Common.Contracts.PowerShellExecution) Method Description public VolumeNameCollection VolumeNames Gets or sets the collection of volume names for { get; set; } transfer. public ShadowCopyType ShadowCopyType { get; set; } Gets or sets the type of copying for transfer. Available values: Unknown, Copy, and Full. public AgentTransferConfiguration TransferConfiguration { get; set; } Gets or sets the transfer configuration.
Method Description public bool ForceBaseImage { get; set; } Gets or sets the value indicating whether the base image was forced. public bool IsLogTruncation { get; set; } Gets or sets the value indicating whether the job is a log truncation. public uint LatestEpochSeenByCore { get; set; } Gets or sets latest epoch value. Table 9. VirtualMachineLocation (namespace Replay.Common.Contracts.
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).) public override int GetHashCode() Returns the hash code for this VolumeNameCollection. (Overrides Object.GetHashCode().) Table 11. VolumeSnapshotInfo (namesapce Replay.Common.Contracts.
# 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 \AppRecovery Agent 5') $regVal = $regLM.GetValue('InstallLocation') $regVal = $regVal + 'Common.Contracts.dll' [System.Reflection.Assembly]::LoadFrom($regVal) | out-null # Converting input parameter into specific object $TransferPostscriptParameterObject = $TransferPostscriptParameter -as [Replay.Common.
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 contains this script in the PowerShell script folder as PostExportScript.ps1. # receiving parameter from export job param([object]$ExportJobRequest) # building path to Core's Common.Contracts.dll and loading this assembly $regLM = [Microsoft.Win32.
switch ($JobClassMethod) { # working with NightlyAttachability Job NightlyAttachabilityJob { $NightlyAttachabilityJobRequestObject = $NightlyAttachabilityJobRequest -as [Replay.Core.Contracts.Sql.NightlyAttachabilityJobRequest]; null'; echo 'Nightly Attachability job results:'; if($NightlyAttachabilityJobRequestObject -eq $null) { echo 'NightlyAttachabilityJobRequestObject parameter is } else { echo 'AgentId:' $NightlyAttachabilityJobRequestObject.
echo 'AgentId:' $ChecksumCheckJobRequestObject.AgentId; echo 'IsNightlyJob:' $ChecksumCheckJobRequestObject.IsNightlyJob; } break; } # working with Log Truncation Job TransferJob { $TransferJobRequestObject = $TransferJobRequest -as [Replay.Core.Contracts.Transfer.TransferJobRequest]; echo 'Transfer job results:'; if($TransferJobRequestObject -eq $null) { echo 'TransferJobRequestObject parameter is null'; } else { echo 'TransferConfiguration:' $TransferJobRequestObject.
$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.
# working with Log Truncation Job TransferJob { $TransferJobRequestObject = $TransferJobRequest -as [Replay.Core.Contracts.Transfer.TransferJobRequest]; echo 'Transfer job results:'; if($TransferJobRequestObject -eq $null) { echo 'TransferJobRequestObject parameter is null'; } else { echo 'TransferConfiguration:' $TransferJobRequestObject.TransferConfiguration; echo 'StorageConfiguration:' $TransferJobRequestObject.
Getting help 10 Finding documentation and software updates In the AppAssure Core console there are direct links to AppAssure, Appliance documentation, and software updates. To access the links, click the Appliance tab, and then click Overall Status. Links to the software updates and documentation are located under the Documentation section.
