If you have a very large store, it can take a LONG time to copy those backup sets to a new machine. If you can do that, it's surely the easiest method. There's no doubt that this procedure works. zip files have been copied) as the last argument of the kmsrecover command. Be sure to enter the new folder (where the backup. zip) files, or your manual backupfiles (Starting with C)from the old machine to a folder on the new machine.Įxecute the kmsrecover command to do a full recovery according to the instructions in section 15.3 of the Kerio Connect Administrator's guide. To do this, in the Admin Console, go to Archiving and Backup -> Backup and click on Start Now.Ĭopy the latest full and your newly-created differential backup (Files starting with F and I. To do this, in the Admin Console, go to Archiving and Backup -> Backup and click on "Add." and submit a Differential backup to occur in 2-5 minutes from the current time. Run either a final differential backup on the old machine to save any emails sent since the last full backup (this is quicker for large message stores). To do this, log in to the admin console, go to Services, then right-click and stop each of the services. Should you actually experience this issue, use kmsrecover as explained above or contact me for assistance.Stop the services for the mailserver, to freeze your message store in it's current state but still allowing you full access to the administration console. You can access that site from the "Suggest idea" link in your configuration Dashboard and add your vote. There is a feature request at "Automatic backup of mailserver.cfg or option to backup JUST configuration files". What can you do?īecause Kerio considers this expected behavior, it's not scheduled to be fixed any time soon. That would make it reflect the most recent changes. bak file were written when the administrator logs out (or is logged out due to inactivity). I think it would make much more sense if the. That would be more than unusual, wouldn't it? I can't think of any other case where that. The only circumstance I can think of is where you managed to mess things up so badly that you cannot restart. Under what circumstances would that have any value? As noted, this is a copy of mailserver.cfg as of the last restart. I also wonder about the purpose of the file. However, under any other circumstances, I'd call that behavior a bug. There may be some circumstances where that's unavoidable for example if the computer crashed just as configuration changes were about to be written. Expected behavior?įirst, I hardly think it's expected that an operating system crash should cause Kerio to create a zero length mailserver.cfg file. As explained at the "kmsrecover" documentation, you'd use "./kmsrecover -m cfg" to do that. Should you experience this problem, you need to recover from backup. I may not even remember what those changes were if my last restart was months ago! If I made changes to my configuration since that upgrade, those changes are NOT in the. I don't know when I restarted before that! When was the last time you restarted your mailserver? I know that I restarted mine a few days ago, but that was because I did an upgrade. bak file is only copied from mailserver.cfg upon a server restart. bak file over the empty file would fix you up. If you experienced a crash that left you with a zero length "mailserver.cfg" file, you might naively assume that a quick copy of the. You might reasonably assume that is a backup of your configuration, and it is, but IT IS NOT NECESSARILY A CURRENT BACKUP. If you look in the directory where "mailserver.cfg" lives, you'll also find. Kerio Connect can't run without it, and therefore will refuse to start upon reboot. The "mailserver.cfg" file contains the major part of your configuration. Here's the issue: under some circumstances, if your operating system crashes, you may end up with an empty "mailserver.cfg" file. Either way, this is something you need to be aware of. Kerio tech support says it is "expected behavior". Let's start by saying that I consider this to be a bug.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |