Managing the Blue Mountain RAM and Document Databases
The backups of the Blue Mountain RAM database and the associated Document database should be managed in tandem for the remainder of their lifespan after implementation as these databases work contingently upon one another. Neglecting to maintain and restore these backups in tandem can potentially result in orphaned document references within the Blue Mountain RAM database causing application errors.
Should backup and restore of these databases be sequential?
Yes. This ensures that the data in both databases will be synchronized and that application errors will not occur as a result. Whenever a backup is performed on the Blue Mountain RAM database, it should immediately be followed by a backup of the Document database. The precedence of these backups is important to maintain data integrity. Since backups are generated periodically, we recommend using a naming convention to ensure the backup-pair are easily associated with one another so that they can be identified in the event that database restore is necessary. If a database restore is needed, then both backup files that comprise the backup-pair should be restored before users access the system.
What are some tips concerning the names of the databases?
We recommend that you retain the original name of the Document database after integration since the Blue Mountain RAM database is now specifically linked to that Document database name. However, if the Document database must be renamed, it is essential to use the Document Library Synchronization tool. This is useful in cases where you may want to restore multiple sets of a Blue Mountain RAM and Document databases on a single server. It is also beneficial when you wish to rename a Document database according to your company’s naming standards.
What is the relationship between the databases?
When the two databases are integrated, a separate Document Library is created in the Document database for each Site that exists within the Blue Mountain RAM database. The Blue Mountain RAM database maintains a mapping of each of its Sites to the Document Libraries. The “Site-to-Library” mappings, along with a reference to the name of the actual Document database established during integration, exist in the Blue Mountain RAM database.
The bytes for any document and/or image uploaded using the Blue Mountain RAM application are stored in the Document database. References to those documents are stored in the Blue Mountain RAM application. The Document database exists without any external knowledge of the application that uploads and references documents within it; however the Blue Mountain RAM application does maintain external knowledge of the Document database.
It is important to understand the basic relationship that is established between the Blue Mountain RAM database and Document database in order to avoid potential data loss and to ensure that database recoverability is maintained.