Introducing your Dell DL1000 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.
Dell DL1000 data protection features Dell DL1000 Core The Core is the central component of the DL1000 deployment architecture. The Core stores and manages machine backups and provides services for backup, recovery, retention, replication, archival, and management. The Core is a self-contained network, addressable computer that runs a 64-bit version of Microsoft Windows Server 2012 R2 Foundation and Standard operating systems.
Snapshot process Your DL1000 protection process begins when a base image is transferred from a protected machine to the Core. In this phase, full copy of the machine is transported across the network under normal operation, followed by incremental snapshots forever. The DL1000 Agent for Windows uses Microsoft Volume Shadow copy Service (VSS) to freeze and quiesce application data to disk to capture a file- system-consistent and an application-consistent backup.
AppAssure service provider. In the event of a disaster, the MSPs can instantly spin-up virtual machines for the customer. The DL1000 is not multi-tenant. The MSPs can use the DL1000 at multiple sites and create a multi-tenant environment at their end.
DL1000 Core, which consists of the central repository. The Dell software License Portal manages license subscriptions, groups and users for the agents and cores in your environment. The License Portal allows users to log in, activate accounts, download software, and deploy agents and cores per your license for your environment.
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.
Console. 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. • Type one of the following URLs in your web browser: – https://<yourCoreServerName>:8006/apprecovery/admin/core –...
Restart Firefox. Managing licenses You can manage your DL1000 licenses directly from the Core Console. From the console, you can change the license key and contact the license server. You can also access the Dell AppAssure License Portal from the Licensing page in the Core Console.
• 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: Navigate to the Core Console, select Configuration → Licensing. The Licensing page is displayed.
AppAssure Core Clear the browser cache. 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.
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: Navigate to the Core Console and select Configuration → Settings. In the Nightly Jobs section, click Change.
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.
Click OK. Modifying deploy settings To modify deploy settings: Navigate to the Core Console and click the Configuration tab, and then Settings. In the Deploy Settings pane, click Change. The Deploy Settings dialog box displays. In the Agent Installer Name text box, enter the name of the agent executable file. The default is Agentweb.
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.
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.
For example, you could select 30 days(default). Click Save. Managing repositories A repository stores the snapshots that are captured from your protected workstations and servers. The repository for your DL1000 is pre-configured. The repository resides on the internal storage of your system.
Managing security Your DL1000 provides strong encryption. By doing so, backups of protected machines are inaccessible. Only the user with the encryption key can access and decrypt the data. Encryption does not affect performance.
Adding an encryption key To add an encryption key: In the Core Console, click Configuration → Security. From the Actions drop–down menu, click Add Encryption Key. The Create Encryption Key dialog box displays. In the Create Encryption Key dialog box, enter the details for the key described as follows. Text Box Description Name...
Importing an encryption key To import an encryption key: From the Core Console, click Configuration → Security. From the Actions drop-down menu, and then click Import. The Import Key dialog box appears. In the Import Key dialog box, click Browse to locate the encryption key that you want to import, and then click Open.
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: In the Core Console, click the Tools tab. In the left menu, click Clouds. On the Clouds page, click Add New Account.
Cloud Type Text Box Description Rackspace Cloud Block Storage User Name 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.
Monitoring your DL1000 You can monitor the status of the DL1000 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.
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 . Insert the RASR USB key created. Reboot the appliance through the RASR USB key.
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 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. Click Show details to view more information about the status of the agent deployment. 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.
CAUTION: AppAssure uses AES 256-bit encryption in the Cipher Block Chaining (CBC) mode with 256-bit keys. While using encryption is optional, Dell highly recommends that you establish an encryption key, and that you protect the passphrase you define. Store the passphrase in a secure location as it is critical for data recovery.
Text Box Description Passphrase Enter the passphrase used to control access. Confirm Re-enter the passphrase you just entered. Passphrase 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. •...
Creating custom schedules 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.
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: • Mon - Fri. This range of time denotes a typical five-day work week. •...
Text Box Description Display Name 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.
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.
Sets the maximum number of simultaneous disk write actions per agent Concurrent Writes connection. NOTE: Dell recommends setting this value to the same value that you select for Maximum Concurrent Streams. If you experience packet loss, set this value slightly lower. For example, if Maximum Current Streams is set at 8, set this option to 7.
Text Box Description • SQLServerWriter • System Writer • Task Scheduler Writer • VSS Metadata Store Writer • WMI Writer Transfer Data Sets the port for transfers. The default setting is 8009. Server Port Transfer Timeout Specifies in minutes and seconds the amount of time to allow a packet to be static without transfer.
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.
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). •...
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.
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: •...
In the Core Console, navigate to the protected machine you want to view. The information about the machine displays on the Summary page. The details that display include the following: • Host name • Last Snapshot taken • Next Snapshot scheduled •...
To deploy and protect multiple agents, perform the following tasks: Deploy AppAssure to multiple machines. Deploying To Multiple Machines. Monitor the activity of the batch deployment. Monitoring The Deployment Of Multiple Machines. Protect multiple machines. Protecting Multiple Machines NOTE: This step can be skipped if you selected the Protect Machine After Install option during deployment.
• 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.
• 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. • If you have selected Advanced configuration for the Protect Machine Wizard, click Next and proceed to Step 9 to see repository and encryption options.
Recovering data 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.
Text Box Description Raw Capacity Indicates the amount of raw storage space on the entire volume. Formatted Indicates the amount of storage space on the volume that is available for data after Capacity 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: Navigate to the Core Console, click Tools → Mounts . On the Local Mounts page, click Dismount All. 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.
• 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.
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.
NOTE: Only the Dell DL1000, 3 TB with 2 VMs configuration supports the one-time export and continuous export (virtual standby) capabilities.
Performing a one-time ESXi export To perform a one-time ESXi export: 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. Select a machine for export for export and then click Next.
• 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: In the Core Console, navigate to the machine you want to export. On the Summary click Actions → Export → One-time. The Export Wizard displays on the Protected Machines page. Select a machine for 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. •...
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 Specify the version of VMware Workstation for the virtual machine. You can choose from: •...
On the Summary page, click Finish to complete the wizard and to start the export. Performing a continuous (virtual standby) Hyper-V export NOTE: Only the 3 TB with 2 VMs configuration of DL1000 supports the one-time export and continuous export (virtual standby) capabilities.
To perform a continuous (virtual standby) Hyper-V export: 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. Select the machine you want to export and then click Next. On the Summary tab, click Export →...
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).
• 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, on the Summary tab in the Actions drop-down menu for that machine, click Export →...
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: In the Core Console, click the Restore tab. The Restore Machine Wizard appears. From the Protected Machines page, select the protected machine for which you want to restore data, and then click Next.
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. Select Show advanced options and then do the following: •...
• 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.
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.
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: From the Core Console on which the server you want to restore is located, select the Core and then click the Tools tab. Click Boot CDs. Select Actions, and then click Create Boot ISO. The Create Boot CD dialog box displays.
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.
To inject drivers to your target server: Download the drivers from the manufacturer’s website for the server and unpack them. Compress the folder that contains the drivers by using a file compressing utility (for example, Win Zip) and copy it to the target server. In the Universal Recovery Console, click Driver Injection.
d. Click Restore, and then proceed to step 3. 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.
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.
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.
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. Verify that /etc/fstab contains the correct UUIDs for the root and boot volumes. Install Grand Unified Bootloader (GRUB) by using the following commands: mount --bind /dev/ /mnt/dev mount --bind /proc/ /mnt/proc chroot/mnt/bin/bash...
Replicating recovery points 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: •...
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.
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.
Under Incoming Replication, select the correct source core by using the drop-down menu, and then click Consume. The Consume window appears. 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...
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.
Text Box Description Remote The name of the desired repository on the target core in which to store the Repository 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.
• • • • 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. Click OK.
Section Description Available Actions and create a seed drive for the new protected machine's initial transfer. Incoming Replication Lists all source machines from On a target core, in the drop- which the target receives down menu, you can select the replicated data.
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: From the source core, open the Core Console, and click the Replication tab.
Option Description Relationship Only Removes the source core from replication but retains the replicated recovery points. With Recovery Removes the source core from replication and deletes all replicated recovery Points points received from that machine. In the Incoming Replication dialog box, click Yes to confirm deletion. Recovering replicated data Day-to-day replication functionality is maintained on the source core, while only the target core is capable of completing the functions necessary for disaster recovery.
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. Click Continue. In the left navigation area, under Protected Machines, select the machine that has the associated AppAssure Agent software with recovery points.
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.
Reporting 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.
• 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 •...
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:...
To contact Dell for sales, technical support, or customer-service issues, go to software.dell.com/ support. Documentation feedback Click the Feedback link in any of the Dell documentation pages, fill up the form, and click Submit to send your feedback.