The New-Repository command creates a new DVM repository in the Rapid Recovery Core. The size specified must be between 250MB and 16TB.
Usage
The usage for the command is as follows:
New-Repository | –name [name] -size [size] -datapath [location] -metadatapath [location]
Command Options
The following table describes the options available for the New-Repository command:
Table 131: New-Repository 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. |
-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. |
-name |
Repository name. |
-size |
Size of repository extent. Available units are: b, Kb, MB, GB, TB, PB. |
-datapath |
For local location only. Determines data path of repository extent. |
-metadatapath |
For local location only. Determines metadata path of repository extent. |
-uncpath |
For share location only. Determines data and metadata paths of repository extent. |
-shareusername |
For share location only. Determines login to share location. |
-sharepassword |
For share location only. Determines password to share location. |
-comment |
Optional. Description of repository. |
-concurrent
Operations |
Optional. Maximum number of operations that can be pending at one time. Value by default: 64. |
Example:
Create new DVM repository of minimum size in local drive E:
>New-Repository –name Repository2 -size 250Mb -datapath e:\Repository\Data -metadatapath e:\Repository\Metadata
The New-ScheduledArchive command lets you use PowerShell to make changes to an existing scheduled archive.
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 132: New-ScheduledArchive 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. |
-protectedserver |
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. |
-all |
Archive recovery points for all protected machines. |
-path |
The path to where to save the archived data. For example:
- Local machine: "d:\work\archive"
- Network path: "\\servername\sharename"
- Folder in a cloud account: "Folder Name"
Note: The number of symbols should not be greater than 100 for local and network locations, and should not be greater than 150 for a cloud location. |
-archiveusername |
Optional. The user name for logging in to the remote machine. It is required for a network path only. |
-archivepassword |
Optional. The password for logging in to the remote machine. It is required for a network path only. |
-cloudaccountname |
Optional. Use only for cloud archiving. The name of the cloud account where you want to save the archive. |
-cloudcontainer |
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. |
-recycleaction |
The type of recycle action. Specified by using one of the following four values:
- "replacethiscore" - Overwrites any pre-existing archived data pertaining to this Core, but leaves the data for other Cores intact.
- "erasecompletely" - Clears all archived data from the directory before writing the new archive.
- "incremental" - Lets you add recovery points to an existing archive. It compares recovery points to avoid duplicating data that already exists in the archive.
|
-scheduletype |
Type of schedule interval. Specified the option with one of the following four values:
- "daily" - For a daily automatically created archive.
- "weekly" - For a weekly automatically created archive. You must specify the "-dayofweek" parameter.
- "monthly" - For a monthly automatically created archive. You must specify the "-dayofmonth" parameter. If a month does not have the day specified—for example, "31"—then the archive will not occur for that month.
- "lastdayofmonth" - For automatically creating an archive on the last day of each month.
|
-dayofweek |
Use only for the "weekly" option of the "-scheduletype" parameter. The day of the week on which to automatically create the archive (for example, "Monday"). |
-dayofmonth |
Use only for the "month" option of the "-scheduletype" parameter. The day (number) of the month on which to automatically create the archive (for example, "15"). |
-time |
The hour of the day when you want to create an archive. |
-initialpause |
Optional. Specify this option if you want to initially pause archiving after you configure the archiving schedule. |
Examples:
Archive all recovery points with creation dates starting from 04/30/2012 02:55 PM for all machines on the Core, and replace pre-existing archived data pertaining to this Core:
>New-ScheduledArchive -core 10.10.10.10 -user administrator -password 23WE@#$sdd -path "d:\work\archive" -s
tartdate "04/30/2012 02:55 PM" -all -recycleaction replacethiscore
Archive recovery points that fall within a date range for two protected machines, and clear all archived data from the directory before writing the new archive:
>New-ScheduledArchive -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" -recycleaction erasecompletely
Create an incremental archive for all recovery points with creation dates starting from 04/30/2012 02:55 PM for all machines on the Core to the cloud account with the name "Amazon S3" and a container named "Container":
>New-ScheduledArchive -core 10.10.10.10 -user administrator -password 23WE@#$sdd -path "ArchiveOnCloud" -cloudaccountname "Amazon S3" -cloudcontainer "Container" -startdate "04/30/2012 02:55 PM" -all -recycleaction incremental
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-Snapshot [-all] | -protectedserver [machine name]] -core [host name] -user [user name] -password [password]
Command Options
The following table describes the options available for the New-Snapshot command:
Table 133: New-Snapshot command options
-? |
Display this help message. |
-all |
Force all protected machines. |
-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 a snapshot for all protected machines:
>New-Snapshot -all
The New-VBVirtualStandby command lets you use PowerShell to create a new virtual export to a VirtualBox virtual machine (VM).
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 134: New-VBVirtualStandby 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. |
-protectedserver |
Show jobs for a specific protected machine, indicated by IP address. |
-volumes |
Optional. List the volume names you want to export. If not specified, all volumes in the recovery point(s) are exported. Values must be enclosed in double quotes and separated by space; for example, "c:", "d:".
Note: Do not use trailing slashes in volume names. |
-vmname |
The Microsoft Windows name of the virtual machine. |
-ram |
Allocate a specific amount of RAM on the virtual server. |
-usesourceram |
Optional. Allocate the same amount of RAM on the virtual server that the source protected machine has. |
-linuxhostname |
The Linux VirtualBox server host name. |
-hostport |
The Linux VirtualBox server port. |
-targetpath |
The local, network, or Linux path to the folder where you want to store the virtual machine files. |
-pathusername |
The user name for logging in to the network machine. It is only required when you specify a network location for the target path. |
-pathpassword |
The password for logging in to the network machine. It is only required when you specify a network location for the target path. |
-accountusername |
Optional. You can specify a user account with which to register the exported virtual machine. It is the user name for logging in to the user account. Use this option for a local or network machine only. |
-accountpassword |
Optional. You can specify a user account with which to register the exported virtual machine. It is the password for logging in to the user account. Use this option for a local or network machine only. |
-initialexport |
Optional. Specify this option if you need to start an initial on-demand virtual machine export after configuring the virtual standby. |
Example:
Create a VirtualBox virtual standby machine named ExportedMachine1 in a specified location:
>New-VBVirtualStandby -protectedserver 10.10.10.4 -volumes C:\ -vmname ExportedMachine1 -usesourceram -targetpath I:\VMExport
