kennysarmy Posted May 8, 2017 Posted May 8, 2017 One of our file servers became unresponsive over the weekend and I had to restart it last night. On checking the VEEAM logs this morning I see this: 05/05/2017 21:49:56 :: Error: bad allocation Unable to retrieve 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?
Davit2005 Posted May 8, 2017 Posted May 8, 2017 Not one I've seen before. A restart may well of fixed the underlying issue if anything wrong with the server, is this backing up Hyper-V or VMWare? All other backups run smoothly? Enough space on the datastore for Veeam to create snapshots?
kennysarmy Posted May 8, 2017 Author Posted May 8, 2017 Looking through the vSphere logs: error 5/7/2017 9:41:39 PM vpxuser Error message on FP2 on esx01.curriculum.local in Balcarras: NVRAM: write failed. Below is where that fits in to the rest of the log - not sure what any of this means though It's been pretty stable until we've had a new VEEAM backup system put in place! info 5/7/2017 9:43:08 PM Changed resource allocation for FP2 info 5/7/2017 9:42:39 PM CURRICULUM\Admin A ticket for FP2 of type mks on esx02.curriculum.local in Balcarras has been acquired info 5/7/2017 9:42:38 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged in as VMware VI Client/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 Message on FP2 on esx02.curriculum.local in Balcarras: Install the VMware Tools package inside this virtual machine. After the guest operating system starts, select VM > Install VMware Tools… and follow the instructions. info 5/7/2017 9:42:38 PM Changed resource allocation for FP2 info 5/7/2017 9: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/7/2017 9:42:34 PM Virtual machine FP2 is connected warning 5/7/2017 9:42:34 PM Renamed FP2 from /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx to FP2 in Balcarras info 5/7/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 Task: Power On virtual machine info 5/7/2017 9:42:31 PM CURRICULUM\Admin Task: Initialize powering On info 5/7/2017 9:42:17 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged in as VMware VI Client info 5/7/2017 9:42:13 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged in as VMware-client/5.1.0 info 5/7/2017 9:42:12 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged out (login time: Sunday, May 7, 2017 8:42:12 PM, number of API invocations: 3, user agent: VixDiskLib) info 5/7/2017 9:42:12 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged in as VixDiskLib info 5/7/2017 9:42:09 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged in as VMware-client/5.1.0 info 5/7/2017 9:42:07 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged out (login time: Sunday, May 7, 2017 8:33:49 PM, number of API invocations: 7, user agent: VMware VI Client) info 5/7/2017 9:42:03 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged out (login time: Sunday, May 7, 2017 8:42:02 PM, number of API invocations: 2, user agent: VixDiskLib) info 5/7/2017 9:42:02 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged in as VixDiskLib info 5/7/2017 9:41:45 PM CURRICULUM\Admin Task: Create virtual machine snapshot info 5/7/2017 9:41:45 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged in as VMware VI Client info 5/7/2017 9:41:42 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged out (login time: Sunday, May 7, 2017 8:41:42 PM, number of API invocations: 2, user agent: VixDiskLib) info 5/7/2017 9:41:42 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged in as VixDiskLib info 5/7/2017 9:41:41 PM Alarm 'Virtual machine memory usage' on /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx changed from Green to Gray info 5/7/2017 9:41:41 PM Alarm 'Virtual machine CPU usage' on /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx changed from Green to Gray info 5/7/2017 9: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 Error message on FP2 on esx01.curriculum.local in Balcarras: NVRAM: write failed. info 5/7/2017 9:41:39 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged in as Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.34209) info 5/7/2017 9:41:39 PM Changed resource allocation for /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx info 5/7/2017 9:41:39 PM Configuration file for /vmfs/volumes/53cfcacc-72b49f62-3af5-d8d385ac457e/FP2/FP2.vmx on esx01.curriculum.local in Balcarras cannot be found warning 5/7/2017 9: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 5/7/2017 9:41:38 PM CURRICULUM\Admin FP2 on esx01.curriculum.local in Balcarras is stopping info 5/7/2017 9:41:38 PM CURRICULUM\Admin Task: Power Off virtual machine info 5/7/2017 9:41:38 PM CURRICULUM\Admin Task: Remove snapshot info 5/7/2017 9:41:34 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged out (login time: Sunday, May 7, 2017 8:35:35 PM, number of API invocations: 2, user agent: VMware VI Client) info 5/7/2017 9:41:32 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged out (login time: Sunday, May 7, 2017 8:35:31 PM, number of API invocations: 5, user agent: VMware-client/5.1.0) info 5/7/2017 9:41:32 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged out (login time: Sunday, May 7, 2017 8: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\Admin@IPADDRESS logged in as VMware-client/5.1.0 info 5/7/2017 9:41:30 PM CURRICULUM\Admin User CURRICULUM\Admin@IPADDRESS logged out (login time: Sunday, May 7, 2017 8:35:33 PM, number of API invocations: 11, user agent: VMware-client/5.1.0) info 5/7/2017 9:41:30 PM CURRICULUM\Admin Task: Release disk lease
mikkydoos Posted May 8, 2017 Posted May 8, 2017 Veeam 9.5 seems a little more buggy than previous versions. I've had a few issues with Veeam and VMWare. I'd say log a support call.
adhutton Posted May 8, 2017 Posted May 8, 2017 Veeam 9.5 has caused me loads of problems which just didn't exist in Veeam 9.0 Very buggy!! Andrew
localzuk Posted May 8, 2017 Posted May 8, 2017 Are you running Veeam on the same physical server as the VM you're backing up? I had no end of trouble when I had it set up that way.
kennysarmy Posted May 8, 2017 Author Posted May 8, 2017 Are you running Veeam on the same physical server as the VM you're backing up? I had no end of trouble when I had it set up that way. No. VEEAM is on virtual machine - is that what you meant?
localzuk Posted May 8, 2017 Posted May 8, 2017 No. VEEAM is on virtual machine - is that what you meant? Is that VM on the same physical machine as the VM that failed to backup? That's more what I mean. I moved Veeam off our cluster entirely, and it runs on another server.
kennysarmy Posted May 8, 2017 Author Posted May 8, 2017 Is that VM on the same physical machine as the VM that failed to backup? That's more what I mean. I moved Veeam off our cluster entirely, and it runs on another server. We have two ESX hosts - we had two VM's that locked up and failed over the weekend - one was on the same host as the VEEAM VM and the other was not - so inconclusive. 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.
mikkydoos Posted May 8, 2017 Posted May 8, 2017 (edited) Veeam on a VM on the same host is supported. I was advised to run it on its own VM so it can act properly as a proxy when processing other VMs. It can use itself as a proxy when backing up itself but not when processing other VMs in the same job. Edited May 8, 2017 by mikkydoos 1
kennysarmy Posted May 9, 2017 Author Posted May 9, 2017 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 cloud connect to work because VEEAM cannot work through a proxy - it required a direct internet connection - as far as I'm aware all our school traffic has to go through the SWGfL proxies...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now