Embedded Files
- Stop Apache Tomcat and Scala transmission server service.
- As with the backup process, pgAdmin is used to restore the database.
If the database schema you’re restoring already exists, you must first delete it. Open pgAdmin by navigating to: Start -> Programs ->PostgresSQL--> pgAdmin.
- Connect to your database server using the same Username and Password you entered when you installed Content Manager.
- Select the database schema you want to delete, then right-click and select Delete/Drop. In the “Drop Database?” dialog, click Yes.
- Select Databases, and then right click > New Database. Type the database schema name you want to restore. Make sure the encoding is set to UTF-8. Click OK.
- You can now restore the tables and data. Select the database, right click, and choose Restore. In the resulting dialog box, choose the database backup file that was created. If you backed up the database using specific options, you must change the restore options accordingly. Otherwise the defaults are okay.
- Wait for the restore process to finish, and verify that the final message is Process returned exit code 0. If a different exit code is shown, it indicates that some part of the restore process has failed.
- If returned exit code 1,
- check errors.
- try it again.
- it might be missing foreign keys.
- did not go through a specific Content Manager version when you were updating your network. 6.0.17 6.2.13 10.5.13 11.00.09 11.01.04 11.02.04
- Troubleshooting
- Confirm Schema and database name are same (Case sensitive). And Click on Test Connection.
- System>Database Configuration>Test Connection
- Confirm Schema and database name are same (Case sensitive). And Click on Test Connection.
You may choose to use the command line tool pg_restore.exe to restore the database. To restore a backup, execute the following command:
pg_restore --dbname=cm --format=custom -U postgres -W C:\tmp\db.backup
Please refer to the PostgreSQL manual for more details on the command line tools.
Report abuse