Need help in creating a backup plan (template)

A backup plan needs to specify for each data store (i.e., application, database, file server, etc.):
- How much data can I afford to lose?  This is called the Recovery Point Objective (RPO).  Maybe you can afford to lose a day's worth of email, an hour's worth of personnel data, and only a minute's worth of orders.  In general, the less data you can afford to lose, the more expensive the solution will be.
- How long can this data store be allowed to be down?  This is called the Recovery Time Objective (RTO).  Maybe manufacturing has to be back up in an hour, while email can be down for three hours.  In general, the shorter the desired recovery time, the higher the cost of the solution.
- What are my legal and business requirements for data retention?  Tax data may have to be kept for three or seven years.   Contracts and related data needs to be kept for the length of the contract and another year or two.  Medical records may need to be kept for the life of the patient plus a few years.
- Are there legal or business requirements for encrypting the data?  
- What is the budget?  Knowing how much money the business principles want to spend, you can try to develop a solution that meets the requirements.  Of course, it may well be that people have an unrealistic idea of how much a data protection solution costs... but if you know the requirements, you can go back to them and say, "If this is the requirement, the cheapest solution is ____.  Or, we can leave out x and y and do it or $z."
- What are the most likely threats?  Accidental or intentional deletion of data?  Employee theft?  Power outages?  Natural Disasters?  Hardware failure?  Computer virus or other malicious code?    Each of these can require a different solution to keep the business up and running.


To develop your backup plan, you need to understand the business needs (and possibly legal requirements) that go into each of those four areas. Once you know that certain systems need to be back up and running in two hours, you can ask intelligent questions here about what kind of solution would meet that need.  

Some things to keep in mind:
- Copies on disk don't do a good job of meeting archival needs
- Backups to the cloud may not give you good restore times (RTO)
- Encryption is increasingly important, and has become easy.  Key management, on the other hand, can be more of a challenge, and is critically important -- lose your keys, lose your data.

Appreciate if you can provide  template/example for doing the same.

Many thanks,
Little bit struggling in the beginning, but when  completed one server it is become easy.