What are the real differences between warm and cold storage in an Archiver when working with a virtual deployment?The only benefit I could think is that data stored in the cold tiers would take less space than data stored in the warm tiers. But is this the case? If I plan on deploying a virtual Archiver on top of VMware using SAN for storage, is there any real benefit in using cold storage over hot/warm?
The compression rates on warm and cold storage are the same. The only difference is the storage you choose to use for each. If you would like to use slower storage media for a "cold" tier, it will move data to warm storage first and then from warm to cold as warm fills up.
What about the differences between hot and warm/cold? Based on the image in the configuration guide the compression is configured per collection. Does this mean that I cannot configure a collection to use hot storage without compression for x days, after which the collection would use warm storage with compression for y days? I.e. the compression has to be configured for all the tiers for a collection or alternatively for none?
Is there a scenario planner that would take into account the different compression options? I presume that the scenario planner I am using (v10.6.04.2017) is not using compression for its storage calculations.
Something else to keep in mind. Cold storage was added to allow the data to be taken off the archiver into some vault.
As far as warm and cold storage, the difference there was hot storage is on the SAS attached DACs where as warm was built to support NAS connections. The only required stage is hot. Warm and cold are optional
The compression rates on warm and cold storage are the same. The only difference is the storage you choose to use for each. If you would like to use slower storage media for a "cold" tier, it will move data to warm storage first and then from warm to cold as warm fills up.