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. |
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.) |
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).
Lists or cleans up partial images.
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center