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.
ost --delete_client --name acme-99
Successfully deleted OST client acme-99.
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.
Table 2: Supported OST Client Modes and Settings
|OST Client Mode Settings
||32–Bit OST Client (4 or more CPU Cores)
||64–Bit Client (4 or more CPU Cores)
||32–Bit OST Client (Less than 4 CPU Cores)
||64–Bit OST Client (Less than 4 CPU Cores) |
ost --update_client --name acme-81 --mode dedupe
NOTE: You may be able to force writes for OST clients running in the Passthrough mode using the DR Series system CLI mode --dedupe command. The change in OST client mode is effective on the next backup operation when you are using Veritas NetBackup. (If you are using Veritas Backup Exec, you will need to restart this service for it to recognize that a new mode has been configured.)
OST client updated successfully.
Limits the bandwidth consumed by OST (OpenStorage Technology) for a system you define by IP address or hostname (--target), by which you define the speed in kilobytes/second (KBps), megabytes/second (MBps), gigabytes/second (GBps), or an unlimited bandwidth (default).
ost --limit --speed 10mbps --target acmesys-49
Successfully updated bandwidth limit for acmesys-49 to 10 MBps.
Changing traffic control policies ... done.
Lists or cleans up partial images.
- Container id — ID of container.
- Partial image path — OST partial image path to delete.
- Timeout — Maximum timeout (in seconds) to list partial images.
ost --partial_images --containerid 6
Image Name: K12
Image Date: 1481535029
Image Policy: DPA
Image Path: /1481500800/K12
Image Size: 251821817856
Image Status: 0