RECOVER (Global Project Administration)
- Last UpdatedFeb 22, 2022
- 3 minute read
Function:
Recovers data when a Database (DB) has been corrupted.
Description:
This command can be used on both Primary and Secondary DBs, but for Primary DBs it may be better to restore the DB from the latest backup copy, because the copies at other Locations may not be up-to-date.
For a Primary DB, by default recovery will be made from the most recent session at a neighboring (parent/child) DB. For a Secondary DB, by default recovery will be made from the neighboring DB which is first on the route to the Primary DB.
Both Locations must be online.
Note:
The Global DB can sometimes be recovered using the daemon.
If the Global DB for a Location is corrupt or the network of Locations has changed, it cannot be recovered using the daemon, since the daemon needs to use the Global DB to understand the network. The System administrator must copy this DB to the required Locations outside the AVEVA base product. When reconfiguring or renewing a DB, the administrator should then recover the DB at all its Secondary Locations in order to prevent reverse propagation. This also applies if a DB is replaced by one from another Project. The RECOVER TO ALL command can be used to recover a DB from its Primary Location to all Secondary Locations.
Examples:
The examples are based on the following configuration:
|
Secondary constructor DBs: RECOVER PIPEN/PIPEN Recovers from BBB or DDD, whichever is the most recent. RECOVER STEELN/STEELN Recovers from BBB, that is the next DB on the route to the Primary Location. RECOVER STEELN/STEELN FROM DDD Recovers from DDD. |
|
Remote recovery of secondary constructor DBs: RECOVER STEELN/STEELN AT DDD Recovers from CCC, the only neighboring Location in this case. If there was a child of DDD, the recovery would be from the most recent copy. RECOVER STEELN/STEELN AT DDD FROM BBB Recovers DB at DDD from BBB. |
|
System DBs: RECOVER SYSTEM FOR EEE FROM BBB Recovers System DB for EEE from the copy at BBB. RECOVER SYSTEM FROM BBB Recovers System DB for the true current Location from BBB. |
|
Remote recovery of System DBs: RECOVER SYSTEM FOR EEE AT AAA FROM BBB Recovers AAA's copy of the System Database for EEE from the copy at BBB. |
|
System DBs: RECOVER SYSTEM FOR EEE FROM BBB Recovers the System DB for EEE from the copy at BBB. RECOVER SYSTEM FROM BBB Recovers the System DB for the true current Location from BBB. |
|
Remote recovery of System DBs: RECOVER SYSTEM FOR EEE AT AAA FROM BBB Recovers AAA's copy of the System DB for EEE from the copy at BBB. |
|
System DBs: RECOVER SYSTEM FOR EEE FROM BBB Recovers the System DB for EEE from the copy at BBB. RECOVER SYSTEM FROM BBB Recovers the System DB for the true current Location from BBB. |
|
Remote recovery of System DBs: RECOVER SYSTEM FOR EEE AT AAA FROM BBB Recovers AAA's copy of the System DB for EEE from the copy at BBB. |
|
Recover to all Locations: RECOVER PIPEN/PIPE TO ALL Recover a DB to all allocated Locations. The command can only be issued from the Hub, the Primary Location of a DB or the administering Location of its Primary Location. |
|
RECOVER PIPEN/PIPE AT CCC TO ALL Note: |
|
Recover a Global Database: RECOVER GLOBAL TO ALL The User can recover a Global DB from the Hub to a Satellite or Satellites. The command is only available from the Hub. |
|
RECOVER GLOBAL AT <LOC> If the AT <LOC> is omitted, then the DB will be recovered at the current Location from the next Location on the route to the Project Hub. It is recommended that changes to the network are not distributed this way, since results might be unpredictable. |
Command Syntax:
|
>- RECOVer -+- SYSTEM -+-- FOR <loc> -. |