I would like to do a projection of data requirements for 5 yearss with a Vault that will start off at 300 GB. Are there any guidelines or recommendations on how to do such a projection?
Solved! Go to Solution.
I have asked the same question of our dealer with who kind of looked down at the ground and then at each other. Twice no with no answer.
Your going to have to work this out your self ! I am trying to identify this myself.
Unfortunaly I cannot give much guidance regarding either. There are many variables that wille effect the growth of vault (something else to consider is database growth vs filestore growth). Some examples below:
How many versions for your designs are you anticipating to be created?
Are you planing to trim the filestore periodically by purging undesired versions?
How many new files / designs are you planning to implement?
Will you be using an item or document release process or none?
Will you be catagorizing several differnt file types?
How many properties are you planning to extract from various filetypes?
These are examples of factors that will attribute to vault growth. If you generally do not add much new content or newer versions to vault and your vault size will reflect minimal grown. However, if you plan on versioning files continuously after each change and keepign those versions, I would expect the size to grow fairly rapidly.
I know that is a very vague answer, but I hope it helps.
the part files are mofified without the user making any changes to them. This is especially painful when some of the parts are Released.
ok, thankyou. this is the same undesirable behaviour i have seen, its Inventors fault. Its about time Autodesk got Inventor & Vault to play nice in this regard. A similar thing happens with Derived parts.
You change a sketch to modify one of the bodies. None of the other bodies are affected. However, upon update of the assembly, all child parts that use the source model (skeletal or otherwise) want to be updated. Again a absolute nightmare when you have released parts. You may only want to up rev 1 of 10 parts, but you have to put the other 9 into quick change just so you maintain a stable model. NOT COOL!
This morning, I had an assembly and a drawing of the assembly open with most of the associated files checked out. I saved everything, and checked it all in. Then I checked out just the assembky file. I switched to the drawing and back to the assembly. Inventor began throwing the would you like to edit locked parts dialog over and over again.
Most of our Vault is set as Quick Change because of this terrible behavior.
We go through a database sizing exercise when ever we install a SQL data base and identify backup plans etc blah blah blah.
I found plenty of info in the advanced_config_guide_-_2012.pdf but no planning guide for capacity. So I have to take a flyer (calculate) on it and say five times current storage minimum given our workflows and same for backups. This is why we never implimented three years ago the cost was high when this was considered and with no indication of this from the supplier in his costs only un-answered questions. For me the biggest problem with all of this is the cost of expanding the storage, but at least I planned ahead based on the identifying this issue in the past. We upgraded server and storage in the last tweleve months due to end of life and I got what I needed in an on our Equallogic storage solution you might be in trouble if your storage solution is based on standalone servers do the calcs for capacity and backup time we moved away from tape to disc. So I can tell my manager that we are in a position to impliment having a reduction in the real world cost.
Whats your real cost of implimentation in twelve months time? So plan accordingly and make sure you include it in your budget or else you be upgrading storage and backup along with your CV!
All the best.
Yes, I originally took the increase of data for the past year (88%) and multiplied the data by 1.88 for each year for the next 5 years. However IT got a bit concerned with the projected size (7.2 TB) so I decided to use a linear progression (add last year's increase to each future year) This brings it down to 3.1 TB so I'm going to take a flyer with this too.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!