How to find and backup different COS users: Difference between revisions
Line 7: | Line 7: | ||
==Purpose== | ==Purpose== | ||
In this article we will show how | In this article we will show how to: | ||
*Back-up COS subtree (LDAP). | *Back-up COS subtree (LDAP). | ||
*Find which users belong to which COS, and place them into different files, based on COS. | *Find which users belong to which COS, and place them into different files, based on COS. | ||
*Restore COS subtree. | *Restore COS subtree. | ||
*Assign users to specific COS | *Assign users to specific COS | ||
==Resolution== | ==Resolution== |
Revision as of 12:36, 24 December 2016
How to backup & restore COS, including the COS users.
Purpose
In this article we will show how to:
- Back-up COS subtree (LDAP).
- Find which users belong to which COS, and place them into different files, based on COS.
- Restore COS subtree.
- Assign users to specific COS
Resolution
1. Backup COS.
This step assumes that you would like to migrate a server to another one, and this is a way to move just the COS to the other server.
- Download JXplorer from http://jxplorer.org/downloads/users.html
Create new entry as follows:
Host: "client" server IP Port 389 ; Protocol v3 Base DN: cn=zimbra
Authentication:
Level: User + Password User DN: cn=config Password is the output from: zmlocalconfig -s ldap_root_password
Click OK.
- From the left Tree View, expand cos.
- Select the COS that you want to export&move.
- From the File menu line above, click on LDIF > Export Subtree > Save on the local disk.
- Do that with all COS you want to move.
2. Create files for each non-default COS, and their respective user members.
This step assumes that you are going to move the users from this server to another, and you want to create file for each non-default COS, and to include their members in it.
A short script accomplishes that:
#!/bin/bash # The result is a file/s for each COS, and the users within this specific COS # Note: If there are no custom created COS, there will be no users listed in the default and default_external files. That # means all users are in the "default" COS. # Since the default and the default_external files will contain no users, their respective files are deleted at # the end. Zimbra only detect users that are not in the default COS. Thus, every non detected user is in the default COS. mkdir /tmp/cos_users source ~/bin/zmshutil; zmsetvars for i in `zmprov gac` do id=`zmprov gc $i | grep -e "\bzimbraId\b"|cut -d " " -f 2` ldapsearch -x -H $ldap_master_url -D $zimbra_ldap_userdn -w $zimbra_ldap_password| grep -e $id -e "dn: uid=" -e mail:|grep -v Email| grep -e zimbraCOSId -B1 -A1|grep mail|awk '{print $2}' > /tmp/cos_users/$i /bin/rm -rf /migration/cos_users/default* done
3. How to restore COS.
This step assumes you are restoring the backed up COS to the new server.
- Create new entry in the JXplorer as in point 1, but this time specify the "destination" server IP.
- Click on the "cos"
- LDIF > Import File > Select File > Import
Do that with all COS you want to import.
4. This step assumes that you moved the users from the old to the new server, and this script will assign the correct COS to the migrated users.
#!/bin/bash # The script first list the exported cos names, then iterate through all members within this cos and finally assigns the # user to the COS. for cos in `/bin/ls -1 /tmp/cos_users | tr " " "\n"` do for i in `cat /tmp/cos_users/$cos` do zmprov sac $i $cos done done
Additional Content
References: https://wiki.zimbra.com/wiki/How_to_merge_two_independent_ZCS_servers_into_one