HP StorageWorks Storage Mirroring for Linux User's Guide (T2558-96078, February 2008)

10 - 12
Transmission schedule examples
This section shows examples of how the different schedule commands could be used together.
 Example 1—In this example, transmission is set to begin on January 12, 2007, at 10:30 p.m. and to end after 6 hours.
This schedule is also set to repeat every day:
schedule indy start starttime=1/12/07 22:30, every 1 day
schedule indy end duration=6 hr
schedule indy enable
If all the data is not transmitted within the 6-hour duration, the remaining data will remain in the queue and will be
transmitted during the next scheduled transmission.
 Example 2—In this example, transmission is set to begin after the source queue contains 41943040 bytes (40 MB) of data,
and transmission is set to end after 52428800 bytes (50 MB) of data have been sent from the source to the target:
schedule indy start queuesize=41943040
schedule indy end bytes=52428800
schedule indy enable
If there is data remaining in the source queue after the transmission ends, the data will be sent when the source queue
again reaches 41943040 bytes (40 MB) of data.
 Example 3—In this example, transmission is set to begin after the source queue contains 52428800 bytes (50 MB) of data,
and transmission is set to end after 62914560 bytes (60 MB) of data have been sent from the source to the target.
However, transmission can only occur if the start criteria is met within the defined 6-hour window:
schedule indy start queuesize=52428800
schedule indy end bytes=62914560
schedule indy window 22:00 to 04:00
schedule indy enable
If additional data remains in the source queue after the transmission ends, that data will be sent when the start criteria is
again met within the defined 6-hour window. However, if the start criteria is not met within the defined 6-hour window,
data remains in the queue until the start criteria is met within the defined window.
NOTE: The numbers and times were randomly selected for these examples. Be sure to use values that work for your
environment.
NOTE: You do not have to specify the exact number of bytes in 1 MB. You can approximate. For example, the following
is acceptable:
schedule indy start queuesize=5000000
schedule indy end bytes=6000000
At any time, transmission can be manually started, stopped, paused, or resumed regardless of scheduled
transmission criteria.