Rapid Recovery 6.0 on DL Appliances User’s Guide August 2020 Rev.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2016 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents Chapter 1: Introduction to DL Appliance....................................................................................... 11 Deployment architecture...................................................................................................................................................11 Smart Agent.................................................................................................................................................................. 12 DL Appliance Core......
Removing a cloud account........................................................................................................................................ 82 Archiving..............................................................................................................................................................................82 Understanding archives............................................................................................................................................
Managing aging data.......................................................................................................................................................194 About Rapid Recovery data retention and archiving........................................................................................ 194 Managing retention policies.................................................................................................................................... 195 Replication.....................
Using the Reports menu.......................................................................................................................................... 273 Using the Reports toolbar....................................................................................................................................... 273 Understanding the Job report................................................................................................................................
RestoreArchive.......................................................................................................................................................... 323 RestoreUrc..................................................................................................................................................................324 Resume.............................................................................................................................................................
New-EsxiVirtualStandby..........................................................................................................................................378 New-HyperVVirtualStandby................................................................................................................................... 380 New-Mount................................................................................................................................................................
Qualifiers......................................................................................................................................................................432 Input Parameters for PowerShell Scripting.............................................................................................................. 433 Sample PowerShell scripts............................................................................................................................................
PowerShell scripting...................................................................................................................................................... 0 prohibited characters .................................................................................................................................................... 0 prohibited phrases ...................................................................................................................................................
1 Introduction to DL Appliance The DL Appliance with Rapid Recovery software is a backup, replication, and recovery solution that offers near-zero recovery time objectives and recovery point objectives. Rapid Recovery offers data protection, disaster recovery, data migration and data management .You have the flexibility of performing bare-metal restore (to similar or dissimilar hardware), and you can restore backups to physical or virtual machines, regardless of origin.
Figure 1. Basic deployment architecture You can also deploy multiple Cores as shown in the following diagram. A central console manages multiple cores. Figure 2. Multi—Core deployment architecture Smart Agent 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 forever block-level snapshots approach prevents repeated copying of the same data from the protected machine to the Core.
target-based inline compression, encryption, and deduplication of the data received from the protected machine. The Core then stores the snapshot backups in repositories such as, Storage Area Network (SAN) or Direct Attached Storage (DAS). The repository can also reside on internal storage within the Core. The Core is managed by accessing the following URL from a Web browser: https://CORENAME:8006/apprecovery/admin. Internally, all core services are accessible through REST APIs.
Understanding repositories A repository is a central location in which backup snapshot data captured from your protected workstations and server is stored and managed. Data is saved to a repository in the form of recovery points. A repository can reside on different storage technologies, including Storage Area Network (SAN), Direct Attached Storage (DAS), or Network Attached Storage (NAS). NOTE: Store repositories for Rapid Recovery Core on primary storage devices.
For more information on working with DVM repositories, see Managing a DVM repository on page 60. Deduplication in Rapid Recovery Deduplication is a data compression technique that reduces both storage requirements and network load. The process involves physically storing unique blocks of data only once on disk. In Rapid Recovery, when any unique data block occurs a second time within a repository, instead of storing the data again, a virtual reference to the data is stored.
CAUTION: Rapid Recovery takes a new snapshot whenever you apply an encryption key to a protected machine. A new snapshot is also triggered after you disassociate an encryption key for a protected machine. Encryption keys generated from the Rapid Recovery Core are text files that contain four parameters, as described in the following table: Table 1.
Figure 3. Point-to-point replication configuration ● Multipoint-to-point replication. Replicates protected machines from multiple source Cores to a single target Core. Figure 4. Multipoint-to-point replication configuration ● Point-to-multipoint replication. Replicates one or more protected machines from a single source Core to more than one target Core.
Figure 5. Point-to-multipoint replication configuration ● Multi-hop replication. Replicates one or more protected machines from one target Core to another target Core, producing additional failover or recovery options on the replicated Core. Figure 6.
If using Dell Data Protection backup appliances such as the DL1x00 or DL4x00 series, the target Core to which you replicate must have a valid software license configured. These hardware appliances include a replication target license with purchase. Check for your license key in the welcome email message you received when purchased the appliance. Retention and archiving In your appliance, backup and retention policies are flexible and, therefore, easily configurable.
Additionally, you can now archive your repository data to the cloud using Microsoft Azure, Amazon S3, Rackspace Cloud Block Storage, or other OpenStack-based cloud services. Alerts and event management In addition to HTTP REST API, your appliance also includes an extensive set of features for event logging and notification using e-mail, Syslog, or Windows Event Log. email notifications can be used to alert users or groups of the health or status of different events in response to an alert.
2 Working with the DL Appliance Core Topics: • • • • • • • • • • Understanding the Rapid Recovery Core Console Core settings Roadmap for configuring the Core Repositories Managing security Managing cloud accounts Archiving Events Rapid Appliance Self Recovery The Local Mount Utility Understanding the Rapid Recovery Core Console This section describes the different elements of the Rapid Recovery Core Console user interface (UI).
If you choose to perform any configuration tasks suggested by the Quick Start Guide, follow the prompts indicated in any step of the guide, and the appropriate wizard or relevant area in the user interface appears. Procedures to complete each task suggested by the guide is described in this document, as indicated in the table below. NOTE: Not all configuration tasks suggested by the Quick Start Guide are required for all users. You must understand which tasks you want to accomplish for your specific needs.
It also appears when you select Quick Start Guide from the Help drop-down menu, and each time you access the Home page on the Core Console. Use the procedure below to hide the Quick Start Guide. ● From the Rapid Recovery Core Console, if you are viewing the Welcome page of the Quick Start Guide, do the following: ○ If you want to hide the Welcome page of the Quick Start Guide, select Don't show again.
● If you see the page title Recovery Points Only, you are viewing information about all of the recover points-only machines on this Core. For information about the features and functions available from each page, see the appropriate section below. For more information about viewing protected machines, see Viewing the Protected Machines menu on page 26. For more information on managing protected machines, see Managing protected machines on page 132.
Table 3. Home page options UI Element Description Protected Machines The Protected Machines pane lists the machines that this Core protects. This pane appears regardless of whether any machines have been added to your Core for protection. This section includes the following information for each protected machine: ● Machine type. An icon shows whether the machine is a physical machine, virtual machine, or a protected cluster. ● Status.
Table 3. Home page options (continued) UI Element Description DVM Repositories This pane appears for the DL1000, regardless of whether any DVM repositories have been created. This pane does not appear unless your Core has one or more DVM repository. It includes the following information for each DVM repository: ● Type. An icon depicts a repository. ● Status.
The Protected Machines menu includes a drop-down menu on the right side which lists functions that can be performed on all protected machines.
Viewing the Summary pane The Summary pane contains summary information about the protected machine, including the host name, date and time of the last snapshot, date and time of the next scheduled snapshot, encryption key information, and version information for the Rapid Recovery Agent software. There is also a link to a detailed System Information page for the machine.
Viewing events for a protected machine On the Events page, you can view the jobs that occurred or are in progress for the protected machine you selected. Buttons at the top of the page let you navigate to lists of jobs in each of the three categories of activities: ● Tasks. A job that the Rapid Recovery must perform to operate successfully. ● Alerts. A notification related to a task or event that includes errors and warning. ● Journal. A composite of all protected machine tasks and alerts.
Table 6. Detailed information for the Event summary table (continued) UI Element Job Details Message Description Available for tasks only. Opens the Monitor Active Task dialog box, so you can view details of the specific job or task. These details include an ID for the job, rate at which the core transferred data (if relevant), elapsed time for the job to complete, total work in amount of gigabytes, and any child tasks associated with the job. Available for alerts and journal items.
CAUTION: This action removes all of the recovery points-only machines in your Rapid Recovery Core, permanently deleting them and precluding you from restoring information from those recovery points from this Core. Viewing the Custom Groups menu The custom groups menu appears in the left navigation area only if you have defined one or more custom groups. As with all menu labels in the navigation area, the label for this menu appears in all upper-case letters.
Table 7. Rapid Recovery Core configurable settings (continued) Configuration Setting Description General General settings include configuration options that apply generally to the Rapid Recovery Core, including display options and ports for the web server and for the Rapid Recovery service. For more information about the general settings for Rapid Recovery Core, including how to configure these settings, see Configuring Core general settings on page 34.
Table 7. Rapid Recovery Core configurable settings (continued) Configuration Setting Description You can configure credential information (username and password) for the local Mongo service database using the Local database settings. For more information on adjusting local database settings, see Modifying local database connection settings on page 44. SMTP server Configure simple mail transfer protocol (SMTP) server settings for the Core, you can also to send Core event information by email.
Table 7. Rapid Recovery Core configurable settings (continued) Configuration Setting Description For more information on vSphere settings for VMware or ESXi agentless protection, see Configuring vSphere settings on page 55. Log Uploads When this option is set to Yes, Rapid Recovery Core uploads log files to Dell for analysis in its on-going effort to improve overall product quality. This setting is optional.
occur from Core version 6.0.1.609 to 6.0.2.142 (both start with 6.0). On the same machine, the Core would not update automatically from 6.0.2.142 to 6.1.1.XXX, because the digits after the first decimal are not equal. Instead, you are notified (by a banner at the top of the Core Console) that an update to the Core software is available. This notification gives you an opportunity to review release notes, and determine if updating to the latest Core version is appropriate for your needs.
Understanding nightly jobs Nightly jobs are daily automated tasks that occur at a predetermined time outside of normal business hours. These jobs are memory-intensive, and include various integrity checks and data consolidation tasks that are best conducted when the Rapid Recovery Core is less active. All the nightly jobs, and the scope for which they can be applied, are described in the following table. Nightly jobs can be managed at the Core level (which applies to all machines protected on the Core).
Table 10. Nightly jobs information (continued) Job Name Scope Description Check checksum of Exchange databases Protected machine Checks the integrity of recovery points containing Exchange Database (EDB) files. NOTE: This option does not appear if you are not protecting an Exchange Server in your Core. Truncate SQL logs (simple recovery model only) Protected machine Maintains the size of SQL Server logs by truncating the database transaction log to match the last recovery point.
1. Navigate to the Rapid Recovery Core Console. 2. On the icon bar, click (Settings), and then do one of the following: ● From the list of Core settings on the left side of the Settings page, click Transfer Queue. ● Scroll down on the right side of the Settings page until you can see the Transfer Queue heading. The Transfer Queue core settings appear. 3. Click on the setting you want to change. The setting you selected becomes editable. 4.
Table 12. Client timeout settings information (continued) Setting Description Read/Write Timeout Controls the timeout for the connection between the Core and protected machines when reading or writing stream data across http. An example is receiving changed data blocks from a protected machine to the Core for an incremental snapshot. Enter the amount of time you want to lapse before a timeout occurs during a read/write event. Uses HH:MM:SS format. NOTE: The default setting is 0:05:00 or five minutes.
NOTE: Depending on your settings, the AppRecovery directory may not be visible on the Rapid Recovery Core. To see this directory, you may need to change the Folder Options control panel to show hidden files, folders, and drives. Assuming the Rapid Recovery Core is installed on the C drive, these locations are typically as follows: Table 13. Default storage locations for DVM deduplication cache settings Setting Default Storage Location Primary Cache Location C:\ProgramData\AppRecovery\RepositoryMetaData\
Table 14. DVM deduplication cache settings information (continued) Setting Description Since the primary and secondary caches are the same size, collective storage for these two caches requires twice the amount of space as the amount allocated for the deduplication cache size. For example, if you specify the default amount of 1.5GB for the deduplication cache size, ensure that each of the two storage locations have at least 1.5GB.
Table 15. Replay engine settings information Text Box Description IP Address The Core uses this IP address when performing mount and restore for a recovery point, to allow feedback between protected machines and the Сore. The IP address for the Replay engine automatically populates with the IP address of the Core machine. If you manually enter the server IP address, then this value is used in cases where the protected machine cannot resolve the automatically provided IP address.
Table 16. Deployment settings information Text Box Description Agent installer name The default filename is Agent-Web.exe. If you wish to change this file name for any reason, you can use this setting to specify a new name of the Core Web Installer executable file. This file streams a download of the latest version of the Rapid Recovery Core installer, which runs directly from the Web and lets you pause and resume the process as needed. Core address Enter the address of your Core server.
You are prompted to confirm this action, which results in abandoning any customized database connection settings. 4. Click on the setting you want to change. The setting you selected becomes editable. 5. Enter the configuration information as described in the following table. Table 17. Database connection settings information Text Box Description Host name Enter a host name for the database connection.
The setting you selected becomes editable. 4. Enter the appropriate credentials for connecting to the service database, as described in the following table. Table 18. Local database settings information Text Box Description User name Enter the name of a user with administrative privileges to the MongoDB service database. Password Enter the password associated with the user name you specified. 5. For each setting, when satisfied with your changes, click mode without saving.
Option Description ● ● ● ● ● ● ● ● ● Tabloid Ledger Legal A3 A4 Executive B4 C3Envelope C4Envelope Page orientation This option controls the page orientation for exported reports. The default orientation is Portrait. You can choose from the following layout options: ● Portrait ● Landscape 3. To change any of the settings for Reports, click in the appropriate setting field. The setting field appears as a configurable drop-down menu. 4. Click the drop-down menu, and select one of the values available.
● Scroll down on the right side of the Settings page until you can see the Attachability heading. 3. To use the SQL Server instance installed on the protected SQL Server machine, select Use SQL Server on the protected machine. This is the default option. 4. To use the SQL Server instance installed on the Rapid Recovery Core, select Use SQL Server on the Core, and then enter the authentication information as described in the following table. Table 19.
Table 20. Core jobs (continued) Job Name Description Maximum Concurrent Jobs Try Count Settings 1 0 Default ● Close the database. ● Dismount the database. ● Dismount the recovery point. Check checksum of Exchange databases Checks the integrity of recovery points containing Exchange databases. Process: ● Mount the latest recovery point for protection groups containing SQL databases. ● Connect to the database from SQL Server. ● Open the database. ● Close the database. ● Dismount the recovery point.
Table 20. Core jobs (continued) Job Name Description Maximum Concurrent Jobs Try Count Settings Export to virtual machine Exports data from specified recovery point of protected machine to destination path as a virtual machine. Process: 1 0 Add Import archives Imports recovery point from the specified backup 1 on a previously created Core archive. 0 Add Maintain repository Performs a check of the repository. Process: 1 0 Add ● Mount recovery point.
2. The number of times a job should be attempted if a network or other communication error prevents the job from succeeding the first time. This must be set to a value between 0 to 10. Several jobs are automatically included in Core settings. These jobs include a value of "Default" in the Settings column (as shown in the topic Understanding Core jobs on page 47).
NOTE: Although you can only use this feature for the job types included in Core settings by default, you can set other job types to defaults by removing them from the list and adding them again. Complete the steps in the following procedure to edit the settings of a job. 1. Navigate to the Rapid Recovery Core Console. 2. On the icon bar, click (Settings), and then do one of the following: ● From the list of Core settings on the left side of the Settings page, click Jobs.
● Add License. This option is available only for Dell backup appliances and lets you upload a license file or entering a license key. ● License Portal Group. This option opens the license portal for group management. ● License type. Types of licenses include Trial, Subscription, or Enterprise. For more information, see the topic About Dell Data Protection | Rapid Recovery License Portal Software License Types in the Dell Data Protection | Rapid Recovery License Portal User Guide. ● License status.
4. To update or change the existing license associated with your Core, at the top of the License Details core settings area, click Change License. The Change License dialog box appears. 5. To enter a license key or upload a license file, do one of the following: a. If you want to manually enter the license key, in the Change License dialog box, type the key carefully, and then click Continue.
Once the license is applied to the license server, any associated protected machines automatically update with the new license. Contacting the Dell Data Protection | Rapid Recovery License Portal server The Rapid Recovery Core Console frequently contacts the portal server to remain current with any changes made in the Dell Data Protection | Rapid Recovery License Portal. For non-trial licenses, the Rapid Recovery Core contacts the license portal once every hour.
● From the list of Core settings on the left side of the Settings page, click SNMP Configuration. ● Scroll down on the right side of the Settings page until you can see the SNMP Configuration heading. The SNMP Configuration settings appear. 3. Modify the SNMP settings as described in the following table. Table 21. SNMP connection settings information Text Box Description Incoming port Enter a port number for the SNMP connection. NOTE: The default setting is 8161.
1. Navigate to the Rapid Recovery Core Console. 2. On the icon bar, click (Settings), and then do one of the following: ● From the list of Core settings on the left side of the Settings page, click vSphere. ● Scroll down on the right side of the Settings page until you can see the vSphere heading. The vSphere settings appear. 3. Modify the vSphere settings as described in the following table. Table 22.
For example, type C:\Users\Your_User_Name\Documents\AA5CoreSettings and then click Back Up. A file named AppRecoveryCoreConfigurationBackup.xml is saved to the local destination you specified. 6. To restore Core settings from a backup XML file saved previously using this method, perform the following steps. NOTE: When you restore the Core configuration settings, the Rapid Recovery Core service restarts. a. From the top of the Settings page, click Restore. The Restore Core Configuration dialog box appears.
Table 23. Other Core-level tools UI Element Description System information Rapid Recovery lets you view information about the Rapid Recovery Core that includes system information, local and mounted volumes, and Replay engine connections. For more information on the information displayed on the System information page, see Understanding system information for the Core on page 58. For more information on how to view System information, see Viewing system information for the Core on page 59.
For more information, see Viewing system information for the Core on page 59. Viewing system information for the Core System information for the Core includes general information, information about local volumes, and information about mounted volumes for the Core. For a detailed description of the information available on this page, see Understanding system information for the Core on page 58. Complete the steps in this procedure to view system information for the Core.
Roadmap for configuring the Core Configuration includes tasks such as creating and configuring the repository for storing backup snapshots, defining encryption keys for securing protected data, and setting up alerts and notifications. After you complete the configuration of the Core, you can then protect agents and perform recovery.
1. Navigate to the Rapid Recovery Core Console. 2. On the icon bar, click (More), and then select Repositories. The Repositories page appears. On the Repositories page, the DVM Repositories pane appears. 3. At the top of the page, click Add New DVM Repository. The Add New Repository dialog box appears. 4. Enter the information as described in the following table. Table 25. Add New Repository settings Text Box Description Repository Name Enter the display name of the repository.
● Or, select Add file on CIFS share to specify a network share location, and then enter the information as described in the following table. Table 27. CIFS share credentials Text Box Description UNC path Enter the path for the network share location. 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).
11. When all of the storage locations you want to create for the repository at this time have been defined, in the Add New Repository dialog box, click Create. The Add New Repository dialog box closes, and your changes are applied. The Repositories page appears, showing your newly added repository in the DVM Repositories summary table. Expanding repository The Expand Repository feature is available on all DL models (1300, 4300, 4000), except DL 1000.
Viewing or modifying repository details 1. Navigate to the Rapid Recovery Core Console. 2. On the icon bar, click (More), and then select Repositories. The Repositories page appears. The DVM Repositories pane appears. 3. From the Repositories page menu, you can perform the following general actions: Option Description Add New DVM Repository Add a new DVM repository. Open Existing DVM Repository Open an existing DVM repository from another Core, which changes ownership of the repository to this Core.
1. Navigate to the Rapid Recovery Core Console. 2. On the icon bar, click (More), and then select Repositories. The Repositories page appears. The DVM Repositories pane appears. 3. In the repositories summary table, from the row representing the DVM repository for which you want to add a storage location, click Settings and select Add Storage Location. The Add Storage Location dialog box displays. 4. Specify how to add the file for the storage location.
Table 32. Storage location details (continued) Text Box Description If the storage location is a NTFS volume using Windows 8, 8.1 or Windows Server 2012, 2012 R2, the file size limit is 256 TB. NOTE: For Rapid Recovery to validate the operating system, Windows Management Instrumentation (WMI) must be installed on the intended storage location.
If your Core has been upgraded at any point from AppAssure 5.3.x and you used replication, you must run this job before you can configure dissimilar retention policies between the source Core and a target Core, or configure a custom retention policy on a replicated machine. You will not see or be able to run this job unless you have one or more eligible repositories (created prior to 5.4.x and not yet performed).
deduplication cache. If any repeated strings are found in the repository, that data is replaced with references to the data, which saves storage space in the repository. This is sometimes referred to as off-line deduplication, since this deduplication process occurs upon your request, instead of incrementally as snapshot data is transferred. The optimization process is processor-intensive. The amount of time it takes to run this job depends on several factors.
1. Navigate to the Rapid Recovery Core Console. 2. On the icon bar, click (More), and then select Repositories. The Repositories page appears. The DVM Repositories pane appears. 3. If you want to interrupt an optimization job, do the following: a. In the repositories summary table, from the row representing the appropriate repository, click Interrupt Optimization Job. and then select A warning prompt appears asking you to confirm the interruption. b. Click to confirm the optimization. 4.
Deleting a repository Complete the steps in this procedure to delete a repository. 1. Navigate to the Rapid Recovery Core Console. 2. On the icon bar, click (More), and then select Repositories. The Repositories page appears. On the Repositories page, the DVM Repositories pane appears. 3. In the repositories summary table, from the row representing the repository you want to delete, click drop-down menu, and then select Delete. to expand the A warning message appears to confirm deletion. 4.
Managing security The Core can encrypt protected machine snapshot data within the repository. Instead of encrypting the entire repository, you can specify an encryption key during the protection of a machine in a repository which lets the keys be reused for different protected machines. Encryption does not affect performance, as each active encryption key creates an encryption domain, thus letting a single core support multitenancy by hosting multiple encryption domains.
○ Modify the configuration settings for a specific protected machine. The encryption key you want to use for this approach must already exist on the Rapid Recovery Core, be a universal key type, and must be in an unlocked state. Encryption is part of the General settings. For more information, see Viewing and modifying protected machine settings on page 133. ○ Click the Not Encrypted icon on the Protected Machines page.
Table 34. New encryption key details (continued) Text Box Description Confirm Passphrase Re-enter the passphrase. It is used to confirm the passphrase entry. 4. Click OK. The dialog box closes. The encryption key you specified has been applied to future backups for this protected machine, and the lock now appears as closed. Optionally, if you want the encryption key applied immediately, force a snapshot. For more information, see Forcing a snapshot on page 231.
Table 35. Information about each encryption key (continued) UI Element Description Thumbprint This parameter is a 26-character alphabetic string of randomly generated English upper and lower case letters that helps uniquely identify each encryption key. Type Type describes the origin point of an encryption key and its ability to be applied. An encryption key can contain one of two possible types: Universal. Universal type is the default condition when you create an encryption key.
CAUTION: Store the passphrase in a secure location. Without a passphrase, you cannot recover data from encrypted recovery points. After an encryption key is defined, you can use it to safeguard your data. Encryption keys can be used by any number of protected machines. This step describes how to add an encryption key from the Rapid Recovery Core Console. This process does not apply the key to any machines currently being protected on the Core.
2. On the icon bar, click (More) and then select Encryption Keys. The Encryption Keys page appears. 3. Click Import. The File Upload dialog box appears. 4. In theFile Upload dialog box, navigate to the network or local directory containing the encryption key you want to import. For example, navigate to the Downloads folder for the logged-in user. The key filename starts with "EncryptionKey-," followed by the key ID, and ending in the file extension .key.
○ Select the Until option. ○ In the text field or using the calendar and clock widgets, explicitly specify the data and time you want the encryption key to lock. ○ Then click OK. This option is available for encryption keys added by replication. The dialog box closes and the changes for the selected encryption key are visible on the Encryption Keys page. Locking an encryption key When an encryption key state is locked, it cannot be applied to any protected machine until it is unlocked.
Changing an encryption key passphrase To maintain maximum security, you can change the passphrase for any existing encryption key. Complete the steps in this procedure to change the passphrase for an encryption key. CAUTION: After you edit the passphrase for an encryption key that is used to protect one or more machines, Rapid Recovery Core captures an incremental snapshot for that machine upon the next scheduled or forced snapshot. 1. Navigate to the Rapid Recovery Core. 2.
2. On the icon bar, click (More) and then select Encryption Keys. The Encryption Keys page appears. 3. Locate the encryption key you want to remove. Click its drop-down menu , and select Remove. The Remove Encryption Key dialog box appears. You see a message confirming the action to remove the encryption key. 4. In the dialog box, confirm that you want to remove the encryption key. NOTE: Removing an encryption key does not decrypt the recovery points already saved using the key.
Managing cloud accounts This section describes how to define links to existing cloud storage provider accounts, and how to manage those cloud accounts for use with Rapid Recovery. For example, you can archive Rapid Recovery data to the cloud, or import archived data from the cloud. About cloud accounts Rapid Recovery lets you archive data to a variety of cloud providers, or import archived data stored in a cloud account.
Table 37. Cloud account details (continued) Cloud Type Rackspace Cloud Files Text Box Description Tenant ID Enter your tenant ID for this account. Authentication URL Enter the authentication URL for this account. Display Name Enter a display name for this cloud account to display in the Rapid Recovery Core Console; for example, OpenStack 1. Region Use the drop-down list to select the region for your account. User Name Enter the user name for your Rackspace cloud account.
○ For Write Buffer Size, enter the buffer size you want to reserve for writing archived data to the cloud. ○ For Read Buffer Size, enter the block size you want to reserve for reading archived data from the cloud. b. Click OK. ● To return the cloud configuration to the following default settings, click Reset.
● Continuous archive (by schedule) 3. Click Next. 4. On the Location page, select an option from the Location type drop-down list and then enter the information as described in the following table. Table 38. Archive location type options Option Text Box Description Local 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 Location Enter the location for the output.
Table 40. Continuous archive recycle options Text Box Description Incremental Lets you add recovery points to an existing archive. It compares recovery points to avoid duplicating data that already exists in the archive. Replace this Core Overwrites any pre-existing archived data pertaining to this core but leaves the data for other cores intact. Erase completely Clears all archived data from the directory before writing the new archive. 14.
Editing a scheduled archive Rapid Recovery lets you change the details of a scheduled archive. To edit a scheduled archive, complete the steps in the following procedure. 1. In the Rapid Recovery Core Console, click the More drop-down menu on the icon bar, and then select Archives. 2. On the Archives page, under Schedule Archives, click the drop-down menu next to the archive you want to change, and then click Edit. The Add Archive Wizard opens. 3.
Table 43. Send data options (continued) Option Text Box Description At time Select the hour of the day you want to create a daily archive. 10. Optionally, to postpone archiving to resume at a later time, select Pause initial archiving. NOTE: You may want to pause the scheduled archive if you need time to prepare the target location before archiving resumes. If you do not select this option, archiving begins at the scheduled time. 11. Click Next. 12.
Checking an archive Checking an archive verifies whether an archive and its contents are healthy enough to be restored. You can scan an archive for the integrity of its structure, data segments, and index files by performing an archive check. The archive check verifies the presence of all necessary files within the archive and that the files are healthy. To perform an archive check, complete the steps in the following procedure. 1.
When you attach an archive, the archive name you provide appears as an archive menu in the left navigation menu of the Core Console. Each protected machine with recovery points in the archive is listed separately below the archive menu. You can click any machine name in the archive and browse its recovery points. You can then take the same actions as with any other recovery points currently visible in your Core. Attaching the archive also caches the credentials for accessing the information.
3. Click Next. 4. On the Location page, select the location of the archive you want to import from the drop-down list, and then enter the information as described in the following table: Table 47. Imported archive location type options Option Text Box Description Local 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 Location Enter the location for the output.
Table 49. Schedule import options Option Description Daily Click the clock icon and use the up and down arrows to select at what time you want to the archive job to begin. If you are using a 12-hour time system, click the AM or PM button to specify the time of day. Weekly Select the day of the week and then the time you want the archive job to begin. If you are using a 12-hour time system, click the AM or PM button to specify the time of day.
The contents of the Events page (on the Core or a specified machine) is divided into three sections: Tasks, Alerts, and Journal. These views allow you to filter details about various events, as appropriate. You can define how you are notified of various events by configuring notification groups. For more information, see Configuring notification groups on page 96.
Table 50. Export formats Format Description PDF Portable Document Format (default export format) HTML Web page format CSV Comma-separated values XLS Microsoft Excel® 1997 - 2003 Workbook XLSX Excel Workbook The file of the type you selected is downloaded to the default location on the Core server. 6.
1. To view a journal of all events for the Rapid Recovery Core, from the icon bar, click (Events), and then click Journal.To view all events for the Rapid Recovery Core, navigate to the Rapid Recovery Core Home page and then click (Events). If you want to view a journal of all events for a specific protected machine, then navigate to the Summary page of the specified machine, click the Events menu, and then click Journal. 2.
The setting you selected becomes editable. 4. Enter the configuration information as described in the following table. Option Description SMTP Server Enter the name of the email server to be used by the email notification template. The naming convention includes the host name, domain, and suffix; for example, smtp.gmail.com. From Enter a return email address. It is used to specify the return email address for the email notification template; for example, noreply@localhost.com.
The Edit Email Notification Configuration dialog box appears. 4. Select Enable Email Notifications. The email template is enabled and is visible. The values of the default email template are described in the following step. 5. Review the contents in the Edit Email Notification Configuration dialog box and determine if the default content suits your needs. Option Description Enable email notifications This setting enables or disables the email notification template.
Option Description remoteMasterCoreName The name of the remote source core associated with this event, if the event has source core scope. productName The name of the product, 'Rapid Recovery Core.' This product name can be changed for branding using white labeling. companyName The name of the company selling the product. 7. In the Email Subject text box, enter a subject for the email template.
1. Do one of the following: ● To set notifications at the Core level, from the icon bar, click (More), and then select Notifications. The Notifications page appears. ● To set notifications for a specific protected machine, do the following: a. From the Protected Machines menu, click the machine for which you want to specify notifications. The Custom Notification Groups page appears. b. In the Summary page of the protected machine, from the More drop-down menu, select Notifications.
● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Boot CD Clouds Clusters Core Service Database Retention Dedupe Cache DVM Repository Exchange Export Jobs Licensing Local Mount Log Truncation Metadata Nightly Jobs Notification Persist Core State PowerShell Scripting Protection Push Install Recovery Point Check Remote Mount Repository Common Replication Restore Rollup Scheduled Archives Security Server Logs vSphere ● To define alerts for all events in every group, select the checkbox for All Aler
Option Description Notify by Alerts Select this option if you want alerts to appear as pop-up windows located at the bottom right side of the Core Console. Notify by SNMP trap The Rapid Recovery Core serves as an SNMP agent, sending traps (notifications about specific events) to an SNMP manager. The result is the reporting of Core information such as alerts, repository status, and protected machines. Select this option if you want to notify Core events by SNMP trap. You must also specify a trap number.
5. Click OK to save your settings and close the dialog box. Configuring event retention Events and jobs tracked on the Core are saved for a specified amount of time. The default setting is 30 days. This number can be set between 0 days and 3652 days (approximately 10 years). Complete the steps in this procedure to configure retention for events. 1. Navigate to the Rapid Recovery Core Console. 2.
NOTE: Ensure that you have the latest RUU available and reachable on your appliance. . NOTE: To perform system recovery using RASR, see Recovering a Dell DL Backup and Recovery Appliance using Rapid Appliance Self Recovery (RASR) at https://www.dell.com/support.. To perform a factory reset: 1. Insert the RASR USB key created. 2. Restart the appliance and select Boot Manager (F11). 3. In the Boot Manager Main Menu, select One-shot BIOS Boot Menu. 4.
install the utility, by default, it is installed in the directory C:\Program Files\AppRecovery\Local Mount Utility and a shortcut appears on the machine’s desktop. While the utility was designed for remote access to a Rapid Recovery Core machine, you can also install the LMU on the same machine as a Rapid Recovery Core. When it runs on a Core, the application recognizes and displays all mounts from that Core, including mounts performed through the Rapid Recovery Core Console.
Table 51. Rapid Recovery Core credentials (continued) Option Description NOTE: This option is only available if you chose to use specific credentials. Password The password used to access the Core machine. NOTE: This option is only available if you chose to use specific credentials. 4. Click Connect. 5. If adding multiple Cores, repeat all steps as necessary.
Table 53. Core settings Option Description Host name The name of the Core from which you want to mount recovery points. NOTE: If installing the LMU on a Rapid Recovery Core machine, the LMU automatically adds the localhost machine. Port The port number used to communicate with the Core. The default port number is 8006. Use my Windows user credentials Select this option if the credentials you use to access the Core are the same as your Windows credentials.
Mounting a recovery point using the Local Mount Utility With the LMU, you can mount any recovery point associated with a connected Core machine, including protected machines, replicated machines, and recovery points only machines. Before mounting a recovery point, the local mount utility (LMU) must connect to the Core on which the recovery point is stored.
2. Expand the navigation tree to reveal the recovery points mounted for each machine and their volumes. 3. Click Explore next to the volume you want to explore. Refreshing recovery points The LMU does not receive real-time updates from the Core and protected machines. To refresh a protected machine and see its latest recovery points, complete the following procedure. From the Local Mount Utility user interface, right click the protected machine you want to refresh, and then click Refresh recovery points.
Dismounting all recovery points using Active Mounts window Complete the following procedure to dismount all mounted recovery points at one time from the Active Mounts window. 1. From the Local Mount Utility user interface, click Active Mounts. 2. In the Active Mounts window click Dismount All. 3. To confirm the command, in the window, click Yes. 4. In the Active Mounts window, click Close. Using the Local Mount Utility tray menu The LMU tray menu is located in your desktop task bar.
3 Managing Your Appliance The Core Console includes an Appliance tab, which you can use to provision space, monitor the health of the appliance, and access management tools. Topics: • • • • • Monitoring status of the Appliance Windows backup Provisioning storage Deleting space allocation for a virtual disk Recovery and Update Utility Monitoring status of the Appliance You can monitor the status of the Appliance subsystems by using the Appliance > Health page.
2. 3. 4. 5. c. Edit tag, so it will become d. Save and close. Go to Core Console. Click Appliance > RASR tab. Click Create Windows Backup volume button. Windows backup VD is created if there is enough space.
The Windows Backup Policy window is displayed. 3. Enter the parameters as described below: Text Box Description Following items will be backed up: ● OS Volume ● Recovery partition ● Bare metal recovery binaries All of the above are selected by default. Perform backup Select the frequency at which Winbackup has to be performed. You have the following options: Daily, Weekly, and Monthly. Select the time to schedule the backup: Enter the time to schedule a backup. 4. Click Configure.
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.
Deleting space allocation for a virtual disk In case, if you need to change provisioning configuration please contact technical support. For more information, see Contacting Dell section. 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 Rapid Recovery Core software and appliance-specific components.
8. If the bundled version in the utility is higher than the installed version, then the Recovery and Update Utility prompts you to confirm that you want to upgrade the Rapid Recovery Core software. NOTE: Rapid Recovery Core software downgrades are not supported. 9. If prompted, reboot your system. 10. After all services and applications are installed, click Proceed.
4 Protecting workstations and servers Topics: • • • • • Protecting machines Managing machines VM export Managing aging data Replication Protecting machines This section describes how to protect, configure, and manage the protected machines in your Rapid Recovery environment.
About protecting Linux machines with Rapid Recovery The Rapid Recovery Agent software is compatible with multiple Linux-based operating systems (for details, see the system requirements included in Rapid Recovery Installation and Upgrade Guide or Rapid Recovery Release Notes). The Rapid Recovery Core is compatible only with Windows machines.
Support for cluster shared volumes In Rapid Recovery release 6.x, support for cluster-shared volumes (CSV) is limited to native backup of CSVs running Windows Server 2008 R2. You can also restore CSV volumes running Windows Server 2008 R2 from a recovery point, or perform virtual export to a Hyper-V CSV running Windows Server 2008 R2. You cannot perform virtual export of a cluster-shared volume. New in Rapid Recovery release 6.0.
Understanding the Rapid Recovery Agent software installer Rapid Recovery lets you download installers from the Rapid Recovery Core. From the Downloads page, you can choose to download the Agent Installer, the Local Mount Utility (LMU), or an SNMP MIB file. For more information about the LMU, see The Local Mount Utility on page 101. For more information about SNMP, see Understanding SNMP settings on page 54.
To deploy and protect multiple machines simultaneously, perform the following tasks: ● Deploy Rapid Recovery Agent to multiple machines. See Deploying the Rapid Recovery Agent software to one or more machines on page 118. ● Monitor the deployment. See Verifying the deployment to multiple machines on page 120. ● Protect multiple machines. See About protecting multiple machines on page 145. NOTE: If you selected the Protect Machine After Install option during deployment, skip this task.
7. Click Finish. The system automatically verifies each machine that you selected. If Rapid Recovery detects any concerns during automatic verification, the wizard progresses to a Warnings page, where you can clear machines from selection and manually verify the selected machines. If the machines you added pass the automatic verification, they appear on the Deploy Agent to Machines pane. 8. If the Warning page appeared and you are still satisfied with your selections, click Finish again.
If Rapid Recovery detects any concerns during automatic verification, the wizard progresses to a Warnings page, where you can clear machines from selection and manually verify the selected machines. If the machines you added pass the automatic verification, they appear on the Deploy Agent to Machines pane. 11. If the Warning page appeared and you are still satisfied with your selections, click Finish again. The Rapid Recovery Agent software deploys to the specified machines.
You can also view information regarding the bulk deploy process from the Events page. Complete the steps in this procedure to verify the deployment. (Events), and then click Alerts. 1. Navigate to the Rapid Recovery Core Console, click Alert events appear in the list, showing the time the event initiated and a message. For each successful deployment of the Agent software, you will see an alert indicating that the protected machine has been added. 2. Optionally, click on any link for a protected machine.
When you first enable protection, you also activate the schedule. Thus, using the default settings, regardless of the current time of day, the first backup will occur every hour, on the hour (12:00 AM, 1:00 AM, 2:00 AM, and so on). Selecting periods lets you view the default protection schedule and make adjustments accordingly. Selecting a daily protection time causes Rapid Recovery Core to back up the designated protected machines once daily at a time you specify.
CAUTION: Rapid Recovery does not support bare metal restores (BMRs) of Linux machines with ext2 boot partitions. Any BMR performed on a machine with this type of partition results in a machine that does not start. If you want to be able to perform a BMR on this machine in the future, you must convert any ext2 partitions to ext3 or ext4 before you begin protecting and backing up the machine. 1. Do one of the following: ● If you are starting from the Protect Machine Wizard, proceed to Step 2.
With a default protection schedule, the Core will take snapshots of all volumes on the protected machine once every hour. To change the protection settings at any time after you close the wizard, including choosing which volumes to protect, go to the Summary page for the specific protected machine. ● To define a different protection schedule, in the Schedule Settings option, select Custom protection. 9.
creating in this step is later removed, all files at the storage location of your repository are deleted. If you define your storage location at the root, all other files in the volume (e.g., E:\) are deleted, which could result in catastrophic data loss. The Add Storage Location dialog box appears. c. Click Add Storage Location to define the specific storage location or volume for the repository. This volume should be a primary storage location. d.
Table 65. Storage configuration details (continued) Text Box Description If the storage location is a New Technology File System (NTFS) volume using Windows XP or Windows 7, the file size limit is 16 TB. If the storage location is a NTFS volume using Windows 8, 8.1, Windows 10, or Windows Server 2012, 2012 R2, the file size limit is 256 TB. NOTE: For Rapid Recovery to validate the operating system, Windows Management Instrumentation (WMI) must be installed on the intended storage location.
Table 66. Encryption key settings (continued) Text Box Description Encryption key names must contain between 1 and 130 alphanumeric characters. You may not include special characters such as the back slash, forward slash, pipe, colon, asterisk, quotation mark, question mark, open or close brackets, ampersand or hash. Description Enter a comment for the encryption key. This information appears in the Description field when viewing encryption keys from the Core Console.
NOTE: The default settings schedule a snapshot of all volumes every 60 minutes. 8. To enter custom settings for the cluster (for example, to customize the protection schedule for the shared volumes), do one of the following, and then see Creating custom protection schedules on page 129. ● To customize settings for an individual node, next to the node that you want to customize, click Settings, and then click Function next to the relevant volume.
8. If you want to secure the recovery points for this cluster using Core-based encryption, use the drop-down list to select an encryption key. 9. If you do not want protection to begin immediately after completing this procedure, select Initially pause protection. 10. To enter custom settings (for example, to customize the protection schedule for the shared volumes), do the following: a.
(protecting multiple machines), see About protecting multiple machines on page 145. For information on customizing protection periods when protecting an agent using either of these wizards, see Creating custom protection schedules on page 129. For information about modifying an existing protection schedule, see Modifying protection schedules on page 129. Complete the steps in this procedure to modify an existing protection schedule for volumes on a protected machine. 1.
● When establishing protection using the Protect Machine Wizard or the Protect Multiple Machines Wizard. ● From the Protected Machines drop-down menu in the left navigation area of the Rapid Recovery Core (pausing protection for all protected machines). ● From the Protected Machines page (accessible when you click on the Protected Machines menu). ● From a specific protected machine in the Protected Machines drop-down menu. ● From the top of every page for a specific protected machine.
● 6. If you want to resume protection, do the following: a. At the top of the page, click Resume. b. In the Resume Protection dialog box, click Yes. The Resume Protection dialog box closes, and protection resumes for the selected machine. Managing protected machines This section describes how to view, configure and manage the protected machines in your Rapid Recovery environment.
3. To view the most current information, click Refresh. For information about viewing summary and status information for an individual machine or node in the cluster, see Viewing protected machines on page 132. Configuring machine settings Once you have added machines for protection in Rapid Recovery, you can easily view and modify the settings that govern the behavior of that protected machine. When you modify settings for a specific machine, those settings supersede the behavior set at the Core level.
Table 69. General settings for a protected machine Text Box Description Display Name Enter a display name for the machine. This is the name that displays for a protected machine in the Rapid Recovery Core Console. You can enter up to 64 characters. By default, this is the host name of the machine. You can change this to something more user-friendly if needed. Do not use prohibited characters on page 0 or prohibited phrases on page 0 . Host Name Enter a host name for the machine.
Table 70. Transfer Settings for a protected machine (continued) Text Box Description Maximum Concurrent Streams Sets the maximum number of TCP links that are sent to the Core to be processed in parallel per protected machine, for machines protected in a DVM repository. NOTE: Dell recommends setting this value to 8. If you experience dropped packets, try increasing this setting. Maximum Concurrent Writes Sets the maximum number of simultaneous disk write actions per protected machine connection.
8. License details for a protected machine are read-only. License detail information is described in the following table. Table 72. License details for a protected machine Text Box Description Expiration Date Indicates the expiration date of the license for the selected protected machine. License Status Indicates the current status of the license for the selected protected machine. License Type Indicates the type of the license for the selected protected machine.
Table 74. Nightly Jobs settings information (continued) Text Box Description Check integrity of recovery points Conducts an integrity check of each recovery point created for the virtual machines on the Hyper-V host. 8. Click OK. 9. Under Auto Protection, to determine whether to automatically protect new virtual machines when they are added to the Hyper-V host, click the setting for Auto protect new virtual machines.
The Settings page opens. 3. In the list on the left side, click vSphere. The setting you selected becomes editable, as a text field or a drop-down menu. 4. Under vSphere, click the setting that you want to change. The setting you selected becomes editable, as a text field or a drop-down menu. 5. Enter the configuration information as described in the following table. Table 76. vSphere settings information Text Box Description Allow Rapid Recovery to delete user created VMware The default setting is No.
Throttling transfer speed When transferring backup data or replicated recovery points between protected machines and Cores over the network, you can intentionally reduce the speed of the transfer. This process is known as throttling. When you throttle the transfer speed, you limit the amount of your network bandwidth dedicated to file transfers from Rapid Recovery.
3. Optionally, click the Nightly Jobs link to scroll down in the Settings page to view nightly jobs settings. 4. Under the Nightly Jobs heading, click Change. The Nightly Jobs dialog box appears. NOTE: For information about the Rollup setting, including setting a custom retention policy, see Customizing retention policy settings for a protected machine on page 197. 5. In the Nightly Jobs dialog box, select the jobs you want to include to run nightly, or clear the options you want to omit for this machine.
from current protection, you can continue to restore the machine in the future, but only up to the state captured in a saved recovery point. If you remove the recovery points, this action deletes any snapshot data for that formerly protected machine from the Rapid Recovery Core. CAUTION: If you delete recovery points, you will no longer be able to restore data for that machine. Complete the steps in the following procedure to remove a machine from protection in your Rapid Recovery environment. 1.
Viewing license information on a machine You can view current license status information for the Rapid Recovery Agent software installed on a protected machine. 1. From the Rapid Recovery Core Console, under Protected Machines , click the machine that you want to modify. The Summary page for the selection machine appears. 2. Click the Settings menu. The Settings page appears, showing configuration settings for the selected machine. 3.
Custom groups can include protected machines, server clusters, replicated machines, and recovery point-only machines. Server clusters behave the same as protected machines, with the exception that a server cluster and its nodes behave as a single entity. If you attempt to add a node from a server cluster to a group, the entire cluster is added. A custom group may contain similar or dissimilar members. For groups of similar members, all group actions apply to all members of the group.
4. In the Name field, update the text, or delete the existing label text and type a new label or your custom group. Use a descriptive name that communicates the purpose of the group. For example, to group protected machines, replicated machines, and recovery point-only machines by geographic region, type Tokyo. You can rename a group later. NOTE: Labels must be 50 or fewer characters. You can include a single space between words. You must provide a label for your custom group. 5.
Viewing all machines in a custom group on one page Clicking the name of a custom group takes you to a Machines page that lists all the machines in that custom group. You can then perform some functions on all machines from the Actions menu, or you can perform functions individually by selecting commands from each individual machine. About protecting multiple machines You can add two or more Windows machines for protection on the Rapid Recovery Core simultaneously using the Protect Multiple Machines Wizard.
Table 79. Domain information and credentials (continued) Text Box Description Password The secure password used to connect to the domain. 6. Click Next. 7. On the Select Machines page of the wizard, select the machines you want to protect. The system automatically verifies each machine you selected. 8. Click Next. If the Protection page appears next in the Protect Multiple Machines Wizard, skip to Step 11.
Table 80. Add New Repository settings (continued) Text Box Description Repository names must contain between 1 and 40 alphanumeric characters, including spaces. Do not use prohibited characters on page 0 or prohibited phrases on page 0 . Concurrent Operations Define the number of concurrent requests you want the repository to support. By default the value is 64. Comments Optionally, enter a descriptive note about this repository. You can enter up to 254 characters. For example, type DVM Repository 2.
Table 82. CIFS share credentials (continued) Text Box Description Password Specify a password for accessing the network share location. e. In the Storage Configuration area, click More Details and enter the details for the storage location as described in the following table. Table 83. Storage configuration details Text Box Description Size Set the size or capacity for the storage location. The minimum size is 1 GB. The default is 250 GB.
and that you protect the passphrase you define. Store the passphrase in a secure location as it is critical for data recovery. Without a passphrase, data recovery is not possible. 17. If you want to encrypt these protected machines using an encryption key that is already defined on this Rapid Recovery Core, select Encrypt data using an existing Encryption key, and select the appropriate key from the drop-down menu. Proceed to Step 19. 18.
Table 85. vCenter/ESX(i) connection settings (continued) Text Box Description Port The port used to connect to the virtual host. The default setting is 443. User name The user name used to connect to the virtual host; for example, Administrator or, if the machine is in a domain, [domain name]\Administrator. Password The secure password used to connect to this virtual host.
● If you already have a repository and want to store the data from this machine for protection in the existing repository, then do the following: a. Select Use an existing repository. b. Select an existing repository from the list. c. Click Next. The Encryption page appears. Skip to Step 18 to optionally define encryption. ● If you want to create a repository, select Create a Repository, and then complete the following steps. a. On the Repository, enter the information described in the following table.
Table 87. Local disk settings (continued) Text Box Description levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted. ○ Or, select Add file on CIFS share to specify a network share location, and then enter the information as described in the following table. Table 88. CIFS share credentials Text Box Description UNC path Enter the path for the network share location. If this location is at the root, define a dedicated folder name (for example, Repository).
Table 89. Storage configuration details (continued) Text Box Description Average bytes per record Specify the average number of bytes per record. The default value is 8192. f. Click Next. If you chose the Advanced option in Step 1, the Encryption page appears. 18. Optionally, on the Encryption page, to enable encryption, select Enable Encryption. Encryption key fields appear on the Encryption page.
Protecting multiple machines manually Use this procedure to manually enter each machine that you want to protect. This is used, for example, when protecting Linux machines. 1. On the Rapid Recovery Core Console, click the Protect drop-down menu, and then click Protect Multiple Machines. The Protect Multiple Machines Wizard opens. 2. On the Welcome page, select one of the following options: ● Typical ● Advanced (show optional steps) 3. Click Next. 4.
The Encryption page appears. Skip to Step 19 to optionally define encryption. ● If you want to create a repository, select Create a Repository, and then complete the following steps. a. On the Repository, enter the information described in the following table. Table 91. Add New Repository settings Text Box Description Repository Name Enter the display name of the repository.
Table 93. CIFS share credentials Text Box Description UNC path Enter the path for the network share location. 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). The letters a to z are case-insensitive. Do not use spaces. No other symbols or punctuation characters are permitted.
NOTE: If you enable encryption, it will be applied to data for all protected volumes for this machine. You can change the settings later from the Encryption Keys page in the Rapid Recovery Core Console. For more information about encryption, see the topic Understanding encryption keys on page 15. CAUTION: Rapid Recovery uses AES 256-bit encryption in the Cipher Block Chaining (CBC) mode with 256bit keys.
Settings and functions for protected Exchange servers If you are protecting a Microsoft Exchange Server in your Core, there are additional settings you can configure in the Rapid Recovery Core Console, and there are additional functions you can perform. A single setting, Enable automatic mountability check, is available in the Core Console related to Exchange Server. If enabled, Exchange server mountability checks are conducted automatically.
Forcing log truncation for an Exchange machine In order to force log truncation, an Exchange database must be present on a protected volume. If Rapid Recovery does not detect the presence of a database, the log truncation check does not appear in the Core Console. When you force log truncation for a protected Exchange Server, the size of the logs are reduced. Complete the steps in this procedure to force log truncation on demand. 1.
Complete the steps in this procedure to force the system to perform a checksum check for a specific Exchange server recovery point. 1. In the left navigation area of the Rapid Recovery Core Console, select the protected Exchange server for which you want to force a checksum check, and then click the Recovery Points menu. The Recovery Points page appears for the protected Exchange server. 2. Scroll down to the Recovery Points pane. 3. Navigate through the recovery points to find the desired recovery point.
Setting credentials for a SQL Server machine You must add the SQL Server machine to protection on the Rapid Recovery Core before performing this procedure. For more information about protecting machines, see Protecting a machine on page 122. Once you protect data on a Microsoft SQL Server machine, you can set login credentials for a single instance, or for all SQL Servers, in the Rapid Recovery Core Console. Complete the steps in this procedure to set credentials for each SQL Server. 1.
In previous versions, SQL attachability required a local instance of Microsoft SQL Server to be installed and configured on the Core machine. Rapid Recovery Core now lets you choose to perform the attachability check from a SQL Server instance on the Core, or from a SQL Server instance on a protected SQL Server machine. The instance you select must be a fully licensed version of SQL Server, procured from Microsoft or through a licensed reseller. Microsoft does not allow the use of passive SQL licenses.
Protecting vCenter/ESXi VMs Rapid Recovery lets you protect vCenter/ESXi VMs without installing the Rapid Recovery Agent on the VM or ESXi host, achieving agentless protection. To protect an ESXi environment, the Rapid Recovery Core works with the snapshot technology native to VMware. Rapid Recovery agentless protection uses the ESXi client and the existing application program interface (API) to protect selected VMs on a single host without installing Rapid Recovery Agent software.
Protecting Hyper-V servers and clusters To protect a Hyper-V server agentlessly, you do not need to install the Rapid Recovery Agent on any VMs. You need only install it on the host machine or cluster node. The Agent protects the virtual hard disk on the host and converts any changes to the hard disk files to a volume image or disk image, depending on the file system. A new driver provides file-level support for VMs on hosts and on cluster shared volumes (CSVs).
If you recover a transactional application from a crash-consistent state, the database returns to the last valid state. That most recent valid state may be from the time of the crash, or it may be from earlier than the crash. If it is from earlier, then the database must roll forward some work to make the data files match the information in the logs. This process takes some time when you first open the database, which causes a delay when starting up the machine.
NOTE: VMware Changed Block Tracking (CBT) must be enabled on each of the VMs you want to protect. If it is not enabled, Rapid Recovery automatically enables CBT to ensure protection. 8. If you want to automatically protect new VMs when they are added to the host, select Auto protect new machines, and then complete the following steps. a. Click Next. b. On the Auto Protection page, select any containers in which you expect to add new machines. 9. Click Next. 10.
creating in this step is later removed, all files at the storage location of your repository are deleted. If you define your storage location at the root, all other files in the volume (e.g., E:\) are deleted, which could result in catastrophic data loss. The Add Storage Location dialog box appears. c. Click Add Storage Location to define the specific storage location or volume for the repository. This volume should be a primary storage location. d.
Table 101. Storage configuration details (continued) Text Box Description If the storage location is a New Technology File System (NTFS) volume using Windows XP or Windows 7, the file size limit is 16 TB. If the storage location is a NTFS volume using Windows 8, 8.1, Windows 10, or Windows Server 2012, 2012 R2, the file size limit is 256 TB. NOTE: For Rapid Recovery to validate the operating system, Windows Management Instrumentation (WMI) must be installed on the intended storage location.
Table 102. Encryption key settings (continued) Text Box Description Encryption key names must contain between 1 and 130 alphanumeric characters. You may not include special characters such as the back slash, forward slash, pipe, colon, asterisk, quotation mark, question mark, open or close brackets, ampersand or hash. Description Enter a comment for the encryption key. This information appears in the Description field when viewing encryption keys from the Core Console.
1. In the left navigation area of the Core Console, under the Protected Machines menu, click the arrow to expand the contextsensitive menu for the relevant protected machine. Scroll down to More, expand that menu, and then select The Download Agent Log page appears. 2. On the Download Agent Log page, click Agent Log. Click here to begin the download. 3. In the Opening AgentAppRecovery.
Managing machines This section describes a variety of tasks you can perform in managing your machines.
VM export This section describes how to export a recovery point to create a virtual machine. About exporting to virtual machines with Rapid Recovery From the Rapid Recovery Core, you can export a recovery point from a repository to a virtual machine. This process— sometimes called virtual export—is a physical-to-virtual (P2V) process that creates a virtual machine from a recovery point. The VM is a bootable clone of a protected machine.
NOTE: In a configuration involving replication, the Core shown represents the target Core. When you export to a virtual machine, the following information is exported: ● All of the backup data from a recovery point ● The operating system and settings from the original protected machine You can perform virtual export of recovery points for your protected Windows or Linux machines to VMware, ESXi, Hyper-V, and VirtualBox.
Table 104. Virtual machine options (continued) Option Description Cores per processor The number of cores you want to have for each processor. The minimum is 1. Disk provisioning Select the type of disk provisioning from the following options: ● Thin. Thin provisioning creates a virtual disk the size of the used space on the original volumes, rather than the entire volume size.
Table 106. Virtual machine options Option Description Resource Pool Select a resource pool from the drop-down list. Data Store Select a data store from the drop-down list. Virtual Machine Name Enter a name for the Virtual Machine.
Table 107. Virtual machine parameters Option Description VM Machine Location Specify the path of the local folder or network share on which to create the virtual machine. NOTE: If you specified a network share path, you will need to enter a valid logon credentials for an account that is registered on the target machine. The account must have read and write permissions to the network share. User name Enter the logon credentials for the network location for the export.
○ On the Virtual Standby page, click Add to launch the Virtual Machine Export Wizard. 2. On the Machines page of the Virtual Machine Export Wizard, select the protected machine that you want to export. 3. Click Next. 4. On the Recovery Points page, select the recovery point that you want to use for the export. 5. Click Next. 6. On the Destination page of the Virtual Machine Export Wizard, in the Recover to a Virtual Machine drop-down menu, select VMware Workstation, and then click Next. 7.
NOTE: You can monitor the status and progress of the export by viewing the Virtual Standby or Events pages. Performing a one-time Hyper-V export Complete the steps in this procedure to perform a one-time export to Hyper-V. 1. In the Rapid Recovery Core Console, in the button bar, click the Restore drop-down menu, click VM Export. 2. In the Virtual Machine Export Wizard, select One-time Export. 3. Click Next. 4. On the Machines page, select the protected machine that you want to export. 5. Click Next. 6.
16. To specify generation of Hyper-V to use for export, click one of the following: ● Generation 1 ● Generation 2 NOTE: Only generation 2 supports the secure boot option. 17. Specify the appropriate network adapter for the exported VM. 18. On the Volumes page, select the volume(s) to export; for example, C:\. NOTE: If the selected volumes are larger than the appropriate maximum allocations supported by the application as indicated below, or exceed the amount of space available, you will receive an error.
9. In the Virtual Machine Name text box, enter the name for the virtual machine. The name you enter appears in the list of virtual machines in the Hyper-V Manager console. 10. To specify memory usage, click one of the following: ● Use the same amount of RAM as the source machine. Select this option to identify that the RAM use is identical between the virtual and source machines. ● Use a specific amount of RAM. Select this option if you want to specify the amount of RAM in MB.
Table 111. Virtual machine parameters (continued) Option Description NOTE: The default name is the name of the source machine. 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. The account must have read and write permissions to the network share.
Table 112. Remote Linux machine settings Option Description VirtualBox Host Name Enter an IP address or host name for the VirtualBox server. This field represents the IP address or host name of the remote VirtualBox server. Port Enter a port number for the machine. This number represents the port through which the Core communicates with this machine. Virtual Machine Name Enter a name for the virtual machine being created. NOTE: The default name is the name of the source machine.
Table 113. Virtual standby information Column Description Select item For each row in the summary table, you can select the check box to perform actions from the list of menu options preceding the table. Status indicator Colored spheres in the Status column show the status of virtual standby. If you hover the cursor over the colored circle, the status condition is displayed. ● Green. Virtual standby is successfully configured, is active, and is not paused.
● In the Maximum Concurrent Exports dialog box, enter the number of exports you want to run simultaneously. The default number is 5. ● Click Save. 5. To cancel a one-time or continual export currently listed in the Export Queue, select the export, and then click Cancel. 6. To add a new virtual standby export, you can click Add to launch the Export Wizard.
Table 116. Virtual machine options (continued) Option Description The minimum amount is 1024 MB and the maximum allowed by the application is 65536 MB. The maximum amount of memory usage is limited by the amount of RAM available to the host machine. Number of processors The number of processors (CPUs) you want for the exported virtual machine. The minimum is 1. Cores per processor The number of cores you want to have for each processor. The minimum is 1.
Table 117. ESXi credentials (continued) Option Description User name Enter the logon credentials for the host machine. Password Enter the logon credentials for the host machine. 8. On the Virtual Machine Options page, enter the information described in the following table. Table 118. Virtual machine options Option Description Resource Pool Select a resource pool from the drop-down list. Data Store Select a data store from the drop-down list.
NOTE: To perform this type of export, you should have VirtualBox installed on the Core machine. Virtual Box Version 4.2.18 or higher is supported for Windows hosts. Performing a one-time VirtualBox export Complete the steps in this procedure to perform a one-time export to VirtualBox. 1. In the Rapid Recovery Core Console, in the button bar, click the Restore drop-down menu, click VM Export. 2. In the Virtual Machine Export Wizard, select One-time Export. 3. Click Next. 4.
Complete the steps in this procedure to perform a continuous export to a VirtualBox virtual machine (VM) using Rapid Recovery. 1. In the Rapid Recovery Core Console, do one of the following: ● From the Core Console, in the button bar, click the Restore drop-down menu, and then select VM Export. a. In the Virtual Machine Export Wizard, select Continuous (Virtual Standby). b. Click Next. ● From the Core Console, in the icon bar, click (Virtual Standby).
Performing a one-time VMware Workstation export Complete the steps in this procedure to perform a one-time export to VMware Workstation. 1. In the Rapid Recovery Core Console, in the button bar, click the Restore drop-down menu, click VM Export. 2. In the Virtual Machine Export Wizard, select One-time Export. 3. Click Next. 4. On the Machines page, select the protected machine that you want to export. 5. Click Next. 6.
11. On the Volumes page, select the volumes to export, for example, C:\ and D:\, and then click Next. 12. On the Summary page, click Finish to complete the wizard and start the export. NOTE: You can monitor the status and progress of the export by viewing the Virtual Standby or Events tab. Performing a continual (Virtual Standby) VMware Workstation export Complete the steps in this procedure to perform a continual export to a VMware Workstation virtual machine (VM) using Rapid Recovery. 1.
Table 122. Virtual machine parameters (continued) Option Description ● Use the same amount of RAM as source machine ● Use a specific amount of RAM, and then specify the amount in MB The minimum amount is 1024 MB and the maximum allowed by the application is 65536 MB. The maximum amount of memory usage is limited by the amount of RAM available to the host machine. Number of processors The number of processors (CPUs) you want for the exported virtual machine. The minimum is 1.
3. Click Next. 4. On the Machines page, select the protected machine that you want to export. 5. Click Next. 6. On the Recovery Points page, select the recovery point that you want to use for the export. 7. Click Next. 8. On the Destination page, in the Export to Virtual machine drop-down menu, select Hyper-V. 9. To export to a local machine with the Hyper-V role assigned, click Use local machine. 10.
NOTE: If the selected volumes are larger than the appropriate maximum allocations supported by the application as indicated below, or exceed the amount of space available, you will receive an error. ● For VHDX disk format, your selected volumes should be no larger than 64 TB. ● For VHD disk format, your selected volumes should be no larger than 2040 GB. 19. On the Volumes page, click Finish to complete the wizard and to start the export.
The minimum amount is 1024 MB, and the maximum allowed by the application is 65536 MB. The maximum amount of memory usage is limited by the amount of RAM available to the host machine. 11. To specify the disk format, next to Disk Format, click one of the following: ● VHDX ● VHD NOTE: Hyper-V Export supports VHDX disk formats if the target machine is running Windows 8 (Windows Server 2012) or higher. If the VHDX is not supported for your environment, the option is disabled.
Managing retention policies A retention policy is a set of rules that dictates the length of time for the Core to retain recovery points before starting to roll them up. Retention policies can be set to roll up based on hours, days, weeks, months and years. You can set up to six rules (the default policy sets five rules). Since you can back up as frequently as every 5 minutes, the first rule in the retention policy typically sets how long to retain all recovery points.
The Configuration dialog box for the Core default retention policy appears. 5. To restore Core retention policy settings to the default values at any time, at the bottom of the Configuration dialog box, click Restore Defaults and then click Yes to confirm. All settings are restored to the default values described in the table in Step 6. 6. To define a retention policy, first specify the primary setting that determines how long initial backup snapshots are retained.
In this example, the oldest recovery point would be one year, 4 months, and 6 days old. 7. When satisfied with your retention policy settings, click Save. The Configuration dialog box closes. 8. In the Nightly Jobs dialog box, click OK. The Nightly Jobs dialog box closes. The retention policy you defined is applied during the nightly rollup. You can also to apply these settings when specifying the retention policy for any individual protected machine.
Table 126. Schedule options for custom retention policy (continued) Text Box Description Enter a number to represent the retention period and then select the time period. The default is 3 days. You can choose from: Days, Weeks, Months, and Years …and then keep one recovery Provides a more granular level of retention. It is used as a building block with the primary point per hour for n setting to further define how long recovery points are maintained.
recovery points, one method is to archive. The other approach is to disable rollup or extend the retention period for the relevant protected machines. 11. Click Save. Forcing rollup for a protected machine You can bypass your scheduled retention policy by forcing recovery points to roll up at the protected machine level. 1. From the Protected Machines menu of the Rapid Recovery Core Console, click the name of a specific protected machine. The Summary page for the selection machine appears. 2.
NOTE: In this scenario, customers only have access to their own data. Possible replication configurations include: ● Point-to-point replication. Replicates one or more protected machines from a single source Core to a single target Core. Figure 9. Point-to-point replication configuration ● Multipoint-to-point replication. Replicates protected machines from multiple source Cores to a single target Core. Figure 10. Multipoint-to-point replication configuration ● Point-to-multipoint replication.
Figure 11. Point-to-multipoint replication configuration ● Multi-hop replication. Replicates one or more protected machines from one target Core to another target Core, producing additional failover or recovery options on the replicated Core. Figure 12.
If using Dell Data Protection backup appliances such as the DL1x00 or DL4x00 series, the target Core to which you replicate must have a valid software license configured. These hardware appliances include a replication target license with purchase. Check for your license key in the welcome email message you received when purchased the appliance. Recovery point chains and orphans Rapid Recovery captures snapshots of a protected machine, and saves the data to a repository as a recovery point.
time. Factors involved include the speed of your network, the robustness of your network architecture, and the amount of data to be transmitted to the target Core. For example, if the backup data on the source Core measures 10GB and the WAN link transfers 24Mbps, the transfer could take approximately one hour to complete. Based on the amount of information you want to copy to the target Core, the seed drive can add up to hundreds or thousands of gigabytes of data.
NOTE: Because large amounts of data need to be copied to the storage device, an eSATA, USB 3.0, or other highspeed connection is recommended. If the total size of the seed data archive is larger than the space available on the removable media, the archive can span across multiple devices. 3. For source and target Cores stored on virtual hosts, transfer backup data using a virtual hard disk.
Table 127. Examples of bandwidth per gigabyte (continued) Broadband Bandwidth Max Change Rate Fiber 20 Mbps and up 8.38GB per hour NOTE: For optimum results, adhere to the recommendations listed in the table preceding. If a link fails during data transfer, replication resumes from the previous failure point of the transfer (once link functionality is restored). Depending on your network configuration, replication can be a time-consuming process.
4. On the Target Core page of the Replication Wizard, if you are establishing replication with a target Core from this source Core for the first time, select I have my own Target Core, and then enter the information as described in the following table. Table 128. Target Core information Text Box Description Host Name Enter the host name or IP address of the Core machine to which you are replicating. Port Enter the port number on which the Rapid Recovery Core will communicate with the machine.
Table 129. Archive details (continued) Option Text Box Description NOTE: To select a cloud account, you must first have added it in the Core Console. For more information, see Adding a cloud account on page 80. Container Select a container associated with your account from the drop-down menu. Folder Name Enter a name for the folder in which the archived data is to be saved. The default name is Rapid-Recovery-Archive-[DATE CREATED]-[TIME CREATED] e. Click Next. f.
1. If you selected the option to use a seed drive, replication produces orphaned recovery points on the target Core until the seed drive is consumed and provides the necessary base images. 2. If you specified the use of the a drive, transfer the seed drive archive file to a volume (shared folder, virtual disk, or removable storage media). Then, consume the seed drive. Viewing incoming and outgoing replication If you click the Replication icon from the icon bar, the Replication page appears.
Table 132. Global actions available in the Outgoing Replication pane (continued) UI Element Description When you click the actions drop-down menu in this column, you see a list of actions to perform to affect the specific replication relationship. Information about incoming replication from another Core is described in the following table. Table 133.
● Consume the seed drive. For more information on consuming seed drive data on the target core, see Consuming the seed drive on a target Core on page 215. ● Set the replication priority for a protected machine. For more information on prioritizing the replication of protected machines, see Setting replication priority for a protected machine on page 222. ● Set a replication schedule for a protected machine. For more information on setting a replication schedule, see Scheduling replication on page 217.
Table 136. Third-party target core details Text Box Description Email Address Enter the email address associated with your third-party service subscription. Customer ID (optional) Optionally, enter the customer ID that was assigned to you by the service provider. 6. Click Next. 7. On the Protected Machines page of the Replication Wizard, select the protected machines you want to replicate to the third-party core. 8.
Table 138. Seed drive options Item Description Maximum Size Large archives of data can be divided into multiple segments. Select the maximum amount of space you want to reserve for creating the seed drive by doing one of the following: ● Select Entire Target to reserve all available space in the path provided on the Seed Drive Location page (for example, if the location is D:\work\archive, all of the available space on the D: drive is reserved).
The Pending Replication Requests section appears. 4. Under Pending Replication Requests, click the drop-down menu next to the request you want to review, and then click Review. The Review Replication Request window appears. NOTE: The information that appears in the Source Core Identity section of this window is determined by the request completed by the customer. 5.
Notification that the request has been ignored is sent to the source Core, and the request is removed from the Replication page on the target Core. Adding a machine to existing replication After replication is established between a source and target Core, it is possible to add new protected machines to replicate to the target. Complete the steps in the following procedure on the source Core to add a new protected machine to a paired target Core for replication.
f. On the Seed Drive Options page of the wizard, enter the information as described in the following table. Table 140. Seed drive options Item Description Maximum Size Large archives of data can be divided into multiple segments. Select the maximum amount of space you want to reserve for creating the seed drive by doing one of the following: ● Select Entire Target to reserve all available space in the path provided on the Seed Drive Location page (for example, if the location is D:\work\archive, all of
5. Enter the details for the seed drive archive file, as described in the following table based on the location type you selected in Step 4. Table 141. Archive details Option Text Box Description Local Location Enter the path for the archive. Network Location Enter the path for the archive. User Name Enter the user name. It is used to establish logon credentials for the network share. Password Enter the password for the network path.
The seed drive is removed. If no more seed drives exist on the source Core, the Seed Drives (#) link and outstanding seed drives section are removed from the Outgoing Replication pane. Managing replication settings Rapid Recovery lets you monitor, schedule, and adjust replication at the overall, core, and protected machine levels. You can edit the following replication settings: ● To schedule replication jobs, see Scheduling replication on page 217.
Using the Copy function to create a seed drive If you chose not to create a seed drive when you configured replication, you can create a seed drive using the Copy function in the protected machine drop-down menu. 1. On the source Core, open the Rapid Recovery Core Console, and from the icon bar, click The Replication page appears. (Replication). 2. On the Replication page, in the Outgoing Replication pane, click to expand the Core that protects the machine for which you want to create a seed drive.
Table 143. Seed drive options (continued) Item Description ● Replace this Core. Overwrites any pre-existing seed data pertaining to this core but leaves the data for other cores intact. ● Erase completely. Clears all seed data from the directory before writing the seed drive. Comment Enter a comment that describes the seed drive. Add all Agents to Seed Drive Select this option to replicate all protected machines on the source core using the seed drive. This option is selected by default.
Table 144. Replication tasks (continued) Section Description Available Actions ● Change Settings. Lists the display name and lets you edit the host and port for the target Core. ● Schedule. Lets you set a customized schedule for replication to this target Core. ● Add Machines. Lets you select a host from a drop-down list, select protected machines for replication, and create a seed drive for the new protected machine’s initial transfer.
c. Click Pause from the menu preceding the summary table. Replication for the selected protected machines is paused. 4. To resume replication for all replicated machines, do the following: a. Click the checkbox at the top of the summary table to select the source or target Core. b. Click Resume from the menu at the top of the summary table. Replication for all protected machines in the selected Core is resumed. 5. To resume replication for only certain machines, do the following: a.
Table 145. Replication settings (continued) Option Description Maximum transfer data size (GB) Specify the maximum size in GB for transferring blocks of replicated data. Restore Defaults Select this option to change all replication settings to the system defaults. NOTE: Take note of any customized settings before selecting this option. You will not be prompted to confirm this action 4. When satisfied, click Save to save the replication settings and close the dialog box.
3. Click the (Settings) drop-down menu for the protected machine you want to prioritize, and then click Settings. A dialog box appears. 4. Click the Priority drop-down list and select a priority, from 1 (Highest) to 10 (Lowest), based on your requirements. 5. Click Save. The dialog box closes, and the replication priority for the selected machine updates.
1. On the target Core, open the Rapid Recovery Core Console, and from the icon bar, click (Replication). The Replication page appears. In the Incoming Replication pane, the summary table includes a row for each source Core with protected machines that this target Core replicates. 2. Select the replicated machines to remove as follows: ● To delete all machines replicated from the source Core to your target Core, in the Incoming Replication pane, select the check box for that Core.
5 Recovering data Topics: • • • • Managing recovery Snapshots and recovery points Restoring data Understanding bare metal restore for Windows machines Managing recovery The Rapid Recovery 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.
The Recovery Points page appears, showing a Recovery Points Summary pane and a Recovery Points pane. You can view summary information about the recovery points for the machine as described in the following table. Table 147. Recovery point summary information Info Description Total recovery points Lists the total number of recovery points saved to the repository for this machine. Total protected data Indicates the amount of storage space used in the repository for these recovery points.
Table 149. Exchange database status indicators (continued) Status Color Description Green Indicates that the recovery point contains one or more database, and that mountability checks are enabled, and that mountability check passed or that the checksum check passed. Recovery status point colors for SQL databases The following table lists the status indicators that display for SQL databases. Table 150.
Table 151. Mount Options settings (continued) Option Description ● Writable Create a Windows share for this Mount Optionally, select this check box to specify if the mounted recovery point can be shared, and then set access rights to it, including the Share name and Allowed groups. 7. Click Finish to mount the recovery point.
Working with Linux recovery points The recommended and supported method to mount and unmount recovery points from a protected Linux machine is to use the local_mount utility. The procedures listed below specifically address using local_mount to mount and unmount Linux recovery points. NOTE: For managing Linux recovery points in any other way, see Managing snapshots and recovery points on page 225, as all other management can be conducted from the Core Console.
NOTE: You can also specify a line number in the command instead of the recovery point ID number to identify the recovery point. In that case, you would use the machine line number (from the lm output), followed by the recovery point line number and volume letter, followed by the path, such as, m .
Forcing a snapshot Forcing a snapshot lets you force a data transfer for the current protected machine. When you force a snapshot, the transfer starts immediately or is added to the queue if other jobs are running. You can choose from two types of snapshots. If you select an incremental snapshot and there is no previous recovery point, a base image is captured. Forcing a snapshot does not change the timing for any schedules snapshots. NOTE: Rapid Recovery supports Window 8, Windows 8.
Deleting an orphaned recovery point chain An orphaned recovery point is an incremental snapshot that is not associated with a base image. Subsequent snapshots continue to build onto this recovery point; however, without the base image, the resulting recovery points are incomplete and are unlikely to contain the data necessary to complete a recovery. These recovery points are considered to be part of the orphaned recovery point chain.
● If you want to use an existing repository, select the name of an existing repository. NOTE: When migrating recovery points to an existing repository, ensure that the existing repository has enough free space to contain the migrated recovery points. d. Click OK. 7. Resume protection for the machine or machines that you paused. For more information, see Pausing and resuming protection on page 130. 8. Take a new base image for each of the protected machines you moved.
specific data is requested, the background process prioritizes the restoration of this data immediately. This powerful functionality allows even the most stringent service-level agreement to be met. Once you start Live Recovery, metadata (directory structure, security descriptors, NTFS file attributes, free space map, and so on) of the target volume is quickly restored on the protected machine. Thereafter, the volume and its contents become available to the system.
If you want to restore from a recovery point to a system volume, or restore from a recovery point using a boot CD, you must perform a Bare Metal Restore (BMR).
○ If you have already created the boot CD, then proceed to Step 6. 6. Start the machine you want to restore to using the boot CD. For more information, for BMR on a Windows machine, see Loading the boot CD and starting the target machine on page 245 and for BMR on a Linux machine, see Loading the Live DVD and starting the target machine on page 254. 7.
Restoring a directory or file using Windows Explorer You can use Windows Explorer to copy and paste directories and files from a mounted recovery point to any Windows machine. This can be helpful when you want to distribute only a portion of a recovery point to your users. When you copy directories and files, the access permissions of the user who is performing the copy operation are used and applied to the pasted directories and files.
Performing a restore for SCC (Exchange, SQL) clusters Complete the steps in this procedure to perform a restore for SCC (Exchange, SQL) clusters. 1. Turn off all nodes except one. 2. Perform a restore using the standard Rapid Recovery procedure for the machine as described in About restoring volumes from a recovery point on page 234 and Restoring volumes for a Linux machine using the command line on page 259. 3. After the restore is finished, mount all databases from the cluster volumes. 4.
Rapid Recovery provides the ability to perform a bare metal restore (BMR) for your Windows or Linux machines. BMR is a process that restores the full software configuration for a specific system. It uses the term “bare metal” because the restore operation recovers not only the data from the server, but also reformats the hard drive and reinstalls the operating system and all software applications.
○ If restoring to dissimilar hardware, and the necessary storage and network drivers are not present on the boot CD, you may need to load the drivers from a portable media device. For more information, see Loading drivers using the Universal Recovery Console on page 246. ● Performing a BMR from the Restore Machine Wizard. Optionally, the processes for managing a Windows boot image and for launching the BMR, including all sub-tasks, can be performed from the Restore Machine Wizard.
Performing a bare metal restore using the Restore Machine Wizard You can use the Restore Wizard to create a boot CD as well as perform a bare metal restore (BMR). Before performing a BMR, see Prerequisites for performing a bare metal restore for a Windows machine on page 240 or Prerequisites for performing a bare metal restore for a Linux machine on page 253, as appropriate.
Use this option if you require remote access to the recovery console. You cannot log on using Microsoft Terminal Services while using the boot CD. Table 155. UltraVNC connection Option Description Password Specify a password for this UltraVNC connection. Port Specify a port for this UltraVNC connection. The default port is 5900. 10. When you are satisfied with your selections on the Boot CD page, click Next. 11.
f. Go to Step 18. 17. To map volumes manually, on the Disk Mapping page, complete the following steps: a. From the Volume mapping drop-down menu, select Manual. b. In the Destination column, select a destination volume you want to restore. Optionally, if you do not wish to restore a listed volume, clear the option. NOTE: At least one volume must be selected to perform the restore. 18. Click Finish.
To perform a BMR on a machine, you must start the machine from the boot CD, which launches the URC. The URC is what makes it possible to connect the BMR target to the location of the recovery point you want to use to complete the restore. 1. From the Rapid Recovery Core Console where the server you need to restore is protected, in the icon bar, click the More menu, and then click Boot CDs. 2. On the Boot CDs page, click Create Boot CD. The Create Boot CD dialog box displays. 3.
For more information about monitoring Rapid Recovery events, see Viewing events using tasks, alerts, and journal on page 90. When the ISO image creation is complete, a record of the image appears on the Boot CDs page, which you can access from the More menu in the icon bar. To access the ISO image, you can navigate to the output path you specified or click the link on the Boot CDs page to save the image to a location from which you can then load it onto the new system, such as a network drive.
To launch a BMR from the Rapid Recovery Core Console, perform the following tasks. ● Selecting a recovery point and initiating a BMR on page 247 ● About disk mapping for a bare metal restore on page 248 ● Loading drivers using the Universal Recovery Console on page 246 This process is a step in Performing a bare metal restore for Windows machines on page 239.
The Dell splash screen appears. 6. To start the URC, click the Dell icon. The URC opens to the Boot CD driver manager tab. 7. Expand the Other devices list. This list shows the drivers that are necessary for the hardware but are not included in the boot CD. 8. Right-click a device from the list, and then click Load Driver. 9.
If performing a BMR for a Linux machine from the Core Console, then this task is also a step in Performing a bare metal restore for Linux machines on page 252 It is part of the process for Launching a bare metal restore for a Linux machine using the command line on page 258. 1. In the Rapid Recovery Core Console, from the list of protected machines, click the name of the protected machine you want to restore. The Summary page for the selected machine appears. 2. Click Recovery Points. 3.
This task is a step in Performing a bare metal restore for Windows machines on page 239. It is part of the process for Using the Universal Recovery Console for a BMR on page 245. If performing a BMR for a Linux machine from the Core Console, then this task is also a step in Performing a bare metal restore for Linux machines on page 252. It is part of the process for Launching a bare metal restore for Linux on page 257.
● Creating a boot CD ISO image on page 243 ● Loading the boot CD and starting the target machine on page 245 From the Universal Recovery Console (URC), you can access the Rapid Recovery Core and retrieve a recovery point for a restore. You can also opt to restore your bare metal machine from a recovery point stored in an archive. The URC lets you reach this archive whether it is on a local drive, a network share, or a cloud account. 1. In the URC, click the Restore from Archive tab. 2.
○ Cloud path 5. Click Next. 6. On the Machines page, select the machine you want to restore, and then click Next. 7. On the Recovery Points page, select the recovery point you want to use to restore the machine, and then click Next. 8. On the Mapping page, select one of the following options, and then complete the corresponding steps: ● From the Volume Mapping drop-down list, select Automatic. a. In the left table, verify that the appropriate volumes are listed and are selected.
4. Navigate through the filing system to locate the compressed driver file, and then select the file. 5. Click OK. The URC loads the driver into the operating system you selected. 6. Repeat Step 3 through Step 5 for each additional driver you need to load. 7. Restart the BMR target machine. The BMR is complete. If you experience an issue when you restart, see Repairing boot problems on page 261.
● Verifying a Bare Metal Restore. After starting the bare metal restore, you can verify and monitor your progress. See Verifying the bare metal restore from the command line on page 261. ○ You can monitor the progress of your restore. See Viewing the recovery progress on page 260. ○ Once completed, you can start the restored server. See Starting a restored target server on page 261. ○ Troubleshoot the BMR process.
Downloading a boot ISO image for Linux You must download the Live DVD ISO image that matches your version of Rapid Recovery. The current version of Live DVD is available from the Dell Data Protection | Rapid Recovery License Portal at https://licenseportal.com. If you need a different version, contact Dell Rapid Recovery support NOTE: For more information about the Dell Data Protection | Rapid Recovery License Portal, see the Dell Data Protection | Rapid Recovery License Portal License Portal User Guide.
Managing Linux partitions When performing a BMR, the destination drive onto which you will be restoring data must have the same partitions as in the recovery point you are restoring. You may need to create partitions to meet this requirement. You can launch the restore from the command line using the aamount utility, or you can launch the restore from the Rapid Recovery Core Console. If restoring using the user interface, you must first mount the partitions.
9. To toggle a bootable flag for the boot partition (to make the partition bootable), type the following command and then press Enter: a 10. To assign a bootable flag for the appropriate partition, type the number of the partition and then press Enter. For example, to assign a bootable flag for partition 1, type 1 and then press Enter. 11. Continue partitioning your disk as needed. 12.
1. From the command line, enter the following command and then press Enter to change privileges to run as administrator and then list existing disk partitions: sudo fdisk -l A list of all volumes appears. 2. Format all partitions you will need to perform the BMR to the mount directory. These must match the volumes that are in the recovery point. For example, if the volume you want to mount is called sda1, and the mount directory is mnt, then type the following command and then press Enter: 3.
The screen utility starts on the machine booted with the Live DVD by default. However, if you have closed this application, you must start the Screen utility from the Live DVD using the procedure below. If the machine was booted from the Live DVD, then in the terminal window, type screen and press Enter. The Screen utility starts.
● Location of the volume ● Size of the recovery point ● An ID number for the volume that includes a sequence number at the end, which identifies the recovery point 5. To select the recovery point for a restore, enter the following command and then press Enter: r CAUTION: You must ensure that the system volume is not mounted. NOTE: If you started the machine from the Live DVD, then the system volume is not mounted.
4. Enter the logon credentials, that is, the user name and password, for this server. A list displays showing the machines protected by this Rapid Recovery server. It lists the protected machines found by line item number, host/IP address, and an ID number for the machine (for example: 7d658e5ffa08-4600-95f0-5f486bc1b6a4#de0896fd-571a-4cc5-aeed-264d2c3c72f4#f377e145-dd4d-3ac3-5b15-37ce8f4913ba:2). 5.
1. After you initiate the process restoring data from a recovery point, while the task is in process, you can view its progress from the Running Tasks drop-down menu on the Core Console. 2. Optionally, you can view detailed information in the Events page. Fore more information about monitoring Rapid Recovery events, see Viewing tasks, alerts, and events. Starting a restored target server Complete the steps in this procedure to start the restored target server.
Performing a file system check on the restored volume Once you execute a bare metal restore from the command line, you should perform a file system check on the restored volume to ensure the data restored from the recovery point was not corrupted. This task is a step in Performing a bare metal restore for Linux machines on page 252. It is part of the process for Verifying the bare metal restore from the command line on page 261. Perform the task below to perform a file system check on the restored volume.
For example, if /dev/sda2 is the root volume, then type mount /dev/sda2 /mnt and then press Enter. b. To mount the boot volume, type the following command and then press Enter: mount / /mnt/boot For example, if /dev/sda1 is the boot volume, then type mount /dev/sda1 /mnt/boot and then press Enter. NOTE: Some system configurations may include the boot directory as part of the root volume. 2.
11. If using SLES 12, CentOS 7, RHEL 7, or Oracle 7, install GRUB2 by typing the following command, and then press Enter: grub2-install /dev/sda 12. After you complete installation, run one of the following updates: ● For SLES: grub-install.unsupported --recheck /dev/sda grub-install.unsupported /dev/sda update-grub NOTE: If the update-grub command does not exist on your Linux distribution, omit this option.
6 Generating and viewing reports This section provides an overview of reporting available in Rapid Recovery Core, and in the Rapid Recovery Central Management Console. Topics: • • About Rapid Recovery reports The Central Management Console About Rapid Recovery reports You can generate reports from the Rapid Recovery Core Console. Some of these reports are also available from the Central Management Console. The reports available are described in the following table. Table 160.
Table 160. Rapid Recovery reports (continued) Report type Description ● When run from the Core Console, the categories of information in this report include Core, license, and repository. The information is displayed in list, chart, and table form. ● When run from the Central Management Console, this report can specify summary information for any combination of Cores or Core groups configured in the Console. The only configurable parameters are the report type and the date range.
5. To generate a Repository report only, skip to Step 11. 6. For a Job, Job Summary, Failure, or Summary report, from the Date Range drop-down menu, select a date range. If you do not choose a date range, the default option (Last 31 days) is used. You can choose from the options in the following table. Option Description Last 24 hours Reports activity for the last day, relative to the time you generate the report.
Option Description protected on that source Core. You can select all machines replicated in this target Core, or you can select a subset of them. [Custom groups] If you have any custom groups created on this Core, the name of each custom group appears as an option. Each object in that custom group appears. You can select all objects in the group, or a subset of them. 9. If generating a Summary report, skip to Step 12. 10.
Option Description Last 31 days Reports activity for the last 31 days, relative to the time you generate the report. Last 90 days Reports activity for the last 90 days, relative to the time you generate the report. Last 365 days Reports activity for the last year, relative to the time you generate the report. All Time This time period spans the lifetime of the Core. Custom This time period requires you to further specify start and end dates.
Complete the steps in this procedure to schedule a report. 1. Navigate to the Rapid Recovery Core Console. 2. From the icon bar, click (More), and then select Reports. The Job Report page appears. A downward-facing arrow appears to the right of the current report name. 3. Click the arrow to the right of the report name, and from the drop-down menu, select Scheduled Reports. The Scheduled Reports page appears. 4. To schedule a report to generate on a repeated basis, click Add.
Table 162. Location options for scheduled reports Location type Location type description Location Local Select location type Local to save generated reports in a local path accessible to the Core. Specify the path in the Location field. Type a location accessible to the Core locally. For example, to store reports in the Reports folder on the D drive, enter D:\Reports\. Network Select location type Network to save generated reports in a path accessible to the Core on the network.
The new report schedule appears in the Summary Reports summary table. Modifying a report schedule Once a report is scheduled, you can modify any of its parameters or details. You can edit report configuration information (report name, output format, report type, included repositories. You can also change email notification options, and the destination to save the generated report. Finally, you can also change the schedule of the report.
Using the Reports menu The Reports menu appears at the top of the page when viewing Reports. This menu includes a report title, which is also a dropdown menu that lets you see which report types are available. Below this menu are one or more filters that help you to define your report criteria. The specific filters available depend on the report type. For information on the parameters that apply to each report type, see the topic for understanding that report type.
Table 165. Reports toolbar icons (continued) Icon Description Next page. Progress to the next page in the report view. Enter page number. Click in the page number text field, enter a valid page number, and press Enter to progress to that page in the report view. Zoom out. Lets you zoom out the view of the generated report. Each successive click zooms out further, to a minimum of 25%. Zoom in. Lets you zoom in the view of the generated report. Each successive click zooms in further, to a maximum of 1000%.
When you generate a Job report, report details include the following: ● Selection criteria for the report ● A summary table showing a row for each job in the date range you specified.
When you generate a Failure report, a summary table appears, showing a row for each job in the date range you specified. In addition to listing the appropriate core, protected machine, and job type, each row includes: ● ● ● ● ● ● A summary of the job The job status Any errors related to the job The start and end dates for the job The job duration in seconds The total work in MB Understanding the Summary report The Summary report is available for one or more Cores.
○ Protected machine name ○ Volumes protected by the machine ○ Protected space, in GB (total and current) ○ Daily change rate (average and median) ○ Job statistics (success, completed, failed, canceled) ○ If encryption was applied ● The Core version Understanding the Repository report The Repository report includes information about the repositories on the selected Rapid Recovery Core and about the machines protected by that core. The information appears as two summaries within one report.
Table 166. UI elements in the Rapid Recovery Central Management Console (continued) UI Element Description Reports mode. In the navigation area, when in the Reports mode, selecting Cores or Core groups determines the set of information to appear when you generate reports. Manage mode. In the navigation area, when in the Manage mode, you can navigate through settings for Cores and Core Groups. You can also add and remove Cores and Core Groups in Manage mode.
1. From the Rapid Recovery Central Management Console, click the mode selector drop-down and select Manage. The page refreshes, showing Add Core, Add Group, and Delete icons. 2. From the top of the left navigation menu, click Add Core. The Add Core page appears. 3. Enter the required information for connecting to the Core, as described in the following table. Table 167.
Table 168. Core settings (continued) Text Box Description to [Core name]? ● Use hostname or IP address [host name or IP address]. On what port is [Core name] listening? Select either of the port options. You can choose: If you choose to specify the connection through the use of a host name or IP address, you must enter the appropriate information in the hostname or IP address field.
Table 170. Core group settings Text Box Description Parent group Select the parent group of the Cores for the new Core group settings you want to add. Display name Enter a display name for the Core group. The display name must be limited to 150 characters or less. Best practice is to keep this name under 33 characters. Do not use prohibited characters or prohibited phrases. For more information on prohibited characters or prohibited phrases, see the Dell Data Protection | Rapid Recovery User Guide. 4.
For information on how to generate a report for multiple cores, see Generating a report from the Central Management Console on page 282. Generating a report from the Central Management Console Complete the following procedure to generate a report for multiple Rapid Recovery Cores from the Central Management Console. 1. From the Rapid Recovery Central Management Console, click the mode selector drop-down menu in the upper-right corner, and select Reports. The report selection page appears.
7 Understanding the Rapid Recovery Command Line Management utility Dell Data Protection | Rapid Recovery consists of several software components. Key components relevant to this topic include the following: ● The Rapid Recovery Core manages authentication for protected machines, schedules for transferring data for backup and replication, export to virtual machines, reporting, and bare metal restore (BMR) to similar or dissimilar hardware.
• • Commands Localization Commands This section describes the commands and options available for the Rapid Recovery Command Line Management utility.
Archive Businesses often use long-term storage to archive both compliant and non-compliant data. The archive feature in Rapid Recovery supports extended retention for compliant and non-compliant data. The administrator can save an archive on the local storage or network location by specifying the -path parameter and credentials.
Table 171. Archive command options (continued) Option Description -comment Optional. Comment text must be enclosed in double quotes; for example: -comment “comment goes here...”. Examples: Archive all recovery points with creation dates starting from 04/30/2012 02:55 PM for all machines on the Core: >cmdutil /archive -core 10.10.10.10 -user administrator -password 23WE@#$sdd -path d:\work\archive -startdate “04/30/2012 02:55 PM” -all Archive recovery points that fall within a date range for two protecte
Table 172. CancelActiveJobs command options (continued) Option -jobtype Description Optional. Specifies job type filter.
Table 173. CheckRepository command options (continued) Option Description -password Optional. The password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none is provided, then the credentials for the logged-on user are used. Optional. This option checks all DVM repositories associated with the Core. -all -repository -force The name of the DVM repository. Optional. This option performs the check without your confirmation.
Table 174. CreateArchiveRepository command options (continued) Option -name -path archiveusern ame archivepassw ord cloudaccount name cloudcontain er Description Required. The name of the archive repository. The path to the existing archive. It can be a local, network, or cloud location. For example: d:\work \archive or \\servername\sharename. Optional. This option is the login to the remote machine. It is required for a network path only. Optional.
Command Options The following table describes the options available for the CreateBootCD command: Table 175. CreateBootCD command options Option Description Display this help message. -? -ip Optional. This option specifies the IP address of the target BMR machine. By default, it generates automatically. -mask Optional. This option specifies the subnet mask of the target BMR machine. By default, it generates automatically. defaultgatew ay Optional.
Command Options The following table describes the options available for the createrepository command: Table 176. CreateRepository command options Option -? Description Display help on the command. -core Optional. Remote core host machine IP address (with an optional port number). By default, the connection is made to the core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you must also provide a password.
Create a DVM repository at a share location: >cmdutil /createrepository -name “Repository 1” -size 200 Gb -uncpath \\share\repository -shareusername login -sharepassword pass123 -comment “First repository.” concurrentoperations 8 -core 10.10.10.10:8006 -user administrator -password 23WE@#$sdd DeleteRepository You can use the DeleteRepository command to remove an entire DVM repository created in AppAssure Core or Rapid Recovery Core.
Dismount Use the dismount command to dismount a mounted recovery point specified by the -path option, dismount points for the selected agent by the -protectedserver parameter, or dismount all mounted recovery points—-all. Usage The usage for the command is as follows: /dis[mount] -core [host name] -user [user name] -password [password] [-all | protectedserver [name | IP address] | -path [location] Command Options The following table describes the options available for the dismount command: Table 178.
Usage The usage for the command is as follows: /dismountarchiverepository -core [host name] -user [user name] -password [password] name] -name [archive repository name] Command Options The following table describes the options available for the DismountArchiveRepository command: Table 179. DismountArchiveRepository command options Option Description Display this help message. -? -core Optional. Remote Core host machine IP address (with an optional port number).
Table 180. EditEsxServer command options Option -? Description Display this help message. -core Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine. -user Optional. The user name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used. -password Optional.
Command Options The following table describes the options available for the force command: Table 181. Force command options Option Description Display this help message. -? -force Optional. Type of snapshot to create. Available values: 'snapshot' (incremental snapshot) and 'base' (base image snapshot). By default, an incremental snapshot is performed. -core Optional. Remote Core host machine IP address (with an optional port number).
Table 182. ForceAttach command options Option -? Description Display this help message. -core Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used. -password Optional.
Table 183. ForceChecksum command options (continued) Option Description -core Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used. -password Optional. Password to the remote Core host machine.
Table 184. ForceLogTruncation command options (continued) Option Description -user Optional. User name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used. -password Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none is provided, then the credentials for the logged-on user are used.
Table 185. ForceMount command options (continued) Option Description -rpn The sequential number of a recovery point against which to perform checks (run command /list rps to obtain the numbers). To perform checks against multiple recovery points with a single command, you can specify several numbers separated by spaces. -time Select a recovery point by its creation time. You must specify the exact time in the format “mm/dd/yyyy hh:mm tt” (for example, “2/24/2012 09:00 AM”).
Table 186. ForceReplication command options (continued) Option -all Description Force replication for all machines being replicated to the target core. Example: Force replication for a protected server on a specific target core: >cmdutil /forcereplication -target core 10.10.10.10 -protectedserver 10.20.30.40 ForceRollup Use the forcerollup command to force the rollup of recovery points on a protected machine.
ForceVirtualStandby Exporting data from a protected machine to a virtual machine creates a virtual standby machine. If you have continuous virtual export set up, you can use this command to force Rapid Recovery to export data on demand, regardless of the predetermined schedule.
Usage The usage for the command is as follows: /help Example: Request Command Line help: >cmdutil /help List The list command returns information about all recovery points, active jobs, completed jobs, failed jobs, invalid (failed) recovery points, valid (passed) recovery points, mounts, protected servers, volumes, virtualized servers, unprotected volumes, clusters, protection groups, SQL databases, Exchange databases, replicated servers, and repositories for the specified agent or list of servers current
Table 189. List command options (continued) Option Description ● ● ● ● SQL Server databases ('sqldatabases') MS Exchange databases ('exchangemailstores') replicated servers ('replicatedservers') repositories (‘repositories’) -core Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine.
Mount The mount command mounts a snapshot of one or more drives. You can specify whether the mount should be read, write, or read-only with previous writes. The default selection is read-only.
Table 190. Mount command options (continued) Option Description -localdrive Optional. Perform mount to user disk on local PC. Examples: Mount the most recent recovery points containing volumes “c:\” and “d:\” in the read-only mode: >cmdutil /mount -core 10.10.10.10 -user administrator -password 23WE@#$sdd protectedserver 10.10.5.22 -path c:\mountedrecoverypoint -mounttype read -volumes "c:" "d:" Mount recovery points with numbers 2 and 7: >cmdutil /mount -core 10.10.10.
Examples: Mount the repository named "NewArchive:" >cmdutil /mountarchiverepository -name NewArchive NewCloudAccount Use the NewCloudAccount command to add an account for a cloud provider to the Rapid Recovery Core. You can then use the account to store archives for retention or replication.
Table 192. NewCloudAccount command options (continued) Option Description The authentication key for the cloud account you want to add. This is the credential you use in the authentication process. The property has the following variations based on the cloud type: -key ● ● ● ● Amazon - Secret Key OpenStack - API Key Rackspace - API Key Windows Azure - Access Key -region The region of the cloud account you want to add. This option is required only for OpenStack and Rackspace acocunts.
Table 193. OpenDvmRepository command options (continued) Option shareusernam e sharepasswor d Description The user name you use to log in to the shared folder. The password you use to log in to the shared folder. Example: Open an existing DVM repository on the local machine: >cmdutil /opendvmrepository -localpath E:\Repository Pause An administrator can pause snapshots, export to virtual machines, or replicate a Core. The pause command accepts three parameters: snapshot, vmexport, and replication.
Table 194. Pause command options Option Description Display this help message. -? -pause [snapshots], [replication] or [vmexport]. -core Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used.
Pause incoming replication for all machines on the target core: >cmdutil /pause replication –core 10.10.10.10 -user administrator -password 23WE@#$sdd – incoming 10.10.1.82 Protect The protect command adds a server under protection by a core.
Example: Protect specific volumes of a server with the Core: >cmdutil /protect -core 10.10.10.10 -username administrator -password 23WE@#$sdd repository “Repository 1” -agentname 10.10.9.120 -agentport 5002 -agentusername administrator agentpassword 12345 -volumes “c:” “d:” ProtectCluster The protectcluster command adds a cluster under protection by a core.
Table 196. ProtectCluster command options (continued) Option clustervolum es clusternodes Description List of volumes to protect. Values must be enclosed in double quotes and separated by a space. Do not use trailing slashes in volume names; for example: “c:” “d:”. List of the cluster nodes and the volumes you want to protect on each node. Example: Protect specific volumes of a cluster server with the Core: >cmdutil /protectcluster -core 10.10.10.
Table 197. ProtectEsxServer command options (continued) Option Description -server serveruserna me serverpasswo rd -serverport virtualmachi nes -autoprotect The name or IP address for the vCenter or ESXi server you want to protect. The user name for logging in to the vCenter or ESXi server that you want to protect. The password for logging in to the vCenter or ESXi server that you want to protect. Optional. The port number for the vCenter or ESXi server that you want to protect. Optional.
Table 198. RemoveAgent command options (continued) Option Description -core Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used. -password Optional. Password to the remote Core host machine.
Table 199. RemoveArchiveRepository command options (continued) Option Description -name Required. The name of the archive repository. Examples: Remove the repository named "NewArchive" from the local Core: >cmdutil /removearchiverepository -name NewArchive RemovePoints The removepoints command lets you delete specific recovery points of a protected machine.
Example: Delete the recovery points with number 5 and 7: >cmdutil /removepoints -core 10.10.10.10 -user administrator -password 23WE@#$sdd protectedserver 10.10.5.22 -rpn 5 7 RemoveScheduledArchive Use this command to discontinue an existing Rapid Recoveryscheduled continuous archive.
RemoveVirtualStandby Use this command to discontinue the continuous export of data to a virtual machine in the Rapid Recovery command utility. Usage The usage for the command is as follows: /removevirtualstandby -core [host name] -user [user name] -password [password login] protectedserver [name] | -all Command Options The following table describes the options available for the removevirtualstandby command: Table 202. RemoveVirtualStandby command options Option Description Display this help message.
Usage The usage for the command is as follows: /replicate -request [email | email customer ID] -targetserver [host name | hostname port | hostname user name password | hostname port user name password] -replicationname [name] -seeddrive [localpath | network path username password] [comment] protectedserver [name | name repository] Command Options The following table describes the options available for the Replicate command: Table 203.
Replication Use the replication command to control existing replication between two Rapid Recovery Cores and manage pending replication requests. NOTE: This command succeeds the Replicate command, which establishes the connection—called pairing—between the Cores and uses a seed drive for the initial data transfer. For more information about this command, see Replicate on page 318.
Table 204. Replication command options (continued) Option protectedser ver responsecomm ent deleterecove rypoints scheduletype Description When responding to a replication request, use this option to apply your response to list of protected servers with a repository name or ID. Use the parameter "all" to apply response to all requested machines. The comment you provide with the response to a pending replication request.
Accept pending replication requests for two protect machines: >cmdutil /replication -accept -id customer@email.address -protectedserver 10.10.1.1 Repository1 10.10.1.2 Repository2 -responsecomment A response comment Deny a pending replication request: >cmdutil /replication -deny -id customer@email.
Table 205. RestoreAgent command options (continued) Option Description -rpn The identification number of the recovery point you want to use to restore the machine. To find the correct number, use the command /list rps. -volumes The IDs or names of the volumes you want to restore. To restore all protected volumes, use -volumes all. targetmacchi ne targetvolume forcedismoun t -autorestart The name of the machine to which you want to restore the protected machine.
Table 206. RestoreArchive command options (continued) Option Description -user Optional. User name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used. -password Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none is provided, then the credentials for the logged-on user are used.
Command Options The following table describes the options available for the restoreurc command: Table 207. RestoreUrc command options Option -? Description Display this help message. -core Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you must also provide a password.
Usage The usage for the command is as follows: /resume [snapshot | vmexport | replication] -core [host name] -user [user name] password [password] -all | -protectedserver [name | IP address] -incoming [host name] | outgoing [host name] -time [time string] Command Options The following table describes the options available for the resume command: Table 208. Resume command options Option Description Display this help message. -? -restore [snapshots], [replication] or [vmexport]. -core Optional.
Resume outgoing replication for all protected machines on the target core: >cmdutil /resume replication -core 10.10.10.10 -user administrator -password 23WE@#$sdd outgoing 10.10.1.63 Resume incoming replication for all machines on the target core: >cmdutil /resume replication -core 10.10.10.10 -user administrator -password 23WE@#$sdd incoming 10.10.1.82 SeedDrive You can use a seed drive for the initial data transfer when you establish Rapid Recovery replication.
Table 209. SeedDrive command options (continued) Option Description seeddriveuse rname seeddrivepas sword Optional. The user name for the network location of the seed drive. Optional. The password for the network location of the seed drive. -targetcore Optional. Use only with the -copy option. It is the name or IP address of the remote Core. All protected machines replicating to this Core receive seed drive recovery points. -remotecore Use only with the -consume option.
Usage The usage for the command is as follows: /startexport -exporttype [esxi | vm | hyperv | vb] -core [host name] -user [user name] password [password] -protectedserver [name | IP address] -volumes [volume names] -rpn [recovery point number | numbers] | -time [time string] -vmname [virtual machine name] hostname [virtual host name] -hostport [virtual hostport number] -hostusername [virtual host user name] -hostpassword [virtual host password] [-ram [total megabytes] | usesourceram] -diskprovisioning [thin
Table 210. StartExport command options (continued) Option Description -hostport hostusername hostpassword For ESXi and Hyper-V virtual exports only. The virtual server port number. For ESXi and Hyper-V virtual exports only. The user name for the virtual server host. For ESXi and Hyper-V virtual exports only. The password for the virtual server host. Use this option to allocate a specific amount of RAM on the virtual server. -ram usesourceram diskprovisio ning Optional.
10.10.10.23 -hostport 443 -hostusername root -hostpassword 12QWsdxc@# -usesourceram diskprovisioning thick Create a VMware Workstation machine file on the local drive with protected data from recovery point #4: >cmdutil /startexport -exporttype vmstation -core 10.10.10.10 -user administrator password 23WE@#$sdd -protectedserver 10.10.5.22 -rpn 4 -vmname Win2008-Smith -targetpath c:\virtualmachines -ram 4096 Create a Hyper-V machine files to be stored on a remote machine: >cmdutil /startexport -exporttype hy
Table 211. UpdateRepository command options (continued) Option Description sharepasswor d For share location only. Determines password to share location. -core Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you must also provide a password.
Table 212. Version command options (continued) Option Description -user Optional. User name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used. -password Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none is provided, then the credentials for the logged-on user are used. protectedser ver Optional.
Table 213. VirtualStandby command options (continued) Option Description -user Optional. The user name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used. -password Optional. The password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none is provided, then the credentials for the logged-on user are used.
Table 213. VirtualStandby command options (continued) Option Description ● Thin - This specification allocates the amount of actual disk space occupied on the original drive with a few additional megabytes. The default specification is "thin." -diskmapping For ESXi exports only. Optional. This option determines how to map the disks from the protected machine to the virtual machine. Use one of the following values: ● auto - This value automatically maps the disks.
Localization When running on the same machine on which Rapid Recovery Core is installed, the Rapid Recovery Command Line Management utility bases its display language on the language set for the Rapid Recovery Core. In this release, supported languages include English, Chinese (Simplified), French, Korean, German, Japanese, Portuguese (Brazil), and Spanish. If the Rapid Recovery Command Line Management utility is installed on a separate machine, English is the only language supported.
A Core Console references This appendix includes reference tables that describe many of the functions and icons available in the Rapid Recovery Core Console. It serves as a supplement to Understanding the Rapid Recovery Core Console on page 21 chapter of the Dell Data Protection | Rapid Recovery User Guide.
Table 214. UI elements included in the Core Console (continued) UI Element Description Left navigation area The left navigation area appears on the left side of the user interface, below the icon bar. ● The left navigation area contains the text filter and the Protected Machines menu. ● If you have added replication to this Core, then this area contains a Replicated Machines menu.
Table 215. Button bar buttons and menus (continued) UI Element Description Button bar: Archive button and menu The Archive button opens the Archive Wizard. From this wizard you can create a one-time archive from selected recovery points, or you can create an archive and continually save to that archive based on a schedule you define. Additionally for other archive options, you can access the drop-down menu next to this button, which includes the following options.
Table 216. Icon bar (continued) UI Element Description Console. You can also view the fully qualified domain name of the Core on your network, and the path for your cache metadata and deduplication caches. For more information about changing the display name, see Understanding system information for the Core on page 58. For more information about deduplication cache, see Understanding deduplication cache and storage locations on page 39.
Table 217. Left navigation menu options (continued) UI Element Description If you click a specific machine name shown in this pane, a Summary page appears, showing summary information for the selected machine. For more information on what you can accomplish on the Summary page, see Viewing summary information for a protected machine on page 27.
Table 218. Left navigation area and menus (continued) UI Element Description ● A hollow double-machine icon portrays a VMware VM using agentless protection. ● A hollow triple-machine icon portrays a VMware vCenter host. If you click the Protected Machines menu, a Protected Machines page appears, showing all protected machines on this Core in the Protected Machines pane. For more information, see Viewing the Protected Machines menu on page 26.
Viewing the Protected Machines pane The Protected Machines pane contains information about all machines protected on this Rapid Recovery Core. For each protected machine (if any are protected yet), you see listed in the grid the information described in the following table. Table 219. Information about each protected machine UI Element Description Select item For each row in the summary table, you can select the checkbox to perform actions from the list of menu options above the table.
Table 221. Actions available in the Protected Machines pane (continued) UI Element Description Recovery Points Opens the Recovery Points Summary page. Restore Launches the Restore Machine Wizard. This process lets you restore data from recovery point on the Core to a protected machine. For more information, see About restoring volumes from a recovery point on page 234.
Table 223. Actions available in the Protected Machines pane (continued) UI Element Description Recovery Points Opens the Recovery Points tab for the selected agent machine. For more information, see Managing snapshots and recovery points on page 225. Restore Launches the Restore Machine Wizard. This process lets you restore data from recovery point on the Core to a protected machine. For more information, see About restoring volumes from a recovery point on page 234.
Table 225. Detailed information for the Event summary table UI Element Description Status Shows the status for the task, alert, or journal item. Available for alerts or journal items, click the header to filter the results by status. Name Name is available for tasks only. This text field lists the task type that completed for this protected machine. Examples include transfer of volumes, maintaining repository, rolling up, performing mountability checks, performing checksum checks, and so on.
B Understanding the Rapid Recovery PowerShell module Dell Data Protection | Rapid Recovery consists of several software components. Key components relevant to this topic include the following: ● The Rapid Recovery Core manages authentication for protected machines, schedules for transferring data for backup and replication, export to virtual machines, reporting, and bare metal restore (BMR) to similar or dissimilar hardware.
• • • • Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers Prerequisites for using PowerShell Before using the Rapid Recovery PowerShell module, you must have Windows PowerShell 2.0 or later installed. Due to new features introduced in PowerShell 3.0, including easier access to object properties, PowerShell Web access, and support for REST calls, Dell recommends using PowerShell 3.0 or later. NOTE: Make sure to place the powershell.exe.
Getting cmdlet help and examples After you open PowerShell and import the Rapid Recovery PowerShell module, you can request additional information at any time by using the Get-Help cmdlet. For example, to get information about the virtual machine export cmdlet, enter the following cmdlet and then press Enter: Get-Help Start-VMExport The object returned includes the command name, synopsis, syntax, and any options you can use with the command.
Table 227. Cmdlets in the Rapid Recovery PowerShell Module (continued) Cmdlet name Description Get-Passed Get information about passed recovery points. Get-ProtectedServers Get information about protected servers. Get-ProtectionGroups Retrieve a collection of protection groups. Get-QueuedJobs Retrieve a collection of jobs waiting in the queue. Get-RecoveryPoints Get information about recovery points. Get-ReplicatedServers Get information about replicated servers.
Table 227. Cmdlets in the Rapid Recovery PowerShell Module (continued) Cmdlet name Description ResumeRepositoryActivity Resume repository activity. ResumeScheduledArchive Resume a scheduled archive. Resume-Snapshot Resume snapshot. Resume-VirtualStandby Resume exporting data to a virtual standby virtual machine. Start-Archive Archive recovery points. StartAttachabilityCheck Force attachability check for protected MS SQL databases.
Usage The usage for the command is as follows: Edit-EsxiVirtualStandby [-HostName ] [-HostPort ] [-HostUserName ] [-HostPassword ] [-DiskProvisioning ] [-DiskMapping ] [-ProtectedServer ] [-Volumes ] [-VMName ] [-UseSourceRam] [Ram ] [-User ] [-Core ] [-Password ] [-Verbose] [-Debug] [-ErroAction] [-WarningAction] [-ErrorVariable String>] [-WarningVariable [-
Example: Lists all active jobs on the local Core: >Get-activejobs –all Edit-HyperVVirtualStandby The Edit-HyperVVirtualStandby command lets you use PowerShell to make changes to an existing virtual export to a Hyper-V virtual machine (VM).
Table 229. Edit-HyperVVirtualStandby command options (continued) Option Description -jobtype -time Optional. Specifies the job type filter.
Table 230. Edit-ScheduledArchive command options (continued) Option -password Description Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on. If none are provided, then the logged-on user's credentials will be used. protectedser ver -all -path The protected machine with recovery points that you want to archive. You can specify multiple machine names enclosed in double quotes and separated by commas.
Table 230. Edit-ScheduledArchive command options (continued) Option Description The identifier of the scheduled archive that you want to edit. -id Example: Edit a scheduled archive on the local Core: >Edit-ScheduledArchive -protectedserver protectedserver1 -path d:\work\archive cloudaccountname cloud1 -cloudcontainer cloudarchives -recycleaction incremental scheduletype daily -time 12:00 AM -initialpause -i d archiveid Edit-VBVirtualStandby The Edit-VBVirtualStandby command lets you use PowerShell to ma
Table 231. Edit-VBVirtualStandby command options (continued) Option -all -number -jobtype -time Description Show all jobs, including those performed by the Core and all protected servers. Optional. Determine how many records to display. available values are: all (display all jobs); l[number] or [number] (fetches ## most recent jobs sorted by execution and time); f[number] (displays first ## recovery jobs sorted by execution and time). By default, the 20 most recent jobs are shown. Optional.
Table 232. Edit-VMVirtualStandby command options Option Description Display this help message. -? -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password. If none are provided, then the logged-on user's credentials will be used. -password Optional.
Usage The usage for the command is as follows: Get-ActiveJobs -core [host name] -user [user name] -password [password] -all | -protectedserver [server name or IP address] -number [all | f[number] |l[number] | number] -jobtype [type] -time [time] Command Options The following table describes the options available for the Get-ActiveJobs command: Table 233. Get-ActiveJobs command options Option -? Description Display this help message. -core Optional.
Example: Lists all active jobs on the local Core: >Get-activejobs –all Get-Clusters The Get-Clusters command returns information about server clusters protected in the Core. Usage The usage for the command is as follows: Get-Clusters -core [host name] -user [user name] -password [password] Command Options The following table describes the options available for the Get-Clusters command: Table 234. Get-Clusters command options Option Description Display this help message. -? -core Optional.
Usage The usage for the command is as follows: Get-CompletedJobs -core [host name] -user [user name] -password [password] -all | -protectedserver [server name or IP address] -number [all | f[number] |l[number] | number] -jobtype [type] -time [time] Command Options The following table describes the options available for the Get-CompletedJobs command: Table 235. Get-CompletedJobs command options Option -? Description Display this help message. -core Optional.
Example: Lists all active jobs on the local Core: >Get-CompletedJobs –all Lists all completed create repository jobs on the local Core: >Get-CompletedJobs –jobtype repository Get-ExchangeMailStores The Get-ExchangeMailStores command returns information about male stores on Exchange servers Protected by the Core.
Get-Failed The Get-Failed command returns information about failed recovery points on the local Core. Usage The usage for the command is as follows: Get-Failed -core [host name] -user [user name] -password [password] -all | -protectedserver [server name or IP address] -number [all | f[number] |l[number] | number] Command Options The following table describes the options available for the Get-Failed command: Table 237. Get-Failed command options Option -? Description Display this help message.
Usage The usage for the command is as follows: Get-FailedJobs -core [host name] -user [user name] -password [password] -all | -protectedserver [server name or IP address] -number [all | f[number] |l[number] | number] -jobtype [type] -time [time] Command Options The following table describes the options available for the Get-FailedJobs command: Table 238. Get-FailedJobs command options Option Description Display this help message. -? -core Optional.
Example: Lists all failed jobs on the local Core: >Get-FailedJobs –all Lists all failed create backup jobs on the local Core: >Get-FailedJobs -type backup Get-Mounts The Get-Mounts command returns all recovery points mounted on the local Core.
Get-Passed The Get-Passed command returns information about recovery points that have passed verification checks on the Core. Usage The usage for the command is as follows: Get-Passed -core [host name] -user [user name] -password [password] -protectedserver [server name or IP address] -number [all | f[number] |l[number] | number] Command Options The following table describes the options available for the Get-Passed command: Table 240.
Table 241. Get-ProtectedServers command options Option -? Description Display this help message. -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password. If none are provided, then the logged-on user's credentials will be used. -password Optional.
Table 242. Get-ProtectionGroups command options (continued) Option Description protectedser ver Show jobs for a specific protected machine, indicated by IP address. Example: Lists protection groups on the local Core: >Get-ProtectionGroups -protectedserver 10.10.10.10 Get-QueuedJobs The Get-QueuedJobs command returns all jobs waiting to begin from the Core.
Table 243. Get-ActiveJobs command options (continued) Option -number -jobtype -time Description Optional. Determine how many records to display. available values are: all (display all jobs); l[number] or [number] (fetches ## most recent jobs sorted by execution and time); f[number] (displays first ## recovery jobs sorted by execution and time). By default, the 20 most recent jobs are shown. Optional. Specifies the job type filter.
Table 244. Get-RecoveryPoints command options (continued) Option Description If none are provided, then the logged-on user's credentials will be used. -password Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on. If none are provided, then the logged-on user's credentials will be used. protectedser ver -number Show jobs for a specific protected machine, indicated by IP address. Optional. Determine how many records to display.
Table 245. Get-ReplicatedServers command options (continued) Option -password Description Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on. If none are provided, then the logged-on user's credentials will be used. Example: Lists all replicated servers on the local Core: >Get-ReplicatedServers Get-Repositories The Get-Repositories command returns information about repositories on the Core.
Get-ScheduledArchives The Get-ScheduledArchives command lets you use PowerShell to view information about the existing Rapid Recovery scheduled archives associated with this Core. Usage The usage for the command is as follows: Get-ScheduledArchives -core [host name] -user [login] -password [password] Command Options The following table describes the options available for the Get-ScheduledArchives command: Table 247. Get-ScheduledArchives command options Option Description Display this help message.
Table 248. Get-SqlDatabases command options Option -? Description Display this help message. -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password. If none are provided, then the logged-on user's credentials will be used. -password Optional.
Table 249. Get-UnprotectedVolumes command options (continued) Option Description If none are provided, then the logged-on user's credentials will be used. -password Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on. If none are provided, then the logged-on user's credentials will be used. protectedser ver Show jobs for a specific protected machine, indicated by IP address.
Example: Lists all virtualized servers on the local Core: >Get-VirtualizedServers Get-Volumes The Get-Volumes command returns information about volumes on a specified machine that is protected by the Core. Usage The usage for the command is as follows: Get-Volumes -core [host name] -user [user name] -password [password] -protectedserver [server name or IP address] Command Options The following table describes the options available for the Get-Volumes command: Table 251.
Usage The usage for the command is as follows: New-Base [[-all] | -protectedserver [machine name]] -core [host name] -user [user name] password [password] Command Options The following table describes the options available for the New-Base command: Table 252. New-Base command options Option Description Display this help message. -? Base image for all agents. -all -core Optional. Remote Core host machine IP address (with an optional port number).
Command Options The following table describes the options available for the New-CloudAccount command: Table 253. New-CloudAccount command options Option -? Description Display this help message. -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password.
New-EncryptionKey The New-EncryptionKey command lets you create a new encryption key for securing your Rapid Recovery backed up data. Usage The usage for the command is as follows: New-EncryptionKey -core [host name] -user [login] -password [password] -name [encryption key name] -passphrase [pas sphrase] -comment [comment] Command Options The following table describes the options available for the New-EncryptionKey command: Table 254.
Usage The usage for the command is as follows: New-EsxiVirtualStandby -core [host name] -user [login] -password [password] protectedserver [name | IP address] -volumes [volumes names] -vmname [virtual machine name] -hostname [virtual host name] -hostport [virtual host port number] -hostusername [virtual host login] -hostpassword [virtual host password] [-ram [total megabytes] | usesourceram] -diskprovisioning [thin | thick] -diskmapping [automatic | manual | withvm] -initialexport Command Options The follo
Table 255. New-EsxiVirtualStandby command options (continued) Option Description usesourceram diskprovisio ning Optional. Allocate the same amount of RAM on the virtual server that the source protected machine has. Optional. The amount of disk space to allocate on the virtual machine. Available values include: ● Thick - Specify 'thick' to make the virtual disk as large as the original drive on the protected server.
Table 256. New-HyperVVirtualStandby command options Option -? Description Display this help message. -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password. If none are provided, then the logged-on user's credentials will be used. -password Optional.
Table 256. New-HyperVVirtualStandby command options (continued) Option Description usesourceram initialexpor t Optional. Allocate the same amount of RAM on the virtual server that the source protected machine has. Optional. Specify this option if you need to start an initial on-demand virtual machine export after configuring the virtual standby.
Table 257. New-Mount command options (continued) Option Description latest or last checked recovery point by passed parameter value. By default the latest time option is chosen. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password. If none are provided, then the logged-on user's credentials will be used. -password Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on.
Command Options The following table describes the options available for the New-Replication command: Table 258. New-Replication command options Option Description Display this help message. -? -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password.
Table 259. New-Repository command options Option -? Description Display this help message. -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -password Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none are provided, then the logged-on user's credentials will be used.
Usage The usage for the command is as follows: New-ScheduledArchive -core [host name] -user [login] -password [password] -all | protectedserver [name | IP address] -path [location] -archiveusername [name] archivepassword [password] -cloudaccountname [name] -cloudcontainer [name] recycleaction [type] -schdeuletype [type] -dayofweek [name] -dayofmonth [number] -time [time] Command Options The following table describes the options available for the New-ScheduledArchive command: Table 260.
Table 260. New-ScheduledArchive command options (continued) Option cloudcontain er recycleactio n scheduletype Description Optional. Use only for cloud archiving. The name of the cloud container in the chosen cloud account, where the archive will be saved. When you use this option, you should also specify the "cloudaccountname" parameter. The type of recycle action.
New-Snapshot The New-Snapshot command forces a snapshot resulting in a data transfer for the current protected machine. When you force a snapshot, the transfer will start immediately or will be added to the queue. Only the data that has changed from a previous recovery point will be transferred. If there is no previous recovery point, all data on the protected volumes will be transferred.
Usage The usage for the command is as follows: New-VBVirtualStandby -core [host name] -user [login] -password [password] protectedserver [name | IP address] -volumes [volumes names] -vmname [virtual machine name] [-ram [total megabytes] | -usesourceram] -linuxhostname [linux hostname] hostport [linux port] -targetpath [location] -pathusername [login] -pathpassword [password] -initialexport Command Options The following table describes the options available for the New-VBVirtualStandby command: Table 262.
Table 262. New-VBVirtualStandby command options (continued) Option Description pathusername pathpassword accountusern ame accountpassw ord initialexpor t The user name for logging in to the network machine. It is only required when you specify a network location for the target path. The password for logging in to the network machine. It is only required when you specify a network location for the target path. Optional.
Table 263. New-VMVirtualStandby command options (continued) Option Description -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password. If none are provided, then the logged-on user's credentials will be used. -password Optional. Password to the remote Core host machine.
Push-Replication The Push-Replication command forces replication for one or more protected machines. Usage The usage for the command is as follows: Push-Replication -core [host name] -user [user name] -password [password] -targetcore [host name] -all | -protectedserver [machine name | IP address] Command Options The following table describes the options available for the Push-Replication command: Table 264. Push-Replication command options Option Description Display this help message.
Usage The usage for the command is as follows: Push-Rollup -core [host name] -user [user name] -password [password] -protectedserver [machine name | IP address] Command Options The following table describes the options available for the Push-Rollup command: Table 265. Push-Rollup command options Option -? -all Description Display this help message. Force all protected machines. -core Optional. Remote Core host machine IP address (with an optional port number).
Command Options The following table describes the options available for the Remove-MountAgent command: Table 266. Remove-Agent command options Option Description Display this help message. -? -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password.
Table 267. Remove-Mount command options Option -? -all Description Display this help message. Dismount all mounted recovery points. -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -password Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on. If none are provided, then the logged-on user's credentials will be used.
Table 268. Remove-Mounts command options (continued) Option Description -password Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none are provided, then the logged-on user's credentials will be used. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password. If none are provided, then the logged-on user's credentials will be used.
Table 269. Remove-RecoveryPoints command options (continued) Option -time Description Use this option to delete a chain of recovery points. Optional. To delete a single recovery point, select the recovery point by its creation time. Specify the exact time in the format "mm/dd/yyyy hh:mm tt" (for example, "2/24/2012 09:00 AM"). Keep in mind to specify date and time values of the time zone set on your computer. Required.
Table 270. Remove-Repository command options (continued) Option Description -password Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on. If none are provided, then the logged-on user's credentials will be used. -name The name of the repository that you want to delete. Delete all repositories associated with this Core.
Table 271. Remove-ScheduledArchive command options (continued) Option -id Description The identifier of the archive that you want to remove. To list more than one archive, separate each ID with a space.
Example: Remove all virtual standby jobs associated with this Core: >Remove-VirtualStandby -all Resume-Replication The Resume-Replication command lets you resume replication. See Suspend-Replication on page 423 for more details.
# Repository - ---------1 Repository A 2 Repository B Please, input number of Repository from the list above or type 'exit' to exit: Script pauses, requiring user to specify an index number for the appropriate repository. Enter the index number for the script to complete (in this case, 2). Example continues: 2 Replication job was started. True PS C:\Users\Administrator> Resume-Snapshot An administrator is able to resume snapshots, export to virtual machines, and perform replication.
Example: Resume snapshots for the protected machine with IP 10.10.10.4 for the local Core: >Resume-Snapshot -protectedserver 10.10.10.4 Resume-VirtualStandby The Resume-VirtualStandby PowerShell command lets you resume the suspended export of data to a Rapid Recovery virtual standby machine.
Resume-VMExport The Resume-VMExport command lets an administrator export to virtual machines. See Suspend-VMExport on page 427 for more details. Usage The usage for the command is as follows: Resume-VMExport -core [host name] -user [user name] -password [password] -all | protectedserver [name | IP address] Command Options The following table describes the options available for the Resume-VMExport command: Table 276. Resume-VMExport command options Option -? Description Display this help message.
Usage The usage for the command is as follows: Start-Archive -path -startdate -enddate [-all] | -protectedserver [machine name] or [IP]] -core [host name] -user [user name] -password [password] Command Options The following table describes the options available for the Start-Archive command: Table 277. Start-Archive command options Option Description Display this help message. -? -path Location path. Example path: ‘D:\work\archive’ or network path: ‘\\servername\sharename’.
Example: Archive all recovery points for all machines on the Core: >Start-Archive -path D:\work\archive -startdate 'Example 04/30/2012' –all Start-AttachabilityCheck The Start-AttachabilityCheck command forces an attachability check for all SQL Server databases protected by the Core.
Example: Perform a SQL attachability check on the most recent recovery point for the specified protected SQL server: >Start-AttachabilityCheck - protectedserver 10.10.9.120 Start-ChecksumCheck The Start-ChecksumCheck PowerShell command lets you force a checksum check of Exchange Server recovery points.
Start-EsxiExport The Start-EsxiExport PowerShell command initiates the launch of a virtual export from the selected Rapid Recovery recovery point to an ESX(i) server virtual machine.
Table 280. Start-EsxiExport command options (continued) Option Description -hostport hostusername hostpassword The virtual server port number. The user name to the virtual server host. The password to the virtual server host. Allocate specific amount of RAM on the virtual server. -ram usesourceram diskprovisio ning Optional. Allocate the same amount of RAM on the virtual server as the source protected machine. Optional. The amount of disk space that will be allocated on the virtual machine.
Usage The usage for the command is as follows: Start-HypervExport -core [host name] -user [user name] -password [password] protectedserver [[machine name] or [IP address]] -volumes [volume names] -rpn [number | numbers] | -time [time string] [-vmname [uselocalmachine] | -hostname [virtual host name] -hostport [virtual host port number] -hostusername [virtual host user name] hostpassword [virtual host password] -vmlocation [location]] [-ram [total megabytes] | usesourceram] -diskformat [VHD | VHDX] Command
Table 281. Start-HypervExport command options (continued) Option Description uselocalmach ine -hostname -hostport hostusername hostpassword -vmlocation Optional. Connect the local Hyper-V server. If this parameter is used, the following options are ignored: hostname, host port, host username, host password. The virtual server host name. The virtual server port number. The user name to the virtual server host. The password to the virtual server host.
Table 282. Start-LogTruncation command options (continued) Option Description -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password. If none are provided, then the logged-on user's credentials will be used. -password Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none are provided, then the logged-on user's credentials will be used.
Table 283. Start-MountabilityCheck command options (continued) Option Description protectedser ver Archive of recovery points for the specified machine. Optional. The sequential number of a recovery point to be exported. (You can use the GetRecoveryPoints command to obtain recovery point numbers. NOTE: If neither ‘time’ nor ‘rpn’ option is specified in this command, than the most recent recovery point will be exported. -rpn -time Optional. Determines recovery point to be selected for export.
Table 284. Start-Protect command options (continued) Option -agentname agentusernam e agentpasswor d -agentport -volumes Description Protected machine name or IP address. Log on to the server to be protected. Password to the server to be protected. Protected server port number. List of volumes to protect. Values must be enclosed in double quotes and separated by a space. Do not use trailing slashes in volume names. For example, "c:" or "d:".
Table 285. Start-ProtectCluster command options (continued) Option Description -password Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none are provided, then the logged-on user's credentials will be used. -repository Name of a repository on the Core where the protected machine's data is stored. The name must be enclosed in double quotes.
Table 286. Start-RepositoryCheck command options Option -? Description Display this help message. -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password. If none are provided, then the logged-on user's credentials will be used. -password Optional.
Table 287. Start-RestoreArchive command options (continued) Option Description -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password. If none are provided, then the logged-on user's credentials will be used. -password Optional. Password to the remote Core host machine.
Example: Archive all recovery points for all machines on the Core and store them on the local machine: >Start-RestoreArchive -path D:\work\archive -startdate 'Example 04/30/2012' –all Start-ScheduledArchive The Start-ScheduledArchive PowerShell command lets you force a Rapid Recovery scheduled archive to begin on demand, regardless of the pre-established schedule.
Start-VBExport The start-VBExport command initiates the launch of a virtual export from the selected recovery point to an Oracle VirtualBox server virtual machine.
Table 289. Start-VBExport command options (continued) Option -ram usesourceram linuxhostnam e -hostport -targetpath pathusername pathpassword accountusern ame accountpassw ord Description Allocate specific amount of RAM on the virtual server. Optional. Allocate the same amount of RAM on the virtual server as the source protected machine. Linux VirtualBox server hostname. Linux VirtualBox server port. Local or network or Linux path to the folder where the virtual machine files are to be stored.
Command Options The following table describes the options available for the Start-VirtualStandby command: Table 290. Start-VirtualStandby command options Option Description Display this help message. -? -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password.
Command Options The following table describes the options available for the Start-VMExport command: Table 291. Start-VMExport command options Option -? Description Display this help message. -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password.
Example: Export all volumes from the latest recovery point on machine 10.10.12.97 to a VM called NewVMwareVM: >Start-VBExport -protectedserver 10.10.12.97 -vmname NewVMWareVM -ram usesourceram targetpath D:/exports Stop-ActiveJobs The Stop-ActiveJobs cancels active jobs for a specified protected machine.
Example: Stop transfer job in protected machine: >Stop-ActiveJobs –protectedserver 10.10.1.76 -jobtype transfer Stop all jobs for a specific protected machine: >Stop-ActiveJobs –protectedserver 10.10.1.76 -all Suspend-Replication The Suspend-Replication command lets an administrator pause replication.
Table 293. Suspend-Replication command options (continued) Option Description -incoming Host name of the remote Core that replicates to the Core machine. Replication is suspended for all protected machines on the remote Core. -outgoing Host name of the remote target core to which data is replicating. Replication is suspended for all protected machines on the remote core. Example: Pause outgoing replication on the remote Core with the IP address: 10.10.1.
Table 294. Suspend-RepositoryActivity command options (continued) Option -all -repository Description Suspend activities for all repositories associated with this Core. The name of the repository that you want to lock. The name must be enclosed in double quotes. You can specify several space-separated repositories.
Example: Suspend multiple scheduled archives: >Suspend-ScheduledArchive -ids 799138c8-3dfc-4398-9711-1823733c2a31, 26c29bb7-b320-47f5b5a8-dffc49f50e25 Suspend-Snapshot The Suspend-Snapshot command lets an administrator pause snapshots.
Usage The usage for the command is as follows: Suspend-VirtualStandby -core [host name] -user [login] -password [password] -all | protectedserver [name(s) | IP address] Command Options The following table describes the options available for the Suspend-VirtualStandby command: Table 297. Suspend-VirtualStandby command options Option -? Description Display this help message. -core Optional. Remote Core host machine IP address (with an optional port number).
Command Options The following table describes the options available for the Suspend-VMExport command: Table 298. Suspend-VMExport command options Option Description Display this help message. -? -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password.
Table 299. Update-Repository command options (continued) Option Description -core Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. -user Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password. If none are provided, then the logged-on user's credentials will be used. -password Optional. Password to the remote Core host machine.
Table 300. Rapid Recovery PowerShell module qualifiers Qualifier -core -ProtectedServer -Mode -Volumes -User -Domain -Password -Path 430 Usage Host name of the Core. Default: Localhost Host name/IP address of the Rapid Recovery Agent.
C Extending Rapid Recovery jobs using scripting Rapid Recovery enables administrators to automate the administration and management of resources at certain occurrences through the execution of commands and scripts. The Rapid Recovery software supports the use of PowerShell scripting for Windows and Bourne Shell scripting for Linux. Core jobs are automatically created whenever you initiate operations on the Rapid Recovery Core such as replication, virtual export, or a backup snapshot.
NOTE: Place the powershell.exe.config file in the PowerShell home directory. For example, C:\WindowsPowerShell \powershell.exe.config. powershell.exe.config Testing PowerShell Scripts If you want to test the scripts you plan to run, you can do so by using the PowerShell graphical editor, powershell_is.
Table 301. Rapid Recovery PowerShell module qualifiers (continued) Qualifier -Domain -Password -Path Usage Domain to which the user defined in /User belongs. Password of the user defined in /User. For example: C:\RapidRecoveryMount. Input Parameters for PowerShell Scripting All available input parameters are used in sample scripts. The parameters are described in the following tables.
Table 303. Objects for the AgentTransferConfiguration parameter (continued) Method Description public Priority Priority { get; set; } Gets or sets the priority for transfer request. public uint GetChangedBlocksRetries { get; set; } Gets or sets the count of retries if initial retrieval of changed blocks from the agent failed. public int MaxRetries { get; set; } Gets or sets the maximum number of times a failed transfer should be retried before it is presumed failed.
Table 304. Objects for the BackgroundJobRequest parameter (continued) Method Description public bool IsNightlyJob { get; set; } Gets or sets the value indicating whether the background job is a nightly job. public Guid NightlyJobTransactionId { get; set; } Gets or sets the ID of nightly job transaction. public Guid JobId { get; set; } Gets or sets the ID of background job. public bool Force { get; set; } Gets or sets the value indicating if a job was forced.
NightlyAttachabilityJobRequest (namespace Replay.Core.Contracts.Sql) Inherits its values from the parameter, BackgroundJobRequest. Table 307. Objects for the NightlyAttachabilityJobRequest parameter Method Description public int SimultaneousJobsCount { get; set; } Gets or sets count of jobs that can be run simultaneously. RollupJobRequest (namespace Replay.Core.Contracts.Rollup) Inherits its values from the parameter, BackgroundJobRequest. TakeSnapshotResponse (namespace Replay.Agent.Contracts.
Table 309. Objects for the TransferJobRequest parameter (continued) Method Description ● MaxConcurrentStreams. The maximum number of concurrent TCP connections the core will establish to the agent for transferring data ● MaxTransferQueueDepth. The maximum number of block extents which can be queued up for writing ● MaxConcurrentWrites. The maximum number of block write operations to have outstanding on an epoch at any given time.
TransferPostscriptParameter (namespace Replay.Common.Contracts.PowerShellExecution) The following table presents the available objects for the TransferPostscript parameter. Inherits its value from the TransferScriptParameterBase parameter. Table 310. Objects for the TransferPostscript parameter Method Description public VolumeNameCollection VolumeNames (get; set; ) Gets or sets the collection of volume names for transfer. VolumeNames is a data structure that contains the following data: ● GuidName.
Table 310. Objects for the TransferPostscript parameter (continued) Method Description ● ProviderId. The GUID of the VSS provider to use for snapshots on this host. Administrators typically accept the default. public AgentTransferConfiguration TransferConfiguration { get; set; } (cont.) ● ExcludedWriterIds. Collection of VSS writer IDs which should be excluded from this snapshot. The writer ID is keyed by the name of the writer.
Table 311. Objects for the TransferScriptParameterBase parameter Method Description public AgentTransferConfiguration TransferConfiguration { get; set; } Gets or sets the transfer configuration. public AgentProtectionStorageConfigurationCommon StorageConfiguration { get; set; } Gets or sets the storage configuration. VirtualMachineLocation (namespace Replay.Common.Contracts.Virtualization) The following table presents the available objects for the VirtualMachineLocation parameter. Table 312.
Table 314. Objects for the VolumeNameCollection parameter 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).) public override int GetHashCode() Returns the hash code for this VolumeNameCollection. (Overrides Object.GetHashCode().) VolumeSnapshotInfo (namesapce Replay.Common.Contracts.
PostTransferScript.ps1 The PostTransferScript is run on the protected machine after transferring a snapshot. Sample PostTransferScript # receiving parameter from transfer job param([object] $TransferPostscriptParameter) # 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.
NOTE: There are no input parameters for the PostExportScript when used to run once on the exported protected machine after initial startup. The regular protected machine should contain this script in the PowerShell script folder as PostExportScript.ps1. Sample PostExportScript # receiving parameter from export job param([object]$ExportJobRequest) # building path to Core's Common.Contracts.dll and loading this assembly $regLM = [Microsoft.Win32.Registry]::LocalMachine $regLM = $regLM.OpenSubKey('SOFTWARE\Mi
# 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'; } else { echo 'SimultaneousJobsCount:' $RollupJobRequestObject.SimultaneousJobsCount; echo 'AgentIds:' $RollupJobRequestObject.AgentIds; echo 'IsNightlyJob:' $RollupJobRequestObject.IsNightlyJob; } $AgentsCollection = $Agents -as "System.Collections.Generic.
Sample PostNightlyJobScript # receiving parameters from Nightlyjob param([System.String]$JobClassMethod , [object]$NightlyAttachabilityJobRequest, [object] $RollupJobRequest, [object]$Agents, [object]$ChecksumCheckJobRequest, [object] $TransferJobRequest, [int]$LatestEpochSeenByCore, [object]$TakeSnapshotResponse) # building path to Core's Common.Contracts.dll and loading this assembly $regLM = [Microsoft.Win32.Registry]::LocalMachine $regLM = $regLM.OpenSubKey('SOFTWARE\Microsoft\Windows\CurrentVersion\Uni
} # 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.
To use these scripts, ensure that they reside in the /opt/apprecovery/scripts/ directory. Supported transfer and post-transfer script parameters The following parameters are supported on Linux for transfer scripts. For more information, see Sample Bourne Shell scripts on page 448.
Table 316. TransferPrescript objects (continued) Method Description ● Copy ● Full public string Key { get; set; } The Key method generates a pseudorandom (but not cryptographically secure) key, which can be used as a one-time password to authenticate transfer requests. public bool ForceBaseImage { get; set; } Gets or sets the value indicating whether the transfer was a forced base image capture.
NOTE: Protected machines use the 'exec' shell command to launch the script. You can indicate which interpreter should run the script by defining that information in the first line of the script. If you don’t specify the interpreter, the default shell interprets the script. If you choose something other than the default shell, you must ensure that the specified interpreter is available on all protected machines. The sample scripts for protected machines include: PreTransferScript.
"$curr_name-exported" > /etc/hostname exit 0 450 Extending Rapid Recovery jobs using scripting
D Rapid Recovery APIs The purpose of this section is to provide an introduction and overview of the Rapid Recovery Representational State Transfer (REST) Application Program Interfaces (APIs), their use, and their function. The Rapid Recovery Web Service APIs are RESTful and let you automate and customize certain functions and tasks within the Rapid Recovery software solution to assist you with meeting your business objectives.
Table 318. Components included in the SDK archive (continued) Folder name Contents Description directory. The resulting page shows information for general REST service operations, including methods and descriptions. 2. Open the Core.Client HTML file in a web browser to view detailed C# information. When you click any hyperlinked service contract (class), the browser opens information in the Core.Contracts/doc/ directory.
E About Dell Dell listens to customers and delivers worldwide innovative technology, business solutions, and services they trust and value. For more information, visit http://software.dell.com. Contacting Dell For sales or other inquiries, visit http://software.dell.com/company/contact-us.aspx or call + 1-949-754-8000. Technical support resources Technical support is available to customers who have purchased Dell software with a valid maintenance contract and to customers who have trial versions.
Glossary Agent The Rapid Recovery Agent is software installed on a physical or virtual machine that lets it be added to protection in the Rapid Recovery Core. Rapid Recovery Rapid Recovery sets a new standard for unified data protection by combining backup, replication, and recovery in a single solution that is engineered to be the fastest and most reliable backup for protecting virtual machines (VM), as well as physical and cloud environments.
encryption Data is encrypted with the intent that it is only accessible to authorized users who have the appropriate decryption key. Data is encrypted using 256-bit AES in Cipher Block Chaining (CBC) mode. In CBC, each block of data is XORed with the previous ciphertext block before being encrypted, this way each new ciphertext block depends on all preceding plaintext blocks. A passphrase is used as an initialization vector. event An event is a process that is logged by the Core.
Object File System The Rapid Recovery Scalable Object Store is an object file system component. It treats all data blocks, from which snapshots are derived, as objects. It stores, retrieves, maintains, and replicates these objects. It is designed to deliver scalable input and output (I/O) performance in tandem with global data deduplication, encryption, and retention management. The Object File System interfaces directly with industry standard storage technologies.
Table 320. Prohibited phrases (continued) Phrase General use Prohibited from lpt1, lpt2... through lpt9 line print terminal port machine display name, encryption key, repository, path description protected machine A protected machine—sometimes called an "agent"— is a physical computer or virtual machine that is protected in the Rapid Recovery Core. Backup data is transmitted from the protected machine to the repository specified in the Core using a predefined protection interval.
rollup The rollup process is an internal nightly maintenance procedure that enforces the retention policy by collapsing and eliminating dated recovery points. Rapid Recovery reduces rollup to metadata operations only. seeding In replication, the initial transfer of deduplicated base images and incremental snapshots of protected agents, which can add up to hundreds or thousands of gigabytes of data.
Universal Recovery Rapid Recovery Universal Recovery technology provides unlimited machine restoration flexibility. It enables you to perform monolithic recovery to- and from- any physical or virtual platform of your choice as well as incremental recovery updates to virtual machines from any physical or virtual source. It also lets you perform application-level, item-level, and object-level recovery of individual files, folders, email, calendar items, databases, and applications.
