Veeam Shared Memory Connection Was Closed. Failed to Upload Disk
eighth May 2017,08:12 AM #one
VEEAM failure / Server unresponsive....
One of our file servers became unresponsive over the weekend and I had to restart it concluding night.On checking the VEEAM logs this morning I see this:
05/05/2017 21:49:56 :: Error: bad allocation
Unable to remember next block transmission command. Number of already processed blocks: [16192].
Failed to download disk.
Shared memory connection was closed.
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}.Any ideas anyone?
8th May 2017,08:40 AM #ii
Not one I've seen earlier.A restart may well of fixed the underlying issue if anything wrong with the server, is this backing up Hyper-5 or VMWare?
All other backups run smoothly?
Enough infinite on the datastore for Veeam to create snapshots?
8th May 2017,08:56 AM #3
Looking through the vSphere logs:mistake five/7/2017 ix:41:39 PM vpxuser Mistake message on FP2 on esx01.curriculum.local in Balcarras: NVRAM: write failed.
Below is where that fits in to the residual of the log - not sure what whatever of this means though
It's been pretty stable until we've had a new VEEAM fill-in system put in place!
info 5/seven/2017 9:43:08 PM Inverse resources resource allotment for FP2
info 5/7/2017 ix:42:39 PM CURRICULUM\Admin A ticket for FP2 of type mks on esx02.curriculum.local in Balcarras has been caused
info 5/seven/2017 9:42:38 PM CURRICULUM\Admin User CURRICULUM\[e-mail protected] logged in as VMware 6 Customer/4.0.0
info 5/7/2017 9:42:38 PM DRS powered On FP2 on esx02.curriculum.local in Balcarras
info 5/7/2017 9:42:37 PM vpxuser Bulletin on FP2 on esx02.curriculum.local in Balcarras: Install the VMware Tools package inside this virtual car. Later the guest operating system starts, select VM > Install VMware Tools… and follow the instructions.info 5/7/2017 9:42:38 PM Changed resource resource allotment for FP2
info 5/7/2017 ix:42:35 PM FP2 on host esx02.curriculum.local in Balcarras is starting
info 5/7/2017 9:42:35 PM Completed the relocation of the virtual machine
info 5/seven/2017 9:42:34 PM Virtual machine FP2 is connected
warning five/7/2017 9:42:34 PM Renamed FP2 from /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx to FP2 in Balcarras
info 5/vii/2017 9:42:31 PM Relocating /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx in Balcarras from esx01.curriculum.local, SATA-VMFS-LUN03 to esx02.curriculum.local, SATA-VMFS-LUN03
info 5/7/2017 9:42:31 PM Chore: Power On virtual motorcar
info five/7/2017 9:42:31 PM CURRICULUM\Admin Task: Initialize powering On
info 5/7/2017 ix:42:17 PM CURRICULUM\Admin User CURRICULUM\[email protected] logged in every bit VMware Vi Customer
info 5/seven/2017 nine:42:13 PM CURRICULUM\Admin User CURRICULUM\[e-mail protected] logged in equally VMware-client/5.1.0
info v/7/2017 9:42:12 PM CURRICULUM\Admin User CURRICULUM\[e-mail protected] logged out (login time: Sunday, May vii, 2017 8:42:12 PM, number of API invocations: 3, user amanuensis: VixDiskLib)
info 5/7/2017 9:42:12 PM CURRICULUM\Admin User CURRICULUM\[e-mail protected] logged in equally VixDiskLib
info 5/7/2017 9:42:09 PM CURRICULUM\Admin User CURRICULUM\[email protected] logged in as VMware-customer/5.1.0
info five/7/2017 9:42:07 PM CURRICULUM\Admin User CURRICULUM\[email protected] logged out (login time: Lord's day, May vii, 2017 8:33:49 PM, number of API invocations: vii, user agent: VMware Half-dozen Client)
info 5/7/2017 9:42:03 PM CURRICULUM\Admin User CURRICULUM\[email protected] logged out (login time: Sunday, May 7, 2017 eight:42:02 PM, number of API invocations: two, user agent: VixDiskLib)
info 5/vii/2017 9:42:02 PM CURRICULUM\Admin User CURRICULUM\[email protected] logged in as VixDiskLib
info 5/seven/2017 9:41:45 PM CURRICULUM\Admin Chore: Create virtual auto snapshot
info 5/7/2017 ix:41:45 PM CURRICULUM\Admin User CURRICULUM\[e-mail protected] logged in as VMware VI Client
info 5/7/2017 9:41:42 PM CURRICULUM\Admin User CURRICULUM\[email protected] logged out (login time: Sunday, May 7, 2017 viii:41:42 PM, number of API invocations: 2, user agent: VixDiskLib)
info 5/vii/2017 nine:41:42 PM CURRICULUM\Admin User CURRICULUM\[email protected] logged in equally VixDiskLib
info v/7/2017 ix:41:41 PM Alarm 'Virtual motorcar memory usage' on /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx inverse from Green to Grayness
info 5/7/2017 9:41:41 PM Alarm 'Virtual motorcar CPU usage' on /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx changed from Greenish to Grey
info five/7/2017 nine:41:40 PM CURRICULUM\Admin /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx on esx01.curriculum.local in Balcarras is powered off
error 5/7/2017 9:41:39 PM vpxuser Mistake bulletin on FP2 on esx01.curriculum.local in Balcarras: NVRAM: write failed.info five/7/2017 9:41:39 PM CURRICULUM\Admin User CURRICULUM\[email protected] logged in as Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol four.0.30319.34209)
info 5/vii/2017 nine:41:39 PM Inverse resources allotment for /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx
info five/seven/2017 9:41:39 PM Configuration file for /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx on esx01.curriculum.local in Balcarras cannot exist constitute
warning five/seven/2017 ix:41:39 PM Renamed /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx from FP2 to /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx in Balcarras
info five/7/2017 ix:41:38 PM CURRICULUM\Admin FP2 on esx01.curriculum.local in Balcarras is stopping
info 5/7/2017 nine:41:38 PM CURRICULUM\Admin Task: Power Off virtual machine
info 5/vii/2017 9:41:38 PM CURRICULUM\Admin Job: Remove snapshot
info 5/7/2017 9:41:34 PM CURRICULUM\Admin User CURRICULUM\[e-mail protected] logged out (login fourth dimension: Lord's day, May 7, 2017 8:35:35 PM, number of API invocations: two, user amanuensis: VMware 6 Client)
info 5/7/2017 9:41:32 PM CURRICULUM\Admin User CURRICULUM\[email protected] logged out (login time: Sunday, May 7, 2017 viii:35:31 PM, number of API invocations: five, user agent: VMware-customer/5.i.0)
info v/seven/2017 ix:41:32 PM CURRICULUM\Admin User CURRICULUM\[email protected] logged out (login fourth dimension: Dominicus, May seven, 2017 viii:41:32 PM, number of API invocations: 1, user agent: VMware-client/5.1.0)
info 5/7/2017 9:41:32 PM CURRICULUM\Admin User CURRICULUM\[email protected] logged in as VMware-client/5.i.0
info v/7/2017 9:41:30 PM CURRICULUM\Admin User CURRICULUM\[email protected] logged out (login time: Lord's day, May 7, 2017 viii:35:33 PM, number of API invocations: 11, user amanuensis: VMware-client/5.ane.0)
info v/7/2017 nine:41:30 PM CURRICULUM\Admin Task: Release deejay lease
8th May 2017,10:08 AM #four
Veeam 9.5 seems a little more buggy than previous versions. I've had a few bug with Veeam and VMWare.I'd say log a support call.
8th May 2017,11:fifteen AM #5
Veeam 9.5 has acquired me loads of problems which just didn't exist in Veeam 9.0Very buggy!!
Andrew
8th May 2017,eleven:26 AM #6
Are you running Veeam on the same physical server as the VM you're backing up? I had no stop of trouble when I had information technology set up that way.
8th May 2017,xi:43 AM #7
No.
Originally Posted by localzuk
Are you lot running Veeam on the same physical server as the VM you lot're backing up? I had no finish of trouble when I had it prepare that way.
VEEAM is on virtual automobile - is that what you meant?
8th May 2017,11:47 AM #8
Is that VM on the aforementioned physical machine as the VM that failed to backup? That's more than what I mean. I moved Veeam off our cluster entirely, and it runs on another server.
No.
VEEAM is on virtual car - is that what y'all meant?
8th May 2017,xi:53 AM #9
We have two ESX hosts - we had two VM'south that locked up and failed over the weekend - ane was on the same host as the VEEAM VM and the other was not - so inconclusive.
Is that VM on the aforementioned concrete automobile as the VM that failed to backup? That'south more what I mean. I moved Veeam off our cluster entirely, and it runs on another server.
We moved all the VM's off ESX01 today - rebooted it and have migrated everything back - we'll see how that helps stability going forward this week.
8th May 2017,12:05 PM #10
Veeam on a VM on the same host is supported.I was advised to run it on its own VM then it can human activity properly equally a proxy when processing other VMs.
Information technology can use itself as a proxy when backing upwards itself but non when processing other VMs in the aforementioned job.
Last edited 8th May 2017 at 12:06 PM.
Thanks to mikkydoos from:
9th May 2017,02:52 PM #11
Has anyone got a cloud connect running?I've now been told by the company who sold us the solution that they can't get deject connect to work because VEEAM cannot work through a proxy - it required a direct net connectedness - as far as I'g aware all our school traffic has to go through the SWGfL proxies...
Source: http://www.edugeek.net/forums/enterprise-software/183984-veeam-failure-server-unresponsive.html