Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Connect » I think i've found a backup issue/bug...
  •  
lythaby

Messages: 30
Karma: 0
Send a private message to this user
I've just had to ssh in from home(Somewhat spoiling my bottle of Rosemount Shiraz), to delete the Kerio Backup Folder!!

Our mac mail server mounts another mac servers raid share called BACKUPS, in this share there is a folder called KERIO BACKUP, where the kerio dumps it's zip files.

This in turn then get's backed up to the tape backup JIT.

Since i've updated to version 7.1.0(1906), i've had disk space issues where i've randomly run out of space on the server.

What is happening is that instead of it backing up the the mounted share, it is creating it's own folder of the same name at the root as the backup share, and then trying to dump the backup in there.

This is fine for almost a week, but then kills the local HD space, and needs deleting from /volumes, which incidently shows a network icon (globe) in the gui.

In a word WTF?

When a network volume is mounted, and not disconnected, like this one, X sees it in the volumes as a unique name! Why is Kerio ignoring this and then creating it's own folder in the root?

I've made sure that the full path is correct after the last time it did this in the daytime, and didn't disturb my Shiraz.

This must be fixed, else I fear my Shiraz will be spoiled!!
  •  
j.a.duke

Messages: 356
Karma: 14
Send a private message to this user
lythaby wrote on Wed, 27 October 2010 18:07
I've just had to ssh in from home(Somewhat spoiling my bottle of Rosemount Shiraz), to delete the Kerio Backup Folder!!

Our mac mail server mounts another mac servers raid share called BACKUPS, in this share there is a folder called KERIO BACKUP, where the kerio dumps it's zip files.

This in turn then get's backed up to the tape backup JIT.

Since i've updated to version 7.1.0(1906), i've had disk space issues where i've randomly run out of space on the server.

What is happening is that instead of it backing up the the mounted share, it is creating it's own folder of the same name at the root as the backup share, and then trying to dump the backup in there.

This is fine for almost a week, but then kills the local HD space, and needs deleting from /volumes, which incidently shows a network icon (globe) in the gui.

In a word WTF?

When a network volume is mounted, and not disconnected, like this one, X sees it in the volumes as a unique name! Why is Kerio ignoring this and then creating it's own folder in the root?

I've made sure that the full path is correct after the last time it did this in the daytime, and didn't disturb my Shiraz.

This must be fixed, else I fear my Shiraz will be spoiled!!


Thanks for posting this-I'm having the same issue and just thought it was an issue with the remote AFP volume not mounting after the weekly restart (even though it's in the login items). Not to mention, I thought it was unique to my config.


I'd have to go back to pinpoint when it started, but I did update to 7.1.something on Labor Day, so that's about right for a timeframe.

I'm about to install a launchd agent to keep those volumes mounted to see if that resolves the problem.

I'll keep you posted. If you learn anything, let me know.

Thanks.

Cheers,
Jon
  •  
lythaby

Messages: 30
Karma: 0
Send a private message to this user
Excellent, that makes perfect sense.

I've only rebooted twice since the upgrade, and have the network share in login items.

I'm assuming that Kerio is now wanting you to manually mount the share after reboot, and then re-find the path in the console.

Richard
  •  
Pavel Dobry (Kerio)

Messages: 5245
Karma: 251
Send a private message to this user
lythaby wrote on Thu, 28 October 2010 10:37

I'm assuming that Kerio is now wanting you to manually mount the share after reboot, and then re-find the path in the console.
Richard


There was no change. If you're using a mounted network share for backup you must make sure that the disk is mounted before the Kerio Connect starts (so mounting in Login Items is too late). You need to use LaunchDaemon for this and make a script to define services dependency - mount first then start Kerio Connect. Alternatively you can add disk mounting to the Kerio Connect start-up script (and do it with every update).
Also the disk must remain mounted otherwise the backup will fail.

This requirement was there all the time.
  •  
lythaby

Messages: 30
Karma: 0
Send a private message to this user
Although I don't want to appear argumentative, i really must make this point.

We've had KMS/Connect for about 4 years on this site, without issue, and only since upgrading to Connect have i started to see this problem.

Before then i was part of a Kerio reseller for about 3 years, so i have seen my fair share of installs/configs.

Hence maybe the issue isn't a point upgrade bug, but a version upgrade bug?

I'll have a play with the scripts.
  •  
