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 © 2014 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 Event Retention ....................................................................................................... 23 Managing Repositories .......................................................................................................................23 Viewing Repository Details........................................................................................................... 24 Checking A Repository ..........................................................................
Canceling Operations On A Machine ..........................................................................................48 Viewing Machine Status And Other Details .................................................................................49 Managing Multiple Machines .............................................................................................................50 Deploying To Multiple Machines ..........................................................................................
Replicating Agent Data On A Machine ........................................................................................ 91 Setting Replication Priority For An Agent .................................................................................... 92 Monitoring Replication .................................................................................................................92 Managing Replication Settings .....................................................................................
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 Dell DL1000 is capable of handling up to petabytes 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.
the agent. The Core then stores the snapshot backups in the repository, which resides on the appliance. Cores are paired for replication. The repository resides on internal storage within the Core. The Core is managed by accessing the following URL from a JavaScript enabled web browser: https://CORENAME:8006/apprecovery/admin. Dell DL1000 Smart Agent The Smart Agent is installed on the machine that is protected by the Core.
Replication begins with seeding — the initial transfer of deduplicated base images and incremental snapshots of the protected agents 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 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/manuals 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.
Interoperability Guide Provides information on supported software and hardware for the DL1000 appliance as well as usage considerations, recommendations, and rules.
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.
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.
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. Navigate to the Core Console, click Configuration → Settings. 2. In the Deduplication Cache Configuration section, click Change.
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.
3. 4. Select Enable email notifications, and then enter details for the email server as follows: 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.
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, you must 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. 4. Select a compatible cloud provider from the Cloud Type drop-down list. The Add New Account dialog box opens.
5. Enter the details described in the following table based on the cloud type selected in Step 4. 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. Secret Key Enter the secret key for this 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. Monitoring Your DL1000 You can monitor the status of the DL1000 Appliance subsystems by using the Appliance tab Overall Status page.
5. Click Next. The Recovery Mode Selection screen is displayed with three options: 6. • System Recovery • Windows Recovery Wizard • Factory Reset Select Factory Reset option. This option will recover the operating system disk from the factory image. 7. Click Next. The Storage Configuration screen is displayed. 8. In the OS Recovery screen, following warning message is displayed: This operation will recover the operating system. All OS disk data will be overwritten. in a dialog box. 9.
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.
6. Click Deploy. 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.
7. The host name or IP address you specified in the Connect dialog box appears in this text field. Optionally, enter a new name for the machine to be displayed in the Core Console. 8. Select the appropriate protection schedule: • To use the default protection schedule, in the Schedule Settings option, select Default protection (hourly snapshots of all volumes). With a default protection schedule, the Core will take snapshots of the agent machine once every 3 hours.
15. Enter the information as described in the following table to add an encryption key for the Core. Text Box Description Name Enter a name for the encryption key. Description Enter a description to provide additional details for the encryption key. 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.
3. Enter logon and protection settings as follows: • Host name — Specifies the host name or IP address of the machine that you want to protect. • User name — Specifies the user name used to connect to this machine; for example, administrator. • Password — Specifies the password used to connect to this machine. • Protect machine after install — Selecting this option enables AppAssure to take a base snapshot of the data after you add the machine for protection. This option is selected by default.
the interval on weekends from 60 minutes to 180 minutes, resulting in snapshots every three hours when traffic is low. Other options in the Protection Schedule Wizard page include for a setting a daily protection time. This results in a single backup daily at the period defined (the default setting is 12:00 PM). The option to initially pause protection prevents a base image from occurring (and in fact, prevents all backups) until you explicitly resume protection.
To modify protection schedules: 1. In the Core Console, select the machine with a defined protection schedule that you want to change. The Summary tab displays for the machine. 2. Select the volumes for the protected machine that you want to change, and click Set a schedule. To select all volumes at once, click in the checkbox in the header row. Initially, all volumes share the same protection schedule.
9. When your protection schedule meets your requirements, click Apply. The Protection Schedule dialog box closes. Configuring Protected Machine Settings After you add protection for machines in AppAssure, you can modify basic machine configuration settings (such as name and host name), protection settings (changing the protection schedule for volumes on the machine, adding or removing volumes, or pausing protection), and more.
To view system information for a machine: 1. In the left navigation area of the Core Console, under Protected Machines, select the machine to view detailed system information. 2. Click the Tools tab.
Restore A process that restores backup information on a protected machine. Data transfer in DL1000 involves the transmission of a volume of data along a network from AppAssure Agent machines to the Core. In the case of replication, transfer also occurs from the originating or source Core to the target Core. Data transfer can be optimized for your system through certain performance option settings.
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 • 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.
3. Enter the details for the archive as described in the following table based on the location type you selected in Step 3. 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.
7. On the Options page, enter the information described in the following table. Text Box Description Maximum Size Large archives of data can be divided into multiple segments. Select the maximum amount of space you want to reserve for creating the archive by doing one of the following: • • Select Entire Target to reserve all available space in the path provided on the destination provided in Step 4.
9. On the Date Range page, enter the Start Date and Expiration Date of the recovery points to be archived. • To enter a time, click on the time shown (default, 8:00 AM) to reveal the slide bars for selecting hours and minutes. • To enter a date, click the text box to reveal the calendar, and then click on the preferred day. 10. Click Finish. Importing An Archive To import an archive: 1. 2. 46 In the Core Console, click Tools → Archive → Import.
3. Enter the details for the archive as described in the following table based on the location type you selected in Step 3. 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.
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. For more information see, Creating An Archive.
Viewing Machine Status And Other Details To view machine status and other details: 1. In the Core Console, navigate to the protected machine you want to view. The information about the machine displays on the Summary page.
Managing Multiple Machines This topic describes the tasks that administrators perform to deploy AppAssure 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. See Protecting Multiple Machines .
3. Optionally, click on any link for a protected machine.
7. On the Protection page, select the appropriate protection schedule: • To use the default protection schedule, then in the Schedule Settings option, select Default protection (hourly snapshots of all volumes). • 8. If you want to define a different protection schedule, then in the Schedule Settings option, select Custom protection and then click Next.
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 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.
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.
3. Select one of the following options: • To delete all currently stored recovery points, click Delete All. • To delete a set of recovery points in a specific data range, click Delete Range. 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.
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 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. AppAssure therefore does not support the export of complex or non-simple dynamic volumes.
Managing Exports On the Virtual Standby tab in the Core Console, you can view the status of exports that you have set up, including one-time exports and continuous exports for virtual standby. On this tab, you can manage exports by pausing, stopping, removing exports, or viewing a queue of upcoming exports.
NOTE: Only the Dell DL1000, 3 TB with 2 VMs configuration supports the one-time export and continuous export (virtual standby) capabilities. 1. On the Core Console, navigate to the Virtual Standby tab. On the Virtual Standby tab you can view a table of saved export settings, which includes the information described in the following table. Menu Description Status NOTE: The status of the virtual standby configuration, is defined by the color of the icon.
• 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. 2. In the Core Console, navigate to the machine you want to export. 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.
Performing A Continuous (Virtual Standby) ESXi Export To perform a continuous (virtual standby) ESXi export: 1. In the Core Console, perform one of the following: • 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.
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.
Defining One-Time Settings For Performing A VMware Workstation Export To define one-time settings for performing a VMware Workstation export: 1. On the Destination page in the Export Wizard, in the Recover to Virtual machine drop-down menu, select VMware Workstation, and then click Next. 2. On the Virtual Machine Options page, enter the parameters for accessing the virtual machine as described in the following table.
4. On the Summary page, click Finish to complete the wizard and start the export. NOTE: You can monitor the status and progress of the export by viewing the Virtual Standby or Events tab. Performing a Continuous (Virtual Standby) VMware Workstation Export To perform a continuous (virtual standby) VMware Workstation export: 1. In the Core Console, perform one of the following: • On the Virtual Standby tab, click Add to launch the Export Wizard.
4. On the Virtual Machine Options page, enter the parameters for accessing the virtual machine as described in the following table. Text Box Description Target Path Specify the path of the local folder or network share on which to create the virtual machine. NOTE: If you specified a network share path, enter a valid logon credentials for an account that is registered on the target machine. The account must have read and write permissions to the network share.
Exporting Windows Data Using Hyper-V Export In AppAssure, you can choose to export data using Hyper-V Export by performing a one-time or continuous export. Complete the steps in the following procedures to export using Hyper-V Export for the appropriate type of export. 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.
7. To specify the disk format, next to Disk Format, click one of the following: • VHDX • 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. 8. On the Volumes page, select the volume(s) to export; for example, C:\. Your selected volumes should be no larger than 2040GB for VHD.
9. To specify the disk format, next to Disk Format, click one of the following: • VHDX • 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. 10. On the Volumes page, select the volume(s) to export; for example, C:\. Your selected volumes should be no larger than 2040 GB for VHD.
9. 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. Performing a Continuous VirtualBox Export To perform a continuous VirtualBox export: 1. In the Core Console, do one of the following: • On the Virtual Standby tab, click Add to launch the Export Wizard.
7. Click Next. 8. On the Volumes page, select the volumes to export, for example, C:\ and D:\, and then click Next. 9. 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. 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.
6. To connect to the Universal Recovery Console (URC) on the target machine, do the following: a. Select I already have a boot CD running on the target machine. b. In the IP address text box, enter the IP address of the target machine with the boot CD. c. In the Authentication Key text box, enter the authentication key from the URC on the target machine, and then click Next. The Disk Mapping page appears. Proceed to Step 20. 7.
13. To inject a driver, do the following: a. Select Add an archive of drivers. b. Navigate to a ZIP file containing the archive, select the ZIP file, and click Open. The archive uploads and appears in the Driver Injection page. c. Then click Next. 14. On the ISO Image page, you can see the status as the boot CD ISO image is created. When the boot CD is successful, click Next. The Connection page appears. 15. Start the agent machine for which you want to restore data from the boot CD.
19. In the Disk Mapping Preview page, review the parameters of the restore actions you selected. To perform the restore, click Finish. CAUTION: If you select Finish, all existing partitions and data on the target drive will be removed permanently, and replaced with the contents of the selected recovery point, including the operating system and all data. The Restore Machine Wizard closes, and the data is restored from the selected volumes of the recovery point to the target machine. Proceed to Step 22. 20.
6. To select a recovery point for rollback, enter the following command: r [volume_recovery_point_ID_number] [path] 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: To identify the recovery point, you can also specify a line number in the command instead of the recovery point ID number.
Creating A Bootable CD ISO Image To perform a BMR for a Windows machine, you must create a bootable CD/ISO image in the AppAssure Core Console, which contains the AppAssure Universal Recovery Console interface. The AppAssure Universal Recovery Console is an environment used to restore the system drive or the entire server directly from the AppAssure Core. The ISO image that you create is tailored to the machine being restored; therefore, it must contain the correct network and mass storage drivers.
Injecting Drivers In A Boot CD Driver injection is used to facilitate the operability between the recovery console, network adapter, and storage on the target server. If you anticipate restoring to dissimilar hardware, you must inject storage controller, RAID, AHCI, chipset and other drivers in the boot CD. These drivers make it possible for the operating system to detect and operate all devices successfully. NOTE: Keep in mind that the boot CD will automatically contain Windows 7 PE 32-bit drivers.
To load a boot CD: 1. Navigate to the new server, load the boot CD, and then start the machine. 2. Specify to Boot from CD-ROM, which loads the following: • Windows 7 PE • AppAssure 5 Agent software The AppAssure Universal Recovery Console starts and displays the IP address and authentication password for the machine. 3. Record the IP address displayed in the Network Adapters Settings pane and the authentication password displayed in the Authentication pane.
5. Expand the recovery point from which you want to restore, then click Rollback. 6. In the Rollback dialog box, under Choose Destination, select Recovery Console Instance. 7. In the Host and Password text boxes, enter the IP address and the authentication password for the new server to which you want to restore data. NOTE: The Host and Password values are the credentials you recorded in the previous task. 8. Click Load Volumes to load the target volumes to the new machine.
NOTE: To return to the recovery points for the source machine from the Active Task dialog box, click Close. Starting The Restored Target Server To start the restored target server: 1. Navigate back to the target server, and in the AppAssure Universal Recovery Console interface, click Reboot to start the machine. 2. Specify to start Windows normally. 3. Log on to the machine. The system is restored to its state prior to the bare metal restore.
3. Run the AppAssure aamount utility as root, for example: sudo aamount 4. At the AppAssure mount prompt, enter the following command to list the protected machines: lm 5. When prompted, enter the IP address or host name of your AppAssure Core server. 6. Enter the logon credentials, that is, the username and password, for this server. A list is displayed showing the machines protected by this AppAssure Core server.
Installing The Screen Utility Before you begin utilizing the AppAssure commands, you can install the screen utility. The screen utility enables you to scroll the screen to view larger amounts of data, such as a list of recovery points. To install the screen utility: 1. Using the Live CD file, start the Linux machine. A terminal window opens. 2. Enter the following command: sudo apt-get install screen. 3. To start the screen utility, type screen at the command prompt.
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 agent data, monitor and manage replication, and perform recovery. Performing replication in AppAssure involves performing the following operations: • Configure self-managed replication. • Configure third-party replication. • Replicate a new agent attached to the source core.
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. 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.
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.
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. If the seed drive was saved to a portable storage device such as a USB drive, connect the drive to the target core. 2. From the AppAssure Core Console on the target core, select the Replication tab. 3.
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.
5. Click Show Advanced Options, and edit the following settings as needed. Text Box Description Display Name Enter a name for the machine to be displayed in the Core Console. Repository Select the repository on the AppAssure Core where the data from this machine is stored. Encryption Key Specify whether encryption is applied to the data for every volume on this machine stored in the repository.
Setting Replication Priority For An Agent To set replication priority for an agent: 1. From the Core Console, select the protected machine for which you want to set replication priority, and click the Configuration tab. 2. Click Select Transfer Settings, and then use the Priority drop-down list to select one of the following options: • Default • Highest • Lowest • 1 • 2 • 3 • 4 NOTE: The default priority is 5.
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: 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. It is listed here until the MSP accepts the request.
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.
3. In the drop-down menu for the agent that you want to remove from replication, click Delete, and then select one of the following options. Option Description Relationship Only Removes the agent from replication but retains the replicated recovery points. With Recovery Point Removes the agent from replication and deletes all replicated recovery points received from that machine. Removing A Target Core From Replication To remove a target core from replication: 1.
Understanding Failover And Failback AppAssure supports failover and failback in replicated environments, in case of a severe outage in which the source core and agents fail. Failover refers to switching to a redundant or standby target (AppAssure Core) upon system failure or abnormal termination of a source core and associated agents. The main goal of failover is to launch a new agent identical to the failed agent.
To perform failback: 1. Navigate to the Core Console on the target core, and click the Replication tab. 2. Under Incoming Replication, select the failover agent and expand the details. 3. On the Actions menu, click Failback. The Fail Back dialog box opens to describe the steps you need to follow before you click the Continue button to complete failback. 4. Click Cancel. 5. If the failed-over machine is running Microsoft SQL Server or Microsoft Exchange Server, stop those services. 6.
Reporting 6 About Reports Your DL1000 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.
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. From the drop-down menu, click Reports and then select one of the following options: • Compliance Report • Summary Report 3. • Failure Report From the left navigation area, select the Core or Cores for which you want to run the report. 4.
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.
