The Stop-ActiveJobs
cmdlet cancels active jobs for a specified protected machine.
The usage for the command is as follows:
Stop-ActiveJobs [-protectedserver [machine name | IP address] | -core [host name]] -user [user name] -password [password] -jobtype [jobtype]
The following table describes the options available for the Stop-ActiveJobs
command:
Option | Description |
---|---|
-? |
Display this help message. |
-all |
Select and cancel events of the specified type for 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. |
-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. |
-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. |
-protectedserver |
Determines protected machine on which jobs should be canceled. |
-jobtype |
Optional. Specifies job type filter. Available values are: ‘transfer’ (data transfer), ‘repository’ (repository maintenance), ‘replication’ (local and remote replications), ‘backup’ 9backup and restore), ‘bootcdbuilder’ (create boot CDs), ‘diagnostics’(upload logs), ‘exchange’ (Exchange Server files check), ‘export (recovery point export), ‘pushinstall’ (deploy Agent software to protected machines), ‘rollback’ (restore data from recovery point), ‘rollup’ (recovery point rollup’s), ‘sqlattach’ (agent attachability checks), ‘mount’ (not repository). By default, all jobs of the specified type are canceled. |
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
Use the Stop-CoreService
cmdlet to gracefully stop the Core service on a Core machine.
The usage for the command is as follows:
Stop-CoreService -core [host name] -user [user name] -password [password] -cancelactivejobs [true | false] -wait [time in seconds]
The following table describes the options available for the Stop-CoreService
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 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. |
-cancelactivejobs |
Optional. Use this option to cancel all active jobs on the Core. The default setting is "false." |
-wait |
Optional. This option indicates that the command should wait until the Core service is fully stopped for the specified period of time in seconds before canceling active jobs. |
Stop the Core service:
>Stop-CoreService -core 10.10.127.42 -user admin -password 676df#df -cancelactivejobs true -wait 600
The Suspend-Replication
cmdlet lets an administrator pause replication. Once paused, replication does not resume unless you explicitly run cmdlet Resume-Replication or resume from the Rapid Recovery Core Console.
A user can pause replication in three ways:
-
outgoing parameter
)
The administrator must specify the remote machine name with outgoing replication pairing to pause outgoing replication on the source Core.
>Suspend-replication -outgoing 10.10.12.10
-
protectedserver
parameter) >Suspend-replication -protectedserver 10.10.12.97
-
incoming parameter
)
If the local Core is a target Core, the administrator can pause replication by specifying the source Core using the –incoming parameter.
The following table describes the options available for the Suspend-Replication
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. |
-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. |
-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. |
Pause all replication (incoming and outgoing) for the local Core:
>Suspend-replication –incoming all -outgoing all
Pause outgoing replication on the remote Core with the IP address: 10.10.1.15, for the single protected machine with the IP address: 10.10.1.76:
>Suspend-replication –core 10.10.1.15 –protectedserver 10.10.1.76
Pause outgoing replication from the local Core to remote target with the IP address: 10.10.1.63 for all protected machines:
>Suspend-replication –outgoing 10.10.1.63
Pause incoming replication from 10.10.1.82 on the remote Core with the IP address: 10.10.1.15 (Administrator is able to pause incoming replication only for whole machine):
>Suspend-replication –core 10.10.1.15 –incoming 10.10.1.82
The Suspend-ScheduledArchive
PowerShell cmdlet lets you pause a scheduled archive. This command prevents the archive from occurring as scheduled until you reactivate it using Remove-ScheduledArchive or from the Rapid Recovery Core Console .
The usage for the command is as follows:
Suspend-ScheduledArchive -core [host name] -user [login] -password [password] -all -ids [id | id1 id2]
The following table describes the options available for the Suspend-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. |
-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. |
-all |
Pauses all scheduled archives. |
-id or -ids |
The identification number or numbers of scheduled archives to suspend. If suspending more than one scheduled archive, separate each with a comma. Obtain IDs using command Get-ScheduledArchives |
Suspend multiple scheduled archives:
>Suspend-ScheduledArchive -ids 799138c8-3dfc-4398-9711-1823733c2a31, 26c29bb7-b320-47f5-b5a8-dffc49f50e25
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center