Difference between revisions of "Rsync based SysVol replication workaround"

(Fixed dublicate -s in command)
(Doing some rewrites on the HowTo and removed links to the script and replaced it with a simple rsync command for making it easier.)
Line 1: Line 1:
 
= Introduction=
 
= Introduction=
  
Samba AD currently doesn't provide support for SysVol replication. To achive this important feature in a Multi-DC environment, until it's implemented, workarounds are necessary to keep it in sync. This HowTo provides a basic workaround solution based on a script that uses rsync.
+
Samba AD currently doesn't provide support for SysVol replication. To achive this important feature in a Multi-DC environment, until it's implemented, workarounds are necessary to keep it in sync. This HowTo provides a basic workaround solution based on rsync.
 
 
'''Like on every change/enhancement, it's highly recommended to test the procedure in a test environment and have a [[Backup_and_Recovery|recoverable backup]]!'''
 
  
  
Line 18: Line 16:
  
 
Even if you say the unidirectional replication of rsync is a limitation, it has also many advantages:
 
Even if you say the unidirectional replication of rsync is a limitation, it has also many advantages:
- already available on most distributions and can be installed through it's packet manager (if not already installed anyway)
+
* already available on most distributions and can be installed through it's packet manager (if not already installed anyway)
- setup is fast done
+
* setup is fast done
- configuration is very easy
+
* configuration is very easy
- etc.
+
* etc.
  
If you prefer to use rsync through a SSH tunnel, you can adapt the script to your needs. But typically there's no confidential content on the SysVol share. It should be sufficient for most if the transfer is unencrypted. The rsync module on the PDC is also defined as read only, because it is used only as source. So no content can be pushed to it.
+
If you prefer to use rsync through a SSH tunnel, you can adapt the command to your needs. But typically there's no confidential content on the SysVol share. It should be sufficient for most if the transfer is unencrypted. The rsync module on the PDC is also defined as read only, because it is used only as source. So no content can be pushed to it.
  
  
Line 71: Line 69:
  
 
== Setup on all other Domain Controller(s) ==
 
== Setup on all other Domain Controller(s) ==
 
'''It's suggested to test the script on a save place, to avoid any problems in production! The script comes without any warranty!'''
 
  
 
* Install rsync by using your paket manager or compile from source. Make sure, that you use a version that supports extended ACLs!
 
* Install rsync by using your paket manager or compile from source. Make sure, that you use a version that supports extended ACLs!
  
* Create a file <tt>/usr/local/samba/etc/rsync-sysvol.secret</tt> and fill it with the password, set on the PDC for the <tt>sysvol-replication</tt> rsync account (permissions of that file must not be world-readable!):
+
* Create a password file <tt>/usr/local/samba/etc/rsync-sysvol.secret</tt> and fill it with the password, set on the PDC for the <tt>sysvol-replication</tt> rsync account (permissions of that file must not be world-readable!):
  
 
  pa$$w0rd
 
  pa$$w0rd
  
