RECOVER (Global Project Administration)

Administrator Command Reference Manual

Command Details : Detailed Descriptions of Commands : RECOVER (Global Project Administration)

RECOVER (Global Project Administration)

Recovers data when a database has been corrupted.

This command can be used on both Primary and Secondary databases, but for Primary databases it may be better to restore the database from the latest backup copy, because the copies at other Locations may not be up-to-date.

For a Primary database, by default recovery will be made from the most recent session at a neighbouring (parent/child) Database. For a Secondary database, by default recovery will be made from the neighbouring database which is first on the route to the Primary database.

Both Locations must be on-line.

Note:

The Global database can sometimes be recovered using the daemon.
If the Global database 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 database to understand the network. The System Administrator must copy this database to the required locations outside AVEVA E3D™. Refer to Recovering the Global Database for a detailed description of this process.
When Reconfiguring or Renewing a database, you should then recover the database at all its secondary locations in order to prevent reverse propagation. This also applies if a database is replaced by one from another project. The RECOVER TO ALL command can be used to recover a database from its primary location to all secondary locations.

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 (available from the Hub or the administering location of the satellite) RECOVER STEELN/STEELN AT DDD Recovers from CCC, the only neighbouring 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 database for EEE from the copy at BBB. RECOVER SYSTEM FROM BBB Recovers System database for the true current location from BBB.
Remote recovery of System DBs (available at the Hub or the administering location of the satellite) 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 System database for EEE from the copy at BBB. RECOVER SYSTEM FROM BBB Recovers System database for the true current location from BBB.
Remote recovery of System DBs (available at the Hub or the administering location of the satellite) 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 System database for EEE from the copy at BBB. RECOVER SYSTEM FROM BBB Recovers System database for the true current location from BBB.
Remote recovery of System DBs (available at the Hub or the administering location of the satellite) RECOVER SYSTEM FOR EEE AT AAA FROM BBB Recovers AAA's copy of the System database for EEE from the copy at BBB.
Recover to All Locations RECOVER PIPEN/PIPE TO ALL Recover a database to all allocated locations. The command can only be issued from the HUB, the Primary location of a database or the administering location of its Primary location.
RECOVER PIPEN/PIPE AT CCC TO ALL Note that this will recover the database from its primary location to online secondary locations, even if the destination is not explicitly stated. The syntax RECOVER <DBNAME> AT <LOC> FROM <LOC> should be used to recover a database from a secondary location.
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 locations are omitted, then the database 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. The user should refer to Recovering the Global Database for the recommended recovery procedure.

Command Syntax:


>- RECOVer -+- SYSTEM -+-- FOR <loc> -. \| \| \| \| ‘--------------\| \| \| ‘- dbname ----------------+- AT <loc> ------. \| \| \|-----------------+-- FROM <loc>--. \|-To ALLlocations-+ \| \| \| \| ‘-----------------+---------------+-->

1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.