Any ideas as to what happens if DRS is kicked in during Veeam backup or if a manual move is kicked in - Does it impact or cause the Veeam backup to fail?
How much does the service console memory come into play when using Veeam backup?
-
- Influencer
- Posts: 17
- Liked: never
- Joined: Dec 24, 2009 2:39 am
- Full Name: Chet
- Contact:
-
- Chief Product Officer
- Posts: 31753
- Liked: 7257 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: DRS during Veeam Backup
Jobs using direct SAN access processing modes will not be affected (because the VM disk data is read directly from shared storage). What will be affected is legacy host-based backup mode ("Network" mode, 3rd radiobutton) in the mode selection step - this limitation is documented in the Known Issues section of the Release Notes document.
Service console is not used by Veeam Backup other than for the said legacy host-based backup mode, and to speed up restores when restoring to "fat" ESX. Veeam Backup will work fine with the default service console memory settings, so you do not really need to tweak those. I have also seen some recommendation on the Internet about increasing ESX service console memory in order to improve snapshot processing performance, but I don't believe they come from VMware and are official/recommended.
Service console is not used by Veeam Backup other than for the said legacy host-based backup mode, and to speed up restores when restoring to "fat" ESX. Veeam Backup will work fine with the default service console memory settings, so you do not really need to tweak those. I have also seen some recommendation on the Internet about increasing ESX service console memory in order to improve snapshot processing performance, but I don't believe they come from VMware and are official/recommended.
Who is online
Users browsing this forum: Bing [Bot], Dima P. and 96 guests