* Go to [http://marc-muehlfeld.de/samba/sysvol-replication/ http://marc-muehlfeld.de/samba/sysvol-replication/], download the latest version of the <tt>rsync-sysvol-replication.sh</tt> script and make it executable.
+
* For replicating the SysVol folder, run the following command (<tt>--dry-run</tt> mean that no modifications are done):
 
 
* If you use a different rsync username than mentioned above and/or a different path to the <tt>rsync-sysvol.secret</tt> file, change it in the configuration area in the head of the script.
 
 
 
* First run the script in dry-run mode:
 
 
 
# /path/to/rsync-sysvol-replication.sh -d -s /usr/local/samba/var/locks/sysvol/
 
 
 
:'''Warning: Make sure, that the given SysVol folder (<tt>-s ...</tt>) is really your SysVol folder, because the script will replicate to this directory and removes everything in it, that isn't also on the source! You could maybe damage your System! So check the output carefully if the replication is doing, what you expect!'''
 
 
 
* The script auto-discovers the path to the local SysVol share through <tt>testparm</tt>. As the share is automatically setup in your <tt>smb.conf</tt> when [[Samba4/HOWTO/Join_a_domain_as_a_DC|joining as DC]], this should work without any problems.
 
 
 
* The PDC IP is auto-discovered through DNS (<tt>_ldap._tcp.pdc._msdcs.your.domain.</tt>). If you encounter any problems, you can define the PDC host by <tt>-p [IP]</tt>.
 
 
 
* If everything looks fine on the dry-run, you can start the real replication process:
 
  
  # /path/to/rsync-sysvol-replication.sh -s /usr/local/samba/var/locks/sysvol/
+
  # rsync --dry-run -XAavz --delete-after --password-file=/usr/local/samba/etc/rsync-sysvol.secret rsync://sysvol-replication@{IP-of-you-PDC}/SysVol/ /path/to/your/sysvol/folder/
2013-07-23 21:05:24 **********************************************************************
+
   
2013-07-23 21:05:24 Auto-discovered PDC: 10.99.0.1
+
  receiving file list ... done                                                                                                                                                                                  
  2013-07-23 21:05:24 Replicating from 10.99.0.1:
+
created directory /usr/local/samba/var/locks/sysvol                                                                                                                                                           
  2013-07-23 21:05:25      receiving file list ... done
+
  ./                                                                                                                                                                                                            
  2013-07-23 21:05:25      ./
+
  samdom.example.com/                                                                                                                                                                                          
  2013-07-23 21:05:25      samdom.example.com/
+
  samdom.example.com/Policies/                                                                                                                                                                                  
  2013-07-23 21:05:25      samdom.example.com/Policies/
+
  samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/                                                                                                                                          
  2013-07-23 21:05:25      samdom.example.com/Policies/{31B2F340-016D-11D2-945F- 00C04FB984F9}/
+
  samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/GPT.INI                                                                                                                                    
  2013-07-23 21:05:25      samdom.example.com/Policies/{31B2F340-016D-11D2-945F- 00C04FB984F9}/GPT.INI
+
  samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/MACHINE/                                                                                                                                  
  2013-07-23 21:05:25      samdom.example.com/Policies/{31B2F340-016D-11D2-945F- 00C04FB984F9}/MACHINE/
+
  samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/MACHINE/Registry.pol                                                                                                                      
  2013-07-23 21:05:25      samdom.example.com/Policies/{31B2F340-016D-11D2-945F- 00C04FB984F9}/MACHINE/Registry.pol
+
  samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/USER/                                                                                                                                      
  2013-07-23 21:05:25      samdom.example.com/Policies/{31B2F340-016D-11D2-945F- 00C04FB984F9}/USER/
+
  samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/USER/Documents & Settings/                                                                                                                
  2013-07-23 21:05:25      samdom.example.com/Policies/{31B2F340-016D-11D2-945F- 00C04FB984F9}/USER/Documents & Settings/
+
  samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/USER/Scripts/                                                                                                                              
  2013-07-23 21:05:25      samdom.example.com/Policies/{31B2F340-016D-11D2-945F- 00C04FB984F9}/USER/Scripts/
+
  samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/USER/Scripts/Logoff/
  2013-07-23 21:05:25      samdom.example.com/Policies/{31B2F340-016D-11D2-945F- 00C04FB984F9}/USER/Scripts/Logoff/
+
  samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/USER/Scripts/Logon/
  2013-07-23 21:05:25      samdom.example.com/Policies/{31B2F340-016D-11D2-945F- 00C04FB984F9}/USER/Scripts/Logon/
+
  samdom.example.com/Policies/{6AC1786C-016F-11D2-945F-00C04FB984F9}/
  2013-07-23 21:05:25      samdom.example.com/Policies/{6AC1786C-016F-11D2-945F- 00C04FB984F9}/
+
  samdom.example.com/Policies/{6AC1786C-016F-11D2-945F-00C04FB984F9}/GPT.INI
  2013-07-23 21:05:25      samdom.example.com/Policies/{6AC1786C-016F-11D2-945F- 00C04FB984F9}/GPT.INI
+
  samdom.example.com/Policies/{6AC1786C-016F-11D2-945F-00C04FB984F9}/MACHINE/
  2013-07-23 21:05:25      samdom.example.com/Policies/{6AC1786C-016F-11D2-945F- 00C04FB984F9}/MACHINE/
+
  samdom.example.com/Policies/{6AC1786C-016F-11D2-945F-00C04FB984F9}/USER/
  2013-07-23 21:05:25      samdom.example.com/Policies/{6AC1786C-016F-11D2-945F- 00C04FB984F9}/USER/
+
  samdom.example.com/scripts/
  2013-07-23 21:05:25      samdom.example.com/scripts/
+
  samdom.example.com/scripts/logonscript.bat
  2013-07-23 21:05:25      samdom.example.com/scripts/logonscript.bat
+
   
  2013-07-23 21:05:25     
+
  sent 124 bytes  received 1064 bytes  2376.00 bytes/sec
  2013-07-23 21:05:25      sent 191 bytes  received 1908 bytes  1399.33 bytes/sec
+
  total size is 1207  speedup is 1.02 (DRY RUN)
  2013-07-23 21:05:25      total size is 1207  speedup is 0.58
 
  
* Run the script with the <tt>-h</tt> option for further information and parameters.
+
:'''Warning: Make sure, that the destination folder is really your SysVol folder, because the command will replicate to the given directory and removes everything in it, that isn't also on the source! You could maybe damage your System! So check the output carefully if the replication is doing, what you expect!'''
  
* To automatically syncronize the SysVol share every 5 minutes incl. logfile creation, setup a Cron job:
+
* If everything looks like expected, you run the command without the <tt>--dry-run</tt> option for letting rsync do the replication.
  
*/5 * * * *    /path/to/rsync-sysvol-replication.sh -l /var/log/sysvol-replication.log -s /usr/local/samba/var/locks/sysvol/ > /dev/null
+
* To automate the syncronisation, you can run the command via cron (e. g. every 5 minutes).
  
:For testing purposes, you should first run the cronjob in dry-run mode (<tt>-d</tt>) and check the logs, if the script is doing what you expect!
+
*/5 * * * *          rsync --dry-run -XAavz --delete-after --password-file=/usr/local/samba/etc/rsync-sysvol.secret rsync://sysvol-replication@{IP-of-you-PDC}/SysVol/ /path/to/your/sysvol/folder/
  
 
* Repeat this steps on every DC (except your PDC!).
 
* Repeat this steps on every DC (except your PDC!).

Revision as of 21:40, 25 July 2013

Introduction

Samba AD currently doesn't provide support for SysVol replication. To achive this important feature in a Multi-DC environment, until it's implemented, workarounds are necessary to keep it in sync. This HowTo provides a basic workaround solution based on rsync.



Information on rsync-based replication

Group Policy Management Console option for PDC

This HowTo describes a solution for SysVol replication, that is based on rsync. As the nature of this tool, it is unidirectional. This means, files can only be transfered in one direction. That's why for rsync-based SysVol replicaton, you have to choose one DC, on which you do all modifications (GPO edits, logon script changes, etc.). And all other DCs are retrieving the changes from this host, because modifications on them are overwritten when syncing.

A good choice for this "master" host is the one, that contains the FSMO role "PDC Emulator", because you can configure the Group Policy Management Console to connect especially to this machine (default), instead of choosing any of your DC. To which machine the GPMC connects, you can define at „Action“ / „Change Domain Controller“. There you should select „The domain controller with the Operations Master token for the PDC emulator“ (default).

Even if you say the unidirectional replication of rsync is a limitation, it has also many advantages:

  • already available on most distributions and can be installed through it's packet manager (if not already installed anyway)
  • setup is fast done
  • configuration is very easy
  • etc.

If you prefer to use rsync through a SSH tunnel, you can adapt the command to your needs. But typically there's no confidential content on the SysVol share. It should be sufficient for most if the transfer is unencrypted. The rsync module on the PDC is also defined as read only, because it is used only as source. So no content can be pushed to it.



Setup the SysVol replication

Setup on the Domain Controller with the PDC Emulator FSMO role

  • Install rsync by using your paket manager or compile from source. Make sure, that you use a version that supports extended ACLs!
  • If you start your rsync-server through xinetd, you can use the following configuration file (/etc/xinetd.d/rsync):
service rsync
{
   disable         = no
   only_from       = 10.99.0.0/28     # Restrict to your DC address(es) or ranges, to prevent other hosts retrieving the content, too.
   socket_type     = stream
   wait            = no
   user            = root
   server          = /usr/bin/rsync
   server_args     = --daemon
   log_on_failure += USERID
}
  • Create the file /etc/rsyncd.conf (adapt the path variable to your PDCs SysVol path):
[SysVol]
path = /usr/local/samba/var/locks/sysvol/
comment = Samba Sysvol Share
uid = root
gid = root
read only = yes
auth users = sysvol-replication
secrets file = /usr/local/samba/etc/rsyncd.secret
  • Create a file /usr/local/samba/etc/rsyncd.secret (permissions must not be world-readable!) with the following content (adapt the password!):
sysvol-replication:pa$$w0rd
  • Restart xinetd.



Setup on all other Domain Controller(s)

  • Install rsync by using your paket manager or compile from source. Make sure, that you use a version that supports extended ACLs!
  • Create a password file /usr/local/samba/etc/rsync-sysvol.secret and fill it with the password, set on the PDC for the sysvol-replication rsync account (permissions of that file must not be world-readable!):
pa$$w0rd
  • For replicating the SysVol folder, run the following command (--dry-run mean that no modifications are done):
# rsync --dry-run -XAavz --delete-after --password-file=/usr/local/samba/etc/rsync-sysvol.secret rsync://sysvol-replication@{IP-of-you-PDC}/SysVol/ /path/to/your/sysvol/folder/

receiving file list ... done                                                                                                                                                                                   
created directory /usr/local/samba/var/locks/sysvol                                                                                                                                                            
./                                                                                                                                                                                                             
samdom.example.com/                                                                                                                                                                                            
samdom.example.com/Policies/                                                                                                                                                                                   
samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/                                                                                                                                            
samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/GPT.INI                                                                                                                                     
samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/MACHINE/                                                                                                                                    
samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/MACHINE/Registry.pol                                                                                                                        
samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/USER/                                                                                                                                       
samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/USER/Documents & Settings/                                                                                                                  
samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/USER/Scripts/                                                                                                                               
samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/USER/Scripts/Logoff/
samdom.example.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/USER/Scripts/Logon/
samdom.example.com/Policies/{6AC1786C-016F-11D2-945F-00C04FB984F9}/
samdom.example.com/Policies/{6AC1786C-016F-11D2-945F-00C04FB984F9}/GPT.INI
samdom.example.com/Policies/{6AC1786C-016F-11D2-945F-00C04FB984F9}/MACHINE/
samdom.example.com/Policies/{6AC1786C-016F-11D2-945F-00C04FB984F9}/USER/
samdom.example.com/scripts/
samdom.example.com/scripts/logonscript.bat

sent 124 bytes  received 1064 bytes  2376.00 bytes/sec
total size is 1207  speedup is 1.02 (DRY RUN)
Warning: Make sure, that the destination folder is really your SysVol folder, because the command will replicate to the given directory and removes everything in it, that isn't also on the source! You could maybe damage your System! So check the output carefully if the replication is doing, what you expect!
  • If everything looks like expected, you run the command without the --dry-run option for letting rsync do the replication.
  • To automate the syncronisation, you can run the command via cron (e. g. every 5 minutes).
*/5 * * * *          rsync --dry-run -XAavz --delete-after --password-file=/usr/local/samba/etc/rsync-sysvol.secret rsync://sysvol-replication@{IP-of-you-PDC}/SysVol/ /path/to/your/sysvol/folder/
  • Repeat this steps on every DC (except your PDC!).