Error: Shared memory connection was closed

[frankive]

I have a SBS 2011 server I want to protect. Trying Veeam Endpoint Backup. Backing up to a usb-drive connected mapped to B:
The 10 other servers I have tested all work fine!

The error messiage I get is:

4/15/2015 3:25:42 PM :: Error: Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: The system cannot find the file specified. Failed to write data to the file [B:\VeeamBackup\Backup Job DC01\Backup Job DC012015-04-15T151952.vbk]. Failed to download disk.

I can confirm the b: (usb-drive) is online and works fine.

[Dima P.]

Hello Frank,
For an issue like this application logs are required for troubleshooting. Could you, please, open a support case thru the Veeam Endpoint Backup Control Panel > Support? Thank you in advance.

[frankive]

Thanks. Opened a case. Looking forward to see what might cause this.

[Dima P.]

Frank,
Thanks. The error refers to the mechanism used for components to “talk” with each other. Might be a memory overrun, but, honestly, I am just guessing now. Let’s wait for support and QA investigation.

[marius roma]

Maybe my experience can be of any help.
Aftare replacing the USB wireless network adapter on a Windows 8.1 64bit PC I started getting the following error, similar but not identical to yours:
04/05/2015 20.05.45 :: Error: Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Periodo di timeout del semaforo scaduto. Error code: 121 Failed to write data to the file [G:\VeeamBackup\Backup Job PCNAME\Backup Job PCNAME2015-05-04T195527.vbk]. Failed to download disk. (The semaphore timeout period has expired)..
I made several tests including removing and reinstalling VEB before deciding to remove the new USB wireless adapter.
At that point VEB started working again.
I presume the USB wireless network adapter is damaged because the brand and the model look to be the same as athe previous USB wireless network adapter and because the same device failed working on a Linux box (that's the reason because I swapped it with the working one).
Hope this helps...
Marius

[Dima P.]

Hello Mario,
Thanks for the heads up, but please next time do not forget to create a support case thru Veeam Endpoint Backup Control Panel. We offer free support at best effort and submitting issues will help us to improve the quality of the product

[frankive]

my issue was a bad hard drive. after placing the usbdrive the job went through.

[Vitaliy S.]

Thanks for coming back and updating the topic!

[marius roma]

After upgrading from Windows 8.1 to Windows 10 and formatting the target USB drive I was unable to complete any backup job.
The errors I get include:

Code: Select all

22/11/2015 22.33.35 :: Preparing for backup 
22/11/2015 22.35.22 :: Creating VSS snapshot 
22/11/2015 22.40.04 :: Unable to exclude files from snapshot: Shadow Copy Optimization Writer timed out (see Windows event log for more info). 
22/11/2015 22.40.13 :: Calculating digests 
(...)
23/11/2015 5.00.40 :: Failed to backup [<filename>] 
23/11/2015 5.00.55 :: Finalizing 
23/11/2015 5.01.34 :: Error: Shared memory connection was closed. Agent failed to process method {FileBackup.SyncDirs}. Exception from server: Failed to decompress LZ4 block: Bad crc (original crc: 18180b2f, current crc: 59bd69bf).  
                   :: Processing finished with errors at 23/11/2015 5.01.45 

I had a very similar error the night before, with the process closing while processing a different file of the same disk.
I executed chkdsk /f /r on the disk containing the file <filename> with no error reported.
Is the problem related to the installed program (should I reinstall it?), to the source drive, to the target or to what else?
Regards
marius

[Mike Resseler]

What version were you running at the moment you upgrades to windows 10? Was that a supported version already? Just to verify and to be sure you aren't running v1 which doesn't work in Windows 10.

From what I can see in the snippet, it looks like there is a problem with the vss. And after that, I see an issue with a crc... If you have a supported version, please log a support case through the control panel, our support guys will need more info to figure out what and where it went wrong

Thanks

Mike

[Dima P.]

Hey guys,

Test your source disk (and target repository as well) for bad blocks with any 3rd party tool (for example http://hddscan.com/) - check disk might be not that accurate to be honest.

[marius roma]

I made some further investigation and it looks like there was a problem with the USB ports on the PC and/or the drivers used to manage the USB disk.
I reinstalled the drivers and created a new job to copy only part of the source files and it run successfully.
I changed the settings to extend the data backed up by the job and it worked fine again.
Now it looks to work fine.
Thank you for your support.
Marius

[Rageboom]

Hi everyone,

I have a problem with a VEP backup onto a Backup & Replication repository.
I can configure my backup, but it always fails with the following message:

"02/03/2016 16:51:05 :: Error: Shared memory connection was closed. Agent failed to process method {FileBackup.SyncDirs}. Exception from server: There are no connections in the specified pool 3. "

My permissions are fine on my Backup&Replication repository.

Here are the versions of my software:
Veeam Endpoint: 1.1.2.119
Veeam Backup & Repository : 8.0.0.2084

Do you have any ideas?

Thanks!

[JaxIsland7575]

Welcome Rageboom to the forums!

There is another thread relating to your issue over here

You may want to try and check the drivers or run a scan on the hard drive but the first thing I would suggest is going into the Control Panel of Veeam and submitting a case so they can review the log files of the backups.

Please post your case ID back here when you have it.

Cheers!

[Rageboom]

Hi.

I saw this thread but didn't found any solutions, that's why I opened a new thread .

I opened a case from my VEP, here is the ID : 01716163.

Cheers.

[Rageboom]

Hello everyone,

Support helped me this morning. if you guys have this message :

"02/03/2016 16:51:05 :: Error: Shared memory connection was closed. Agent failed to process method {FileBackup.SyncDirs}. Exception from server: There are no connections in the specified pool 3. " , you probably changed one setting on your Backup & Replication server. To fix it, follow these steps :
1. Open Backup & Replication
2. Open your properties (top left corner)
3. Network Traffic
4. Check the number near "Use multiple upload streams per job". Endpoint need at least 3 streams to work.

Good luck =)/

[Dima P.]

Rageboom,

Thanks for getting back to us and sharing the solution. This options should be set to at least 2 as per Known Issues in the Release Notes document. Cheers!

[JWalkerMR]

Hello,

i had the same error message after installing a new usb wlan stick. Simply changing the backup target to a new directory solved this issue.

[Dima P.]

Hi JWalkerMR and welcome to the community,

You had the same issue while backing up to the local repository or shared folder destination, right?

[JWalkerMR]

Hi Dima,

yes, i got the error message "Error: Shared memory connection was closed" when trying backing up to the previous used USB 3.0 harddisk after installing a new USB 3.0 WLAN stick. Even removing this WLAN stick and uninstalling the drivers didn't help. The solution was to create a new backup directory.

[ds2]

I've seen this error - caused by a USB-HDD formated in FAT32 as targetdrive, and it appeared naturally if the backup exceeded the 4 GB limit of the filesystem.

[JWalkerMR]

@ds2:
in my case the targetdrive is NTFS formatted, so there is no 4 GB limit

[Xeronimo74]

anyone know why this happens when I try to restore from a USB drive? Thanks!

[Dima P.]

Hi Xeronimo74,

Please open a support case thru Veeam Endpoint Backup Control Panel > Support and post here the case ID. Thanks in advance.

[upapi]

Although I checked all related topics in the forum I didn't found a solution.
Version of VEB is 1.5.0.306 on a Windows 10 PC (1607 Build 14393.105).

Backup of the entired PC is configured over WLAN to a NAS. In most cases everything works perfect.
Sometimes Backup failed with the following error:
Error: Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Der angegebene Netzwerkname ist nicht mehr verfügbar.

Perhaps it is a temporary problem caused by an instable WLAN connection?

Thanks in advance

[PTide]

Hi,

Perhaps it is a temporary problem caused by an instable WLAN connection?

It might be so. If the problem appears with a connection that you're 100% sure is stable, then please open a support case and post your case ID

Thank you

[dslogistic]

Hi,

when I am backuping to NAS, I get this errors:

Code: Select all

12.10.2016 14:56:25 :: Error: Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Zadaný síťový název není již dále k dispozici. Error code: 64 Failed to write data to the file [\\192.168.1.190\homes\veeam\Backup Job IVA\Backup Job IVA2016-10-12T144626.vbk]. Failed to download disk.  
12.10.2016 14:57:29 :: Could not perform threshold check for backup location "\\192.168.1.190\homes\veeam" due to space info retrievement fail! 
12.10.2016 15:04:23 :: Error: Zadaný síťový název není již dále k dispozici. Error code: 64 Failed to open file [\\192.168.1.190\homes\veeam\Backup Job IVA\Backup Job IVA.vbm_tmp]. --tr:Failed to call DoRpc. CmdName: [FcWriteFileEx] inParam: [<InputArguments><FilePath value="\\192.168.1.190\homes\veeam\Backup Job IVA\Backup Job IVA.vbm_tmp" /><DesiredAccess value="1073741824" /><ShareMode value="0" /><CreationDisposition value="2" /><FlagsAndAttrs value="0" /><Offset value="0" /><BytesToWrite value="0" /></InputArguments>].

I tried delete previous backups and recreate new full backup, but problem is still persists. Could you help me, please?
Thanks a lot.

Honza K.

[Dima P.]

Hi Honza,

The error is very generic and it's hard to identify the root cause without application logs. Kindly, open a support case via Control Panel > Support and let the support team investigate this issue.

[dslogistic]

Hi Dima,

I wasn´t able to open help topic from Control > Support, so I am using forum, I am appologize. This is in log for this job:

Code: Select all

[10.10.2016 15:13:03] <01> Error    Invoke failed. Command: 'DataTransfer.RestoreText', parameters: {(EStringArray) Links[]=[veeamfs:0:6745a759-2205-4cd2-b172-8ec8f7e60ef8 (03de0294-0480-056b-a506-320700080009)/summary.xml@\\192.168.1.190\homes\veeam\Backup Job IVA\Backup Job IVA2016-09-02T075011.vbk](EBoolean) Option.Remote=false; }.   v Veeam.Backup.AgentProvider.CBackupClient.OnInvokeError(Exception e, String command, CVCPCommandArgs inArgs)
[10.10.2016 15:13:03] <01> Error       v Veeam.Backup.AgentProvider.CBackupClient.Invoke(String command, CVCPCommandArgs inArgs, Boolean noLog)
[10.10.2016 15:13:03] <01> Error       v Veeam.Backup.AgentProvider.CBackupClient.Tar2Text(IFileVfsLink backupFileLink)
[10.10.2016 15:13:03] <01> Error       v Veeam.Backup.Core.CRawSummary.Load(CBackupClient agent, String backupFileName, String insideDirectoryName)
[10.10.2016 15:13:03] <01> Error       v Veeam.Backup.Core.CTransformIncrementsTask.PatchOib(COib fullPointOib, COib incrementalPointOib, CTransformVsbLayer vsbLayer, IBackupRepositoryClient repositoryClient)
[10.10.2016 15:13:03] <01> Error       v Veeam.Backup.Core.CTransformIncrementsTask.TransformOibPair(CStorage fullStorage, CTransformIncrementsOibsPair oibsPair, CTransformVsbLayer vsbLayer, IBackupRepositoryClient repositoryClient)
[10.10.2016 15:13:03] <01> Error       v Veeam.Backup.Core.CTransformIncrementsTask.Execute()
[10.10.2016 15:13:03] <01> Error       v Veeam.Backup.Core.CDefaultTransformAlgTaskManager.ExecuteTasks(IEnumerable`1 tasks)
[10.10.2016 15:13:03] <01> Error       v Veeam.Backup.Core.CTransformIncrementsAlg.TransformPoint(CPoint incrementalPoint, CTransformIncrementsCatOibRefs oldCatOibRefs, CUnpublishingOibsHolder deletedOibsHolder, ITransformAlgTaskManager transformAlgTaskManager)
[10.10.2016 15:13:03] <01> Error       v Veeam.Backup.Core.CTransformIncrementsAlg.Transform(ITransformAlgTaskManager transformAlgTaskManager)
[10.10.2016 15:13:03] <01> Error       v Veeam.Backup.Core.CTransformaAlgorithm.ExecuteTransform(IBackupTransformAlg transformAlg, ITransformAlgTaskManager transformAlgTaskManager)
[10.10.2016 15:13:03] <01> Error       v Veeam.Backup.Core.CTransformaAlgorithm.Execute()
[10.10.2016 15:13:03] <01> Error    File does not exist. File: [\\192.168.1.190\homes\veeam\Backup Job IVA\Backup Job IVA2016-09-02T075011.vbk].
[10.10.2016 15:13:03] <01> Error    Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://frontend::CDataTransferCommandSet::RestoreText_{79b75c23-7d9e-4df6-bc3e-70c1dda7ca98}]. CHMOD mask: [0].
[10.10.2016 15:13:03] <01> Error    Agent failed to process method {DataTransfer.RestoreText}.
[10.10.2016 15:13:03] <01> Error       v Veeam.Backup.AgentProvider.CClientAgentProtocol.Invoke(String command, CVCPCommandArgs inArgs, Boolean noLog, Boolean agentNoLog)
[10.10.2016 15:13:03] <01> Error       v Veeam.Backup.AgentProvider.CBackupClient.Invoke(String command, CVCPCommandArgs inArgs, Boolean noLog)
[10.10.2016 15:13:03] <01> Error    File does not exist. File: [\\192.168.1.190\homes\veeam\Backup Job IVA\Backup Job IVA2016-09-02T075011.vbk].   in c++: Failed to open storage for read access. Storage: [\\192.168.1.190\homes\veeam\Backup Job IVA\Backup Job IVA2016-09-02T075011.vbk].
[10.10.2016 15:13:03] <01> Error       in c++: Cannot apply patches stored in folder [HostFS://\\192.168.1.190\homes\veeam\Backup Job IVA\Backup Job IVA2016-09-02T075011.vbk[6745a759-2205-4cd2-b172-8ec8f7e60ef8 (03de0294-0480-056b-a506-320700080009)]].
[10.10.2016 15:13:03] <01> Error       in c++: Failed to build restore point.

Could be wrong NAS (Synology DS2415+)? It has about 930 GB free of 16,1 TB (backup is normally about 3 GB, full 22 GB).

Thanks, H.

[Dima P.]

Hi Honza,

Sorry for the late reply, somehow missed your last post. Did you resolve your issue or you still need our help? Were you able to reach our support team? Thanks.