Scribd
Upload
91 views6 pages

Testing Backups: Prepared By: Cristine Joy B. Lucapa

Testing backups is essential to ensure the ability to recover important files, virtual machines, physical servers, and applications in the event of data loss or corruption. Key things to test include file, VM, physical server, and application recovery on a regular schedule as well as when major changes are made. It is important to understand the seriousness of backup testing, have a documented testing plan, and make testing a routine part of the backup strategy. Regular testing helps identify issues and ensure the backups will work properly when needed.

Uploaded by

CJ Lucapa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
91 views6 pages

Testing Backups: Prepared By: Cristine Joy B. Lucapa

Testing backups is essential to ensure the ability to recover important files, virtual machines, physical servers, and applications in the event of data loss or corruption. Key things to test include file, VM, physical server, and application recovery on a regular schedule as well as when major changes are made. It is important to understand the seriousness of backup testing, have a documented testing plan, and make testing a routine part of the backup strategy. Regular testing helps identify issues and ensure the backups will work properly when needed.

Uploaded by

CJ Lucapa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 6

TESTING BACKUPS

PREPARED BY: CRISTINE JOY B. LUCAPA


Backup testing: What to test, when to
test, how often to test

 Data protection – is an essential component in any data


management strategy, and one that all system and
storage administrators should fully embrace.

 Virtual Machine (VM) – is just a set of files that contain


the operating system and data of the VM, plus details on
VM configuration.
Backup: What to test?

 File recovery - This process is easy to apply to physical and virtual


servers, as well as backups of the file servers. The choice of data to
recover really depends on what data is being stored.
 VM recovery – This is clearly one for virtual environments, rather than
physical ones. Recovering a virtual machine image is relatively easy,
but considerations has to be given to where the VM will be powered
up.
 Physical recovery – Physical sever recovery is more complex and
depends on the configuration of the platform. Some servers may boot
from SAN, whereas others may have local boot disks.
 Data recovery - Depending on the backup process, data recovery can
be an option in testing.
 Application recovery – Full application testing can be more complex
because it relies on understanding the relationships between individual
virtual machines and physical severs.
Backup: How often to test

 Schedule a restore test for each application on a regular interval.


 Schedule a restore test when significant changes have been made
to an application, such as upgrading to a new software release or
when installing a major patch package or operating system
change.
 When application data changes significantly. If an application has
a regular import of data from an external source.
 When a new application is built. This means testing the restore of a
new VM or server when first created.
Ten important steps for testing backups

1. Understand the seriousness of regular backup testing.


2. Create a documented backup testing plan.
3. Make testing backups of routine.
4. Take a holistic approach.
5. Test frequently according to regular schedules.
6. Take full advantage of automation.
7. Ensure that the backup test covers all bases.
8. Make testing backups an integral part of internal app development and
deployment.
9. Ensure backup accuracy.
10. Have redundant backups.
7 Reasons Why Testing Backups is
Critical

 Reason 1: Hardware
 Reason 2: Human Error
 Reason 3: Physical Security
 Reason 4: Technology Change
 Reason 5: Cost
 Reason 6: Restore Speeds
 Reason 7: Learning

You might also like