| Testing Backup [message #123753] |
Wed, 26 August 2015 23:16  |
Bud Durland
Messages: 586
Registered: December 2013
Location: Plattsburgh, NY
|
|
|
|
I'm looking for a good way to test that the system generated backup of or mail server is usable. At first blush, I would expect that I can use the 'listing' option of KMSRECOVER, but would like to confirm that. Our mail store is quite large, and the backup is about 280 segment files.
|
|
|
|
| Re: Testing Backup [message #123764 is a reply to message #123753] |
Thu, 27 August 2015 16:32  |
matti763
Messages: 27
Registered: February 2006
|
|
|
|
Only sure thing is to make full restore. We had one migration project, where restore to new server did´t work. The solution was remove corrupted message and run full backup again.
Create new virtual machine with same OS and install same KC-version to it. Then simply run full restore and see what happens. You need lots of free space to test this, but it can be SATA disk for testing purposes.
|
|
|
|
| Re: Testing Backup [message #123773 is a reply to message #123764] |
Thu, 27 August 2015 19:45 |
Bud Durland
Messages: 586
Registered: December 2013
Location: Plattsburgh, NY
|
|
|
|
My data store is about 1TB, and it takes about 36 ours to do a full backup. Because a 2 day restore process is out of the question, I and using Zerto backup and recovery as the primary disaster recovery mechanism. However, I want to use the Kerio backup as my off-site backup.
The best time to know that your backup is bad is before you need it, so I would like to test it prior to taking it off-site. I find it hard to believe that there's no mechanism to test that the archive is readable. Traditionally, this has been my problem using KMSRecover; it will get partway through the restore, then fall down on what it claims is a corrupt zip file.
|
|
|
|
| Re: Testing Backup [message #123774 is a reply to message #123773] |
Thu, 27 August 2015 21:19 |
matti763
Messages: 27
Registered: February 2006
|
|
|
|
I looked that migration case again and found some more information. List-mode works fine, but recovery stops here:
Recovery of volume 26 done.
Recovery of volume 27 done.
Recovery completed.
Cannot write to ≡¶°☺
Error occurred during recovery process (code 14).
The problem was not corrupted message. It was simply that one user has created folders that name contain dots. Like:
drwx------ 4 root root Laura..
drwx------ 4 root root Bob...
This was enough that backup cannot restored. This was from Linux to Windows migration. Maybe you can run list-mode restore and grep all ".." or "..." -characters from the output.
But your original problem is how to make reliable off-site backup. Can you simply use rsync? It takes a week to run first full backup but in the future you can quickly update the old copy.
|
|
|
|
| Re: Testing Backup [message #123775 is a reply to message #123774] |
Thu, 27 August 2015 22:16 |
Bud Durland
Messages: 586
Registered: December 2013
Location: Plattsburgh, NY
|
|
|
|
I had a similar problem (folder with invalid characters) when I migrated one of our branches from Exchange to Kerio Connect on Windows. I've since moved my KC installation to Linux, and have no plans to go back. So, problems like that are not my concern.
I'm very surprised that KMSRecover still lacks a '--test' option. I can probably run list mode, but my server's message store has literally millions of files. I really don't want all that noise in the output (yes, yes, GREP is my friend if I don't mind using the resources).
Off to make a suggestion...
|
|
|
|
Members
Search
Help
Register
Login
Home
