Move a Hypertrieve Vault

To move a Hypertrieve vault from one server to another (for example, to upgrade the server hardware), we recommend that you back up the vault on the source server with the Prepare for Backup Wizard and restore the vault on the destination server with the Restart After Restore Wizard. To move only a vault's content files without moving its metadata, see Move the Document Content Files.

Important!

The following task should only be performed after business hours and after backing up all related files and registry settings.

It is not possible to move (by restoring from backup) a vault from a pre-Windows Server 2008 computer (including Windows XP, Windows Server 2000, or Windows Server 2003) to a post-Windows Server 2008 (including Windows Vista) or later computer without adverse side effects. The possible side effects include folders and documents not being accessible, and vault corruption.

The cause is Windows API functions that behave differently between pre-Windows Server 2008 and post-Windows Server 2008 operating systems.

There are two supported methods to move an existing vault from a pre-Windows Server 2008 computer to a post-Windows Server 2008 computer:

  • Import the vault from the source server into a new vault on the post-Windows Server 2008 computer.

  • Restore a backup of the vault from the source server onto the new server and reindex the vault with the icosnlsver tool as described in Change Operating System Versions. Migration assistance is available from Accruent Partners and Accruent Technical Support.

See Operating Systems for the names and versions of supported operating systems.

The general procedure to move a Hypertrieve vault is:

  1. If the vault will be moved to a different server, ensure that enough free disk space is available as described in Document Storage Space Requirements, install the Meridian Enterprise software on the destination server as described in Installation and ensure that client computers can connect to it before proceeding.

  2. If the License Server service will also be moved to the other server, register the licenses as described in Register Licenses - Administrator.

    If the computer running the License Server service is separate from the source server, this step is not necessary but the License Server computer must also be accessible from the destination server.

  3. Create a backup of the vault on the source computer as described in Prepare For Backups.

  4. Ensure that no users are connected to the source server by viewing the current license usage as described in View Current License Usage.

  5. Confirm that a DataStore.ini file is present in the Backup folder.

    Before you can move the data, you must first stop the services that use the data.

  6. In Meridian Enterprise Administrator, right-click EDM Server in the left pane and select Properties.

    The service's Properties dialog box appears.

    Note:

    You may also use the Services applet in Control Panel to perform the following several steps.

  7. Change Startup type to Disabled.

    You must disable the services so that they will not automatically restart if requested by client applications.

  8. Click Apply.

  9. Click Stop.

    You are prompted to stop the Accruent Filesystem Server service.

  10. Click Yes.

    Both services are stopped.

  11. Repeat steps 3 to 6 with the Accruent License Server service and the AutoManager Task Server service (if used).

  12. If PowerWeb is used, also stop the World Web Publishing service on the web server.

  13. Copy the entire vault folder contents (including the Backup and streams folder structures) to the BC-Meridian Vaults folder of the destination computer.

    The original vault folder contents will act as a temporary online backup. After you have completed moving the vault and confirmed that users are correctly accessing the vault in the new location, you can safely delete the original vault folder contents.

    Note:

    Copying the vault folder can take a long time depending on the size of the vault, content indexing options, and so on. Allow sufficient time for the copy to complete before proceeding.

  14. If the vault stream files are not located in the default location (subfolders of the vault database folder) and you are moving the vault to a different server, copy them to the new location also at this time.

    This step can also take a long time. If the stream files are located on a drive that is also accessible from the destination server using the same UNC or drive letter (for example, NAS or SAN devices) and you do not want to move them, they can remain in place.

  15. Copy the custom extensions folder and its subfolders to the new location, if necessary.

    By default, the folder is located at C:\BC-Meridian Extensions.

  16. If the Task Server is used, copy any pending tasks to the new server by copying the contents of the following folder to the same location on the new server: C:\Documents and Settings\All Users\Application Data\Cyco\AMTasks.

  17. Edit the DataStore.ini file on the destination computer and correct the paths in the Databasename and RootPath settings, if necessary to match the destination computer.

  18. Restore the vault as described in Restore Backups using the edited DataStore.ini file.

  19. In the Meridian Enterprise Administrator or the Services applet of Control Panel, change the Startup type property of the services that you cleared previously back to Automatic and restart the services.

  20. Test access to the vault by various security roles and that changes to documents are saved correctly.

2024