![]() ![]() Using native quiescing does not prevent you from doing app-aware restores using the Veeam Explorer tool for AD/Exchange/SQL/Oracle either. I also use an admin accounts to do guest file system indexing on our file server VMs, but most VMs don't need this. I use this method for all of my VMs except for SQL Server VMs where I want Veeam to truncate the SQL transaction logs. This removes the need for Veeam to have admin access to the VM. ![]() Most organizations rely on hybrid solutions that combine the cloud, virtualized IT infrastructures and physical servers. You can use VMTools (for VMWare) or Hyper-V Native Quiescence which means VMWare or Hyper-V will inform the guest to take a VSS snapshot rather than Veeam. Windows and Physical Servers Backup Best Practices. I guess, if you want to have an consistent domaincontroller backup you need full administrator right on it. Consider that some tasks within a job are still sequential processes. By using multiple VM per job we will reduce management complexity, as it’s much easier to manage a small amount of jobs than trying to manage hundreds of jobs. Avoid using one VM per job unless is strictly necessary. Unfortunately it is impossible - we need access to ADMIN$ of the guest VM in order to upload VSS agents, and for generic VM you can you can use local admin, but it is disabled on DCs.Īnother solution would be to backup this machine without VSS, but you would have to create DC DB using some other tool as it will be inconsistent without VSS. For per VM backup files: up to 300 VMs per job. I have asked that question about 3 years ago in a support ticket and the answer I got is this: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |