Hello,
I am a new customer of Veeam and have this serious issue.
I have Exchange 2010 environment on vSphere 5.1 that must have backups and consists of several VM's including 3 Mailbox Servers.
Each Mailbox server have 15 disks connected to it and all of them were created as mount points inside the servers, with MS recommendation.
I am able to successfully create backup with HotAdd on every VM, except for the mailbox servers.
Each time I am trying to create backup of one of the mailbox servers, I'm getting error HotAdd is not supported - failing to Network mode, this result in the backup process 50MB/S instead of 250MB/S, which in turn takes hours to backup the entire VM since the entire VM is 5TB, not to mention that after 1 successful backup, removing the snapshot from the VM takes also hours.
I double checked everything that should prevent me from using HotAdd, including creating 3 more SCSI controllers to avoid SCSI issues, nothing is helping me out.
Can anyone assist me with this?
-
- Novice
- Posts: 9
- Liked: never
- Joined: May 08, 2013 7:00 am
- Full Name: Tomer Leibovich
- Contact:
-
- Product Manager
- Posts: 20400
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Case#00441074 - HotAdd not supported
Hi, Tomer. Have you already seen the list of VMware Hot-ADD limitations? Also, it might be worth double checking whether disks in questions are ISCSI, not IDE ones. Thanks.
-
- Novice
- Posts: 9
- Liked: never
- Joined: May 08, 2013 7:00 am
- Full Name: Tomer Leibovich
- Contact:
Re: Case#00441074 - HotAdd not supported
Hi,
The disks are ISCSI and already checked the list, so far so good but still not so good.
The disks are ISCSI and already checked the list, so far so good but still not so good.
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Case#00441074 - HotAdd not supported
Then let's wait for what support can come up with, as the exact reason of the failure to use hotadd should clearly be stated in the corresponding job log.