GroupWise Disaster Recovery Scheduler Not Running Jobs or Jobs Do Not Finish

  • 7019906
  • 20-Oct-2009
  • 11-Mar-2019

Environment

GroupWise Disaster Recovery (Reload) (all versions)

Situation

The profiles and schedules are set up, but the jobs are not being queued to run. How can this be corrected?

Resolution

There are a number of reasons that could cause a scheduled job not to run. In order to determine why a job did not run, first examine the logs for any errors. The logs are found in /opt/beginfinite/reload/logs  or in the Web Interface. The logs to look at are the agent.log  or the error.log. The system may have run out of disk space or there may have been a network issue. However, if there is no error and no indication that the job was ever queued to run, then there may be a problem with the schedule configuration file, the profile or the scheduler.

1) Check the license. Go to Overview tab in the GroupWise Disaster Recovery (GWDR) WEB UI. Check the Technical Support expiration. If that is expired, reapply a new license. The scheduler will turn off if a license has expired, or is not valid. 

2) Check Disk Space, both on the GWDR server and GroupWise server. Add additional space as necessary, or remove older backups from GWDR

3) Try re-creating the schedule configuration file. Navigate to where the schedule file is and rename the file. Then setup the schedule again through the GWDR menu. It will create a new schedule file. For information on the schedule files and where to find them, please see GWDR  Profile Schedule Files.

4) If the job still fails to be queued, try re-creating the profile. Simply set up a second profile for the same post office. Then disable the original profile’s schedule. You will find the option to disable/enable the schedule under the job type schedule menu for the profile. Click the link to help in creating a new profile. Recreate Profile

5) If the system is still not queuing the jobs, then there may be an issue with GWDR itself. Try reinstalling the software and make certain that it is up to date. To reinstall, see How to uninstall, and then install GWDR.

6) Check NFS Mount Points - Check the NFS Server on the GroupWise side, and run a test and refresh profile from the Reload Administration. From a terminal prompt on the GWDR server type reload. Go to Profiles, select the Profile. Select Advanced. From here the connectivity can be checked, or changed if necessary, or test and refresh a profile. If any errors occur with the test and refresh follow the onscreen instructions and verify the NFS mount points and export paths are correct. 

7) If using a Collector, check to see that the collector is still paired to the Reload Server. This can be done by testing and refreshing the profile. Other issues with the collector could be that the job hangs in the middle of the job and doesn't finish, preventing the data from being copied to the Reload server. The result will can be the backup finishes on the collector server, but the Reload server never receives the data and is behind. These can be resolved here: 


8) A rare issue can also occur that the GWDR jobs do not start, when everything else has been accounted for (no errors, license valid, configuration correct, schedules enabled etc...). The fix is to disable the Standard Schedule job and set up intra-day backup instead, using the Cron process on the Linux system. 

9) Other causes of the jobs starting, but not finishing are due to mounting issues with NFS, untested profiles, stalled job, connection issues, such as SSH, or not enough dbcopy threads. The following will help to fix each of the areas mentioned. 

All of these issues with the jobs not starting or finishing will help to get things going. If all of the above have been attempted with no success reach out to GWDR Customer Care for additional assistance. 

 

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 1503.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.