Source:Backup Strategy Best Practices: Difference between revisions
mNo edit summary |
No edit summary |
||
Line 21: | Line 21: | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]. | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]. | ||
|}</div></noinclude> | |}</div></noinclude> | ||
A comprehensive backup strategy, along with a disaster recovery plan, is an essential part of protecting any business from data loss (e.g., from disk failures, malware attacks, human error | A comprehensive backup strategy, along with a disaster recovery plan, is an essential part of protecting any business from data loss (e.g., from disk failures, malware attacks, human error). To be fully protected, you need an efficient data protection strategy that helps recover lost data quickly and seamlessly and ensures business continuity when all preventive measures fail. Therefore your critical business data must be backed up regularly (on different media and off-site) and available for restore in the case of a data loss. | ||
Before you | Before you begin developing a backup strategy, consider the following: | ||
*Determine what | *Determine what is critical data (is vital to the survival and continued business operation) and how often should it be backed up. Note that the frequency of backups must be tailored to your specific business requirements. | ||
* | *Determine where the data is backed up: local/on-site vs. cloud/remote backup. | ||
*Decide how accessible backups should be to keep your business running. | *Decide how accessible backups should be to keep your business running. Understand the difference between disaster recovery and backups. | ||
A backup strategy and a disaster recovery plan constitute the all-encompassing business continuity plan that is essential to keeping an operation going following a hardware failure, human error, hacking, malware, etc., resume operations and recover as quickly as possible. | |||
{{tip|SEP sesam provides both, long-term retention of your multiple versions of business data (backups) as well as a DR solution for your business infrastructure. Talk to SEP sesam experts to help you build a business continuity plan that includes disaster recovery for your critical infrastructure or use [https://www.sep.de/sep-sesam/backup-as-a-service/ SEP sesam Backup as a Service ].}} | |||
==Recommended backup strategies== | ==Recommended backup strategies== | ||
There are several backup strategies available to protect your environment | There are several backup strategies available to protect your environment that can be easily implemented with SEP sesam. So far, the [[Special:MyLanguage/GFS_Backup_Retention_Strategy|GFS backup rotation strategy]], where backups rotate daily, has proven to be efficient, but the backups are only stored on tapes, so GFS does not provide optimal protection against data loss. | ||
In addition to regular backups and thoughtful scheduling, storing your data in multiple locations ensures that you always have a local copy as well as a copy stored securely in another location. By keeping backup copies both locally and off-site (especially in the cloud), you double the protection of your data in the event of a disaster. | In addition to regular backups and thoughtful scheduling, storing your data in multiple locations ensures that you always have a local copy as well as a copy stored securely in another location. By keeping backup copies both locally and off-site (especially in the cloud), you double the protection of your data in the event of a disaster. | ||
The 3-2-1 backup strategy is an evolution of the tape-based strategy, where you only have one media copy and you need to put it to an off-site location. With SEP sesam you can implement a 3-2-1 strategy or its variations (e.g., 3-1-2), but keep in mind that each storage solution has drawbacks. To choose the right solution, you must develop a backup storage strategy based on your unique business requirements. | The 3-2-1 backup strategy is an evolution of the tape-based strategy, where you only have one media copy and you need to put it to an off-site location. With SEP sesam you can implement a 3-2-1 strategy or its variations (e.g., 3-1-2), but keep in mind that each storage solution has its drawbacks. To choose the right solution, you must develop a backup storage strategy based on your unique business requirements. | ||
Regardless of which backup strategy you choose, you should consider the following to efficiently protect your data: | Regardless of which backup strategy you choose, you should consider the following to efficiently protect your data: | ||
Line 42: | Line 44: | ||
*Test your backups regularly. | *Test your backups regularly. | ||
*Keep the storage repository for backups clear and organized. | *Keep the storage repository for backups clear and organized. | ||
Before implementing any strategy, make sure that your SEP sesam environment is properly configured to be able to use reliable storage and perform backups successfully. For details, see [[Special:MyLanguage/SEP_sesam_Configuration_–_First_Steps|SEP sesam Configuration – First Steps]]. | |||
===3-2-1 backup strategy=== | ===3-2-1 backup strategy=== | ||
The 3-2-1 backup strategy means that you have three copies of your data (your production data and two backup copies) on two different media (disk and tape) and one copy off-site (cloud, storage unit, etc.) for disaster recovery. All copies contain the same data from the same point in time. This method aims to recover at least one copy of the data when the others fail or disappear. | The 3-2-1 backup strategy means that you have three copies of your data (your production data and two backup copies) on two different media (disk and tape) and one copy off-site (cloud, storage unit, etc.) for disaster recovery. All copies contain the same data from the same point in time. This method aims to recover at least one copy of the data when the others fail or disappear. | ||
To implement the 3-2-1 strategy with SEP sesam, proceed as follows: | To implement the 3-2-1 strategy with SEP sesam, proceed as follows: | ||
<ol><li>Back up your critical data to the first media (typically a | <ol><li>Back up your critical data to the first media (typically a data store) following [[Special:MyLanguage/Standard_Backup_Procedure|Standard Backup Procedure]].</li> | ||
<li>Back up the data (another copy of data) to the second media (typically a tape) that is separate from one another, even if they are in the same geographic location. For more details on supported devices, see [[Special:MyLanguage/Managing_Devices_and_Media|Managing Devices and Media]].</li> | <li>Back up the data (another copy of data) to the second media (typically a tape) that is separate from one another, even if they are in the same geographic location. For more details on supported devices, see [[Special:MyLanguage/Managing_Devices_and_Media|Managing Devices and Media]].</li> | ||
{{Note|With SEP sesam migration you can also set up a disk-to-disk-to-tape (D2D2T) backup strategy to reduce your backup and recovery times, move older data offsite for long-term data retention and prepare for disaster recovery. For details, see [[Special:MyLanguage/Configuring_Migration|Configuring Migration]].}} | {{Note|With SEP sesam migration you can also set up a disk-to-disk-to-tape (D2D2T) backup strategy to reduce your backup and recovery times, move older data offsite for long-term data retention and prepare for disaster recovery. For details, see [[Special:MyLanguage/Configuring_Migration|Configuring Migration]].}} | ||
<li>Back up the third copy of data (or replicate it in the case of a cloud) to an offsite location, such as another office, a data center, offsite tape, a cloud (e.g., HPE Cloud Bank Storage or S3), etc. If you are copying the data to the cloud, see the SEP sesam documentation on [[Special:MyLanguage/S3_Cloud|S3 Cloud]] or [[Special:MyLanguage/HPE_StoreOnce|HPE StoreOnce]].</li></ol> | <li>Back up the third copy of data (or replicate it in the case of a cloud) to an offsite location, such as another office, a data center, offsite tape, a cloud (e.g., HPE Cloud Bank Storage or S3), etc. If you are copying the data to the cloud, see the SEP sesam documentation on [[Special:MyLanguage/S3_Cloud|S3 Cloud]] or [[Special:MyLanguage/HPE_StoreOnce|HPE StoreOnce]].</li></ol> | ||
===3-1-1/3-1-2 strategy variations=== | ====3-1-1/3-1-2 strategy variations==== | ||
In addition to the classic 3-2-1 backup strategy | In addition to the classic 3-2-1 backup strategy, you can also store one (3-1-1) or two (3-1-2) copies of your critical data in the cloud. | ||
<ol><li>Back up your critical data to disk by following [[Special:MyLanguage/Standard_Backup_Procedure|Standard Backup Procedure]].</li> | <ol><li>Back up your critical data to disk by following [[Special:MyLanguage/Standard_Backup_Procedure|Standard Backup Procedure]].</li> | ||
<li>[[Special:MyLanguage/SEP_sesam_Glossary#replication|Replicate]] the copy of your data to the [[Special:MyLanguage/S3_Cloud|S3 Cloud]] or [[Special:MyLanguage/HPE_StoreOnce|HPE Cloud Bank Storage.]]</li> | <li>[[Special:MyLanguage/SEP_sesam_Glossary#replication|Replicate]] the copy of your data to the [[Special:MyLanguage/S3_Cloud|S3 Cloud]] or [[Special:MyLanguage/HPE_StoreOnce|HPE Cloud Bank Storage.]]</li> | ||
<li>If you are using the 3-1-2 strategy, replicate another copy of the data to the cloud; otherwise, skip this step. If you are using the same cloud, make sure that the copies are geographically separated, but you can also use a different cloud.</li></ol> | <li>If you are using the 3-1-2 strategy, replicate another copy of the data to the cloud; otherwise, skip this step. If you are using the same cloud, make sure that the copies are geographically separated, but you can also use a different cloud.</li></ol> | ||
===3-2-2 backup strategy === | |||
===3-2-3 backup strategy=== | |||
<noinclude>==See also== | <noinclude>==See also== | ||
[[Special:MyLanguage/Standard_Backup_Procedure|Standard Backup Procedure]] – [[Special:MyLanguage/S3_Cloud|S3 Cloud]] – [[Special:MyLanguage/HPE_StoreOnce|HPE StoreOnce]] – [[Special:MyLanguage/Managing_Devices_and_Media|Managing Devices and Media]] – [[Special:MyLanguage/4_4_3_Beefalo:About_Replication|About Replication]] – [[Special:MyLanguage/4_4_3_Beefalo:Ransomware_Protection_Best_Practices|Ransomware Protection Best Practices]]</noinclude> | [[Special:MyLanguage/Standard_Backup_Procedure|Standard Backup Procedure]] – [[Special:MyLanguage/S3_Cloud|S3 Cloud]] – [[Special:MyLanguage/HPE_StoreOnce|HPE StoreOnce]] – [[Special:MyLanguage/Managing_Devices_and_Media|Managing Devices and Media]] – [[Special:MyLanguage/4_4_3_Beefalo:About_Replication|About Replication]] – [[Special:MyLanguage/4_4_3_Beefalo:Ransomware_Protection_Best_Practices|Ransomware Protection Best Practices]]</noinclude> |
Revision as of 10:58, 16 March 2021
Overview
A comprehensive backup strategy, along with a disaster recovery plan, is an essential part of protecting any business from data loss (e.g., from disk failures, malware attacks, human error). To be fully protected, you need an efficient data protection strategy that helps recover lost data quickly and seamlessly and ensures business continuity when all preventive measures fail. Therefore your critical business data must be backed up regularly (on different media and off-site) and available for restore in the case of a data loss.
Before you begin developing a backup strategy, consider the following:
- Determine what is critical data (is vital to the survival and continued business operation) and how often should it be backed up. Note that the frequency of backups must be tailored to your specific business requirements.
- Determine where the data is backed up: local/on-site vs. cloud/remote backup.
- Decide how accessible backups should be to keep your business running. Understand the difference between disaster recovery and backups.
A backup strategy and a disaster recovery plan constitute the all-encompassing business continuity plan that is essential to keeping an operation going following a hardware failure, human error, hacking, malware, etc., resume operations and recover as quickly as possible.
Tip | |
SEP sesam provides both, long-term retention of your multiple versions of business data (backups) as well as a DR solution for your business infrastructure. Talk to SEP sesam experts to help you build a business continuity plan that includes disaster recovery for your critical infrastructure or use SEP sesam Backup as a Service . |
Recommended backup strategies
There are several backup strategies available to protect your environment that can be easily implemented with SEP sesam. So far, the GFS backup rotation strategy, where backups rotate daily, has proven to be efficient, but the backups are only stored on tapes, so GFS does not provide optimal protection against data loss.
In addition to regular backups and thoughtful scheduling, storing your data in multiple locations ensures that you always have a local copy as well as a copy stored securely in another location. By keeping backup copies both locally and off-site (especially in the cloud), you double the protection of your data in the event of a disaster.
The 3-2-1 backup strategy is an evolution of the tape-based strategy, where you only have one media copy and you need to put it to an off-site location. With SEP sesam you can implement a 3-2-1 strategy or its variations (e.g., 3-1-2), but keep in mind that each storage solution has its drawbacks. To choose the right solution, you must develop a backup storage strategy based on your unique business requirements.
Regardless of which backup strategy you choose, you should consider the following to efficiently protect your data:
- Schedule your backups to keep them up to date automatically. For details, see Scheduling.
- Test your backups regularly.
- Keep the storage repository for backups clear and organized.
Before implementing any strategy, make sure that your SEP sesam environment is properly configured to be able to use reliable storage and perform backups successfully. For details, see SEP sesam Configuration – First Steps.
3-2-1 backup strategy
The 3-2-1 backup strategy means that you have three copies of your data (your production data and two backup copies) on two different media (disk and tape) and one copy off-site (cloud, storage unit, etc.) for disaster recovery. All copies contain the same data from the same point in time. This method aims to recover at least one copy of the data when the others fail or disappear.
To implement the 3-2-1 strategy with SEP sesam, proceed as follows:
- Back up your critical data to the first media (typically a data store) following Standard Backup Procedure.
- Back up the data (another copy of data) to the second media (typically a tape) that is separate from one another, even if they are in the same geographic location. For more details on supported devices, see Managing Devices and Media.
- Back up the third copy of data (or replicate it in the case of a cloud) to an offsite location, such as another office, a data center, offsite tape, a cloud (e.g., HPE Cloud Bank Storage or S3), etc. If you are copying the data to the cloud, see the SEP sesam documentation on S3 Cloud or HPE StoreOnce.
Note | |
With SEP sesam migration you can also set up a disk-to-disk-to-tape (D2D2T) backup strategy to reduce your backup and recovery times, move older data offsite for long-term data retention and prepare for disaster recovery. For details, see Configuring Migration. |
3-1-1/3-1-2 strategy variations
In addition to the classic 3-2-1 backup strategy, you can also store one (3-1-1) or two (3-1-2) copies of your critical data in the cloud.
- Back up your critical data to disk by following Standard Backup Procedure.
- Replicate the copy of your data to the S3 Cloud or HPE Cloud Bank Storage.
- If you are using the 3-1-2 strategy, replicate another copy of the data to the cloud; otherwise, skip this step. If you are using the same cloud, make sure that the copies are geographically separated, but you can also use a different cloud.
3-2-2 backup strategy
3-2-3 backup strategy
See also
Standard Backup Procedure – S3 Cloud – HPE StoreOnce – Managing Devices and Media – About Replication – Ransomware Protection Best Practices