cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Possibility for different file vault locations

Possibility for different file vault locations

In Integrity Life Cycle Manager you can currently have only one file vault for Source. As another idea suggests why there is not a file vault available for Workflow & Documents e.g. Attachments - what about the rich text attachments ?

Another idea says - we need more options to define what should be stored in the Source file vault.

A question concerning file vaults was: can I have a distributed file system with the file vault - yes you can, but only one. So you might be limitated by Service Level Agreements as your IT department says those file systems cannot grow endless because of backup and restore.

So why can we not have several file vaults - configurable via project policy for Source. Then one could have vaulting 10 years, 5 yerars, 3 years to different file vault locatins for example and then decide which file vault to use per project. You could have for one project the 10 years stuff, for others still 3 years for example - or decide for different selections how your revisions should be stored on the file vault.

 

And why not bringing all these ideas toghether:

You could have several file vaults - configurable per project

You could have different file vaults for Source and Workflow & Document depending of your configuration

You could decide whether to store only Source revisions or Workflow & Document Attachments or both

You could decide what type of W&D attachments to store in the file vault - internal from rtf fields, user attachments or both

You could more selection options like suggested in a another file vault idea -  file size / revision size, time range, document/content type concerning W&D attachments and so on.

 

2 Comments
rlange
3-Visitor

We are facing the use case that our Integrity users use the Integrity Lifecylce Manager to save all data of the project, including data from test and simulation areas, which can be very large files> 10 GB per file. We have seen the database size grow by 500 GB per month. We then limited the size of files for Integrity using a script mechanism. This is very unsatisfactory for the users because relevant project information must now be managed at different storage locations. If we deactivated this size limit again due to the use of FileVault, we would very quickly exceed the limit of 4 TB for data storage communicated by our IT department. Therefore, we would like to have a configuration option to control the FileVault location of a source project.

olivierlp
Community Manager
Status changed to: Archived

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.