BlueCielo Meridian Enterprise 2017 System Requirements

About moving a vault

After a vault has been created, it cannot be easily moved with Meridian Enterprise Administrator tool. These operations require careful copying of the vault data and server configuration that differ depending on whether the vault will be relocated on the same server or moved to a different server.

These operations involve the following data:

• Database files
• Document content (stream) files
• Licenses

The basic process for moving a vault is the same whether the vault will be moved to a new location on the same server or on a new server. Restoring a backup of the vault is the safest and easiest way to ensure that the vault is created properly in the new location.

If you will be moving the vault to a new server and the original server will be taken out of service, consider retaining the name for the new server. Retaining the old server name resolves several issues that will result from using a new server name:

• Security — The recommended procedure for setting security on a vault is to assign Meridian security roles to local user groups. Therefore, the computer name of the Meridian application server is part of the role assignments. If the vault is moved to a server with a different name, all of the role assignments must be removed and reapplied using local groups that exist on the new server. If the same computer name is used for the new server, no changes are required to the security roles of the vault.

• Transparency to the user — Moving a vault to a server with a new name will not go unnoticed by the users. They will have to be informed about the new server name and browse to this server to find their vaults. Likewise, if Web Access is installed on the Meridian application server, the URL for use by Web Access users will also change. Thereafter, Meridian will remember the new application server name.

  But more seriously, changing the server name will cause a new, empty local workspace to be created on the client computers where documents that the users were working on before the move will not yet exist. Manual intervention will be required to move the documents to the new local workspaces.
  

• Customization — In some cases, vault customization might have been programmed that depends in some way on the computer name of the Meridian application server. Such customization might need to be debugged or rewritten for the customization to work again.

Instructions for moving a vault are contained in the following topics. These tasks pertain to Hypertrieve vaults only. To move vaults that use other database engines, see Moving a SQL Server vault to a different folder or Restoring an Oracle vault to another server accordingly.