Overview
- Regular cadence to test validity of backed up data
- Testing backup integrity and accuracy throughout various restore points and scope
- points - “a week ago / a month ago” (point in time)
- scope - file vs directory vs DB (different parts of data)
- Verify backup is what is expected
- Document results of Backup Verification
Why Does This Matter?
-
Backup technologies are imperfect
-
software only backing up what it sees
-
encrypt & compress data
-
data changed on way in
-
need to pull data out and verify process is accurate
let’s be sure programs are working correctly to keep data integrity
-
verify data is complete
-
Provides peace of mind for data
What Value Does This Add?
- Data Protection
- Risk Reduction
- Redundancy
- Disaster recovery
- Configuration
- Aligned to best practice and business needs
Common Problems
- Data wasn’t back up as expected
- verification shows gaps in scope
- Find corruption
- Highlight retention periods are wrong
Why Is A Solution Needed?
-
Time has shown that backup technologies need regular review
-
can easily become out-of-sync
-
Too important not to regularly look at by an engineer
-
Backup issues/oversights not always obvious
-
doesn’t impact day-to-day and underlying issues can exist
Notifications can be set up, but can provide false positives/negatives
What To Expect
Business Leaders can expect
- Data is protected
- Minimum risk of data loss
- Data viable when needed
- Proof & Documentation of work
- Transparency
End Users can expect
-
Ability to retrieve lost data
Ease of mind w/ User-Error
-
accidental deletion
-
corruption
How Does Black Line Do It Better?
-
We simply get it done
-
Part of Black Line discipline
-
Transparency
-
We make sure there is a backup
-
too common for business to say they “backup” but do not in reality
-
engineers don’t usually have disciplines around doing it
We have dedicated team to do this service
-
Dedicated teams for checks and verification (checks & balance)