j.a.duke

Messages: 356
Karma: 14
Send a private message to this user
Kerio_pdobry wrote on Thu, 28 October 2010 05:16
lythaby wrote on Thu, 28 October 2010 10:37

I'm assuming that Kerio is now wanting you to manually mount the share after reboot, and then re-find the path in the console.
Richard


There was no change. If you're using a mounted network share for backup you must make sure that the disk is mounted before the Kerio Connect starts (so mounting in Login Items is too late). You need to use LaunchDaemon for this and make a script to define services dependency - mount first then start Kerio Connect. Alternatively you can add disk mounting to the Kerio Connect start-up script (and do it with every update).
Also the disk must remain mounted otherwise the backup will fail.

This requirement was there all the time.


I'd like to respectfully disagree with the real world experience I've seen.

Before 4 September (when I installed 7.1.0p1), mounting backup shares after login posed no problem with the backup being performed. This behavior has been consistent for at least the last 2 years.

After the update, the problems noted above have occurred. It would seem that Connect 7.1 now enforces the need for that volume to be present when the mailserver process starts, rather than the older behavior of the volume just needed to be mounted when the backup ran.

I don't recall any issues with the 6.x series of releases or with 7.0.x.

I don't have any problem with the volume needing to be present at the time of the backup, but the market at which Connect seems to be targeting might not have the wherewithal to craft the appropriate launchd items to ensure compliance with the more stringent requirements.

Cheers,
Jon
  •  
j.a.duke

Messages: 356
Karma: 14
Send a private message to this user
I just reviewed my notes of what I did on 4 Sept and realized that I had upgraded the server to 10.6.4 at the same time from 10.4.11. I don't know if the OS version has any impact on Connect behavior regarding backup.

Richard, what OS are you running on your server? Intel or PowerPC (if <10.6)?

Also, I'd be happy to share my shell and launchd scripts with you.

Cheers,
Jon
  •  
Pavel Dobry (Kerio)

Messages: 5245
Karma: 251
Send a private message to this user
j.a.duke wrote on Sun, 31 October 2010 02:55
I just reviewed my notes of what I did on 4 Sept and realized that I had upgraded the server to 10.6.4 at the same time from 10.4.11. I don't know if the OS version has any impact on Connect behavior regarding backup.

Cheers,
Jon


This is also the answer you're looking for. Mac OS X Tiger was using different startup scripts, which have dependencies (ie. Kerio Connect was started after all disks are mounted). Leopard and Snow Leopard use different system for starting programs and does not support using of dependencies.
  •  
Ron!

Messages: 3
Karma: 0
Send a private message to this user
Pdobry: Was the startup scripts changed for leopard or snow leopard?

I am running 6.7.x (waiting for all these issue to be discovered and fixed) with leopard and backup daily to a AFP volume. Have not experienced this problem.

  •  
lythaby

Messages: 30
Karma: 0
Send a private message to this user
Sorry for the delay.

We're on a PowerPC G5 Xserve, running 10.4.11.

I've removed the automated mounts, and will do it manually. Luckily, touch wood, i only need to re-boot them about 4-5 times a year.
  •  
mckingsley

Messages: 54
Karma: 3
Send a private message to this user
Hey I have run into this issue a couple times also, and I am not using a network mounted volume for the backup. I am using a plain ole usb external drive. If the drive is not there it should not backup, period. But I also had it taking up space on my boot volume.
  •  
Nielsvk

Messages: 5
Karma: 0
Send a private message to this user
Running into the same problem is describe above.
I'm pretty sure that before 2012 a mounted AFP volume was never a problem.
It's started here somewhere in 2012 with no OSX updates.

What's the best simple fix so far? As i am not a script / Terminal guru.

[Updated on: Wed, 12 June 2013 08:23]

  •  
lythaby

Messages: 30
Karma: 0
Send a private message to this user
I just made a text file, words akin to "mount the backup server, or else", and added it to startup.

It now seems that as-long-as you have it mounted before the backup starts you can get away with it. Also remember that if you reboot the server that its mounted too, it will loose the connection.

It's no problem for me now, as I've moved to O365.
Previous Topic: Web based chat client
Next Topic: Public Folder only for 2 Users visible
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Wed Oct 18 18:24:50 CEST 2017

Total time taken to generate the page: 0.00503 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.