Running Global Projects
Database Recovery
: Recovering Primary Databases
Recovering Primary Databases
Recovering primary databases requires a little more consideration. Because the primary database is the most up-to-date version of that database in the project, there is inevitably going to be some work loss.
The main aim here is to recover the database from the most recent backup or from a secondary location with minimal work loss.
•
Restore from backup if all secondary databases are older than backups or if they had not been synchronised with the primary database before it was corrupted.
•
Restore from a secondary location if this database is an uncorrupted and newer database than the one in the backup. (The user should restore from the latest secondary database.)
Some corruption can be fixed by DICE, so try using DICE first if recovering to a primary location.
This method can also be used to recover the system database. However, the system database cannot be recovered by the daemon unless it is readable, since the daemon uses it to understand the network. If the system database cannot be read, then it must be restored manually.
Note:
When a DICE report indicates that Refblocks have been lost, normally this would require the master database to be patched. However in a Global project, this error is non-fatal if there are working extracts. These databases are non-propagating and only exist at the primary location of their extract owner. This results in the error report, since the Refblocks for working extracts are not accessible at the primary location of the master db. (Refblocks are blocks of reference numbers available for use in the extract).
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.
