I've restored Exchange Server VMs in this manner before, as well as our vCenter VM, and all has been fine. We plan to P2V this server (I'd much prefer to throw up a clean VM and import the data, but Sage costs for this are extremely restrictive) in the next few months, and I had just assumed that, due to Application-aware processing/ticking the box to flush logs on successful backup, we could just do away with the SQL maintenance plan (because a restored VM via Veeam is to a point in time, and at that point in time, logs will have been flushed, so if we restore to it, then I don't see that there would be a problem?). However, we don't have the SQL module for BE, and so there is a maintenance plan running daily from within SQL, in order to commit/flush the transaction logs. Right now, we have the DB server of our CRM system, which is still physical, hosting SQL, and being backed up to tape by BackupExec.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |