The New-ScheduledArchive
cmdlet lets you create a new scheduled archive for your Rapid Recovery Core.
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]
The following table describes the options available for the New-ScheduledArchive
command:
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 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 must also provide a user name.
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:
| ||
-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 in which 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 values:
| ||
-scheduletype |
Type of schedule interval. Specified the option with one of the following four values:
| ||
-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. | ||
-useglacierfordatafilea |
Optional. Specify this option only when archiving to Amazon S3 Glacier. |
Archive all recovery points with creation dates starting from 04/30/2019 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 -protectedserver 10.20.30.40 -path "d:\work\archive" -startdate "04/30/2019 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/2019 02:55 PM" -enddate "05/31/2019 11:00 AM" -recycleaction erasecompletely
Create an incremental archive for all recovery points with creation dates starting from 04/30/2019 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/2019 02:55 PM" -all -recycleaction incremental
The New-Snapshot
cmdlet forces a snapshot resulting in a data transfer for the current protected machine. When you force a snapshot, the transfer starts immediately or is added to the queue. Only the data that has changed from a previous recovery point is transferred. If there is no previous recovery point, all data on the protected volumes is transferred.
The usage for the command is as follows:
New-Snapshot [-all] | -protectedserver [machine name]] -core [host name] -user [user name] -password [password]
The following table describes the options available for the New-Snapshot
command:
Option | Description |
---|---|
-? |
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. |
Force a snapshot for all protected machines:
>New-Snapshot -all
The New-VBVirtualStandby
cmdlet lets you use PowerShell to create a new virtual export to an Oracle VM VirtualBox virtual machine.
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
The following table describes the options available for the New-VBVirtualStandby
command:
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. 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:".
| ||
-vmname |
The Microsoft Windows name of the Oracle VM VirtualBox 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 Oracle VM VirtualBox server host name. | ||
-hostport |
The Linux Oracle VM 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. |
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
The New-VMVirtualStandby
PowerShell command lets you create a new VMware Workstation virtual standby machine using Rapid Recovery.
The usage for the command is as follows:
New-VMVirtualStandby -core [host name] -user [login] -password [password] -protectedserver [name | IP address] -volumes [volumes names] -vmname [virtual machine name] [-ram [total megabytes] | -usesourceram] -targetpath [location] -pathusername [login] -pathpassword [password] -initialexport
The following table describes the options available for the New-VMVirtualStandby
command:
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. 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 you use the value all or use no value, then all volumes in the recovery points are exported. Values must be enclosed in double quotes and separated by a space.
| ||
-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. | ||
-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. | ||
-initialexport |
Optional. Specify this option if you need to start an initial on-demand virtual machine export after configuring the virtual standby. |
Create a new VMware Workstation virtual standby:
>New-VMVirtualStandby -protectedserver 10.10.10.4 -volumes C:\ -vmname ExportedMachine1 -usesourceram -targetpath I:\VMExport
Script pauses, requiring user to specify an index number for the appropriate workstation. Enter the index number for the script to complete (in this case, 2). Example continues:
2 Verify location ... Virtual Standby successfully configured PS C:\Users\Administrator>
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center