What are some of the reasons that keep Scheduled backups from running?
================
UNIX only
Check to see if the 'crontab' process is running
ps -ef | grep omni
If not, start the process from the command line
cron
==============
Check to see if the 'omnitrig' service is running, by running the command
UNIX
/opt/omni/sbin/omnisv status
Windows
cd \Program Files\Omniback\bin
omnisv status
If 'omnitrig' is not running, stop and restart Data Protector, which is supposed to start 'omnitrig'
===========
Hostname Resolution or Incorrect Username
This usually is because the hostname of the Cell Manager is missing or incorrect in the File
UNIX
/etc/opt/omni/server/users/UserList
Windows 2003
Program Files -> Omniback -> Config -> Server -> Users -> userlist
Windows 2008
Program Data -> Omniback -> Config -> Server -> Users -> userlist
To check this, configure a user with wide-open permissions
WARNING:
This should only be left in place for a very short period of time, it will expose the cell to a massive Security risk
In the UserList file, add the line
"*" "*" "*" * "admin"
Save the file, schedule a backup
Note: By default, scheduled backups can only run on the 15-minute mark (15, 30, 45, 00) each hour. This can be changed by editing the 'global' file, and changing this
# SchedulerGranularity=1 or 15
to this
SchedulerGranularity=1
and saving the file, which will allow you to schedule on a 1-minute increment
If the Scheduled Backup starts, edit the UserList file to add your cell manager hostname in place of the * without the " marks, for example
"*" "*" "*" mysys.hp.com "admin"
and schedule another backup. If it doesn't start, you have a problem with hostname resolution of your cell manager not recognizing itself, and it needs to be corrected
If it does start, add the Data Protector Administrator name to the 2nd field, for example
HPUX
"*" "root" "*" mysys.hp.com "admin"
Windows
"*" "ADMINISTRATOR" "*" mysys.hp.com "admin"
and schedule another backup. If it doesn't run, the User in the 2nd field does not have correct permissions
==============
Corrupt Backup Specification
This can be caused by some incorrect filename in the Datalists folder
UNIX:
/etc/opt/omni/server/datalists File System Backups
/etc/opt/omni/server/barlists Applications Backups
Windows 2003
Program Files -> Omniback -> Config -> Server -> Datalists
Program Files -> Omniback -> Config -> Server -> Barlists
Windows 2008
Program Data -> Omniback -> Config -> Server -> Datalists
Program Data -> Omniback -> Config -> Server -> Barlists
Make sure that all the filenames line up with the Backup specification names you are seeing in the GUI
This is a rare case, but it does happen occasionally
