Intralink Vaults
Intralink uses vaults to store information. These are assigned to clusters, which correspond to predefined file storage locations.
When items are checked in, the files are saved into these vaults.
You may need to add a new vault for a couple of reasons:
- The disk containing the vault folder is running out of space, and you need to store files in an alternate location.
Add another disk drive to the server and create a new vault there.
- The vault folder has grown beyond a manageable size.
One rule of thumb is to limit a vault to a few thousand objects. Add new vaults to the storage cluster as required.
The following steps guide you through the process of adding a new file vault in Intralink.
Before starting, it is best to create a backup dump file of the database metadata (using the DSMU or ilink_export). Also switch the dataserver to Read Only mode.
- Log in to the DSMU (Data Server Management Utility - also known as proimgr.bat)
- Use Vault > Create File Vault
- Enter a vault name.
It's simpler to keep this the same as the project or product line.
It's a good idea to use an incremental suffix, ie: comp1, comp2, etc.
- Enter the vault host name.
Network name of the machine
- Enter the path to the vault folder.
An absolute path, including the foldername,
eg: c:\intralink_dir\vaults\comp1
This must be a new folder - Intralink will create it.
Keep the foldername equal to the vault name to avoid confusion.
- After successfully creating the new vault, log on to Intralink as an administrator...
Default: INTRALINK / INTRALINK
- Use
Administration > System > Vaults
to set the older vault to Read Only as shown
- Use Administration > System > Storage Clusters >
to add the new vault to the appropriate cluster as shown.
Additional notes
- Ensure the host for the new vault is set up as an Intralink File Server - if not, install the File server software and use DSMU > Vault > Create File Server to declare the additional File server.
- After the old vault has been made Read Only, it no longer needs a continued backup - a single backup will suffice, since the data is fixed from that point forward.
- Always take care when carrying out operations on Intralink Data Servers - experience has taught me that you can take nothing for granted, and you must always have a database dump before starting...