The Set-AgentMetadataCredentials
command sets the metadata credentials for a specified protected machine.
The usage for the command is as follows:
Set-AgentMetadataCredentials -core [host name] -user [user name] -password [password] -protectedserver [name | IP address] -target [default | SQL | Exchange] -metadatausername [user name] -metadatapassword [password] -sqlinstancename [SQL instance name] -usewindowsauthentication
The following table describes the options available for the Set-AgentMetadataCredentials
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. |
-target |
Optional. The type of metadata, such as SQL, Exchange, or default. |
-metadatausername |
Optional. The metadata-related login. |
-metadatapassword |
Optional. The metadata-related password. |
-sqlinstancename |
Optional. The specific SQL instance name. Use this option in conjunction with the -target "sql." |
-usewindowsauthentication |
Optional. Use this option if your SQL credentials are also used for Windows authentication. |
Set credentials for Exchange metadata:
>Set-AgentMetadataCredentials -core 10.10.10.10 -user administrator -password -23WE@#$sdd -protectedserver 10.10.20.20 -target exchange -metadatausername administrator -metadatapassword 123#
The Set-CredentialsVaultAccount
cmdlet lets you set up a Credentials Vault account for a specified Core.
The usage for the command is as follows:
Set-CredentialsVaultAccount [-AccountId <string>] [-AccountUserName <string>] [-AccountPassword <string>] [-Description <string>] [-User <string>] [-Core <string>] [-Password <string>] [<CommonParameters>]
The following table describes the options available for the Set-CredentialsVaultAccount
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. |
-accountid |
Required. The identifier of the Credentials Vault account that you want to remove. |
-accountusername |
Required. The user name for logging in to the Credentials Vault account that you want to set up. |
-accountid |
Required. The identifier of the Credentials Vault account that you want to remove. |
-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. |
Establish a Credentials Vault account for the Core:
>Set-CredentialsVaultAccount -accountid CVaccount1 -accountusername user1 -accountpassword password1 -core 10.10.10.10
The usage for the command when creating a DVM repository is as follows:
Set-DedupCacheConfiguration -core [host name] -user [user name] -password [password] -primary [cache location] -secondary [cache location] -metadata [metadata location] -size [cache size] -restoredefault
The following table describes the options available for the Set-DedupCacheConfiguration
command:
Option | Description |
---|---|
-? |
Display help on the command. |
-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. |
-primary |
Optional. Primary cache location. |
-secondary |
Optional. Secondary cache location. |
-metadata |
Optional. Metadata cache location. |
-size |
Optional. Deduplication cache size in GB. |
-restoredefault |
Optional. Restore to default deduplication cache configuration. If this parameter is specified, all other parameters are ignored. |
Set primary deduplication cache location and deduplication cache size:
>Set-DedupCacheConfiguration -primary D:\primary -size 6
Set secondary and metadata deduplication location:
>Set-DedupCacheConfiguration -secondary D:\secondary -metadata D:\metadata
Restore default deduplication configuration:
>Set-DedupCacheConfiguration -restoredefault
The Set-License
PowerShell cmdlet lets you change the license associated with your Rapid Recovery Core. This is useful, for example, when moving from a trial license to a subscription or perpetual license.
The usage for the command is as follows:
Set-License -core [host name] -user [user name] -password [password] -licensekey [license key] -licensepath [license file path] -licensenumber [license number] -email [email address]
The following table describes the options available for the Set-License
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. |
-licensekey |
Optional. A 30-character key comprising six groups of five alphanumeric characters, each separate by a hyphen. Use this key when a license file is not available. |
-licensepath |
Optional. The path to the file that ends with the .lic extension. If a license file is available, you can use this option instead of the -licensekey . |
-licensenumber |
Optional. You may have received this nine-digit license number in an order confirmation email. If you provide this number, use the email address that received it for verification. |
Optional. If you use the -licensenumber , you must include the email address that received it for verification. |
Change the license key associated with this Core to JL09F-89FSD-6THFS-DSE34-KS3D5-65DF2:
>Set-License -core 10.10.10.10 -user admin -password 676df#df -licensekey JL09F-89FSD-6THFS-DSE34-KS3D5-65DF2
Change the license key associated with this Core to the key contained in the license file:
>Set-License -core 10.10.10.10 -user admin -password 676df#df -licensepath C:\MyLicenseFile.lic
Change the license number associated with this Core to 111-111-111 using john.doe@example.com to verify the license:
>Set-License -core 10.10.10.10 -user admin -password 676df#df -licensenumber 111-111-111 -email john.doe@example.com
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center