Quest has been named as an ASP "Ten Best Web Support Sites" award winner. Learn more.

Rapid Recovery 6.0.2 - User Guide

*** Legend Introduction to Dell Data Protection | Rapid Recovery Understanding the Rapid Recovery Core Console Working with repositories Managing Rapid Recovery Core settings Using custom groups Working with encryption keys Protecting machines using the Rapid Recovery Core Working with Microsoft Exchange and SQL Servers Protecting server clusters Exporting protected data to virtual machines Managing protected machines Understanding replication Managing events Generating and viewing reports Restoring data Understanding bare metal restore for Windows machines Retention and archiving Managing cloud accounts Working with Linux machines Understanding the Local Mount Utility Central Management Console Understanding the Rapid Recovery Command Line Management utility Understanding the Rapid Recovery PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Extending Rapid Recovery jobs using scripting Rapid Recovery APIs Glossary

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.

Usage

The usage for the command is as follows:

/archive -core [host name] -user [user name] -password [password] -all | -protectedserver [name | IP address] -path [location] -startdate [time string] -enddate [time string] -archiveusername [name] -archivepassword [password] -comment [text]

Command Options

The following table describes the options available for the archive command:

Table 1. Archive 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. 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.
-all
Archive all recovery points for all protected machines on the Core.
-protectedserver
Protected machine with recovery points to be archived. You can specify several machine names enclosed in double quotes and separated by spaces.
-path
Path where archived data should be placed; for example: d:\work\archive or network path \\servername\sharename.
-startdate
Start date for selecting recovery points by creation date. The value must be enclosed in double quotes; for example, "04/30/2012 02:55 PM".
-enddate
Optional. End date for selecting recovery points by creation date. Value must be enclosed in double quotes; for example, "05/31/2012 11:00 AM". The current time system is used by default.
-archiveusername
Optional. User name for the remote machine. Required for network path only.
-archivepassword
Optional. Password to the remote machine. Required for network path only.
-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 protected machines:

>cmdutil /archive -core 10.10.10.10 -user administrator -password 23WE@#$sdd -protectedserver "10.20.30.40" "20.20.10.1" -path d:\work\archive -startdate "04/30/2012 02:55 PM" -enddate "05/31/2012 11:00 AM"

Was this topic helpful?

[Select Rating]



CancelActiveJobs

Use the cancelactivejobs command to cancel the execution of all in-progress jobs of a specific type, such as transfer or replication.

Usage

The usage for the command is as follows:

/cancelactivejobs -core [host name] -user [user name] -password [password] -jobtype [job type filter]

Command Options

The following table describes the options available for the cancelactivejobs command:

Table 1. CancelActiveJobs 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. 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 must also provide a user name. If none is provided, the logged-in user’s credentials are used.
-protectedserver
Determines the protected machine on which the jobs should be canceled.
-all
Select and cancel events of specified type for all protected servers.
-jobtype
Optional. Specifies job type filter. Available values are:
  • ‘transfer’ (data transfer)
  • ‘repository’ (repository maintenance)
  • ‘replication’ (local and remote replications)
  • ‘backup’ (backup and restore)
  • ‘bootcdbuilder’ (create boot CDs)
  • ‘diagnostics’ (upload logs)
  • ‘exchange’ (Exchange Server files check)
  • ‘export’ (recovery point export)
  • ‘pushinstall’ (deploy agents)
  • ‘restore’ (recovery point restore)
  • ‘rollup’ (recovery point rollups)
  • ‘sqlattach’ (agent attachability checks)
  • ‘mount’ (mount repository)

By default, all jobs of the specified type are canceled.

Example:

Cancel all transfer jobs on Core 10.10.10.10:

>cmdutil /cancelactivejobs -core 10.10.10.10:8006 -user administrator -password 23WE@#$sdd -jobtype transfer

Was this topic helpful?

[Select Rating]



CheckRepository

You can use the CheckRepository command to verify the integrity of an existing DVM repository created in AppAssure Core or Rapid Recovery Core.

Usage

The usage for the command is as follows:

/checkrepository -repository [repository name] | -all [check all repositories] -core [host name] -user [user name] -password [password] name] -force

Command Options

The following table describes the options available for the CheckRepository command:

Table 1. CheckRepository 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. 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.
-all
Optional. This option checks all DVM repositories associated with the Core.
-repository
The name of the DVM repository.
-force
Optional. This option performs the check without your confirmation.

Example:

Start checking the DVM repository:

>cmdutil /checkrepository -repository "Repository1" -core 10.10.10.10 -user administrator -password 23WE@#$sdd

Was this topic helpful?

[Select Rating]



CreateArchiveRepository

When you create an archive repository, you create a destination for the contents of a scheduled archive. This feature lets you mount an archived recovery point and restore a machine without importing the archive.

Usage

The usage for the command is as follows:

/createarchiverepository -core [host name] -user [user name] -password [password] name] -name [archive repository name] -path [path to the archive] -archiveusernamme [network user name] -archivepassword [network password] -cloudaccountname [name of the cloud account] -cloudcontainer [name of the cloud container]

Command Options

The following table describes the options available for the CreateArchiveRepository command:

Table 1. CreateArchiveRepository 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. 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.
-name
Required. The name of the archive repository.
-path
The path to the existing archive. It can be a local, network, or cloud location. For example: d:\work\archive or \\servername\sharename.
-archiveusername
Optional. This option is the login to the remote machine. It is required for a network path only.
-archivepassword
Optional. This option is the password for the remote machine. It is only required for a network path only.
-cloudaccountname
Optional. This option is the display name for an existing cloud account. It is required for a cloud path only.
-cloudcontainer
Optional. The cloud container is where the archive is located. It is required for a cloud path only.

Examples:

Create an archive repository with the name "NewArchive:"

>cmdutil /createarchiverepository -name NewArchive -core 10.10.10.10 -user administrator -password 23WE@#$sdd -path d:\work\archive

Additionally, if an archive contains more than one location, then the command should include paths for all of the segments ordered from 1 to N, where N equals the number of segments.

Create an archive repository with the name "NewSegmentArchive:"

>cmdutil /createarchiverepository -name NewSegmentArchive -path1 \\RemmoteServer1\Share\Archive\Segment1 - archiveusername1 Administrator -archivepassword1 23WE@#$sdd -path2 Archives\NewSegment -cloudcontainer2 ArchiveContainer -cloudaccountname AmazonS3Local - path3 d:\work\archive\Third

Was this topic helpful?

[Select Rating]



Related Documents