Ost --delete_client --name Page 57
Page 57
Result
Enter new password for backup_user:
Re-type new password:
OST password updated successfully.
ost --update --opdup_encryption
Description
Sets the type of encryption that will be used by OST initiated opdup replication.
Syntax
ost --update --opdup_encryption aes128
Result
OST OPDUP encryption updated to aes128
ost --delete_client --name
Description
The command deletes the OST client and any edits that have been made to its default values. The next time a connection
is established between the client and the DR Series system, the default OST connection settings will be used. Deleting
an OST client using this CLI command does not affect data already written to the DR Series system.
Syntax
ost --delete_client --name acme-99
Result
Successfully deleted OST client acme-99.
ost --update_client --name
Description
Updates the attributes of an OST client (OST client name and mode). The OST client modes are auto, passthrough, and
dedupe. If an OST client has four or more CPU cores, it is considered to be dedupe-capable. However, the OST client
operating mode depends upon how it is configured in the DR Series system.
•
Auto — Sets the mode to dedupe or passthrough as determined by the media server. The mode used is based on
how many cores the OST client has and whether it is 32–bit or 64–bit. If the OST client has four or more CPU cores, it
will run in the dedupe mode. If the OST client has less than four CPU cores, it will run in passthrough mode. For
details, see the table below.
•
Passthrough — The OST client passes all data to the DR Series system for dedupe processing. This is also known as
“appliance-side dedupe”.
•
Dedupe — The OST client processes hashing on the data. This is also known as “source-side dedupe” and is the
default mode. Keep in mind that the OST client must be dedupe-capable (four or more CPU cores) in order for this
mode to be in effect. If the OST client is not dedupe-capable, it will run in passthrough mode regardless of its dedupe
mode setting.
The following table shows the relationship between the configured OST client mode types and the supported client
mode based on client architecture type and corresponding number of CPU cores.
57