Filter
Top Products
ReadiVoice Administration & Maintenance Guide
96 Proprietary & Confidential
Backing Up Logical Logs
This procedure assumes the CACS is easily accessible. If it’s not, you can:
• Use
ontape -a
to perform a one-time backup of all the full logical logs
until you can get to the site to restart continual backup.
• Use a wrapper script to run
ontape -c
from a
nohup
process, directing
output to a log file. If you do this, be sure you check the log file frequently.
To start logical log backup:
1 Insert a tape into the drive designated for logical log backups (we assume
here that it’s
/dev/rmt/1
).
2 Log into the CACS server as root, open an XTerm window, and become
user informix by entering
su – informix
.
3 Type
ontape -c
and press ENTER.
Informix responds:
Performing continuous backup of logical logs.
Please mount tape 1 on /dev/rmt/1 and press Return to continue.
4 Press ENTER.
Informix backs up the currently full log files and marks them as once again
available for logging. As long as the process continues to run, it backs up
each log as it becomes full and marks it as available again.
You can minimize this XTerm window if you want, but don’t quit. If you
do, the ontape process stops, and your logical logs are no longer being
backed up.
5 In a new XTerm window, use the
onstat
command (see “Checking
Informix Dynamic Server” on page 99) to verify that the system is
operating properly.
Caution!
Informix Dynamic Server must be configured properly to back up logical log files to
tape. If you choose not to back up logical logs to tape, they must be directed to
/dev/null to prevent Informix from halting when all the log files become full. Before
proceeding, read “Understanding Informix Backup” on page 93.
Caution!
Whenever you reboot the Sun, be sure to restart logical log backup. Insert a new
tape when you restart if you don’t want the logical logs already backed up to the
existing tape to be overwritten. Don’t let the logical log backup tape become full! If it
does, Informix stops backing up logical logs, and when all logical log files are full,
the database halts.