![]() ![]() This isn’t a common practice, but for absolutely critical datasets, it is an attractive option. A VM backup, an agent-based backup, a file-based backup and even an application plug-in backup can be used in conjunction with each other. I have even had some organizations over the years do some interesting things in having systems backed up multiple times with Veeam. Backup copy jobs to another storage location.Replication to another host or site with Veeam replication.Backups hosted or managed by a service provider, including Veeam Cloud Connect.Backups in cold archive storage in the public cloud with the Scale-out Backup Repository’s archive tier.Backups in object storage such as in the public cloud with the Scale-out Backup Repository’s capacity tier.Storage snapshots (caution on separate media from production).Backups on disk (DAS, SAN, NAS and appliances).This is very versatile nowadays and each of the following implementations would count towards a 3-2-1 Rule configuration: In the scope of Veeam, one of the things I love about being a software provider with a strong lineup of partnerships is that Veeam can dial up so many combinations of the 3-2-1 Rule. This means of the 2 other copies, the different media is a must-have and the versatility to restore needs to be considered.įor the organizations I talk to nowadays, I see the most critical data sets having 4 copies when the production data is also included. Some people don’t like to include the production data as a copy in the 3-2-1 Rule, and it’s worth bringing that up. ![]() This has 3 different media, so it actually exceeds the criteria.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |