Hub Administration
- Last UpdatedJan 31, 2025
- 1 minute read
Creating Global projects and locations and configuring communication daemons have been described in Setting up a Global Project. This chapter adds to the information, and describes the other tasks that will need to be carried out at the Hub. These are:
-
Controlling database allocation.
-
Changing the primary location of a database.
-
Changing the Hub location.
There are also several tasks that the Hub Administrator can carry out remotely for a Satellite: some of these tasks are also described in Local Administration, as they are essentially local operations. These tasks are:
-
Remotely merging changes.
-
Remote locking and isolation.
-
Remote synchronisation of databases.
-
Remote data recovery.
-
Remote removal of phantom users and elements.
-
Remote integrity checking of databases (Database Integrity Checker (DICE)).
The Hub Administrator is also responsible for the normal administration of databases that are primary at the Hub, and the creation of Users and Multiple Databases (MDBs) for the location that happens to be the Hub. All these tasks are described in the AVEVA Administrator User Guide.
Related Links
- Data Access Control and Stamps in a Global Project
- Database Allocation
- Deleting Databases
- Using Different Database Areas in Global Projects
- Non-propagating Files
- Changing the Primary Location
- Changing the Hub Location
- Deleting Locations
- Location Groups
- Replication in a Global Project
- Remote Operations
- Querying Remote Databases
- Administering System Databases
- Verify Daemon Version