<div>
What I've historically done (but workstations were never included in the backup) is to do a restore test monthly or quarterly. Obviously, document the fact that it was performed, along with keeping a screenshot of the result (this way if you have auditors they cannot claim that you somehow produced a fake result). However, you should be ideally keeping track of the backup results daily and fixing them when you notice.<br />
<br />
What is the current backup policy that you have? It's important that you're matching that.
</div>


What I've historically done (but workstations were never included in the backup) is to do a restore test monthly or quarterly. Obviously, document the fact that it was performed, along with keeping a screenshot of the result (this way if you have auditors they cannot claim that you somehow produced a fake result). However, you should be ideally keeping track of the backup results daily and fixing them when you notice.

What is the current backup policy that you have? It's important that you're matching that.

<div>
We don't include workstations either.<br />
<br />
When you say restore, was it on every server?<br />
<br />
Our policy is 30 day incremental, weekly full for 8 weeks, monthly full for 12 months and year end for 7 years.
</div>


We don't include workstations either.

When you say restore, was it on every server?

Our policy is 30 day incremental, weekly full for 8 weeks, monthly full for 12 months and year end for 7 years.

<div>
<div class="content wysiwyg-content">
Hello EE,<br />
<br />
We are putting in a new backup solution and one of the documents I'd like to do in tandem is a Backup recovery test plan. &nbsp;Given there is no way to test every machine every day as a restore scenario, I wonder if there isn't some sort of template or something a peer would have out there and willing to share as a guideline. &nbsp;If something is found to be tried and true, I'd like to build from that rather than start from scratch
</div>
</div>


Hello EE,

We are putting in a new backup solution and one of the documents I'd like to do in tandem is a Backup recovery test plan.  Given there is no way to test every machine every day as a restore scenario, I wonder if there isn't some sort of template or something a peer would have out there and willing to share as a guideline.  If something is found to be tried and true, I'd like to build from that rather than start from scratch

Backup Recovery test plan template assistance?

Disaster Recovery is the planning for and creation of policies and procedures related to the resumption or continuation of an organization's functions following a catastrophic event. The term is most frequently used in relation to failure of networks, but DR preparations also include other business systems and personnel considerations.

Disaster Recovery

The term "Backup" means the methods and processes involved to copy computer data (system data as well as application data) to media other than the ones where the data originally live (disk, tape, optical, cloud). "Restore" in turn means the methods and processes involved in data recovery, i. e., bringing back copied computer data to their original location. Backup/Restore primarily serves as a means of protection against data loss, be it due to disaster, corruption or sabotage. It can also be used for recovering data from an earlier point in time and even for cloning machines or applications. There is a wide variety of backup/restore software available, from expensive commercial products to free or open source tools.