-
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error RestoreonAccount #31
Comments
Fix for Issue #31 - Error RestoreonAccount
Good afternoon @MarcielMeurer , Could you please update the zmbackup to the release 1.1.1 and try again? I think i might fixed your bug. Regards, |
@lucascbeyeler , i had updated, before adjust the line 136 , with the adjust the message don't have displayed. The restore mensagem is SUCCESS, but the restore don't execute. I used zmbackup version: 1.1.1 Regards, |
Fix for Issue #31 - Error RestoreonAccount
@MarcielMeurer , I fixed this time the zmbackup for good! It wasn't the fact your folders was inside /opt/zimbra/backup that you can't do any restore. The Restore on Account option stopped working after the last update and I didn't notice. I fixed now and release a new update. Could you please update your version and try again? Regards, |
@lucascbeyeler Thanks, its Working. I have successfully tested with unique full backup. Question: I can RestoreonAccount from incremental backup? |
@MarcielMeurer, yes you can. |
Dear @MarcielMeurer, I'm closing this issue, as it's already fixed. Feel free to reopen if the bug occur again. Regards, |
The script for restore not found the archive in /backup/sessions.txt
My backup directory is in /opt/zimbra/backup
The message say SUCCESS, but isn't really.
_ $ zmbackup -r -ro full-20170417111450 user1@mydomain.com restore@mydomain.com
grep: /backup/sessions.txt: Arquivo ou diretório não encontrado
Restore mail process started at - Seg Abr 17 11:29:21 -03 2017
Restoring Session - restore@mydomain.com
Session restore@mydomain.com restored with SUCCESS
Restore mail process completed at - Seg Abr 17 11:29:21 -03 2017 _
The text was updated successfully, but these errors were encountered: