AASTRA BluStar 8000i BAS-Mode Administrator Guides EN - Manual (Page 149)

Data Maintenance
41-001391-00 Rev 03 – 04.2012 10-6
Database Failures
Typical database failures are:
• Disk full
• Disk failure
Disk Full
When the Disk Full failure condition is detected, the database will refuse to start. Additional space must be freed up on
the disk, and the database daemon (postmaster) must then be restarted to recover from this condition.
Sometimes the database start-up fails silently. The only way to find the cause is to manually start the database by typing
the following command at the shell prompt:
su -l postgres -s /bin/sh -c “/usr/bin/pg_ctl -D var/lib/pgsql/data -p /usr/bin/postmaster start”
The output from this command can then be used to determine the cause of the failure, whereupon an appropriate action
can be taken.
Disk Failure
Failure of any disk involved with an active database requires that the database be recovered from a previously prepared
database backup. This backup must have been prepared using the vipr_backup_db command.
Recovery is a two step process that involves creating the schema and then reloading the data. To create the database
schema enter the commands:
cd /opt/m/install/ViPrServers/scripts
./vipr_init_db new
After successful completion of the commands, the data can be reloaded from a recent backup using the vipr_restore_db
command.
For an HA pair refer to Rebuilding a Failed High Availability Server on page 2-17 , to rebuild the failed node from the HA
peer.
Note:
Updates to the database occurring after the last database backup will be lost.