Does anyone else have issue with the lack of archiving capability\nwithin Pro/Intralink?\n\nAs a technical consultancy we have many folders, each allocated to\nclient projects. Project life varies, and at the end of this it is\nimportant to archive data to keep the vault size down. We also need\nto be able to retrieve this data for further future work. We are at\nthe stage now of having nearly 20Gb of data being backed up daily, and\ngrowing.\n\nAs some sort of work-around we were advised to create a new vault and\ncluster for archiving. Projects could then be moved to a new folder\nbased on the archive cluster. Sounds great, but in practise all that\nhappens is a change to the metadata. You then need to modify every\npart before it will move just the most recent version into the archive\nvault. This would then need to be followed by purging of all old\nreleases. This is not archiving!\n\nI can't believe that PTC are so short-sighted as to think this\nfunctionality is not required, especially as this existed within\nPro/PDM.\n\nDoes anyone know of a real approach to archiving in Pro/Intralink?