Hi Dwayne -
Not really. When it was first added to the product, most people used it to reduce the size of their archives.
But better methods exist such as archive compression and splitting archives to use additional storage locations.
When you use cold storage, you are actually adding to the database (to record versions sold stored and etc.).
Can you expand on the better methods? We are running out of space and looking at solutions. Currently have 3 servers and almost at 5TB
Hi James -
5TB? woah! Sounds like in your case Cold Storage might be a viable option.
Typically we recommend Archive Compression and splitting archives among multiple storage locations.
See this blog article Archive Management and Relocation – Part 3 – Compression and Cold Storage
I would strongly suggest contacting your VAR to discuss so they can properly assess your situation.
Cold storage is not something I typically advice to our customers, even though I see archives well over 5TB regularly. If you have 100+ versions per file on average, it might help. When you have few versions per file, there will be less of an impact.
More important though, my first question would be when someone mentions performance issues is what kind of performance issues is seen, and by whom? Is it reproducable or just in certain situations, etc? I don't want to be looking into Cold Storage when perhaps database activity is causing the problems.