![]() Plus, Instant Recovery is not designed to keep VMs running for long periods of time, just long enough to move them to a "real" host. Certainly you can push the technology, I've worked with one customer to get to 17 VMs booting from instant restore, and I've heard stories of 20+ VMs, but that's still a long way from 750 VMs. IVR is a "spare tire" designed to quickly recover a VM or a small set of VMs. ![]() That's simply not what it's designed to do and is far beyond it's design capabilities. The one problem with your theory is the idea that you could power on 750 VMs via IVR. 00000099% chance that something happens to my primary site. I can replicate 50, and have some assurance that the other 750 could be powered on via IVR, for the. This way I don't have to go through all the complexity of replication 800 vm's every night. Those vm's that aren't mission critical, I was hoping to leverage IVR at another site. What I was looking to do is to only replicate those 50 mission critical vm's for DR. The Cloud Edition will work great for long term storage and to move off of tape for long term. Obviously, I wouldn't need to restore a 2 year old vm. You obviously wouldn't be able to perform a IVR into Azure's/AWS's proprietary vm offerings. Not sure that the big guys like Amazon or Azure would let you have your own hypervisor server at their site. You would have to find a cloud vendor that would let you host your own Hypervisor in their cloud. It sounds like your "mover" example would work in order to perform Instant Recoveries in the Cloud. Through reading the documentation, I wasn't sure whether the Veeam Cloud copy was broken out into individual files for individual file restore only. That is good to know that the Cloud Edition would give you access to the. I think it can be considered a form of DR in some cases ![]() BTW, I use instant recovery on a weekly basis for both Hyper-v and VMWare, and it has never failed. But if I am going to copy my backups to another site, and if Veeam has this awesome feature of Instant Recovery, I think I would rather kill 2 birds with one stone and archive them to a place where I can do vm-level and file restores. I understand the Veeam Cloud Service as an avenue to get rid of tapes and for archiving. That way I have access to Hypervisors where I can do instant vm recoveries over a few weeks. I would think I would be in a better place from a DR perspective if those other 750 vm's Veeam backups were being replicated to a co-location site instead of the Veeam Cloud Service. In the event of a disaster, I could bring these 750 vm's up through instant recoveries over a few weeks. ![]() I would think that since these 750 vm's weren't deemed mission critical by the business that backups at another location along with the option for instant recovery would be sufficient. I could replicate all 800 of the vm's to another site as well as backup to the Veeam Cloud Service, but then I am storing 2 copies at another site - 1 for replication and 1 for backups in order to go tapeless. But what about those other 750 vm's, some being very important. Your 50 business critical machines are brought online at your DR site. There is a disaster at your primary site and you lose all 800 vm's. All 800 vm's get backed onsite with Veeam and also to the Veeam Cloud Service. ![]() The 50 vm's get replicated to another site. If I have 800 vm's and 50 of them are deemed "business critical" by the business. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |