Procedure For Recovery From Failed zmmboxmoves: Difference between revisions
(Created page with "{{WIP}}{{Article Infobox|{{admin}}|{{ZCS 8.6}}|{{ZCS 8.5}}|{{ZCS 8.0}}}} =Procedure For Recovery From Failed zmmboxmoves= ==Purpose== Explain the procedure for recovery from a...") |
No edit summary |
||
Line 1: | Line 1: | ||
{{ | {{BC|Certified}} | ||
__FORCETOC__ | |||
<div class="col-md-12 ibox-content"> | |||
=Procedure For Recovery From Failed zmmboxmoves= | =Procedure For Recovery From Failed zmmboxmoves= | ||
{{KB|{{ZC}}|{{ZCS 8.6}}|{{ZCS 8.5}}|{{ZCS 8.0}}|}} | |||
{{WIP}} | |||
==Purpose== | ==Purpose== | ||
Explain the procedure for recovery from a failed zmmboxmove. | Explain the procedure for recovery from a failed zmmboxmove. |
Latest revision as of 20:31, 12 July 2015
Procedure For Recovery From Failed zmmboxmoves
- This article is a Work in Progress, and may be unfinished or missing sections.
Purpose
Explain the procedure for recovery from a failed zmmboxmove.
Resolution
- Check if the 'zimbraMailHost' attribute for the user is still the same as the source, or has changed to the destination server. If it's the same as source, no further action is required.
If it has changed to the destination server and the move wasn't completed, simply change it back to the source:
zmprov ma user@example.com zimbraMailHost source.example.com
This is possible because even after a move is complete, Zimbra don't automatically purge the accounts.
- If the move exited leaving the account in 'maintenance mode', we can use this:
zmsoap -z -t admin UnregisterMailboxMoveOutRequest/account @name={email} @dest={dest hostname}
Additional Content
- Not related content.