http://ptc.com/cs/tpi/115335.htm Description ----------------- How can Pro/INTRALINK administrators proactively manage disk resources allocated by the Pro/INTRALINK system? This TPI explores some organizational concepts that can be implemented to provide administrators a more detailed view of how objects stored in Pro/INTRALINK Commonspace folders translate to disk usage of the Pro/INTRALINK file vaults. Utilizing the suggestions below adds value with respect to managing disk resources and requesting purge operations in the database. Resolution ----------------- Begin by creating a Commonspace folder structure that is based on projects or product lines. Each project/product folder should then be assigned a storage cluster that has been created explicitly for that project. For example, company XYZ develops light and heavy construction tools and the Intralink administrator at company XYZ has created a storage cluster for the hand tool division. Thus, all Commonspace folders created for the purpose of the hand tool division will be assigned the storage cluster, Hand_Tools. Storage Cluster: Hand_Tools Top Level Folder: /Root Folder/Hand Tools Division/ Pro/INTRALINK allows a file vault to be added to multiple storage clusters. Avoid this practice. Instead, ensure each file vault is assigned to one storage cluster only. Furthermore, utilize a similar naming convention when defining file vaults and storage clusters. This will prevent a file vault or storage cluster from being mistakenly used for something other than it was intended. Company XYZ might have the following vaults in its Hand_Tools cluster: Storage Cluster: Hand_Tools Vaults in Cluster: Name Path Host FV1_Hand_Tools /intralink_storage/vaults/fv1_hand_tools Server_A FV2_Hand_Tools /intralink_storage/vaults/fv2_hand_tools Server_A FV3_Hand_Tools /intralink_storage/vaults/fv3_hand_tools Server_A If the above convention is followed, it becomes very easy for an administrator to identify how much disk space is being allocated by each product line because each product line is supported by it's own set of vaults. Since the file vaults have been created with a naming convention that is similar to the product lines, the administrator can easily scan a File Vault Space Report from the DSMU to ascertain this usage information. Armed with this clear understanding of disk usage, the administrator can request purge operations from project leaders who exceed their disk quotas. The same conventions should be employed for Replica vaults. As a rule of thumb, replica data should never be stored in a master storage cluster. When using folder replication, a replica cluster should be created in each location that will receive replicated data. The replica cluster should be assigned vaults that have been created explicitly for the replicated data. Storage Cluster: Replicated_Hand_Tools Vaults in Cluster: Name Path Host Replica_Hand_Tools_FV1 /ptc/ilink_storage/replicas/hand_tools_fv1 Server_B Replica_Hand_Tools_FV2 /ptc/ilink_storage/replicas/hand_tools_fv2 Server_B Since master and replicated data will be stored in their respective, separate storage clusters, an Intralink administrator can easily determine what is real data and what data has been replicated. When data is replicated to a master vault, a HYBRID vault is created. Once this is done, an administrator loses the ability to determine master data from replicated data. For this reason, hybrid vaults should be avoided. ====================