Page 1 Dell DL4000 Appliance User's Guide...
Page 2 WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Dell and the Dell logo are trademarks of Dell Inc.
Page 3: Table Of Contents
Contents 1 Introduction to Dell DL4000 Appliance............10 ..........................10 Core technologies ..........................11 Live Recovery ........................... 11 Verified Recovery .........................11 Universal Recovery ......................11 True Global Deduplication ........................11 True Scale architecture ........................12 Deployment architecture ........................... 14 Smart Agent ..........................14 DL4000 Core ..........................
Page 4 ......................26 Adjusting the nightly job time ..................26 Modifying the transfer queue settings ..................27 Adjusting the client time-out settings .................. 27 Configuring deduplication cache settings ......................28 Modifying engine settings ..................29 Modifying database connection settings ..........................29 About repositories ....................30 Roadmap for managing a repository ........................
Page 5 ........55 Removing a protected machine from replication on the source Core ..............55 Removing a protected machine on the target Core ..................55 Removing a target Core from replication ...................55 Removing a source Core from replication ......................56 Recovering replicated data .....................56 Roadmap for failover and failback ..................56...
Page 6 ......................74 Forcing checksum checks ........................75 Forcing log truncation ....................75 Recovery point status indicators 3 Managing Your Appliance................. 77 ....................77 Monitoring the status of the Appliance ..........................77 Provisioning storage ......................78 Provisioning selected storage ..................79 Deleting space allocation for a virtual disk ..........................
Page 7 ....................105 Protecting multiple machines ..............107 Monitoring the protection of multiple machines ..................107 Managing snapshots and recovery points ......................108 Viewing recovery points ....................108 Viewing a specific recovery point ..............109 Mounting a recovery point for a Windows machine ................... 110 Dismounting select recovery points ....................
Page 8 Generating a report for a Core or agent ..............156 About the Central Management Console Core reports ............156 Generating a report from the Central Management Console 7 Completing a full recovery of the DL4000 Appliance....... 157 ..............157 Creating a RAID 1 partition for the operating system...
Page 9 ..167 VolumeNameCollection (namespace Replay.Common.Contracts.Metadata.Storage) ........................168 Pretransferscript.ps1 ......................... 168 Posttransferscript.ps1 ........................169 Preexportscript.ps1 ........................170 Postexportscript.ps1 ....................... 170 Prenightlyjobscript.ps1 .......................172 Postnightlyjobscript.ps1 ...........................174 Sample scripts 10 Getting help..................... 175 ................175 Finding documentation and software updates ..........................175 Contacting Dell ......................... 175 Documentation feedback...
Page 10: Introduction To Dell Dl4000 Appliance
Introduction to Dell DL4000 Appliance This chapter provides an introduction and overview of DL4000. It describes the features, functionality, and architecture, and consists of the following topics: • Core technologies • True Scale architecture • Deployment architecture • Product features...
Page 11: Live Recovery
Live Recovery Live Recovery is instant recovery technology for VMs or servers. It gives you near-continuous access to data volumes on virtual or physical servers. You can recover an entire volume with near-zero RTO and an RPO of minutes. The backup and replication technology records concurrent snapshots of multiple VMs or servers, providing near instantaneous data and system protection.
Page 12: Deployment Architecture
object and a volume manager with integrated global deduplication, compression, encryption, replication, and retention. The following diagram describes the AppAssure True Scale architecture. Figure 1. AppAssure True Scale architecture The AppAssure Volume Manager and Scalable Object Store serve as the foundation of the AppAssure True Scale architecture.
Page 13 volumes with dependency for comprehensive protection and effective recovery. This ensures that you never have incomplete backups when you are performing recoveries. Backups are performed by using application-aware block-level snapshots. Your appliance can also perform log truncation of the protected Microsoft Exchange and SQL servers. The following diagram depicts a simple deployment.
Page 14: Smart Agent
Core for protection. DL4000 Core The Core is the central component of the deployment architecture. The Core stores and manages all of the machine backups and provides core services for backup, recovery, and retention;...
Page 15: Replication Of Disaster Recovery Site Or Service Provider
AppAssure uses Microsoft VSS because it has built-in support for all Windows internal technologies such as NTFS, Registry, Active Directory, to flush data to disk before the snapshot. Additionally, other enterprise applications, such as Microsoft Exchange and SQL, use VSS Writer plug-ins to get notified when a snapshot is being prepared and when they have to flush their used database pages to disk to bring the database to a consistent transactional state.
Page 16: Repository
Repository The repository uses Deduplication Volume Manager (DVM) to implement a volume manager that provides support for multiple volumes, each of which could reside on different storage technologies such as Storage Area Network (SAN), Direct Attached Storage (DAS), Network Attached Storage (NAS), or cloud storage.
Page 17: Encryption
Figure 4. Diagram of deduplication Your appliance performs target-based inline data deduplication, where the snapshot data is transmitted to the Core before it is deduplicated. Inline data deduplication simply means the data is deduplicated before it is committed to disk. This is different from at-source or post-process deduplication, where the data is deduplicated at the source before it is transmitted to the target for storage, and in post-process the data is sent raw to the target where it is analyzed and deduplicated after the data has been committed to disk.
Page 18: Replication
In replication scenarios, your appliance uses SSL 3.0 to secure the connections between the two cores in a replication topology to prevent eavesdropping and tampering. Replication Replication is the process of copying recovery points from an AppAssure core and transmitting them to another AppAssure core in a separate location for the purpose of disaster recovery.
Page 19: Recovery-As-A-Service (Raas)
replicate to the target site. After data has been transferred to the target core, the newly replicated incremental recovery points automatically synchronize. Recovery-as-a-Service (RaaS) Managed service providers (MSPs) can fully leverage the appliance as a platform for delivering recovery as a service (RaaS).
Page 20: Virtualization And Cloud
appliance solves the big data problem by managing the retention of large amounts of data with complex retention policies and performing rollup operations for aging data using efficient metadata operations. Backups can be performed with an interval of a few minutes. As these backups age over days, months, and years, retention policies manage the aging and deletion of old backups.
Page 21: Service Management Apis
organize the managed cores in hierarchical organizational units. These organizational units can represent business units, locations, or customers for MSPs with role-based access. The central console can also run reports across managed cores. Service management APIs Your appliance comes bundled with a service management API and provides programmatic access to all of the functionality available through the Central Management Console.
Page 22: Working With The Dl4000 Core
Console. Perform one of the following to access the Core Console: • Log on locally to your DL4000 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 –...
Page 23: Roadmap For Configuring The Core
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: Open Server Manager. Select Local Server IE Enhanced Security Configuration displayed on the right. Ensure that it is Configuring browser settings in Internet Explorer and Chrome To modify browser settings in Internet Explorer and Chrome: Open Internet Explorer.
Page 24: Managing Licenses
NOTE: If you are using this Appliance, it is recommended that you use the Appliance tab to configure the Core. For more information about configuring the Core after initial installation, see the Dell DL4000 Appliance Deployment Guide at dell.com/support/home. Managing licenses You can manage licenses directly from the Core Console.
Page 25: Changing The Appassure Language Manually
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: Launch the registry Editor using regdit command. Navigate to HKEY_LOCAL_MACHINE →...
Page 26: Managing Core Settings
Log out and log in again to Windows for the change to take effect. Managing Core settings The Core settings are used to define various settings for configuration and performance. Most settings are configured for optimal use, but you can change the following settings as necessary: •...
Page 27: Adjusting The Client Time-Out Settings
To modify the transfer queue settings: Navigate to the Core Console. Click Configuration → Settings. In the Transfer Queue pane, click Change. The Transfer Queue dialog box appears. In the Maximum Concurrent Transfers text box, enter a value to update the number of concurrent transfers.
Page 28: Modifying Engine Settings
Enter a write timeout value or choose the default setting. The default setting is 00:00:30. No Delay It is recommended that you leave this check box unchecked as doing otherwise will impact network efficiency. If you determine that you need to modify this setting, contact Dell Support for guidance. Click OK.
Page 29: Modifying Database Connection Settings
Modifying database connection settings To modify database connection settings: Navigate to the Core Console. Click Configuration → Settings In the Database Connection Settings area, choose one of the following: • Click Apply Default. • Click Change. The Database Connection Settings dialog box appears. Enter the settings for modifying the database connection described as follows: Text Box Description...
Page 30: Roadmap For Managing A Repository
The Scalable Object File System can deliver scalable I/O performance in tandem with global data deduplication, encryption, and retention management. NOTE: DL4000 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.
Page 31 Text Box Description Repository Name Enter the display name of the repository. By default, this text box consists of the word Repository and an index number which sequentially adds a number to the new repository starting with 1. You can change the name as needed. You can enter up to 150 characters.
Page 32 Text Box Description If this location is at the root, define a dedicated folder name (for example, Repository). The path must begin with \\. When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains).
Page 33: Viewing Repository Details
Text Box Description Bytes per Sector Specify the number of bytes you want each sector to include. The default value is 512. Average Bytes per Specify the average number of bytes per record. The default value is 8192. Record Click Save. The Repositories screen is displayed to include the newly added storage location.
Page 34: Expanding An Existing Repository
Field Description Repository Name Represents the display name of the repository. By default, this text box consists of the word Repository and an index number, which corresponds to the number of the repository. NOTE: You cannot edit the repository name. Description Optionally, enter a descriptive note about the repository.
Page 35 Specify how to add the file for the storage location. You can choose to add the file on the local disk or on a CIFS share. • To specify a local machine, click Add file on local disk, enter the information as follows: Text Box Description Metadata Path...
Page 36: Checking A Repository
Text Box Description If set to Sync, Windows controls the caching as well as the synchronous input/ output. Bytes per Sector Specify the number of bytes you want each sector to include. The default value is 512. Average Bytes per Specify the average number of bytes per record.
Page 37: Recovering A Repository
The Volumes remount. Resolving foreign volumes If a provisioned MD1200 is powered off or disconnected and then later powered back on, an event appears on the Core Console reporting that the MD1200 is connected. However, no task appears on the Appliance tab Tasks screen that permits you to recover it.
Page 38: Adding An Encryption Key
Adding an encryption key To add an encryption key: Navigate to the Core Console. Click Configuration → Security. The Encryption Keys page appears. Click Actions, and then 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...
Page 39: Importing An Encryption Key
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: Navigate to the Core Console. Click Configuration → Security. Select the Actions drop-down menu, and then click Import.
Page 40: Adding A Cloud Account
• Removing a Cloud Account 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.
Page 41: Editing A Cloud 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.
Page 42: Understanding Replication
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: On the Core Console, click the Tools tab.
Page 43 • Mutual Replication. Two data centers in two different locations each contain a core and are protecting agents and serving as the off-site disaster recovery backup for each other. In this scenario, each core replicates the protected machines to the Core that is located in the other data center. •...
Page 44: About Seeding
Figure 8. Multi-Point Replication Architecture Diagram About seeding Replication begins with seeding: the initial transfer of deduplicated base images and incremental snapshots of the protected machines, which can add up to hundreds or thousands of gigabytes of data. Initial replication can be seeded to the target core using external media to transfer the initial data to the target core.
Page 45: About Failover And Failback
Because large amounts of data need to be copied to the portable storage device, an eSATA, USB 3.0, or other high-speed connection to the portable storage device is recommended. About failover and failback In the case of a severe outage in which your source core and protected machines fail, your DL Appliance supports failover and failback in replicated environments.
Page 46: Roadmap For Performing Replication
the amount of data transmitted from core to core, multiple parallel streams may be required to perform at wire speeds up to the speed of a 1 GB Ethernet connection. NOTE: Bandwidth specified by the ISP is the total available bandwidth. The outgoing bandwidth is shared by all devices on the network.
Page 47: Replicating To A Self-Managed Core
• Set replication priority for an agent. For more information on prioritizing the replication of agents, see Setting Replication Priority For An Agent • Monitor replication as needed. For more information on monitoring replication, see Monitoring Replication. • Manage replication settings as needed. For more information on managing replication settings, see Managing Replication Settings •...
Page 48 If you plan to perform the seeding process for the transfer of the base data, complete the following steps: NOTE: Because large amounts of data need to be copied to the portable storage device, an eSATA, USB 3.0, or other high-speed connection to the portable storage device is recommended.
Page 49 Text Box Description Add all Agents to Select the agents you want to replicate using the seed drive. Seed Drive Build RP chains Select this option to replicate the entire recovery point chain to the seed drive. (fix orphans) This option is selected by default. Typical seeding in AppAssure replicates only the latest recovery point to the seed drive, which reduces the amount of time and space required for creating the seed drive.
Page 50: Replicating To A Core Managed By A Third Party
Text Box Description Account Select an account from the drop-down list. To select a cloud account, you must first have added it in the Core Console. Container Select a container associated with your account from the drop-down menu. Folder Name Enter the name of the folder in which the archived data is saved;...
Page 51 Configuring replication to a target core managed by a third party NOTE: This configuration applies to hosted and cloud replication. If you are configuring AppAssure for multipoint to point replication, you must perform this task on all source cores. To configure replication for a core managed by a third party: Navigate to the Core Console, and click the Replication tab.
Page 52 Text Box Description Enter the desired amount of space in the text box. Select the measurement. Recycle action In the event the path already contains a seed drive, select one of the following options: • Do not reuse — Does not overwrite or clear any existing data from the location.
Page 53: Monitoring Replication
Optionally, enter any notes that you want to display in the Comment box. Click Send Response. Replication is accepted. Ignoring a replication request As a third-party service provider of a target core, you have the option of ignoring a request for replication sent from a customer.
Page 54: Managing Replication Settings
Section Description Available Actions • Change Settings — Lists the progress of a replication display name and lets you transmission. edit the host and port for the target core. • Add Agents — Lets you select a host from a drop- down list, select protected machines for replication, and create a seed drive for...
Page 55: Removing A Protected Machine From Replication On The Source Core
• Removing An Agent From Replication On The Source Core • Removing An Agent On The Target Core • Removing A Target Core From Replication • Removing A Source Core From Replication NOTE: Removing a source core results in the removal of all replicated machines that are protected by that core.
Page 56: Recovering Replicated Data
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.
Page 57: Performing Failover On The Target Core
Follow the steps in the Replicating To A Self-Managed Core to add the target core to which to replicate. Performing failover on the target Core When you encounter a disaster situation in which your source core and associated protected machines have failed, you can enable failover to switch protection to your identical failover (target) core.
Page 58: Managing Events
Import the archive you just created in Step 7. 10. Go back to the Core Console on the target core, and click the Replication tab. 11. Under Incoming Replication, select the failover agent and expand the details. 12. On the Actions menu, click Failback. 13.
Page 59: Configuring Notification Groups
– Syslog Server • Specify a time threshold for repetition. • Specify the retention period for all events. Configuring notification groups To configure notification groups: From the Core, select the Configuration tab. From the Manage option, click Events. Click Add Group. The Add Notification Group dialog box opens and displays three panels: •...
Page 60: Configuring An Email Server And Email Notification Template
NOTE: You must also configure notification group settings, including enabling the Notify by email option, before email alert messages will be sent. For more information on specifying events to receive email alerts, see 'Configuring Notification Groups For System Events' in Dell DL4000 Appliance User’s Guide.
Page 61: Configuring Repetition Reduction
Text Box Description The default is 25. 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.
Page 62: Managing Recovery
NOTE: For access to the Agent Installer, see Downloading And Installing The Agent Installer. For more information about deploying the Agent Installer, see the Dell DL4000 Appliance Deployment Guide available at Dell.com/support/home. For access to the Local Mount Utility Installer, see About The Local Mount Utility...
Page 63: Downloading And Installing The Agent Installer
Download the Agent installer file from the License Portal or from the Core. For example: Agent-X64-5.3.x.xxxxx.exe Click Save File. For more information about installing the agents, see the Dell DL4000 Appliance Deployment Guide available at Dell.com/support/home. About the local mount utility The Local Mount Utility (LMU) is a downloadable application that lets you mount a recovery point on a remote Core from any machine.
Page 64: Adding A Core To The Local Mount Utility
a. Choose a destination folder for the LMU by clicking the Change button. NOTE: The default destination folder is C:\Program Files\AppRecovery\LocalMountUtility. b. Select whether or not to Allow Local Mount Utility to automatically send diagnostic and usage information to AppAssure Software, Inc. c.
Page 65: Mounting A Recovery Point By Using The Local Mount Utility
Exploring a mounted recovery point by using the local mount utility NOTE: This procedure is not necessary if you are exploring a recovery point immediately after mounting it, as the folder containing the recovery point automatically opens upon completion of the mounting procedure.
Page 66: Dismounting A Recovery Point By Using The Local Mount Utility
NOTE: Selecting a recovery point that is already mounted causes the Mounting dialog box to prompt you to dismount the recovery point. Dismounting a recovery point by using the local mount utility To dismount a recovery point using the Local Mount Utility: From the machine on which the LMU is installed, launch LMU by double-clicking the desktop icon.
Page 67: Managing Retention Policies
Accessing localhost options To access Localhost options, right-click the Core or agent and then click Reconnect to Core. Information from the Core is updated and refreshed; for example, recently added agents. Accessing remote core options To access remote core options, right-click the Core or agent and then select one of the remote core options described as follows: Option Description...
Page 68: Creating An Archive
Creating an archive To create an archive In the Core Console, click the Configuration tab. From the Manage option, click Archive. The Create Archive dialog box appears. In the Create Archive dialog box, enter the details for the archive described as follows: Text Box Description Date range...
Page 69: Pausing Or Resuming Scheduled Archive
On the Location page of the Add Archive Wizard, select one of the following options from the Location Type drop-down list: • Local: Output location – Enter the location for the output. It defines the location path where you want the archive to reside. •...
Page 70: Editing A Scheduled Archive
To pause or resume scheduled archive: Navigate to the Core Console, and then click the Tools tab. From the Archive option, click Scheduled. On the Scheduled Archive page, do one of the following: • Select the preferred archive, and then click one of the following actions as appropriate: –...
Page 71: Checking An Archive
– At day of week: Select a day of the week on which to automatically create the archive. – At time: Select the hour of the day you want to create a daily archive. • Monthly – At day of months: Select the day of the month on which to automatically create the archive. –...
Page 72: Managing Sql Attachability
Text Box Description Input Location Select the location for importing the archive. User name To establish access to secure the archive, enter the logon credentials. Password Enter a password for accessing the archive. Click Check File to validate the existence of the archive to import. The Restore dialog box appears.
Page 73: Configuring Nightly Sql Attachability Checks And Log Truncation
Use the drop-down menus to select the instance of SQL Server installed on the Core from the following options: You can choose from: • SQL Server 2005 • SQL Server 2008 • SQL Server 2008 R2 • SQL Server 2012 •...
Page 74: Configuring Exchange Database Mountability And Log Truncation
potential failures and ensures that all data on the Exchange servers is recovered successfully in the event of a failure. NOTE: The mountability checks and log truncation features only apply to Microsoft Exchange 2007, 2010, and 2013. Additionally, the AppAssure Agent service account must be assigned the Organizational Administrator role in Exchange.
Page 75: Forcing Log Truncation
The Force Attachability Check window prompts you to indicate if you want to force a checksum check. Click Yes. The system performs the checksum check. NOTE: For information on how to view the status of the attachability checks, see Viewing Events And Alerts.
Page 76 Term heading Description heading • An Exchange database did not exist. • Mountability checks were not enabled. NOTE: This can apply to certain volumes within a recovery point. Yellow Indicates that the Exchange database mountability checks are enabled, but the checks have not yet run.
Page 77: Managing Your Appliance
If storage is available for provisioning, a link to Provision under Actions displays next to the provision task. Provisioning storage The appliance configures available DL4000 internal storage and any attached external storage enclosures for: •...
Page 78: Provisioning Selected Storage
Based on a medium-sized environment that does not need standby virtual machines, you can use all of the storage to back up a significant number of agents. However, if you need more resources for standby virtual machines and back up a smaller number of agent machines, you can allocate more resources for larger VMs.
Page 79: Deleting Space Allocation For A Virtual Disk
> next to Status, and review the error message and recommended action. Upgrading your Appliance To upgrade your appliance: Download the Recovery and Update Utility from dell.com/support to the DL4000 Backup to Disk appliance. Copy the utility to the appliance desktop and extract the files.
Page 80: Repairing Your Appliance
The Core Console launches. Repairing your Appliance To repair your appliance: Download the Recovery and Update Utility from dell.com/support to your Appliance. Copy the utility to the appliance desktop and extract the files. Double-click the launchRUU icon. When prompted, click Yes to acknowledge that you are not running any of the listed processes.
Page 81: Protecting Workstations And Servers
Protecting workstations and servers About protecting workstations and servers To protect your data add the workstations and servers you want to protect in the Core Console; for example, your Exchange server, SQL Server, or your Linux server. NOTE: In this section, generally the word machine also refers to the AppAssure Agent software installed on that machine.
Page 82: Viewing System Information For A Machine
Text Box Description The Core uses the port to communicate with this machine. Repository Select a repository for the recovery points. Displays the repository on the Core in which to store the data from this machine. NOTE: This setting can only be changed if there are no recovery points or the previous repository is missing.
Page 83 To configure notification groups for system events: In the Core Console, click the Machines tab. From the Machines tab, perform one of the following: • Click the hyperlink for the machine that you want to modify. • In the navigation pane, select the machine that you want to modify. The Summary tab appears.
Page 84: Editing Notification Groups For System Events
Text Box Description • Warning • Error NOTE: When you choose to select by type, by default, the appropriate events are automatically enabled. For example, if you choose Warning, the Attachability, Jobs, Licensing, Archive, CoreService, Export, Protection, Replication, and Rollback events are enabled. Notification Select the method to specify how to handle notifications.
Page 85 Text Box Description Description Enter a description for the notification group. Enable Events Select which events to share with the notification group. You can select All or select a subset of events to include: • BootCd • LocalMount • Metadata •...
Page 86: Customizing Retention Policy Settings
Text Box Description – Port — Enter a port number for communicating with the server. Click OK. Customizing retention policy settings The retention policy for a machine specifies how long the recovery points for an agent machine are stored in the repository. Retention policies are used to retain backup snapshots for longer periods of time and to help manage these backup snapshots.
Page 87 Text Box Description • Weeks • Months • Years ...and then keep Provides a more refined level of retention. It is used as a building block to one Recovery further define how long recovery points are maintained. Point per day for n Enter a number that represents the retention period and then select the time [retention time period.
Page 88: Viewing License Information
...and then keep one recovery point per hour for 3 days ...and then keep one recovery point per day for 4 days ...and then keep one recovery point per week for 3 weeks ...and then keep one recovery point per month for 2 months ...and then keep one recovery point per month for 1 year Newest Recovery Point is set to the current day, month, and year.
Page 89: Modifying Transfer Settings
Modifying The Transfer Queue Settings. CAUTION: Changing transfer setting could have dramatic effects on your environment. Before modifying transfer settings values, refer to the Transfer Performance Tuning Guide in the Dell AppAssure knowledge base https://support.software.dell.com/appassure/kb. There are three types of transfers: Snapshots The transfer that backs up the data on your protected machine.
Page 90 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.
Page 91: Restarting A Service
Specifies how many queued read operations will be stored on the back end. Reads per Stream This setting helps to control the queuing of agents. NOTE: Dell recommends setting this value to 24. Excluded Writers Select a writer if you want to exclude it. Since the writers that appear in the list are specific to the machine that you are configuring, you may not see all the writers listed.
Page 92: Viewing Machine Logs
• Click the hyperlink for the machine that you want to restart. • In the Navigation pane, select the machine that you want to restart. Click the Tools tab, and then click Diagnostics. Select the Restart Service option, and then click the Restart Service button. Viewing machine logs If you encounter any errors or issues with the machine, view the logs to troubleshoot.
Page 93 Text Box Description Password The password used to connect to this machine. Click Connect to connect to this machine. NOTE: If the Agent software is not yet installed on the machine that you designated, follow the procedure Deploying The Agent Software When Protecting An Agent.
Page 94: Deploying The Agent Software When Protecting An Agent
For more information about manually forcing a snapshot, see topic 'Forcing A Snapshot' in Dell DL4000 Appliance User’s Guide. • Repository — Select the repository in which to store data from this agent.
Page 95: Creating Custom Schedules For Volumes
Creating custom schedules for volumes To create custom schedules for volumes: In the Protect Machine dialog box (for information about accessing this dialog box, see Protecting A Machine, under Volume Groups, select a volume for protection, and then click Edit. The Protection Schedule dialog box appears.
Page 96: Modifying Sql Server Settings
– Truncate log before checksum check completes You can also modify the logon credentials for your Exchange Server. To do so, scroll down to the Exchange Server Information section and then click Change Credentials. The Set Exchange Credentials dialog box appears. Enter the new credentials and then click OK.
Page 97: Replicating A New Agent
Text Box Description Automatic reboot Select to specify whether the Core starts upon the completion of the after install deployment and installation of the AppAssure Agent Installer. Click Verify to validate the credentials you entered. The Deploy Agent dialog box displays a message indicating that validation is being performed. Click Abort if you want to cancel the verification process.
Page 98: Managing Machines
Text Box Description Remote Core Specify the target core to which you want to replicate the agent. 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;...
Page 99: Setting Replication Priority For An Agent
Outbound replication can be configured to a Managed Service Provider providing off-site backup and disaster recovery service or to a self-managed core. To replicate agent data on a machine: From the Core Console, click the Machines tab. Select the machine that you want to replicate. In the Actions drop-down menu, click Replication, and then complete one of the following options: •...
Page 100: Viewing Machine Status And Other Details
Text Box Description All Operations Cancels all active operations for that machine. Snapshot Cancels the snapshot currently in progress. Viewing machine status and other details To view machine status and other details: In the navigation pane of the Core Console, do one of the following: •...
Page 101: Managing Multiple Machines
• Log File Path • Log Prefix • System Path • MailStore Type Managing multiple machines This topic describes the tasks that administrators perform to deploy Agent software simultaneously to multiple Windows machines. To deploy and protect multiple agents, perform the following tasks: Deploy AppAssure to multiple machines.
Page 102 To push the agent installation program from the Core machine: From the Core machine, copy the agent installation file Agent-X64–5.x.x.xxxxx.exe to the C: \Program Files\apprecovery\core\installers directory. From the Core Console, select the Configuration tab, and then click Settings. In the Deploy Settings section, edit the Agent Installer Name. Deploying to machines on an active directory domain Before starting this procedure, you must have the domain information and logon credentials for the Active Directory server.
Page 103 Text Box Description Repository Use the drop-down list to select the repository on the Core where the data from the machines should be stored. The repository that you select is used for all of the machines that are being protected. NOTE: This option is only available when you select Protect machine after install.
Page 104 Text Box Description Host Enter the name or IP address of the VMware vCenter Server/ESX(i) virtual host. User Name Enter the user name used to connect to the virtual host; for example, administrator. Password Enter the secure password used to connect to this virtual host. On the Add Machines from VMware vCenter Server/ESXi dialog box, check the box next to the machines to which you want to deploy the AppAssure Agent, and then click Add.
Page 105: Monitoring The Deployment Of Multiple Machines
On the Deploy Agent on Machines window, you can see the machines that you added. If you want to select a repository, encryption key, or other settings for a machine, select the check box next to the machine and click Edit Settings. For details on each setting, see Deploying To Machines On An Active Directory Domain.
Page 106 To protect multiple machines: From the Core Console, click the Tools tab, and then click Bulk Protect. The Protect Machines window appears. Add the machines that you want to protect by clicking one of the following options. For details on completing each option, see Deploying To Multiple Machines.
Page 107: Monitoring The Protection Of Multiple Machines
Icon Description Yellow icon AppAssure is able to connect to the machine; however, the agent is already paired with a core machine. Red icon AppAssure cannot connect to the machine. This may be because the logon credentials are incorrect, the machine is shut down, the firewall is blocking traffic, or another problem.
Page 108: Viewing Recovery Points
Viewing recovery points To view recovery points: In the left navigation area of the Core Console, select the machine for which you want to view recovery points, and then click the Recovery Points tab. You can view information about the recovery points for the machine as described in the following table: Info Description Status...
Page 109: Mounting A Recovery Point For A Windows Machine
You can view information about the selected volume in the expanded recovery point as described in the following table: Text Box Description Title Indicates the specific volume in the recovery point. Raw Capacity Indicates the amount of raw storage space on the entire volume. Formatted Indicates the amount of storage space on the volume that is available for data after Capacity...
Page 110: Dismounting Select Recovery Points
Text Box Description Create a Windows Optionally, select the check box to specify whether the mounted recovery share for this point can be shared, and then set access rights to it including the Share name Mount and access groups. Click Mount to mount the recovery point. Dismounting select recovery points You can dismount select recovery points that are mounted locally on the Core.
Page 111: Removing Recovery Points
number for the volume that includes a sequence number at the end (for example, 293cc667-44b4-48ab-91d8-44bc74252a4f:2), which identifies the recovery point. Enter the following command to select and mount the specified recovery point at the specified mount point/path. m <volume_recovery_point_ID_number> <path> NOTE: You can also specify a line number in the command instead of the recovery point ID number to identify the recovery point.
Page 112: Forcing A Snapshot
NOTE: The ability to delete an orphaned recovery chain is not available for replicated recovery points on a target core. To delete an orphaned recovery point chain: On the Core Console, select the protected machine for which you want to delete the orphaned recovery point chain.
Page 113: Restoring Data
USB key or IDSDM. To use this feature, Windows Backup virtual disk should exist. Windows Backup virtual disk is created during AppAssure Appliance Configuration Wizard. For more information see, Rapid Appliance Self Recovery in the Dell DL43000 Appliance Deployment Guide. Without a Windows Backup virtual disk, you cannot configure a policy or create Windows backups.
Page 114: About Exporting Protected Data From Windows Machines To Virtual Machines
If a backup is running, information regarding Current Backup Progress and Start Time is displayed. Windows Backup Policy To configure a Windows backup policy, perform the following steps: In the Core Console, navigate to Appliance → Backup. Click the Configure Policy button. The Windows Backup Policy window is displayed.
Page 115 with a high availability copy of the data. If a protected machine goes down, you can boot up the virtual machine to then perform recovery. The following diagram shows a typical deployment for exporting data to a virtual machine. Figure 9. Exporting data to a virtual machine You create a virtual standby by continuously exporting protected data from your Windows machine to a virtual machine.
Page 116: Exporting Backup Information From Your Microsoft Windows Machine To A Virtual Machine
Exporting backup information from your Microsoft Windows machine to a virtual machine In AppAssure you can export data from your Microsoft Windows machines to a virtual machine (VMware, ESXi, Hyper-V, and Oracle VirtualBox) by exporting all of the backup information from a recovery point as well as the parameters defined for the protection schedule for your machine.
Page 117 Performing a continuous (virtual standby) ESXi export To perform a continuous (virtual standby) ESXi export: In the Select Export Type dialog box, click Continuous (Virtual Standby). Click Next. The Virtual Standby Recovery Point to VMware vCenter Server/ESXi dialog box is displayed. Enter the parameters for accessing the virtual machine as described below.
Page 118: Exporting Windows Data Using Vmware Workstation Export
Exporting Windows data using VMware workstation export In AppAssure, you can choose to export data using VMware Workstation Export by performing a onetime or continuous export. Complete the steps in the following procedures to export using VMware Workstation Export for the appropriate type of export. Performing a one-time vmware workstation export To perform a one-time VMware Workstation export: In the Select Export Type dialog box, click One-time export.
Page 119 Text Box Description NOTE: It is recommended to use a name that is derived from the agent name or one that matches the agent name. You can also create a name derived from the hypervisor type, IP address or DNS name. Memory Specify the memory for the virtual machine.
Page 120: Exporting Windows Data Using Hyper-V Export
Text Box Description Virtual Machine Enter a name for the virtual machine being created. For example, VM-0A1B2C3D4. NOTE: It is recommended to use a name that is derived from the agent name or one that matches the agent name. You can also create a name derived from the hypervisor type, IP address or DNS name.
Page 121 Performing a one-time Hyper-V export To perform a one-time Hyper-V 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, and then click Next.
Page 122 On the Volumes page, select the volume(s) to export. For the virtual machine to be an effective backup of the protected machine include the protected machine’s boot drive. Example. C:\. Your selected volumes should be no larger than 2040 GB for VHD. If the selected volumes are larger than 2040 GB, and the VHD format is selected, you will receive an error.
Page 123: Exporting Microsoft Windows Data Using Oracle Virtualbox Export
• NOTE: Hyper-V Export supports VHDX disk formats if the target machine is running Windows 8 (Windows Server 2012) or higher. If the VHDX is not supported for your environment, the option is disabled. On the Network Adapters page, select the virtual adapter to be connected to a switch.
Page 124 Option Description Target Path Specify a local or remote target path to create the virtual machine. NOTE: The target path should not be a root directory. If you specify a network share path, you will need to enter valid logon credentials (user name and password) for an account that is registered on the target machine.
Page 125: Virtual Machine Management
Enter the parameters for accessing the virtual machine as described in the following table. Option Description Virtual Machine Enter a name for the virtual machine being created. Name NOTE: It is recommended to use a name that is derived from the agent name or one that matches the agent name.
Page 126 VM Management for Hyper-V and ESXi virtual standby(s) Field Description Agent / VM Agent Name: Indicates the name of the protected machine for which you have Information created virtual standby. VM Name: Indicates the name of the VM. NOTE: It is recommended to use a name that is derived from the agent name or one that matches the agent name.
Page 127 Field Description • Not Performed If an export is currently in progress, percentage of export is displayed. Last Export: Indicates the time of last export. Hypervisor Name: Indicates the name of the Hypervisor on which VM is created. Information Status: Indicates the status of connection to the Hyper-V and ESXi hypervisors. •...
Page 128 The maximum number of VNAs per VM depends on the type of hypervisor. For Hyper-V you can add up to 8 adapters for every virtual machine. To create a virtual network adapter: Navigate to the VM Management page. Click the Add Network Adapter button associated with the VM to add a VNA. NOTE: Do not add adapters to a VM for a Virtual Standby that is still running backups or exports of protected machines.
Page 129: Performing A Rollback
Stopping a VM operation To stop a VM operation: Navigate to the VM Management window. Click the Stop button associated with the VM to stop. NOTE: The Stop button is enabled only if the virtual machine is currently running and is available within a 30 second (approximately) refresh after starting the VM.
Page 130: Performing A Rollback For A Linux Machine By Using The Command Line
Select from the following options: • Live Recovery. When selected, the rollback for Windows volumes happens immediately. Selected by default. NOTE: The Live Recovery option is not available for Linux volumes. • Force Dismount. When selected, it forces the dismount of any mounted recovery point prior to performing the rollback.
Page 131: About Bare Metal Restore For Windows Machines
NOTE: To identify the recovery point, you can also specify a line number in the command instead of the recovery point ID number. In that case, use the agent/machine line number (from the lm output), followed by the recovery point line number and volume letter, followed by the path, such as, r [machine_line_item_number] [recovery_point_line_number] [volume_letter] [path].
Page 132: Roadmap For Performing A Bare Metal Restore For A Windows Machine
• Hardware to restore (new or old, similar or dissimilar) • Blank CD and CD burning software • VNC viewer (optional) • Windows 7 PE (32-bit) Compatible Drivers Storage and Network adapter drivers for the target machine • Storage Controller, RAID, AHCI, and chipset drivers for the target operating system NOTE: The Storage Controller Drivers are only needed if the restore being performed is to dissimilar hardware.
Page 133 Naming the boot cd file and setting the path To name the boot CD file and set the path: In the Create Boot CD dialog box, enter the ISO path where to store the boot image on the Core server. If the share on which you want to store the image is low on disk space, you can set the path as needed;...
Page 134: Loading A Boot Cd
Viewing the iso image creation progress To view the ISO image creation progress, select the Events tab, and then under Tasks, you can monitor the progress for building the ISO image. NOTE: You can also view the progress of the creation of the ISO image in the Monitor Active Task dialog box.
Page 135: Launching A Restore From The Core
In the Universal Recovery Console, click Driver Injection. To locate the compressed driver file, navigate through the filing system and select the file. If you clicked Driver Injection in step 3, click Add Driver. If you clicked Load driver in step 3, click Open.
Page 136: Viewing The Recovery Progress
c. Under Destination, from the drop-down menu, select the appropriate destination that is the target volume to perform the bare metal restore of the selected recovery point, and then click Rollback. In the RollbackURC confirmation dialog box, review the mapping of the source of the recovery point and the destination volume for the rollback.
Page 137: Performing A Bare Metal Restore For A Linux Machine
Performing a bare metal restore for a Linux machine You can perform a Bare Metal Restore (BMR) for a Linux machine including rollback of the system volume. Using the AppAssure command line utility aamount, roll back to the boot volume base image. Before you can perform a BMR for a Linux machine, you first must do the following: •...
Page 138: Installing The Screen Utility
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.
Page 139: Viewing Events And Alerts
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...
Page 140: Protecting Server Clusters
Protecting server clusters About server cluster protection In AppAssure, server cluster protection is associated with the AppAssure agents installed on individual cluster nodes (that is, individual machines in the cluster) and the Core, which protects those agents, all as if they were one composite machine. You can easily configure an Core to protect and manage a cluster.
Page 141: Protecting A Cluster
• Basic disks The supported mount types include: • Shared drives that are connected as drive letters (for example, D:) • Simple dynamic volumes on a single physical disk (not striped, mirrored, or spanned volumes) • Shared drives that are connected as mount points Protecting a cluster This topic describes how to add a cluster for protection in AppAssure.
Page 142: Protecting Nodes In A Cluster
b. In the Volumes dialog box, select the volume(s) to protect, and click Edit. c. In the Protection Schedule dialog box, select one of the schedule options for protecting your data as described in the following table. Text Box Description Interval You can choose from: •...
Page 143: Process Of Modifying Cluster Node Settings
Click Protect to start protecting this machine with default protection settings. NOTE: The default settings ensure that all volumes on the machine are protected with a schedule of every 60 minutes. To enter custom settings for this machine, (for example, to change the Display name, add encryption, or customize the protection schedule), click Show Advanced Options.
Page 144: Modifying Cluster Settings
• Modifying Cluster Settings • Configuring Cluster Event Notifications • Modifying the Cluster Retention Policy • Modifying Cluster Protection Schedules • Modifying Cluster Transfer Settings Modifying cluster settings After adding a cluster, you can easily modify basic settings (for example, display name), protection settings (for example, protection schedules, adding or removing volumes, and pausing protection), and more.
Page 145: Modifying The Cluster Retention Policy
Select one of the options described in the following table. Text Box Description Use Core alert This adopts the settings used by the associated core: settings Click Apply. Complete Step 5. Use Custom alert This lets you configure custom settings. Proceed to Step 4. settings If you select Custom alert settings, click Add Group to add a new notification group for sending a list of system events.
Page 146: Modifying Cluster Protection Schedules
periods of time and to help with management of these backup snapshots. The retention policy is enforced by a rollup process that helps in aging and deleting old backups. Do one of the following: • In the Core Console, click the Machines tab, and then select the cluster that you want to modify. •...
Page 147: Converting A Protected Cluster Node To An Agent
Modify the protection settings as described in Modifying Protection Schedules, beginning with Step Converting a protected cluster node to an agent In AppAssure, you can convert a protected cluster node to an AppAssure agent so that it is still managed by the Core, but it is no longer part of the cluster.
Page 148: Viewing Summary Information
Viewing summary information To view summary information: Do one of the following: • In the Core Console, click the Machines tab, and then select the cluster that you want to view. • In the left Navigation area, under Clusters, select the cluster that you want to view. On the Summary tab, you can view such information as the cluster name, cluster type, quorum type (if applicable), and the quorum path (if applicable).
Page 149: Forcing A Snapshot For A Cluster
point transfers. If there is no previous recovery point, all data (the base image) on the protected volumes is transferred. When you pause a snapshot, you temporarily stop all transfers of data from the current machine. For information about forcing snapshots for the individual machines in a cluster, see Forcing A Snapshot.
Page 150: Performing A Rollback For Clusters And Cluster Nodes
Performing a rollback for clusters and cluster nodes A rollback is the process of restoring the volumes on a machine from recovery points. For a server cluster, you perform a rollback at the node, or machine, level. This section provides guidelines for performing a rollback for cluster volumes.
Page 151: Removing Cluster Nodes From Protection
Option Description Keep Recovery To keep all currently stored recovery points for this cluster. Points Remove Recovery To remove all currently stored recovery points for this cluster from the Points repository. Removing cluster nodes from protection Complete the steps in the following procedures to remove cluster nodes from protection. If you just want to remove a node from the cluster, see Converting A Protected Cluster Node To An Agent.
Page 152: Viewing A Cluster Or Node Report
Viewing a cluster or node report You can create and view compliance and errors reports about AppAssure activities for your cluster and individual nodes. The reports include AppAssure activity information about the cluster, node, and shared volumes. For more information about AppAssure reporting, see About Reports.
Page 153: Reporting
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.
Page 154: About Errors Reports
• 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.
Page 155: Agents Summary
• 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 •...
Page 156: About The Central Management Console Core Reports
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:...
Page 157: Completing A Full Recovery Of The Dl4000 Appliance
Completing a full recovery of the DL4000 Appliance Creating a RAID 1 partition for the operating system CAUTION: It is essential that you perform these operations only on the RAID 1 virtual disks that contain the operating system. Do not perform these operations on the RAID 6 virtual disks that contain data.
Page 158: Installing The Operating System
If the media is not valid (if it is the incorrect CD or DVD, for example), a message displays requesting that you insert the correct installation media. Start USC by booting the system and pressing the <F10> key within 10 seconds of the Dell logo being displayed.
Page 159 After all services and applications are installed, click Proceed. The AppAssure Appliance Recovery wizard starts. Complete the steps in the Collecting Information and Configuring phase of the AppAssure Appliance Recovery Wizard and then click Next. The Disk Recovery phase begins. 10.
Page 160: Changing The Host Name Manually
Changing the host name manually It is recommended that you select a host name during the initial configuration of the DL4000 Backup to Disk Appliance. If you change the hostname at a later time using Windows System Properties, you must...
Page 161: Launching The Core With The New Host Name
Launching the Core with the new host name To launch the Core using the new host name that you created manually: Start AppAssure Core services. Right-click the AppAssure 5 Core icon on the desktop, and then click Properties. Replace the old server name with the new <server name:8006>. For example, https://<servername>:8006/apprecovery/admin/Core.
Page 162: Appendix A- Scripting
Appendix A— scripting About powershell scripting Windows PowerShell is a Microsoft .NET Framework-connected environment designed for administrative automation. AppAssure includes comprehensive client software development kits (SDKs) for PowerShell scripting that enables administrators to automate the administration and management of AppAssure resources by the execution of commands through scripts.
Page 163: Input Parameters
NOTE: The configuration file, powershell_ise.exe.config must have the same content as that of the powershell.exe.config file. CAUTION: If the pre-PowerShell or post-PowerShell script fails, the job also fails. Input parameters All available input parameters are used in sample scripts. The parameters are described in the following tables.
Page 164 Method Description Gets or sets a value containing the TCP port upon public ushort TransferDataServerPort which to accept connections from the Core for the { get; set; } actual transfer of data from the agent to the Core. The agent attempts to listen on this port, but if the port is in use, the agent can use a different port instead.
Page 165 Method Description Gets or sets the volume images to include in the public VolumeImageIdsCollection VM export. VolumeImageIds { get; private set; } Gets or sets the priority for export request. public ExportJobPriority Priority { get; set; } NightlyAttachabilityJobRequest (namespace Replay.Core.Contracts.Sql) Inherits its values from the parameter, BackgroundJobRequest.
Page 166 Table 7. TransferPostscriptParameter (namespace Replay.Common.Contracts.PowerShellExecution) Method Description Gets or sets the collection of volume names for public VolumeNameCollection VolumeNames transfer. { get; set; } Gets or sets the type of copying for transfer. public ShadowCopyType ShadowCopyType Available values: Unknown, Copy, and Full. { get;...
Page 167: Volumenamecollection (Namespace Replay.common.contracts.metadata.storage)
Method Description Gets or sets the value indicating whether the base public bool ForceBaseImage { get; image was forced. set; } Gets or sets the value indicating whether the job is public bool IsLogTruncation { get; a log truncation. set; } Gets or sets latest epoch value.
Page 168: Pretransferscript.ps1
Method Description public override bool Equals(object obj) Determines whether this instance and a specified object, which must also be a VolumeNameCollection object, have the same value. (Overrides Object.Equals(Object).) Returns the hash code for this public override int GetHashCode() VolumeNameCollection. (Overrides Object.GetHashCode().) Table 11.
Page 169: Preexportscript.ps1
# building path to Agent's Common.Contracts.dll and loading this assembly $regLM = [Microsoft.Win32.Registry]::LocalMachine $regLM = $regLM.OpenSubKey('SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall \AppRecovery Agent 5') $regVal = $regLM.GetValue('InstallLocation') $regVal = $regVal + 'Common.Contracts.dll' [System.Reflection.Assembly]::LoadFrom($regVal) | out-null # Converting input parameter into specific object $TransferPostscriptParameterObject = $TransferPostscriptParameter -as [Replay.Common.Contracts.PowerShellExecution.TransferPostscriptParameter];...
Page 170: Postexportscript.ps1
Postexportscript.ps1 The PostExportScript is executed on the Core side after any export job. NOTE: There are no input parameters for the PostExportScript when used to execute once on the exported agent after initial startup. The regular agent contains this script in the PowerShell script folder as PostExportScript.ps1.
Page 171 switch ($JobClassMethod) { # working with NightlyAttachability Job NightlyAttachabilityJob { $NightlyAttachabilityJobRequestObject = $NightlyAttachabilityJobRequest -as [Replay.Core.Contracts.Sql.NightlyAttachabilityJobRequest]; echo 'Nightly Attachability job results:'; if($NightlyAttachabilityJobRequestObject -eq $null) { echo 'NightlyAttachabilityJobRequestObject parameter is null'; else { echo 'AgentId:' $NightlyAttachabilityJobRequestObject.AgentId; echo 'IsNightlyJob:' $NightlyAttachabilityJobRequestObject.IsNightlyJob; break; # working with Rollup Job RollupJob { $RollupJobRequestObject = $RollupJobRequest -as [Replay.Core.Contracts.Rollup.RollupJobRequest];...
Page 172: Postnightlyjobscript.ps1
echo 'AgentId:' $ChecksumCheckJobRequestObject.AgentId; echo 'IsNightlyJob:' $ChecksumCheckJobRequestObject.IsNightlyJob; break; # working with Log Truncation Job TransferJob { $TransferJobRequestObject = $TransferJobRequest -as [Replay.Core.Contracts.Transfer.TransferJobRequest]; echo 'Transfer job results:'; if($TransferJobRequestObject -eq $null) { echo 'TransferJobRequestObject parameter is null'; else { echo 'TransferConfiguration:' $TransferJobRequestObject.TransferConfiguration; echo 'StorageConfiguration:' $TransferJobRequestObject.StorageConfiguration;...
Page 173 $NightlyAttachabilityJobRequestObject = $NightlyAttachabilityJobRequest [Replay.Core.Contracts.Sql.NightlyAttachabilityJobRequest]; echo 'Nightly Attachability job results:'; if($NightlyAttachabilityJobRequestObject -eq $null) { echo 'NightlyAttachabilityJobRequestObject parameter is null'; else { echo 'AgentId:' $NightlyAttachabilityJobRequestObject.AgentId; echo 'IsNightlyJob:' $NightlyAttachabilityJobRequestObject.IsNightlyJob; break; # working with Rollup Job RollupJob { $RollupJobRequestObject = $RollupJobRequest -as [Replay.Core.Contracts.Rollup.RollupJobRequest]; echo 'Rollup job results:'; if($RollupJobRequestObject -eq $null) { echo 'RollupJobRequestObject parameter is null';...
Page 174: Sample Scripts
# working with Log Truncation Job TransferJob { $TransferJobRequestObject = $TransferJobRequest -as [Replay.Core.Contracts.Transfer.TransferJobRequest]; echo 'Transfer job results:'; if($TransferJobRequestObject -eq $null) { echo 'TransferJobRequestObject parameter is null'; else { echo 'TransferConfiguration:' $TransferJobRequestObject.TransferConfiguration; echo 'StorageConfiguration:' $TransferJobRequestObject.StorageConfiguration; echo 'LatestEpochSeenByCore:' $LatestEpochSeenByCore; $TakeSnapshotResponseObject = $TakeSnapshotResponse -as [Replay.Agent.Contracts.Transfer.TakeSnapshotResponse];...
Page 175: Getting Help
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.

Dell DL4000 User Manual

1 Introduction to Dell DL4000 Appliance

2 Working with the DL4000 Core

3 Managing Your Appliance

4 Protecting Workstations and Servers

5 Protecting Server Clusters

6 Reporting

7 Completing a Full Recovery of the DL4000 Appliance

8 Changing the Host Name Manually

9 Appendix A- Scripting

10 Getting Help

Quick Links

Related Manuals for Dell DL4000

Summary of Contents for Dell DL4000

Table of Contents