| Command
|
LIMIT BANDWIDTH SCHEDULE ADD
|
| Description
|
Creates a scheduled bandwidth event for limiting transmission of data from the source to the target
|
| Syntax
|
LIMIT BANDWIDTH SCHEDULE ADD <label>
DAYS=<day1>[, day2,..., dayN] STARTTIME=<hh:mm> LIMIT=<bytes>, <seconds> | UNLIMITED TO <target>
|
| Options
|
- label—Unique name that identifies this bandwidth scheduling event
- day1, day2,..., dayN—Day(s) of the week that you want to schedule the bandwidth limitation for. You can either spell out the entire day or use just the first two letters of the day.
- hh:mm—Time, using a 24-hour clock, to indicate when this event will start
- bytes—Number of bytes to be transmitted
- seconds—Number of seconds to wait before transmitting again
- UNLIMITED—Bandwidth is not limited during this scheduled event
- target—Name of the target, an IP address on the target, or a virtual IP address. Depending on the network route Double-Take Availability uses to access the target, you may need to specify the fully qualified domain name.
|
| Examples
|
- limit bandwidth schedule add weekday days=Mo, Tu, We, Th, Fr starttime=06:00 limit=19300 5 to beta
-
limit bandwidth schedule add weekend days=Sa, Su starttime=04:00 limit=unlimited to beta
|
| Notes
|
-
This command transmits in bursts, not bytes per seconds. The time identifies how long to wait before transmitting again. For example, if 5 seconds are specified and it only takes 2 seconds to send the specified bytes, Double-Take Availability will wait an additional 3 seconds before transmitting again.
- Options that contain non-alphanumeric characters must be enclosed in quotation marks.
|