No I whole heartedly agree. It needs to have a phased approach that we work with the stakeholders on identifying what needs to be backed up and what needs to be archived.
As far as the rest of our infrastructure we run on a VCE vBlock 300FX with an EMC VNX5500 storage array. We use recoverpoint for replication and have commvault in place with local and offsite backups and archive.
AV Storage is a new project/beast i am looking to undertake. Trying to isolate a enterprise storage solution locally for best performance to the End AV user while also ensuring data is backed up or snapshotted so they can revert if they mess up, backed up for the most current project, migrating data off to our Enterprise storage array where they can be kept and backed/replicated/archived for long term needs.
I want to protect this data but at the same time I do not want to get so excessive in backups that the insurance plan becomes a money sink that does not pay dividends.
So Example:
Primary Storage at AV Marketing
Use Snapshots, checkpoints, VSS for immediate rollback of projects or Replication to a mirror storage array across town for Redundancy and failback needs.
(or)
Add a mirror copy of Primary storage at our Branch AV Office and simply have Marketing replicate to Branch office and Branch replicate back to Marketing office.
Use Tape for Archive of long term data retention needs and copy a copy on and off site.
All Finished products moved to EMC VNX and stored there where it is backed up (Commvault), replicated (Recoverpoint) and archived (Commvault) as per standardization in datacenter runbook.