![]() ![]() Any concerns or other gotchas when dealing with VMWare snapshots over multiple datastores/LUNs?ĥ. All of our other VMs are on single datastores/LUNs. We have several Exchange databases on the same server, but they are spread over multiple drive letters, each with their own datastore/LUN. I don't expect the backup complete in this amount of time, but thought that it would minimize snapshot growth and give me a "jump start" on the first backup.Ĥ. What are your thoughts about stopping all of the Exchange services on the server before starting the backup? I could have a maintenance window in the middle of the night for about 7 hours. Does VEEAM kick off a process to do this and, if not, should I supplement the backup with sometime of manual integrity check?ģ. When I do a Windows backup of Exchange it starts with an "integrity check" that takes several hours. Should I expect VEEAM to finish faster than the Microsoft backup tool? We will be going to the same backup SAN so disk IO should be the same.Ģ. I had a couple questions before I do this with VEEAM the first time.ġ. The Microsoft backup tool takes about 2 whole days start to finish. ![]() I'm currently using Server 2008 R2's built-in Backup and Recovery tool, but want to switch this over to VEEAM next weekend. I've been using VEEAM to backup our VMWare environment for a month or so, but haven't made the jump to backing up Exchange 2010 yet. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |