The Set-OracleMetadataCredentials command lets you set the metadata credentials for a specified Oracle instance.
The usage for the command is as follows:
Set-OracleMetadataCredentials -core [host name] -user [user name] -password [password] -protectedserver [name | IP address] -instancename [Oracle instance SID] -connectiontype [-basic | TNS] -hostname [host name | IP address] -port [port number] [-usesid] -instanceservicename [service name] -tnsnetworkalias [TNS alias] [-usewindowsauthentication] -oracleusername [user name] -oraclepassword [password] [-edit]
The following table describes the options available for the Set-OracleMetadataCredentials 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. 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. |
-protectedserver |
The name or IP address of the protected machine. |
-instancename |
The Oracle SID from which you want to fetch metadata. |
-connectiontype |
Use this option to identify the connection type. It must be represented by either basic or TNS. |
-hostname |
Optional. The name of the Oracle host. Use it for the basic connection type. |
-port |
Optional. A port number. Use it for the basic connection type. |
-usesid |
Optional. This option uses the -instancename to identify the Oracle instance. Use it for the basic connection type. |
-instanceservicename |
Optional. The Oracle instance service name. Use it when the -usesid is not specified and for the basic connection type. |
-tnsnetworkalias |
Optional. Use this option to identify the TNS network alias when using the TNS connection type. |
-usewindowsauthentication |
Optional. This option lets you authenticate with your Windows credentials. |
-oracleusername |
Optional. The user name for the Oracle instance. |
-oraclepassword |
Optional. The password for the Oracle instance. |
-edit |
Optional. This option lets you omit any number of options. |
Set the metadata credentials for the ORCL instance on a protected server using the basic connection type:
>Set-OracleMetadataCredentials -core 10.10.127.42 -user admin -password -676df#df -protectedserver 10.10.34.88 -instancename ORCL -connectiontype basic -hostname localhost -port 1521 -usesid -oracleusername User-ORA -oraclepassword 676df#df
Set the metadata credentials for the ORCL instance on a protected server using the TNS connection type and Windows authentication:
>Set-OracleMetadataCredentials -core 10.10.127.42 -user admin -password -676df#df -protectedserver 10.10.34.88 -instancename ORCL -connectiontype TNS -tnsnetworkalias ORCL_ALIAS -usewindowsauthentication
Use the Set-ReplicationResponse command to manage pending replication requests.
The usage for the command is as follows:
Set-ReplicationResponse -core [host name] -user [user name] -password [password] -id [replication ID] -accept | -deny | -ignore -protectedserver [name | IP address]
The following table describes the options available for the Set-ReplicationResponse 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 |
-id |
The identifier for the replication job or pending replication request. It can be a remote Core ID, host name, customer ID, email address, or pending replication request ID. |
-accept |
Accepts the replication request. |
-deny |
Denies the replication request. |
-ignore |
Ignores the replication request. |
-protectedserver |
When responding to a replication request, use this option to apply your response to list of protected servers with a repository name or ID. Use the parameter "all" to apply response to all requested machines. |
Accept a pending replication request for one protected machines:
>Set-ReplicationResponse -id customer@email.address -accepted -protectedserver 10.10.1.1 Repository1 10.10.1.2 Repository2 -responsecomment A response comment
Deny a pending replication request:
>Set-ReplicationResponse -id customer@email.address -deny
Businesses often use long-term storage to archive both compliant and non-compliant data.
The archive feature in Rapid Recovery supports the ability for an organization to extend retention of data for compliance or other reasons. You can save an archive to a local storage or network location using the Start-Archive cmdlet, which requires you to specify the archive storage location path and connection credentials.
oranizations the 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 command and credentials.
Businesses often use long-term storage to archive both compliant and non-compliant data. The archive feature in Rapid Recovery is used to support the 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 command and credentials.
The usage for the command is as follows:
Start-Archive -path -startdate -enddate [-all] | -protectedserver [machine name] or [IP]] -core [host name] -user [user name] -password [password]
The following table describes the options available for the Start-Archive command:
| Option | Description |
|---|---|
-? |
Display this help message. |
-path |
Location path. Example path: ‘D:\work\archive’ or network path: ‘\\servername\sharename’. |
-all |
Archive recovery points for all machines on the Core. |
-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. |
-startdate |
Start date of the date range for the created recovery points. Should be in the format specified by the OS on the current PC. |
-enddate |
End date of the date range. Defaults to the current time. |
-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 |
Archive recovery points for the specified 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. |
-archiveusername |
Optional. Required for network path only. |
-archivepassword |
Optional. Required for network path only. |
-comment |
Optional. Example: -comment 'Before install new application'. |
Archive all recovery points for all machines on the Core:
>Start-Archive -path D:\work\archive -startdate 'Example 04/30/2012' –all
The Start-AttachabilityCheck cmdlet forces an attachability check for all SQL Server databases protected by the Core.
The usage for the command is as follows:
Start-AttachabilityCheck -core [host name] -user [username] - password [password] - protectedserver [machine name | IP address] -rpn [number | numbers] | -time [time string]
The following table describes the options available for the Start-AttachabilityCheck 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 user name. If none are provided, then the logged-on user's credentials will be used. |
-protectedserver |
The protected machine on which to perform the SQL attachability check. |
-rpn |
Optional. The sequential number of a recovery point on which to perform the SQL attachability check.
You can use the Note: If neither ‘time’ nor ‘rpn’ option is specified in this command, than the most recent recovery point is used for the attachability check. |
-time |
Optional. Determines recovery point to be selected for SQL attachability check. You need to specify exact time in the format “MM/DD/YYYY hh:mm tt” (for example: “04/24/2015 09:00 AM”).” Specify date time values of the time zone set on your local machine.
Note: If neither ‘time’ nor ‘rpn’ option is specified in this command, than the most recent recovery point will be exported. |
Perform a SQL attachability check on the most recent recovery point for the specified protected SQL server:
>Start-AttachabilityCheck - protectedserver 10.10.9.120© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center