GFI Software

Welcome to the GFI Software community forum! For support please open a ticket from

Home » GFI User Forums » Kerio Connect » Backup on NAS - timeout issue
Backup on NAS - timeout issue [message #153638] Thu, 26 January 2023 13:30 Go to next message
LogitComputer is currently offline  LogitComputer
Messages: 13
Registered: February 2013
Customer has a Kerio Connect Server on Windows 2019.
Was 9.4.2 before, except one Mailbox with 15K Mails the update was more or less OK.

But now the internal backup doesn't work anymore, and it seems that the timeout until the backup aborts was decreased - or the Synology takes longer than usual.
But as the NAS is still the same, just the Kerio Connect was updated to 10.0.0, I think it must be the backup process from Kerio Connect 10.0.0.

Reason for my conclusion:
- Backup folder is a network share on a Synology NAS, e.g. \\servername\kerio-backup\
- Backup-Time is 02:00
- Synology-NAS takes 31(!) seconds until the Windows-Login-Screen appears when tried connect via SMB (tested from a Windows-PC)
- tried with "awaked" Synology - Backup works
- tried manual backup with "sleeping" Synology - Backup fails

My workaround will be a bat-file like
net use X: \\servername\kerio-backup /user:kerio [password]
net use X: /delete

It starts now with the "Windows Task Scheduler" two minutes before the Kerio Backup starts and it works.

Better will be if we can increase this timeout to e.g. 60 Seconds for sleeping NAS who have to spin-up their HDDs?

Thank you in advance.

[Updated on: Thu, 26 January 2023 13:36]

Report message to a moderator

Re: Backup on NAS - timeout issue [message #153640 is a reply to message #153638] Thu, 26 January 2023 18:27 Go to previous message
Bud Durland is currently offline  Bud Durland
Messages: 586
Registered: December 2013
Location: Plattsburgh, NY
Based on my experience in a very similar environment, my recommendation is to set up iSCSI on the Synology (love them, BTW). Create an iSCSI initiator on the Windows server, and map a drive letter to it. Then you can do one of two things:

1- change the parameters of the kerio backup to write to that disk
2- stop using the built-in backup function in kerio and create an automated RoboCopy script.

You did not say what the total size of your mail store is. Once your mail store goes over a certain size, you'll find that the kerio backup process takes For. Freaking. Ever. I have a script I'd be willing to share.

You also didn't mention which Synology device you have. If it has multiple NICs, I'd recommend putting the iSCSI interface on a separate sub-net, isolated from the production network.
Previous Topic: Let's encrypt client not initialized
Next Topic: Webmail handling of appointment Invitations
Goto Forum:

Current Time: Sun Mar 26 11:13:35 CEST 2023

Total time taken to generate the page: 0.04890 seconds