- David Kerrivan, Group Commissioner, 1st Greenwood VC Scouting
- Thomas Kolbe, Systems Architect, University of San Diego
- Adam Little, System Engineer I, Rivers Casino Holdings Acquisitions Co.
- Mark Coney, Systems Engineer, Healthcare/Academic
- Michael Somerville, NISS Manager, University of San Diego
- Phillip Warren, Olivet Nazarene University
- Jackie Ramsey, System Administrator, Liberty Medical Group
- Nick Furnell, Senior Systems Engineer, Transform Medical Group
- Brandon Lovelace, Santa Barbara City College
- Tim Campbell, President, Ascendum IMS LLC
- Business requirements can be vague. Not knowing the business needs often results in overexpenditure and overexposure to liability through data hoarding.
- Backup options are abundant. Disk, tape, or cloud? Each has drawbacks, efficiencies, and cost factors that should be considered.
- Backup infrastructure is never greenfield. Any organization with a history has been doing backup. Existing software was likely determined by past choices and architecture.
- Don’t let failure be your metric.
The past is not an indication of future performance! Quantify the cost of your data being unavailable to demonstrate value to the business.
- Stop offloading backup to your most junior staff.
Data protection should not exist in isolation. Get key leadership involved to ensure you can meet organizational requirements.
- A lot of data is useless. Neglecting to properly tag and classify data will lead to a costly data protection solution that protects redundant, useless, or outdated data
Impact and Result
- Determine the current state of your data protection strategy by identifying the pains and gains of the solution and create a business-facing diagram to present to relevant stakeholders.
- Quantify the value of data to the business to properly understand the requirements for data protection through a business impact analysis.
- Identify the attributes and necessary requirements for your data tiers to procure a fit-for-purpose solution.
This guided implementation is a nine call advisory process.
Guided Implementation #1 - Define the Current State
Call #1 - Establish project rationale.
Call #2 - Create a diagram of the current state.
Call #3 - Identify problems and opportunities.
Guided Implementation #2 - Conduct a Business Impact Analysis
Call #1 - Identify systems and scoring criteria.
Call #2 - Conduct the impact analysis.
Guided Implementation #3 - Propose the Future State
Call #1 - Determine attributes for data protection solution.
Call #2 - Create a diagram of the future state.
Call #3 - Find knockout criteria.
Guided Implementation #4 - Establish Governance