mirror of
https://github.com/lucascbeyeler/zmbackup.git
synced 2026-04-25 07:05:55 +03:00
[GH-ISSUE #167] Emails are not recovered correctly from full bakcup #133
Labels
No labels
Bug Report
Enhancement
Enhancement
Feature Idea
Feature Idea
Not Implemented
Question
Question
Task
Wontfix
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/zmbackup#133
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @soniqsoft on GitHub (Aug 22, 2021).
Original GitHub issue: https://github.com/lucascbeyeler/zmbackup/issues/167
ISSUE TYPE
ENVIRONMENT VERSION
SUMMARY
Started to recover email account with m option (mailbox only) and received recovered partially with error:
ERROR: zclient.IO_ERROR (Read timed out) (cause: java.net.SocketTimeoutExce|
ption Read timed out)
STEPS TO REPRODUCE
ERROR: zclient.IO_ERROR (Read timed out) (cause: java.net.SocketTimeoutExce|
ption Read timed out)
@ananiasfilho commented on GitHub (Apr 27, 2022):
Its said "Time Out"
Try restore backup using zmmailbox
zmmailbox -z -m user@example.com -t 0 postRestURL "//?fmt=tgz&resolve=reset" /backup/user@example.com.tar.gz
-t 0 is the tip that say to zmmailbox to run command without timeout limit.
@soniqsoft commented on GitHub (Apr 27, 2022):
Thank you @ananiasfilho!
I found it earlier but forgot to mention it here.
Thanks a lot anyway.
@andreagobetti commented on GitHub (Feb 22, 2024):
For me the
-t 0option was not enough, but I managed to solve this issue increasing thesocket_so_timeoutvalue from 30000 to3000000using these commands:
Like mgarbo suggested here: https://community.zextras.com/forum/zimbra-ose-9-by-zextras/zmmailbox-postresturl-doesnt-work/