Dell DL1000 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 © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Introducing your Dell DL1000............................................................................ 7 Dell DL1000 core technologies............................................................................................................ 7 Live Recovery................................................................................................................................... 7 Universal Recovery.........................................................................................
Configuring an Email notification template ................................................................................ 23 Configuring repetition reduction .................................................................................................24 Configuring Event Retention ....................................................................................................... 24 Managing repositories ...............................................................................................
Viewing machine logs .................................................................................................................. 47 Uploading machine logs............................................................................................................... 47 Canceling operations on a machine ........................................................................................... 47 Viewing machine status and other details ..................................................................
Replicating to a core managed by a third party...........................................................................86 Replicating a new agent ...............................................................................................................86 Replicating agent data on a machine .......................................................................................... 87 Setting replication priority for an agent ..............................................................................
Introducing your Dell DL1000 1 Your Dell DL1000 combines backup and replication into a unified data protection product. It provides reliable application data recovery from your backups to protect virtual machines and physical machines. Your appliance is capable of handling up to terabytes of data with built-in global deduplication, compression, encryption, and replication to specific private or public cloud infrastructure.
True Global Deduplication True Global Deduplication eliminates redundant or duplicate data by performing incremental block-level backups of the machines. The typical disk layout of a server consists of the operating system, application, and data. In most environments, the administrators often use a common version of the server and desktop operating system across multiple systems for effective deployment and management.
Dell DL1000 Smart Agent The Smart Agent is installed on the core-protected machine. The 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 block-level snapshots’ forever approach prevents repeated copying of the same data from the protected machine to the Core. After the agent is configured, it uses smart technology to track the changed blocks on the protected disk volumes.
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. 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.
site or a managed service provider for off-site recovery. A basic local deployment consists of a backup server called the Core and one or more protected machines known as the agents. The off-site component is enabled using replication that provides full recovery capabilities in the disaster recovery site. The DL1000 Core uses base images and incremental snapshots to compile recovery points of protected agents.
Figure 3. DL1000 Multi—Core Deployment Architecture Other information you may need NOTE: For all Dell OpenManage documents, go to dell.com/openmanagemanuals. NOTE: Always check for updates on dell.com/support/home and read the updates first because they often supersede information in other documents. NOTE: For any documentation related to Dell OpenManage Server Administrator, see dell.com/ openmanage/manuals.
Resource Media Any media that ships with your system that provides documentation and tools for configuring and managing your system. This includes those pertaining to the operating system, system management software, system updates, and system components that you purchased with your system.
Working with your DL1000 2 Accessing the DL1000 Core Console To access the DL1000 Core Console: 1. Update trusted sites in your browser. 2. Configure your browsers to remotely access the DL1000 Core Console. See Configuring Browsers To Remotely Access The Core Console. 3. Perform one of the following to access the DL1000 Core Console: • Log on locally to your DL1000 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. To modify browser settings in Internet Explorer and Chrome: 1. Open Internet Explorer. 2. From the Tools menu, select Internet Options, Security tab. 3.
• Time of last contact with the licensing server • Next scheduled attempt of contact with the licensing server • License constraints Changing a license key To change a license key: 1. Navigate to the Core Console, select Configuration → Licensing. The Licensing page is displayed. 2. From the License Details page, click Change. The Change License Key dialog box is displayed. 3. In the Change License Key dialog box, enter the new license key and then click OK.
7. c. AppAssure Core Clear the browser cache. 8. Close the browser and restart the core console from the desktop icon. Changing the OS language during installation On a running Windows installation, you can use the control panel to select language packs and configure additional international settings. To change OS language: NOTE: It is recommended that the OS language and the AppAssure language be set to the same language. otherwise, some messages may be displayed in mixed languages.
4. Click OK. Changing the nightly job time The Nightly Job option schedules jobs such as rollup, attachability, and truncation for agents protected by the Core. To adjust the nightly job time: 1. Navigate to the Core Console and select Configuration → Settings. 2. In the Nightly Jobs section, click Change. The Nightly Jobs dialog box appears. 3. In the Nightly Jobs Time text box, enter a new start time. 4. Click OK.
deduplication cache holds references to unique blocks. By default, the deduplication cache is 1.5 GB. If the amount of redundant information isso large that the deduplication cache is full, your repository can no longer take full advantage of further deduplication across your repository for newly added data. You can then increase the size of the deduplication cache by changing the deduplication cache configuration in the Core Console. To configure deduplication cache settings: 1.
6. Click OK. Modifying deploy settings To modify deploy settings: 1. Navigate to the Core Console and click the Configuration tab, and then Settings. 2. In the Deploy Settings pane, click Change. The Deploy Settings dialog box displays. 3. In the Agent Installer Name text box, enter the name of the agent executable file. The default is Agentweb. exe. 4. In the Core Address text box, enter the address for the core. 5.
Managing Events 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, e-mail SMTP settings, Server Settings, Enabled Trace Logs, Cloud Configuration, repetition reduction, and event retention.
• To create alerts specific to errors, warnings, informational messages, or a combination, select one of the following: – red triangle icon (Error) – yellow triangle icon (Warning) – blue circle (Information) – curved arrow (Restores default) • To create alerts for specific events click the > symbol next to the relevant group and select the check box to enable the alert. Configuring notification options 1. In the Notification Options panel, specify how to handle the notification process.
3. Enter details for the email server as follows: 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. 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. Username Enter a user name for the email server.
4. Text Box Description Email Subject Enter a subject for the email template. It is used to define the subject of the email notification template; for example, - . Email Enter information for the body of the template that describes the event, when it occurred, and the severity. Click Send Test Email perform the following:. a. In the Send Test Email dialog box, enter a destination email address for the test message and click Send. b.
Key repository concepts and considerations include: • The repository is based on the AppAssure Scalable Object File System. • 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. Viewing repository details To view repository details: 1. In the Core Console, click Configuration → Repositories. 2.
Adding an encryption key To add an encryption key: 1. In the Core Console, click Configuration → Security. 2. From the Actions drop–down menu, click Add Encryption Key. The Create Encryption Key dialog box displays. 3. 4. In the Create Encryption Key dialog box, enter the details for the key described as follows. Text Box Description Name Enter a name for the encryption key. Description Enter a description of the encryption key. It is used to provide more details for the encryption key.
Importing an encryption key To import an encryption key: 1. From the Core Console, click Configuration → Security. 2. From the Actions drop-down menu, and then click Import. The Import Key dialog box appears. 3. In the Import Key dialog box, click Browse to locate the encryption key that you want to import, and then click Open. 4. Click OK. Exporting an encryption key To export an encryption key: 1. From the Core Console click Configuration → Security. 2.
Adding a cloud account Before you can export your archived data to a cloud, add the account for your cloud provider in the Core Console. To add a cloud account: 1. In the Core Console, click the Tools tab. 2. In the left menu, click Clouds. 3. On the Clouds page, click Add New Account. The Add New Account dialog box opens. 4. 5. Select a compatible cloud provider from the Cloud Type drop-down list. Enter the details described in the following table based on the cloud type selected in Step 4. Table 1.
Cloud Type Text Box Rackspace Cloud Block Storage User Name 6. Description Enter the user name for your Rackspace cloud account. API Key Enter the API key for this account. Display Name Create a display name for this account in AppAssure; for example, Rackspace 1. Click Add. The dialog box closes, and your account is displayed on the Clouds page of the Core Console. Editing a cloud account Perform the following steps to edit a cloud account: 1. In the Core Console, click the Tools tab. 2.
2. • Click Next. Click Reset. Returns the configuration to the following default settings: – Request Timeout: 01:30 (minutes and seconds) – Retry Count: 3 (attempts) Removing a Cloud account You can remove a Cloud account to, discontinue your cloud service, or stop using it for a particular Core. To remove a cloud account: 1. On 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 Remove. 4.
NOTE: Dell recommends you to create RASR USB key after you have set up the Appliance. To create RASR USB key, see Creating the RASR USB Key section . 1. Insert the RASR USB key created. 2. Reboot the appliance through the RASR USB key. 3. Click on Rapid Appliance Self Recovery. A welcome screen is displayed. 4. Click Next. The Prerequisites check screen is displayed. NOTE: Ensure all the hardware,and other prerequisites are checked before performing the RASR. 5. Click Next.
6. NOTE: Make sure to use the Safely Remove USB Drive or the Windows Eject Drive function to prepare the USB key for removal. Otherwise, the content in the USB key may be damaged and the USB key will not work as expected. Remove the key, label, and store for future use.
Protecting workstations and servers 3 About protecting workstations and servers To protect your data using DL1000, 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 chapter, the word machine also refers to the AppAssure Agent software installed on that machine.
A message indicating that the deployment has started appears. You can view the progress in the Events tab. 7. Click Show details to view more information about the status of the agent deployment. 8. Click OK. Protecting a machine This topic describes how to start protecting the data on a machine that you specify. NOTE: The machine must have the AppAssure Agent software installed in order to be protected.
8. Select the appropriate protection schedule: • To use the default protection schedule, in the Schedule Settings option, select Default protection (3 hour snapshots of all volumes). With a default protection schedule, the Core will take snapshots of the agent machine once every 3 hours. Snapshots of the agent machine can be taken once every hour (minimum).
Text Box Description Passphrase Enter the passphrase used to control access. Confirm Passphrase Re-enter the passphrase you just entered. 16. Click Finish to save and apply your settings. The first time protection is added for a machine, a base image (that is, a snapshot of all the data in the protected volumes) will transfer to the repository on the Core following the schedule you defined, unless you specified to initially pause protection.
• Port — Specifies the port number on which the Core communications with the Agent on the machine. The default value is 8006. • Repository — Select the repository in which to store data from this agent. NOTE: You can store data from multiple agents in a single repository. • 4. Encryption Key — Specifies whether encryption should be applied to the data for every volume on this machine to be stored in the repository.
Creating custom schedules 1. On the Protection Schedule page of the Protect Machine or Protect Multiple Machines Wizard, to change the interval schedule for any period, do the following: a. Select Periods. The existing periods display and can be modified. Editable fields include a start time, end time, and interval (in minutes) for each period. b. Click in the interval field and type an appropriate interval in minutes.
5. If you want to remove an existing time period from the schedule, clear the check boxes next to each time period option. Options include the following: • 6. Mon - Fri. This range of time denotes a typical five-day work week. • Sat - Sun. This range of time denotes a typical weekend. If the weekday start and end times are from 12:00 AM to 11:59 PM, then a single period exists. To change the start or end time of a defined period, do the following: a. Select the appropriate time period. b.
Text Box Display Name Description Enter a display name for the machine. A name for this machine to be displayed in the Core Console. By default, this is the host name of the machine. You can change the display name 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 Core uses the default port 8006 to communicate with this machine. Encryption Key Edit the encryption key if necessary.
Viewing license information You can view current license status information for the AppAssure Agent software installed on a machine. To view license information: 1. In the navigation pane, select the machine that you want to view. 2. Click Configuration → Licensing. The Status screen displays the details about the product licensing. Modifying transfer settings You can modify the settings to manage the data transfer processes for a protected machine.
The Transfer Settings dialog box appears. 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 • SQLServerWriter • System Writer • Task Scheduler Writer • VSS Metadata Store Writer • WMI Writer Transfer Data Server Port Sets the port for transfers. The default setting is 8009. Transfer Timeout Specifies in minutes and seconds the amount of time to allow a packet to be static without transfer. Snapshot Timeout Specifies in minutes and seconds the maximum time to wait to take a snapshot. 5.
Table 2. Creating an archive Option Text Box Description Local Output location Enter the location for the output. It is used to define the location path where you want the archive to reside; for example, d:\work\archive. Network Output location Enter the location for the output. It is used to define the location path where you want the archive to reside; for example, \\servername \sharename. User Name Enter a user name. It is used to establish logon credentials for the network share.
Text Box Description • Select Entire Target to reserve all available space in the path provided on the destination provided in Step 4. (for example, if the location is D:\work \archive, all of the available space on the D: drive is reserved). • Select the blank text box, use the up and down arrows to enter an amount, and then select a unit of measurement from the drop-down list to customize the maximum space you want to reserve. NOTE: Amazon cloud archives are automatically divided into 50 GB segments.
Table 3. Importing an archive Option Text Box Description Local Output location Enter the location for the output. It is used to define the location path where you want the archive to reside; for example, d:\work\archiveea. Network Output location Enter the location for the output. It is used to define the location path where you want the archive to reside; for example, \\servername \sharename. User Name Enter a user name. It is used to establish logon credentials for the network share.
Archiving to a cloud You can archive your data to a cloud by uploading it to a variety of cloud providers directly from the Core Console. Compatible clouds include Windows Azure, Amazon, Rackspace, and any OpenStack-based provider. To export an archive to a cloud: • • • Add your cloud account to the Core Console. For more information see, Adding A Cloud Account. Archive your data and export it to your cloud account. Retrieve archived data by importing it from the cloud location.
1. In the Core Console, navigate to the protected machine you want to view. The information about the machine displays on the Summary page.
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. See Protecting Multiple Machines . NOTE: This step can be skipped if you selected the Protect Machine After Install option during deployment. 4. Monitor the activity of the batch protection.
• The encryption key, if any, used for this protected agent • The version of the Agent software Protecting multiple machines After bulk deploying the AppAssure Agent software to the Windows machines, you must protect the machines to protect the data. If you select Protect Machine After Install when you deployed the agent, you can skip this procedure. NOTE: Agent machines must be configured with a security policy that makes remote installation possible. To protect multiple machines: 1.
• If you have selected a Typical configuration for the Protect Multiple Machines Wizard and specified custom protection, click Next and set up a custom schedule. • 9. If you have selected Advanced configuration for the Protect Machine Wizard, click Next and proceed to Step 9 to see repository and encryption options. On the Repository page select Use an existing repository. 10. Click Next. The Encryption page appears. 11. To enable encryption, on the Encryption page, select Enable Encryption.
Recovering data 4 Managing recovery The AppAssure 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. These snapshots are application-aware, meaning all open transactions and rolling transaction logs are completed and caches are flushed to disk before creating the snapshot.
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. Type Defines a recovery point as either base or differential. Creation Date Displays the date when the recovery point was created. Size Displays the amount of space that the recovery point consumes in the repository. Viewing a specific recovery point To view a specific recovery point: 1.
Text Box Description 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. Mounting a recovery point for a Windows machine In AppAssure, you can mount a recovery point for a Windows machine to access stored data through a local file system.
Dismounting all recovery points To dismount all recovery points: 1. Navigate to the Core Console, click Tools → Mounts . 2. On the Local Mounts page, click Dismount All. 3. In the Dismounting the Recovery Point window, click Yes to confirm. Mounting a recovery point for a Linux machine Using the aamount utility in AppAssure, you can remotely mount a volume from a recovery point as a local volume, on a Linux machine. 1.
• 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. The Delete dialog box appears. In the Delete Range dialog box, specify the range of recovery points that you want to delete by using a start date and time and an end date and time, and then click Delete. Deleting an orphaned recovery point chain An orphaned recovery point is an incremental snapshot that is not associated with a base image.
Restoring data Using AppAssure, 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.
Dynamic and basic volumes support limitations Dell AppAssure supports taking snapshots of all dynamic and basic volumes. AppAssure also supports exporting simple dynamic volumes that are on a single physical disk. Simple dynamic volumes are not striped, mirrored or spanned volumes. Dynamic disks (except simple dynamic disks as previously described) are not available for selection in the Export Wizard. Non-simple, dynamic volumes have arbitrary disk geometries that cannot be fully interpreted.
• 3. 4. Force: To force a new export. This option could be helpful when virtual standby is paused and then resumed, which means the export job will restart only after a new transfer. If you do not want to wait for the new transfer, you could force an export. To remove an export from the system, click Remove. When you remove an export, it is permanently removed from the system and you will not be able to re-start it.
Performing a one-time ESXi export To perform a one-time ESXi 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 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.
• 2. 3. 4. On the Virtual Standby tab, click Add to launch the Export Wizard. On the Protected Machines page of the Export Wizard, select the protected machine you want to export, and then click Next. • Navigate to the machine you want to export, and click Actions → Export → Virtual Standby. On the Destination page of the Export Wizard, in the Recover to a Virtual Machine drop-down menu, select ESXi.
Performing a one-time VMware Workstation export To perform a one-time VMware Workstation export: 1. In the Core Console, navigate to the machine you want to export. 2. On the Summary 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.
Text Box Description Memory Specify the memory usage for the virtual machine by clicking one of the following: • Use the same amount of RAM as the source machine - To specify that the RAM configuration is the same as the source machine. • Use a specific amount of RAM - To specify how much RAM to use; for example, 4096 Megabytes (MB). The minimum amount allowed is 512 MB and the maximum is determined by the capability and limitations of the host machine. (recommended) 3. Click Next. 4.
Text Box Description Virtual Machine Enter a name for the virtual machine being created; for example, VM-0A1B2C3D4. NOTE: The default name is the name of the source machine. Version Memory Specify the version of VMware Workstation for the virtual machine. You can choose from: • VMware Workstation 7.0 • VMware Workstation 8.0 • VMware Workstation 9.
Defining one-time settings for performing a 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.
To perform a continuous (virtual standby) Hyper-V export: 1. In the Core Console, on the Virtual Standby tab, click Add to launch the Export Wizard. On the Protected Machines page of the Export Wizard. 2. Select the machine you want to export and then click Next. 3. On the Summary tab, click Export → Virtual Standby. 4. 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. 5.
12. On the Summary page, click Finish to complete the wizard and to start the export. NOTE: You can monitor the status and progress of the export by viewing the Virtual Standby or Events tab Exporting Windows data using Oracle VirtualBox export In AppAssure, you can choose to export data using VirtualBox Export by performing a one-time or continuous export, or by establishing a continuous export (for virtual standby). Complete the steps in the following procedures for the appropriate type of export.
• On the Virtual Standby tab, click Add to launch the Export Wizard. On the Protected Machines page of the Export Wizard, select the protected machine you want to export, and then click Next. • 2. Navigate to the machine you want to export, and, on the Summary tab in the Actions drop-down menu for that machine, click Export → Virtual Standby. On the Destination page in the Export Wizard, in the Recover to Virtual machine drop-down menu, select VirtualBox, and then click Next. 3.
Restoring Volumes from a Recovery Point You can restore the volumes on a protected machine from the recovery points stored in the AppAssure Core. To restore volumes from a recovery point: 1. In the Core Console, click the Restore tab. The Restore Machine Wizard appears. 2. From the Protected Machines page, select the protected machine for which you want to restore data, and then click Next.
7. On the Volume Mapping page, for each volume in the recovery point that you want to restore, select the appropriate destination volume. If you do not want to restore a volume, in the Destination Volumes column, select Do not restore. 8. Select Show advanced options and then do the following: • For restoring to Windows machines, if you want to use Live Recovery, select Live Recovery.
• Boot the agent machine from an ISO image, if possible. • If not, copy the ISO image to physical media (a CD or DVD), load the disc in the agent machine, configure the machine to load from the boot CD, and restart from the boot CD. NOTE: You may need to change the BIOS settings of the agent machine to ensure the volume that loads first is the boot CD. The agent machine, when started from the boot CD, displays the Universal Recovery Console (URC) interface.
databases after the restore is complete, select Automatically remount all databases after the recovery point is restored. Click Finish. 21. Click OK to confirm the status message that the restore process has started. 22. To monitor the progress of your restore action, on the Core Console, click Events. Restoring volumes for a Linux machine using the Command Line In AppAssure, you can restore volumes on your protected Linux machines using the command-line aamount utility.
8. Upon a successful rollback, the aamount utility automatically mounts and reattach the kernel module to the rolled back volume if the target was previously protected and mounted. If not, mount the rollback volume to the local disk and then verify that the files are restored. For example, you can use the sudo mount command and then the ls command.
To create a bootable CD ISO image: 1. From the Core Console on which the server you want to restore is located, select the Core and then click the Tools tab. 2. Click Boot CDs. 3. Select Actions, and then click Create Boot ISO. The Create Boot CD dialog box displays. To complete the dialog box, use the following procedures.
The injected drivers appear highlighted in the Drivers pane. Creating the boot cd To create a boot CD, after you have named the boot CD and specified the path, created a connection and optionally injected the drivers, from the Create Boot CD screen, click Create Boot CD. The ISO image is then created. 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.
To inject drivers to your target server: 1. Download the drivers from the manufacturer’s website for the server and unpack them. 2. Compress the folder that contains the drivers by using a file compressing utility (for example, Win Zip) and copy it to the target server. 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.
d. Click Restore, and then proceed to step 3. 2. To manually map volumes, do the following: a. On the Disk Mapping page of the Restore Machine Wizard, select the Manually Map Volumes tab. b. In the Volume Mapping area, under Source Volume, verify that the source volume is selected and that the appropriate volumes are both listed beneath and are selected. c.
Launching a bare metal restore for a Linux machine Your DL1000 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.
Replicating recovery points 5 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.
Roadmap for performing replication To replicate data using AppAssure, you must configure the source and target cores for replication. After you configure replication, you can then replicate data of the protected machine, monitor and manage replication, and perform recovery. Performing replication in AppAssure involves performing the following operations: • Configure self-managed replication. For more information on replicating to a self-managed target core, see Replicating To A Self-Managed Core.
Text Box Description Port Enter the port number on which the AppAssure Core communicates with the machine. The default port number is 8006. User Name Enter the user name for accessing the machine. For example, Administrator. Password Enter the password for accessing the machine. If the Core you want to add has been paired with this source core previously, perform the following: a. b. c. d. Select Use an existing target core. Select the target core from the drop-down list. Click Next.
Text Box Description required for copying the seed drive, but is not reserved immediately after starting the copying process). • Select the blank text box, enter an amount, and then select a unit of measurement from the drop-down list to customize the maximum space you want to reserve. Customer ID (optional) Optionally, enter the customer ID that was assigned to you by the service provider.
3. Under Incoming Replication, select the correct source core by using the drop-down menu, and then click Consume. The Consume window appears. 4. 5. 6. For Location type, select one of the following options from the drop-down list: • Local • Network • Cloud Enter the following information as needed: Text Box Description Location Enter a path to where the seed drive is located, such as a USB drive or a network share (for example, D:\).
4. Click Yes to confirm the action. The seed drive is removed. If there are no more seed drives that exist on the source core, then the next time that you open the Replication tab, the Outstanding Seed Drive (#) link and Outstanding seed drives section do not appear. Replicating to a core managed by a third party A third-party core is a target core that it managed and maintained by an MSP. Replicating to a core managed by a third party does not require you to have access to the target core.
Text Box Description 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. Schedule Select one of the following options: • Protect all volumes with default schedule • Protect specific volumes with custom schedule NOTE: The default schedule is every 15 minutes.
• 1 • 2 • 3 • 4 NOTE: The default priority is 5. If one agent is given the priority 1, and another agent is given the priority Highest, the agent with the Highest priority replicates before the agent with the 1 priority. 3. Click OK. Monitoring replication When replication is set up, you can monitor the status of replication tasks for the source and target cores. You can refresh status information, view replication details, and more. To monitor replication: 1.
Section Description Available Actions and create a seed drive for the new protected machine's initial transfer. Incoming Replication Lists all source machines from which the target receives replicated data. It includes the remote core name, state, machines, and progress. On a target core, in the dropdown menu, you can select the following options: • • 3. Details — Lists the ID, host name, customer ID, email address, and comments for the replicated core.
NOTE: Removing a source core results in the removal of all replicated machines that are protected by that core. Removing a protected machine from replication on the source Core To remove a protected machine from replication on the source core: 1. From the source core, open the Core Console, and click the Replication tab. 2. Expand the Outgoing Replication section. 3. In the drop-down menu for the protected machine that you want to remove from replication, click Delete. 4.
3. Option Description Relationship Only Removes the source core from replication but retains the replicated recovery points. With Recovery Points Removes the source core from replication and deletes all replicated recovery points received from that machine. In the Incoming Replication dialog box, click Yes to confirm deletion.
3. On the Actions menu for that core, click Failover. The Fail Over dialog box appears and lists the next steps required for completing a failover. 4. Click Continue. 5. In the left navigation area, under Protected Machines, select the machine that has the associated AppAssure Agent software with recovery points. 6. Export the backup recovery point information on that agent to a virtual machine. 7. Export the backup recovery point information on that agent to a virtual machine. 8.
NOTE: When you launch the restore you must use the recovery points that were imported from the target core to the agent on the virtual machine. 16. Wait for the BMR reboot and for the agent service to restart, and then view and record the network connection details of the machine. 17. Navigate to the Core Console on the source core, and, on the Machines tab, modify the machine protection settings to add the new network connection details. For more information, Configuring Machine Settings. 18.
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.
Getting help 7 Finding documentation and software updates Direct links to AppAssure and DL1000 Appliance documentation and software updates are available from the Core Console. Documentation To access the link for documentation: 1. On the Core Console, click the Appliance tab. 2. From the left pane, navigate Appliance → Documentation link. Software updates To access the link for software updates: 1. On the Core Console, click the Appliance tab. 2.
