Dell DL1300 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. © 2016 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Introducing your Dell DL1300............................................................................ 8 Dell DL1300 core technologies............................................................................................................ 8 Live Recovery...................................................................................................................................8 Universal Recovery..........................................................................................
Configuring an Email notification template ................................................................................ 24 Configuring repetition reduction .................................................................................................25 Configuring Event Retention ....................................................................................................... 25 Roadmap for managing a repository ...................................................................................
Deploying an Agent (Push Install) ......................................................................................................45 Protecting a machine .........................................................................................................................46 Pausing and resuming protection ............................................................................................... 48 Deploying the Agent Software when protecting an agent............................................
Restoring data ..................................................................................................................................... 71 About exporting protected data from Windows machines to virtual machines......................... 71 Managing exports.......................................................................................................................... 72 Exporting backup information from your Windows machine to a virtual machine ..................
About the Core Summary Report .................................................................................................... 112 Repositories summary ................................................................................................................ 112 Agents summary ......................................................................................................................... 113 Generating a report for a Core or agent ..........................................................
Introducing your Dell DL1300 1 Your Dell DL1300 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 DL1300 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 DL1300 Core uses base images and incremental snapshots to compile recovery points of protected agents.
Figure 3. DL1300 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.
Working with your DL1300 2 Accessing the DL1300 Core Console To access the DL1300 Core Console: 1. Update trusted sites in your browser. 2. Configure your browsers to remotely access the DL1300 Core Console. See Configuring Browsers To Remotely Access The Core Console. 3. Perform one of the following to access the DL1300 Core Console: • Log on locally to your DL1300 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.
• Replication slave cores (outbound) • Simultaneous rolluos • Rollup retention policy • Encryption keys • Vartual standby exports • Mountability checks • Exchange log truncations • SQL log truncation • Minimum snapshot interval Contacting the license portal server The Core Console contacts the portal server to update changes made in the license portal. Communication with the portal server occurs automatically at designated intervals; however, you can initiate communication on demand.
Changing the AppAssure language manually AppAssure allows you to change the language that you had selected while running AppAssure Appliance Configuration Wizard to any of the supported languages. To change the AppAssure language to the desired language: 1. Launch the registry Editor using regedit command. 2. Navigate to HKEY_LOCAL_MACHINE → SOFTWARE → AppRecovery → Core → Localization. 3. Open Lcid. 4. Select decimal. 5.
9. Log out and log in again to Windows for the change to take effect. Managing core settings The Core settings are used to define various configuration and performance settings.
Set a number from 1 to 60. The smaller the number, the lesser the load is on network and other system resources. As the capacity that is processed increases, so does the load on the system. 4. In the Maximum Retries text box, enter a value to update the maximum number of retries. 5. Click OK. Adjusting the client time-out settings Client Timeout Settings specifies the number of seconds or minutes the server waits before it times out when connecting to a client. To adjust the client time-out settings: 1.
• 4. To use the preferred IP address from your TCP/IP, click Automatically Determined. • To manually enter an IP address, click Use a specific IP Address. Enter the configuration information described as follows: Text Box Description Preferable Port Enter a port number or accept the default setting (8007 is the default port). The port is used to specify the communication channel for the engine. Admin Group Enter a new name for the administration group. The default name is BUILTIN \Administrators.
Modifying database connection settings To modify database connection settings: 1. Navigate to the Core Console, click Configuration → Settings. 2. In the Database Connection Settings section, perform one of the following: • To restore the default configuration, click Restore Default. • To modify the database connection settings, click Change. On clicking change, the Database Connection Settings dialog box appears. 3.
– Replication – Rollback • Specify the type of alert (error, warning, and informational). • Specify to whom and where the alerts are sent. Options include: – Email Address – Windows Events Logs – Syslog Server • Specify a time threshold for repetition. • Specify the retention period for all events. Configuring notification groups To configure notification groups: 1. From the Core Console, select Configuration → Events. 2. Click Add Group.
Text Box Description Notify by Windows Event Log Select this option if you want notification of alerts to be reported through the Windows Event Log. Notify by sys logd Select this option if you want alerts to be reported through sys logd. Enter the details for the sys logd in the following text boxes: Notify by Toast alerts 2. • Hostname: • Port:1 Select this option if you want the alert to appear as a pop-up in the lower-right corner of your screen. Click OK.
Text Box Description Timeout (seconds) To specify how long to try a connection before timing out, enter an integer value. It is used to establish the time in seconds when trying to connect to the email server before a time-out occurs. The default is 30 seconds. TLS 4. Select this option if the mail server uses a secure connection such as Transport Layer Security (TLS) or Secure Sockets Layer (SSL). Click Send Test Email perform the following: a.
Configuring repetition reduction To configure repetition reduction: 1. From the Core Console, click Configuration → Events. 2. From the Repetition Reduction section, click Change. The Enable Repetition Reduction dialog box appears. 3. Select Enable Repetition Reduction. 4. In the Store events for text box, enter the number of minutes to store the events for repetition reduction. 5. Click OK. Configuring Event Retention To configure event retention: 1.
When you create a repository, the Core preallocates the space required for storing data and metadata in the specified location. To further increase the size of a repository, you can add new storage locations or volumes. NOTE: The DL1300 Appliance allows you to create only one repository. All the DL1300 versions support in-box upgrades. The initial repository size available after provisioning storage in your appliance corresponds to the version of your system.
NOTE: Repositories are stored on primary storage devices. Archival storage devices such as Data Domain are not supported due to performance limitations. Similarly, repositories must not be stored on NAS filers that tier to the cloud as these devices tend to have performance limitations when used as primary storage. The Add Storage Location dialog box is displayed. 6.
Text Box Description • Off • Sync If the value is set to On, which is the default, Windows controls the caching. NOTE: Setting the write caching policy to On could result in faster performance. If you are using a version of Windows Server prior to Server 2012, the recommended setting is Off. If set to Off, AppAssure controls the caching. If set to Sync, Windows controls the caching as well as the synchronous input/ output. 8.
To modify repository settings: 1. Navigate to the Core Console. 2. Click Configuration → Repositories. 3. Click the Settings icon next to the Compression Ratio column below the Actions button, and then Settings. The Repository Settings dialog box appears. 4. Edit the repository information described as follows: Field Description Repository Name Represents the display name of the repository.
To expand the repository using the unused storage and the attached external enclosure: 1. Install the MD1400 or upgrade the trial license. Open the Core Console and select the Appliance tab, click Tasks → Provisioning. 2. On the Provisioning screen, click Provision next to the external storage controller. Perform this step only when you attach an external enclosure. 3. On the Provisioning screen, click Expand in the Action column next to appropriate provisioning task.
Text Box Description • On • Off • Sync If set to On, which is the default, Windows controls the caching. NOTE: Setting the write caching policy to On could result in faster performance; however the recommended setting is Off. If set to Off, AppAssure controls the caching. If set to Sync, Windows controls the caching as well as the synchronous input/ output. 5. Bytes per Sector Specify the number of bytes you want each sector to include. The default value is 512.
When you delete a repository, then you must go through the Open Manage System Administrator and delete the virtual disks that housed the repository. After you delete the virtual disks, you can reprovision the disks and recreate the repository. Remounting volumes The storage partitions such as repository, storage for the VM images, and storage for Windows backup images are created after provisioning storage in your Appliance. The paths for such partitions are accessible and visible for the OS.
To recover a repository from a failed import state: 1. Navigate to the Core Console. The Repositories screen displays the failed repository with a red status indicator. 2. Click Configuration → Repositories. 3. Expand the failed repository by clicking > next to Status. 4. From the Actions section, click Check, and then click Yes to confirm that you want to run the check. The appliance recovers the repository.
• Encryption is performed using 256 bit AES in Cipher Block Chaining (CBC) mode that is compliant with SHA-3. • Deduplication operates within an encryption domain to ensure privacy. • Encryption is performed without impact on performance. • You can add, remove, import, export, modify, and delete an encryption key configured on the Core. Adding an encryption key To add an encryption key: 1. 2. In the Core Console, click Configuration → Security.
CAUTION: It is recommended that you protect the passphrase. If you lose the passphrase, you cannot access the data on the system. 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.
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 2.
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.
After the prerequisites are checked Create the RASR USB Drive window displays the minimum size required to create the USB drive and List of Possible target paths. 4. Select the target and click Create. A warning dialog box is displayed. 5. Click Yes. The RASR USB Drive key is created. NOTE: Make sure to use 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. 6.
Recovery and Update Utility The Recovery and Update Utility (RUU) is an all-in-one installer to recover and update DL Appliances (DL1000, DL1300, DL4000 and DL4300) software. It includes the AppAssure Core software and appliance-specific components. RUU consists of updated versions of the Windows Server Roles and Features, ASP .NET MVC3, LSI Provider, DL Applications, OpenManage Server Administrator and AppAssure Core Software.
NOTE: As part of the AppAssure Core Software upgrade process, the Recovery and Upgrade Utility notifies you of the currently installed AppAssure version and prompts you to confirm that you want to upgrade the Core software to the version that is bundled in the utility. AppAssure Core software downgrades are not supported. 7. If prompted, reboot your system. 8. After all services and applications are installed, click Proceed. The Core Console launches.
Managing Your Appliance 3 The Core Console includes an Appliance tab, which you can use to provision space, monitor the health of the appliance, and access management tools. Monitoring the status of the Appliance You can monitor the status of the Appliance subsystems by using the Appliance tab Overall Status page. The Overall Status page displays a status light next to each subsystem, along with a status description indicating the health of the subsystem.
To complete disk provisioning for all available storage: 1. In the Appliance tab, click Tasks → Provisioning. The Provisioning screen displays estimated capacity for provisioning. This capacity is used to create a AppAssure Repository. CAUTION: Before proceeding ensure Step 2 through Step 4 is followed in this procedure. 2. Open the Provisioning Storage window by clicking Provision in the Action column next to the storage that you want to provision. 3.
3. Select the virtual disk that you want to remove, and then select Delete from the Tasks drop-down menu. 4. After confirming the deletion, the space appears on the Core Console Appliance tab Tasks screen as available for provisioning. Resolving failed tasks AppAssure reports failed verify, provision, and recovery tasks with an event on the Core Console Home page, and also on the Appliance tab Tasks screen. To understand how to resolve a failed task, select the Appliance tab and then click Tasks.
Protecting workstations and servers 4 About protecting workstations and servers To protect your data using DL1300, 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 3. 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 4. 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.
3. In the Nightly Jobs pane, click change. The Nightly Job dialog box appears. 4. Select Attachability Check Job and then click Settings. 5. Use the drop-down menus to select the instance of SQL Server installed on the Core from the following options: You can choose from: 6. • SQL Server 2005 • SQL Server 2008 • SQL Server 2008 R2 • SQL Server 2012 • SQL Server 2014 Select the credential type. You can choose from: • 7. 8.
Viewing system diagnostics In AppAssure, diagnostic information is available for you to view machine log data for any protected machine. Additionally, you can view and upload diagnostic information for the Core. Viewing machine logs If you encounter any errors or issues with the machine, it may be useful to view the logs for troubleshooting purposes. To view machine logs: 1. In the Core Console, click Tools → Diagnostics → View Log. The Download Core Log page appears. 2.
• Host name • Last Snapshot taken • Next Snapshot scheduled • Encryption status • Version number • Mountability Check status • Checksum Check status • Last Log Truncation performed Detailed information about the volumes contained on this machine also appear and include: • Name • File System type • Space Usage • Current Schedule • Next Snapshot • Total size • Used Space • Free space If SQL Server is installed on the machine, detailed information about the server also appears a
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. See Monitoring the Protection of Multiple Machines. Deploying To Multiple Machines You can simplify the task of deploying the AppAssure Agent software to multiple Windows machines by using the Bulk Deploy feature of AppAssure.
NOTE: Agent machines must be configured with a security policy that makes remote installation possible. To protect multiple machines: 1. From the Core Console, click Protect → Bulk Protect. The Protect Multiple Machines Wizard window appears. 2. Select the appropriate installation option: • If you do not need to define a repository or establish encryption, select Typical. • 3.
11. To enable encryption, on the Encryption page, select Enable Encryption. Encryption key fields appear on the Encryption page. NOTE: If you enable encryption, it will be applied to data for all protected volumes for the machines you have specified for protection. You can change the settings later from the Configuration tab in the Core Console. For more information about encryption, see Managing Security . 12. Enter the information as described in the following table to add an encryption key for the Core.
Recovering data 5 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.
Virtual Machine Management NOTE: The virtual machine management from the Appliance tab can be configured only on the systems that support VM creation. The VM Management tab displays the status of the protected machines. You can start, stop, and add network adapters (applicable for Hyper-V and ESXi virtual machines only). To navigate to the VM Management tab, click Appliance → VM Management.
Field Description NOTE: The above status values depend on the hypervisor type. Not all hypervisors display all the status values. Location: Indicates the location of VM. For example, D:\export. The VM location must have sufficient space to hold the VM metadata and virtual drives needed for the virtual machine. Export Status Status 1. 2.
Field Description 2. If an export is currently in progress, percentage of export is displayed as a progress bar. Last Export: Indicates the time of last export. Creating a virtual network adapter Virtual machines must have one or more Virtual Network Adapters (VNAs) to connect to the internet. A VM should have a VNA for each real network adapter (RNA) on the protected machine. The VNA and the matching RNA should have a similar configuration.
NOTE: Do not click the Start button if an export task to the virtual machine is currently running or is likely to start soon. Verify the schedule of the next export task by viewing the Protected Machines tab and Virtual Standby tab. If an export task has been scheduled in the near future, cancel or skip the export task or, wait for the export task to complete before starting the virtual machine.
then select Recover to a protected machine (only non-system volumes) , verify that the destination machine (Machine1) is selected, and then click Next. The Volume Mapping page appears. Proceed to Step 7.
Option Description IP Address Specify an IP address or host name for the restored machine. Subnet Mask Specify the subnet mask for the restored machine. Default Gateway Specify the default gateway for the restored machine. DNS Server Specify the domain name server for the restored machine. • To define UltraVNC information, select Add UltraVNC as described in the following table. Use this option if you require remote access to the recovery console.
NOTE: At least one volume must be selected to perform the restore. c. Select the destination disk for the restore. d. Click Next, and then proceed to Step 19. 18. If you want to map volumes manually, do the following: a. Select Manual volume mapping. b. In the Manual volume mapping area, from the Destination Volumes drop-down list for each volume, select the volume you want to restore. If you do not wish to restore a listed volume, clear the option.
5. Enter the following command to list the currently mounted recovery points for the specified machine: lr NOTE: You can also enter the machine ID number in this command instead of the line item number. A list is displayed that shows the base and incremental recovery points for that machine.
Roadmap for performing a Bare Metal Restore for a Windows machine To perform a BMR for a Windows machine: 1. Create a boot CD. 2. Burn the image to disk. 3. Boot the target server from the boot CD. 4. Connect to the recovery disk. 5. Map the volumes. 6. Initiate the recovery. 7. Monitor the progress.
Creating connections To create connections: 1. 2. In Connection Options do one of the following: • To obtain the IP address dynamically using Dynamic Host Configuration Protocol (DHCP), select Obtain IP address automatically. • Optionally, to specify a static IP address for the recovery console, select Use the following IP address and enter the IP address, subnet mask, default gateway, and DNS server in the appropriate fields. You must specify all of these fields.
Loading a boot CD When you have created the boot CD image, boot the target server with the newly created boot CD. NOTE: If you created the boot CD using DHCP, note the IP address and password. To load a boot CD: 1. Navigate to the new server, load the boot CD, and then start the machine. 2.
NOTE: AppAssure Restore does not recognize teamed NICs. The process is not able to resolve which NIC to use if presented with more than one active connection. 2. Navigate back to the Core server and open the Core Console. 3. On the Machines tab, select the machine from which you want to restore data. 4. Click the Actions menu for the machine, click Recovery Points to view a list of all recovery points for that machine. 5. Expand the recovery point from which you want to restore, then click Rollback.
1. After you initiate the rollback process, the Active Task dialog box displays, showing that the rollback action initiated. NOTE: This appearance of the Active Task dialog box does not indicate successful completion of the task. 2. Optionally, to monitor the rollback task progression, from the Active Task dialog box, click Open Monitor Window. You can view the status of the recovery as well as the start and end times from the Monitor Open Task window.
To perform a bare metal restore for a Linux machine: 1. Using the Live CD file you receive from AppAssure, boot up the Linux machine and open a Terminal window. 2. If needed, create a new disk partition, for example, by running the fdisk command as root, and make this partition bootable by using the a command. 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.
CAUTION: Do not unmount a protected Linux volume manually. In the event that you need to manually unmount a protect Linux volume, you must execute the following command before unmounting the volume: bsctl -d In this command, does not refer to the mount point of the volume but instead refers to the file descriptor of the volume; it must be in a form similar to this example: /dev/sda1.
Replicating recovery points 6 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. Start the virtual machine that now includes the exported backup information. 8.
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. Navigate to the Core Console on the target core, and delete the agent from the Replication tab. 19.
Reporting 7 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 8 Finding documentation and software updates Direct links to AppAssure and DL1300 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.
