When running Sure Backup Jobs for Exchange, i often encounter the error
"Mount with leaseid 'b4d5c2c-f64a-41cg3fs94-1f6b48382490' already activated".
Contacted support on this issue and i was asked to restart the Veeam server. It works after restart, but keeps coming back again.
The backups repo is a dedup appliance.
Thanks
-
- Veteran
- Posts: 367
- Liked: 41 times
- Joined: May 15, 2012 2:21 pm
- Full Name: Arun
- Contact:
-
- Chief Product Officer
- Posts: 31766
- Liked: 7266 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Sure Backup Job errors-Case no:00127518
Hi Arun, I am not sure what is the question here. Did support refuse to further troubleshoot this issue for you? Thanks.
-
- Veteran
- Posts: 367
- Liked: 41 times
- Joined: May 15, 2012 2:21 pm
- Full Name: Arun
- Contact:
Re: Sure Backup Job errors-Case no:00127518
Hi Gostev,
No support did not refuse to further troubleshoot this issue.
I posted the error with the case no. just in case if i could get some idea from anyone on why the error was happening because previous resolution from support of rebooting the Veeam server didn't work this time.
The case was escalated to the next level yesterday and they did a good job trying to resolve it.
What was done was ,the registry on the Veeam server needed some tweaking and all old entries under HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\ItemsCache had to be removed.
Also the settings of the repository were tweaked from the Veeam console.
1) Decompress backup data block before storing was checked.
2) Path to the vPower NFS root folder was changed.
3) The option to 'Write data to this share: Through the following proxy server was selected' instead of 'Directly from backup proxy server' ( Not certain if this makes a difference)
It seems to be working now.
Thanks
No support did not refuse to further troubleshoot this issue.
I posted the error with the case no. just in case if i could get some idea from anyone on why the error was happening because previous resolution from support of rebooting the Veeam server didn't work this time.
The case was escalated to the next level yesterday and they did a good job trying to resolve it.
What was done was ,the registry on the Veeam server needed some tweaking and all old entries under HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\ItemsCache had to be removed.
Also the settings of the repository were tweaked from the Veeam console.
1) Decompress backup data block before storing was checked.
2) Path to the vPower NFS root folder was changed.
3) The option to 'Write data to this share: Through the following proxy server was selected' instead of 'Directly from backup proxy server' ( Not certain if this makes a difference)
It seems to be working now.
Thanks
-
- Veteran
- Posts: 367
- Liked: 41 times
- Joined: May 15, 2012 2:21 pm
- Full Name: Arun
- Contact:
Re: Sure Backup Job errors-Case no:00127518
The error has come back again and the issue needs further investigation. Today morning got a mail from support saying
'Mount lease ID already activated' is a common issue and our developers have already confirmed the bug. Note that this bug affects only slow storages or for example in case of a big number of incremental restore points, when storage experiences high load.
This bug will be fixed in the first hotfix for Veeam 6.5. '
For now as a workaround is to manually restart NFS service.
Thanks
'Mount lease ID already activated' is a common issue and our developers have already confirmed the bug. Note that this bug affects only slow storages or for example in case of a big number of incremental restore points, when storage experiences high load.
This bug will be fixed in the first hotfix for Veeam 6.5. '
For now as a workaround is to manually restart NFS service.
Thanks
Who is online
Users browsing this forum: No registered users and 28 guests