Last Update: 17 November 2006
Product: StarQuest Data Replicator
Version: 3.3 or later
Article ID: SQV00DR015
It may be desirable to automatically pause and resume a SQDR Incremental Replication (IR) Group if the source or destination database server is expected to be unavailable for a given length of time, such as during a nightly/weekly backup or during operating system updates. Pausing an IR Group while the source or destination database server is unavailable will prevent the IR subscriptions from being flagged with warnings, and will ultimately result in fewer unnecessary email notifications and Windows Event Viewer messages.
The SQDR software provides a Windows Script called PauseResumeIRGroup.vbs that can be used to both pause and resume an IR Group. This script can be found in the \Program Files\StarQuest\SQDR directory.
This document explains how to schedule this script to run using the Windows Scheduled Tasks facility.
In the following steps you create two Windows Scheduled Tasks, one to pause an IR Group, and one to resume the Group.
"C:\Program Files\StarQuest\SQDR\PauseResumeIRGroup.vbs" "<IRGroupName>" "0"
The resulting command should look like the following:
C:\WINDOWS\system32\wscript.exe "C:\Program Files\StarQuest\SQDR\PauseResumeIRGroup.vbs" "<IRGroupName>" "0"
"C:\Program Files\StarQuest\SQDR\PauseResumeIRGroup.vbs" "<IRGroupName>" "1"
The resulting command should look like the following:
C:\WINDOWS\system32\wscript.exe "C:\Program Files\StarQuest\SQDR\PauseResumeIRGroup.vbs" "<IRGroupName>" "1"
C:\WINDOWS\system32\wscript.exe "C:\Program Files\StarQuest\SQDR\PauseResumeIRGroup.vbs" "<IRGroupName>" "0"
C:\WINDOWS\system32\wscript.exe "C:\Program Files\StarQuest\SQDR\PauseResumeIRGroup.vbs" "<IRGroupName>" "1"
The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization. The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.