The New-Base command forces a new base image resulting in a data transfer for the current protected machine. When you force a base image, 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-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 123: New-Base command options
-? |
Display this help message. |
-all |
Base image for all agents. |
-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. |
-protectedserver |
Force for the current protected machine’s name. |
-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. |
Example:
Force base image for all protected machines:
>New-Base –all
This command lets you create a bare metal restore (BMR) boot CD without using the Rapid Recovery Core Console.
Usage
The usage for the command is as follows:
New-BootCD -core [host name] -user [user name] -password [password] -ip [IP address] -mask [mask] -defaultgateway [defaultgateway] -dnsserver [dnsserver] -vncpassword [vncpassword] -vncport [vncport] -isofilepath [destination for the boot image] -driverspath [drivers path]
Command Options
The following table describes the options available for the New-BootCD command:
Table 124: New-BootCD command options
-? |
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. |
-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. |
-defaultgateway |
Optional. This option specifies the default gateway of the target BMR machine. By default, it generates automatically. |
-dnsserver |
Optional. This option specifies the DNS server for the target BMR machine. By default, it generates automatically. |
-vncpassword |
Optional. This option specifies the user password for an existing UltraVNC account. By default, this option is empty. |
-vncport |
Optional. This option specifies the port to use for UltraVNC. You can change it only if you used the -vncpassword option. By default, the port is 5900. |
-isofilepath |
Optional. This option specifies the patch to the boot CD file. The default path is C:\ProgramData\AppRecovery\Boot CDs. |
-driverspath |
Optional. This option specifies the path to the archive of drivers. |
Example:
Create a boot CD:
>New-BootCD -ip 192.168.20.188 -mask 255.255.255.0 -defaultgateway 192.168.20.2 -dnsserver 192.168.20.2 -isofilepath D:\bcd\newbcd3.iso
The New-CloudAccount command lets you add a new cloud account to the Rapid Recovery Core.
Usage
The usage for the command is as follows:
New-CloudAccount -core [host name] -user [login] -password [password] -displayname [display name] -type [cloud acco
unt type] -username [user name] - key [secret key] -region [region] - tenantid [tenant Id] -authurl [authorization
url]
Command Options
The following table describes the options available for the New-CloudAccount command:
Table 125: New-CloudAccount command options
-? |
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. 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. |
-displayname |
The name of the cloud account to display. |
-type |
The type of cloud account you want to add. Supported values include:
- amazon
- openstack
- rackspace
- windowsazure
- "windows azure"
- azure
|
-username |
The user name for the cloud account that you want to add. It is used in the authentication process. This property resolves as "Access Key" for Amazon™ cloud, "User Name" for Rackspace and OpenStack, and "Storage Account Name" for Windows Azure cloud accounts. |
-key |
The key for the cloud account you want to add. It is used in the authentication process. This property resolves as "Secret Key" for Amazon™ cloud, "Api Key" for Rackspace and OpenStack, and "Access Key" for a Windows Azure cloud accounts. |
-region |
The region of the cloud account that you want to add. This property is required only for RackSpace and OpenStack cloud accounts. |
-tenantid |
The identifier that is used in the authentication process of an OpenStack cloud account. This option is required only for OpenStack cloud accounts. |
-authurl |
The URL that is used in the authentication process of an OpenStack cloud account. This option is required only for OpenStack cloud accounts. |
Example:
Create a new Amazon™ S3 cloud account named "Amazon S3 Account" with the access key "akey" and the secret key "skey."
>New-CloudAccount -displayname "Amazon S3 Account" -type Amazon -username akey -key skey
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 126: New-EncryptionKey command options
-? |
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. 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 encryption key that you want to create. |
-passphrase |
The passphrase to the encryption key that you want to create. |
-comment |
Optional. The description of the encryption key. |
Example:
Create an encryption key on the local Core:
>New-EncryptionKey –name EncryptionKey1 -passphrase 123456
