VBR 11 + DDVE free: Veeam.Backup.AgentProvider.AgentClosedException

[cstps]

Hey all,

Just wondering if anybody's encountered any errors with a Data Domain VE + Veeam. I'm using an unlicensed (500GB limit) version of DDVE.

The error I receive is: Processing [VM] Error: Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown.

I've configured dozens of physical DD units with Veeam with zero issue; I'm honestly a little puzzled as to what the issue I'm having here could be as I've never encountered anything other than flawless operation between the two platforms, straight out of the box.

Here's a sample of where it seems to fall over in the logs:

Code: Select all

[19.01.2022 14:37:24] <01> Info         [SimplePointGenerationPolicy] Exiting storage retention
[19.01.2022 14:37:24] <01> Info         Searching last sets for compact
[19.01.2022 14:37:24] <01> Info         Searched last sets for compact old way
[19.01.2022 14:37:24] <01> Info         [ParallelStorageCompact] Full compact is disabled
[19.01.2022 14:37:24] <01> Info         [CStorageLinksHelper] Asserting storage links...
[19.01.2022 14:37:24] <01> Info         Checking storages links
[19.01.2022 14:37:24] <01> Info         Checked storages links old way
[19.01.2022 14:37:24] <01> Info         [CStorageLinksHelper] Storage links checked successfully
[19.01.2022 14:37:24] <01> Info         [BackupHealthCheckScheduleCalculator] Previous schedule time is 31/12/2021 12:00:00 AM
[19.01.2022 14:37:24] <01> Info         [BackupHealthCheck] Recheck is disabled
[19.01.2022 14:37:24] <01> Info         [BackupHealthCheck] Integrity check is not needed
[19.01.2022 14:37:24] <01> Info             Disposing CBackupRepositoryClient [0x1c55822]
[19.01.2022 14:37:24] <01> Info                 [AP] Disposing client from thread 1
[19.01.2022 14:37:24] <01> Info             Disposing BaseAgentProtocol [0x370e2ef]
[19.01.2022 14:37:24] <01> Info             Disposing CSocketAgentService [0x2f7fa6d], sessionId [f458]
[19.01.2022 14:37:24] <01> Info             [SocketAgentService] Closing connection to agent 'W2K22-01', id f458
[19.01.2022 14:37:24] <01> Error        Failed to stop socket agent service, id f458
[19.01.2022 14:37:24] <01> Error        Socket has been forcibly closed. Failed to recover connection. (Veeam.Backup.Common.ConnectionException)
[19.01.2022 14:37:24] <01> Error           at Veeam.Backup.Common.Reconnect.CInterlockedReconnectEngine.CheckFailed()
[19.01.2022 14:37:24] <01> Error           at Veeam.Backup.Common.Reconnect.CPacketSender.SendPacketWithReconnect(CPacket packet)
[19.01.2022 14:37:24] <01> Error           at Veeam.Backup.Common.Reconnect.CPacketSender.SendStop()
[19.01.2022 14:37:24] <01> Error           at Veeam.Backup.Common.Reconnect.CProtocolMethods.SendStopOnce()
[19.01.2022 14:37:24] <01> Error           at Veeam.Backup.Common.Reconnect.CReconnectableSocket.Close(Int32 timeoutSec)
[19.01.2022 14:37:24] <01> Error           at Veeam.Backup.Crypto.CCryptoSocket.Close(Int32 timeout)
[19.01.2022 14:37:24] <01> Error           at Veeam.Backup.AgentProvider.CSocketAgentService.SafeCloseSocket()

This is all deployed in a basic lab environment - ESXi 7 and no firewall enabled on the Veeam host. Backups to a CIFS share on the DDVE work fine.

Any thoughts at all? Thanks in advance!

[Andreas Neufert]

Do you have Windows 2022 or Windows 2019 with latest updates on the Veeam Server?
See veeam-backup-replication-f2/issue-with- ... ml#p442667

[rennerstefan]

can you share the while env. details and versions you use?
I just deployed it in my lab (also the DDVE unlicensed version) and was able to use it without any issue.

Thanks

[foggy]

Hi Chris, versions will help to verify the compatibility in general and I also recommend opening a case with our technical support for a closer logs review - chances are the log excerpt above will tell something to our engineers while the people behind this forum are completely clueless regarding that.

[cstps]

Do you have Windows 2022 or Windows 2019 with latest updates on the Veeam Server?
See veeam-backup-replication-f2/issue-with- ... ml#p442667

I think this might be my issue - it's a fresh 2022 install! Thanks for this.

can you share the while env. details and versions you use?
I just deployed it in my lab (also the DDVE unlicensed version) and was able to use it without any issue.

Thanks

Windows Server 2022 with VBR 11.0.1.1261. DDVE 7.7.0.6-1006242. Looks like it's almost certainly the issue above.

Hi Chris, versions will help to verify the compatibility in general and I also recommend opening a case with our technical support for a closer logs review - chances are the log excerpt above will tell something to our engineers while the people behind this forum are completely clueless regarding that.

Thanks foggy, will do.

[foggy]

Right, according to Dell, Windows 2022 is not officially supported by DDBoost yet.

[Howardchang]

The host CPU where this problem occurs is relatively new, and the fault disappears after enabling EVC. What can be determined is that the fault is not a compatibility issue with Windows 2022.