Novell Home

AppNote: Using RSync to synchronize data to and from NetWare servers

Novell Cool Solutions: AppNote
By Thomas Erickson

Digg This - Slashdot This

Posted: 9 Nov 2004
 

Thomas Erickson
Master CNE, CDE, LPIC-1, CLE, MCSE and CCNA

Table of Contents:

Abstract
Disclaimer
Introduction
Configuring RSync on the destination server (server)
Lab legend
Obtain the RSync Binary
Install RSync
Configure RSync
Configuring RSync on the source server (client)
Obtain the RSync Binary
Install RSync
Configure RSync
Create RSync NetWare Control File (NCFs)
Examples of RSync NCF files
Practical uses of RSync including synchronizing trustees, data and Data Information Base
(DIBs)
RSync one file
RSync DIBs
RSync Trustees
RSync sys volume
RSync vol1 and create new sub-directory
RSync one directory
RSync vol2 and create new sub-directory
Restore lost data
Scheduling RSync via CRON
Cluster enabling RSync (Fault tolerance)
Install RSync onto the Cluster enabled volume
Configure RSync
Example Load Script
Example Unload Script
RSync Support and Limitations
How is RSync Supported?
RSync Limitations
RSync Alternatives
Lessening RSync Disconnects
Conclusion
Appendix A: Configuring the CO server without RSYNCNRM.NLM
References

Abstract

RSync is an open source application/utility that is able to detect differences without local access to the source and destination files, then remotely synchronize only the differences between the RSync Client and RSync Server.

Disclaimer

Currently Novell Technical Services (NTS) does not support RSync Client (Source Server) outside of Novell Branch Office. The only support of RSync Client on NetWare is via the forge.novell.com forums.

Introduction

This document will show you how to install, configure and use RSync to synchronize data to/from NetWare servers.

Today most organizations have a mixed environment of UNIX, NetWare and Windows. It is challenging to synchronize files to/from the different operating systems in your environment.

Keeping files and resources close to users across a WAN is important for file access performance. However, there is a great need for data integrity and availability. Today your environment may have hundreds of Novell NetWare servers across a WAN that need to synchronize data to a central office.

Though RSync has many uses, I believe the intended use is to synchronize data for the purpose of mirroring data. This data does not need to be critically up-to-date. Meaning, a once-a-day or twice-a-day sync is sufficient. One could use RSync to distribute Novell Application Launcher (NAL) source files to geographically disperse areas, sync HTTP/FTP files, user data files, and practically any type of intelligent file/directory synchronization.

RSync is useful for Business Continuity and Disaster Recovery. Delta copies across a LAN or a WAN on a schedule of your choosing.

In this article I show the reader how to use cron to automate rsync. There is a forge.novell.com project that combines cron, perl and rsync (CPR). You may find this helpful in your rsync implementation. http://forge.novell.com/modules/xfmod/project/?cpr-backup

You can use RSync to synchronize multiple volumes/directories at the same time via a NCF that loads RSync multiple times. By doing multiple volumes/directories one does not need to worry about the timing of JobA so JobB can start.

RSync was born Saturday, June 22, 1996 with the initial release 1.1.1.1.

"RSync is an open source utility under a GNU-style license that has been ported to NetWare? and that is being used in the Nterprise Branch OfficeTM, the Novell soft appliance. RSync for NetWare uses SSL encryption through NICI. RSync itself does not perform any encryption. Instead, it uses Winsock through NICI to encrypt and decrypt the data.
For more information and documentation, see http://samba.anu.edu.au/rsync/, Configuring Replication (rsync) to the Central Office, and Configuring Replication and Backup" (Novell, n.d. c).

RSync solves the file differences problem in the following way:

"The problem is that the normal methods for creating a set of differences between two files rely on being able to read both files. Thus they require that both files are available beforehand at one end of the link. If they are not both available on the same machine, these algorithms cannot be used (once you had copied the file over, you wouldn't need the differences). This is the problem that rsync addresses" (Tridgell, n.d.).

Eight years later RSync has grown up to be a very powerful solution for synchronizing data. In fact, RSync for NetWare has been downloaded more than 11,000 times. See the following URL for current statistics: http://forge.novell.com/modules/xfmod/project/showfiles.php?group_id=1148&release_id=276

Configuring RSync on the destination server (server)

Lab legend

NEO-FS1 is a NetWare 6.0 SP4 server at IP Address 10.10.10.25 in Tree MATRIX_TREE (typically the Central Office (CO) server/destination server).

NW60-FS1 is a NetWare 6.0 SP4 server at IP Address 10.10.10.5 in NW60_TREE (typically the source server).

Configuring the destination server

Prepare the destination server, AKA Central Office (CO) Server.

Once RSYNCNRM.NLM is loaded you can configure the CO server from NetWare Remote Manager (NRM) from your web browser.

Note: If you prefer not to use RSYNCNRM.NLM see Appendix A for instructions on configuring the destination server without RSYNCNRM. To me, it is easier to use the RSYNCNRM.NLM.

  1. Obtain the RSync Binary

    You can obtain the RSYNCNRM.NLM from a NetWare 6.5 box.

    If you do not have a NetWare 6.5 box handy, download a CO server patch. The current CO patch is @ http://support.novell.com/servlet/filedownload/pub/cosp2.exe
    If you are unable to find the current service pack then simply search for it with Novell's filefinder. http://support.novell.com/servlet/filefinder

    In the text box, search for cosp*.exe. This stands for Central Office SP. Once you have downloaded and extracted the package, search for zip files. Today the zip file is called SRC.ZIP. Inside this package is RSYNCNRM.NLM.

    Now obtain the RSync binary from Novell's open source collaboration site. http://forge.novell.com. In the search text box, type RSync. Once you get to the RSync project page you can download the latest RSync binary. Currently the URL is: http://forge.novell.com/modules/xfmod/project/?rsync


  2. Install RSync

    Download and extract the RSync-2.6.0.zip (If you have WinZip, simply right click and go to the WinZip piece and select extract)

    Copy the RSync-2.6.0\RSync to SYS:
    Copy RSYNCNRM.NLM to SYS:\SYSTEM\

    Modify the SYS:\SYSTEM\AUTOEXEC.NCF with the following:
    LOAD RSYNCNRM.NLM
    SEARCH ADD SYS:\RSync
    SEARCH ADD SYS:\RSync\SYS\RSync

    Now change the attributes of the files:
    On Windows 2000 and above do the following:
    Map a drive to the root of SYS volume.
    Start | run | cmd | cd F:\RSync | attrib.exe *.* /s --r

    If you do not have your NetWare servers in DNS or do not have SLP configured correctly, you can modify your SYS:\ETC\HOSTS file and put the source and destination servers in the host file.

    For example the CO server's name is NEO-FS1
    NEO-FS1's SYS:\ETC\HOSTS file looks like:
    10.10.10.25 NEO-FS1.MYDOMAIN.COM NEO-FS1
    10.10.10.5 NW60-FS1.MYDOMAIN.COM NW60-FS1

    From the System Console, type the following command:
    LOAD RSYNCNRM.NLM
    This will auto-load RSync.NLM
    You should now have a new System Console Screen that looks like:

    RSyncd version 2.6.0 starting, listening on 10.10.10.25:873


  3. Configure RSync

    Now you are ready to configure the CO server from a web browser. For example, browse to https://10.10.10.25:8009 and authenticate as an admin.msinfosec (see FIG 1).


    Now fill in the destination server's DNS name or IP Address. Consider disabling SSL until after your first successful run. Once you have configured this the way you want, click Apply (see FIG 2).


    Now click 'Branch Office Configuration' | Add Branch Office (see FIG 3).

    Click Apply | enable ?Transfer Logging' | put the IP Address of the source server (see FIG 4).


    If you have multiple source servers, add another one until you have added all your source servers (see FIG 5).



Configuring RSync on the source server (client)

Now that the Destination Server or Central Office Server is configured and listening for RSync traffic, let us configure the source server.

  1. Obtain the RSync Binary

    Now obtain the RSync binary from Novell's open source collaboration site: http://forge.novell.com. In the search text box, type RSync. Once you get to the RSync project page you can download the RSync binary. Currently the URL is: http://forge.novell.com/modules/xfmod/project/?rsync


  2. Install RSync

    Download and extract the RSync-2.6.0.zip (If you have WinZip, simply right click and go to the WinZip piece and select extract)

    Copy the RSync-2.6.0\RSync to SYS:

    Now change the attributes of the files
    On Windows 2000 and above do the following:
    Map a drive to the root of SYS volume.
    Start | run | cmd | cd F:\RSync | attrib.exe *.* /s --r


  3. Configure RSync

    To configure the source server do the following:

    Modify the SYS:\SYSTEM\AUTOEXEC.NCF with the following near the bottom of the AUTOEXEC.NCF:

    SEARCH ADD SYS:\RSync
    SEARCH ADD SYS:\RSync\SYS\RSync
    LOAD CRON
    #Note, ensure Cron exists in SYS:\SYSTEM\

    If you do not have your NetWare servers in DNS or do not have SLP configured correctly, you can modify your SYS:\ETC\HOSTS file and put the source and destination servers in the host file.

    For example, the source server's name is NW60-FS1.
    NW60-FS1's SYS:\ETC\HOSTS file looks like:
    10.10.10.5 NW60-FS1.MYDOMAIN.COM NW60-FS1
    10.10.10.25 NEO-FS1.MYDOMAIN.COM NEO-FS1

    Now add the following search paths to your server.
    Go to the System Console and type the following:
    SEARCH ADD SYS:\RSync
    SEARCH ADD SYS:\RSync\SYS\RSync


  4. Create RSync NetWare Control File (NCFs)

    The best way to configure the source server is to use a NetWare Control File (NCF) and call this NCF file on a schedule with CRON.

    See section 'Examples of RSync NCF files'.

Examples of RSync NCF files

Practical uses of RSync including synchronizing trustees, data and Data Information Base (DIBs)

Here are some example NCF files with descriptions:

Use Notepad or another ASCII text editor to create the NCF files.
Once you have the NCF file, "Save As" to SYS:\RSync\

Note: Make sure Notepad does not append a .txt to your file name. You want FileName.NCF and NOT FileName.NCF.txt.

SYS:\RSYNC\BKAUTO.NCF:

echo RSync Start File
#Example 1 sync the source server's autoexec.ncf
#/system/autoexec.ncf is the source server's file being RSync'd
#/sys/system is so on the destination server the same directory structure is maintained
sys:RSync/RSync -arz -v /system/autoexec.ncf NEO-FS1::NW60-FS1/sys/system/ --volume=sys: --port=873
--progress
#--volume is the source server's volume

See FIG 6 for further explanation of syntax related to source and destination servers.

Now type BKAUTO.NCF on the System Console and you should see something like FIG 7:

Now confirm on the destination server that the file came across.

Directory of H:\RSync\NW60-FS1\sys\system
08/14/2004 06:17 PM            2,358 autoexec.ncf

#Example 2
#this takes the source sys:\system\dsr_dib and puts it in the destination
#\RSync\NW60-FS1\system\DSR_DIB
echo RSync Start File
sys:RSync/RSync -arz -v /system/DSR_DIB NEO-FS1::NW60-FS1/sys/system --volume=sys: --port=873
--progress

#Example 3
#Note: To get a trustees.xml file you need trustbar.nlm (Available from support.novell.com/filefinder 
# simply search for trustbar and download the smallest package).
# Here is the syntax for trustbar: trustbar vol1: -b --v
echo RSync Start File
sys:RSync/RSync -arz -v /trustees.xml NEO-FS1::NW60-FS1/sys/ --volume=sys: --port=873  --progress
#--volume is the source server's volume
#trustee.xml is the source server's trustees.xml to be replicated

#Example 4
#sync the whole sys volume to NEO-FS1
#BKSYS.NCF
echo RSync Start File
sys:RSync/RSync -arz -v / NEO-FS1::NW60-FS1/sys --volume=sys: --port=873  --progress
#--volume is the source server's volume

This is what it looked like on the source server:

This is the Netware(r) port of RSync 2.5.6.
Copyright (C) Andrew Tridgell, Paul Mackerras, Martin Pool
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
Modifications for Novell(r) Netware(r) Copyright (c) 2002 Lee Wiltbank
675 Mass Ave, Cambridge, MA 02139, USA
Welcome.
building file list ...
24863 files to consider

Note: Once it builds the list in memory it starts to sync the files.

See FIG 8: Synchronizing the files on the source and destination server.

#Example 5
#sync the whole VOL1 volume to NEO-FS1 and create a new sub-directory under RSync\NW60-FS1\
echo RSync Start File
sys:RSync/RSync -arz -v / NEO-FS1::NW60-FS1/vol1 --volume=vol1: --port=873  --progress
#--volume is the source server's volume

#Example 6 
#sync the directory sys:/tmp to NEO-FS1
#BKTMP.NCF
echo RSync Start File
sys:RSync/RSync -arz -v /tmp NEO-FS1::NW60-FS1/sys/ --volume=sys: --port=873  --progress
#--volume is the source server's volume

#Example 7 
#sync vol2 to NEO-FS1 and create a destination directory called vol2
#BKvol2.NCF
echo RSync Start File
sys:RSync/RSync -arz -v / NEO-FS1::NW60-FS1/vol2 --volume=vol2: --port=873  --progress
#--volume is the source server's volume

FIG 9 shows the file structure after a sync to the destination server.

#Example 8
#sync two volumes at the same time -- Tip learned from Sam Morris.
#sync the whole VOL1 volume to NEO-FS1 and create a new sub-directory under RSync\TRINITY-FS2\
echo RSync Start File
sys:RSync/RSync -arz -v / NEO-FS1::TRINITY-FS2/vol1 --volume=vol1: --port=873  --progress
#--volume is the source server's volume
#sync vol2 to NEO-FS1 and create a destination directory called vol2
#BKvol2.NCF
echo RSync Start File
sys:RSync/RSync -arz -v / NEO-FS1::TRINITY-FS2/vol2 --volume=vol2: --port=873  --progress
#--volume is the source server's volume

Restoring lost data from the CO server to a new RSync client server

OK, several months/years later the source server dies and you need to sync the data back. Build a new server and insert it back into the tree (after first cleaning up the tree).

Configure the former source server (NW60-FS1) after a hardware/software server crash. For this example we copied the RSync-2.6.0\RSync\ to sys:\RSync

Modify the SYS:\SYSTEM\AUTOEXEC.NCF with the following:

SEARCH ADD SYS:\RSYNC
SEARCH ADD SYS:\RSYNC\SYS\RSYNC

Type the following on the console:

SEARCH ADD SYS:\RSYNC
SEARCH ADD SYS:\RSYNC\SYS\RSYNC

On the NW60-FS1 System Console type the following:

RSyncstr.ncf

This is what the NW60-FS1/SYS:/RSYNC/RSYNCSTR.NCF looks like:

echo RSync Start File
REM Single Server:
REM
REM RSync will assume that RSyncD.CONF is in SYS:\ETC
REM and that the certificate being used is SSL CertificateIP
REM
sys:RSync/RSyncst
sys:RSync/RSync    --progress --address=10.10.10.5 --port=873   --daemon --config=sys:etc/RSyncd.conf

This is what the NW60-FS1/sys/etc/RSyncd.conf looks like:

uid = nobody 
gid = nobody
max connections = 0
syslog facility = local5
pid file = SYS:/RSync/RSyncd.pid
log file = SYS:/RSync/RSyncd.log
motd file = SYS:/RSync/RSyncd.motd

[NEO-FS1]
   path=SYS:/
   comment=
   read only=no
   use chroot=no
   strict modes = no
   transfer logging=yes
   timeout=3600
   use lfs=no
   hosts allow=10.10.10.25
   hosts deny=*

Now on NEO-FS1 build a RESTORE.NCF

#Example 8
#sync the directory NEO-FS1/VOL1:/RSync/NW60-FS1/SYS/tmp to NW60-FS1
#RESTORE.NCF
echo RSync Start File
sys:RSync/RSync -arz -v /RSync/nw60-fs1/sys/tmp NW60-FS1::NEO-FS1/tmp/ --volume=vol1: --port=873  --progress
#--volume is the source server's volume

In FIG 10 you will see this restore on the source server (NEO-FS1) and the destination server (NW60-FS1).


Scheduling RSync via CRON

There are two ways to schedule RSync on NetWare. You can use NetWare Remote Manager (NRM), or you can use CRON (my preferred method).

The following is an example CRONTAB which is checked every minute by the CRON daemon.

On the source server create/modify SYS/ETC/CRONTAB

#One must have CRON.NLM loaded.  Verify this by  typing MODULES CRON on the system console.
#Minute    Hour    D-o-M    Month    D-o-W    Command
0          18       *         *       0       dsrepair --rc
#This takes a weekly DIB Sunday at 6pm
0          20       *         *       0       BKDIB.NCF
#this RSyncs the sys:\system\dsr_dib from NW60-fs1 to NEO-FS1/vol1/RSync/nw60-fs1/ on Sunday once a #week
at 8pm 
#backup volume trustees.  Just to be safe, give each volume an hour to backup trustees.
0         15     *        *      1     trustbar vol1: -b -v
0         16     *        *      1     trustbar vol2: -b -v
#Now RSync the trustees.xml file
30         16     *        *       1     BKTrustv1.ncf
35         16     *        *       1     BKTrustv2.ncf
#Now for heavy lifting using RSync
0          18     *        *       *     BKSYS.NCF
#SYS data should not change that much, so it should sync quickly
0          21     *        *       *     BKVOL1.ncf
#RSync vol1 at 9pm.  Some adjusting may need to be done depending on the #size of your volumes. Check the 
logs to see when  SYS volume typically finishes and give it a 30 minute buffer.
0          3      *        *       *      BKVOL2.ncf
#RSync vol2 at 3am.  Again, you may need to adjust the time depending on your environment.

Cluster enabling RSync (Fault tolerance)

Novell Cluster Services is a high availability solution that provides fault tolerance and load balancing from a 2 to 32 node Cluster. Basically the Cluster resource is a secondary IP Address and an eDirectory object tied to a shared NSS volume. This secondary IP Address and volume automatically migrate from Node to Node when there is a hardware or OS outage. These shared NSS volumes/pools can be hosted on a shared SCSI (2 node only), Fiber Channel SAN, or iSCSI.

For more information on configuring Novell Cluster Services (NCS) see Novell's documentation web site at http://www.novell.com/documentation.

Products like RSync can be Cluster enabled with load and unload scripts. These load and unload scripts are configured inside the properties of a Cluster Resource.

Look for a 'Cluster Enabling SSL RSYNC' TID from Novell in the near future.

To configure Clustering you can use ConsoleOne or NetWare Remote Manager (NRM).

In FIG 11 you can see where you configure Clustering inside NRM. Use Remote Console to view the migration process (see Fig 11).

"Selecting a Cluster Resource Using the NRM RSync Snap-in   If you are unable to select a cluster resource using the NRM RSync snap-in, unload the RSYNCNRM.NLM program and then reload it. You must also modify the autoexec.ncf file and place RSyncnrm.nlm (NLM load line after the ldncs.ncf file because the RSyncnrm program requires clustering to be loaded in order to function" (Novell, 2004, p. 13).

  1. Install RSync onto the Cluster enabled volume

    Simply copy the sys:\rsync directory from your destination server to the Cluster enabled volume.

    Modify each node's /etc/hosts file with all cluster nodes and cluster resources.
    For example:
    10.10.10.30 ncs1_vol1_server
    10.10.10.31 ncs1_vol2_server
    10.10.10.198 ncs1_SVOL1_server

    Create a DNS "A record" for 10.10.10.198 so the RSync clients (source servers) point to the same name/address no matter which node is hosting the Cluster resource.

    It is critical that the scripts execute correctly, otherwise your cluster load will produce a "comatose state".

    Most organizations will choose to have the RSYNC load/unload commands with a volume resource.


  2. Configure RSync

    Configure the Cluster Resource and load/unload scripts from NRM's Cluster Config. Once you are in NRM, click Cluster Config and then click your Cluster Resource (see FIG 12).


    Once you are in the Cluster Resource Configuration, click on the load script (see FIG 13).



    FIG 14 shows the Cluster Load Script.

Example Cluster LOAD SCRIPT

nss /poolactivate=SPOOL1 
mount SVOL1 VOLID=254
CLUSTER CVSBIND ADD CLUSTER_SPOOL1_SERVER 10.10.10.198
NUDP ADD CLUSTER_SPOOL1_SERVER 10.10.10.198
add secondary ipaddress 10.10.10.198

search add SVOL1:\RSync
search add SVOL1:\RSync\sys\RSync
REM DELAY 5   Use this delay if needed.
rsync -v --progress --address=10.10.10.198 --config=SVOL1:rsync/rsyncd.conf port=873 --daemon
rsyncnrm.nlm 

Note: Manually edit the SVOL1:rsync/rsyncd.conf or configure the 'Global Configuration' and 'Branch Office Configuration' from each node's perspective. In other words, have the RSync volume active and load rsyncnrm.nlm from each node one at a time, and configure the Global and Branch Office configuration similar to the configuration in the section "Configuring RSync on the destination server (server)".

Example UNLOAD SCRIPT

del secondary ipaddress 10.10.10.198
CLUSTER CVSBIND DEL CLUSTER_SPOOL1_SERVER 10.10.10.198
NUDP DEL CLUSTER_SPOOL1_SERVER 10.10.10.198
nss /pooldeactivate=SPOOL1 /overridetype=question
 
UNLOAD RSyncNRM.NLM
UNLOAD RSync.NLM 

Once you have the load and unload scripts configured, you should test 'migrating' the Cluster Resource from Node to Node. To do this, use NRM's Cluster Management and select the resource, then click migrate.

FIG 15 shows how to migrate the Cluster Resource.


RSync Support and Limitations

How is RSync Supported?

"This product is Open Source. Open Source support is typically provided through the hosting organization's web site forums and news groups. Open source projects that Novell hosts are available on Novell Forge" (Novell, n.d. d).

One can use HTTP or Network New Transfer Protocol (NNTP) to search and post in the Novell Forums. Point your NNTP client to forums.novell.com and subscribe to novell.forge.rsync.public and novell.forge.rsync.help. Many RSync supporters monitor these forums and help each other out. Often code fixes are handed out on an "as needed" basis (Post only after searching your question in the forums).

Look for a 'Troubleshooting Rsync' TID from Novell in the near future.

RSync Limitations

  • RSync logging is not similar to enterprise backup solutions. Perhaps someday someone will build a log parser for RSync.
  • No phone support.
  • Several hundred gig syncs must be refined/tweaked.

RSync Requirements

I have run RSync on NetWare 5.1, 6.0, and 6.5. RSYNC 2.6.0 requires NetWare 6.0 SP4; otherwise you may experience a public symbol error message. "Loader cannot find public symbol: mkstemp for module RSYNC.NLM"

"The rsync.nlm can run on NetWare 5.1 SP5 or later and NetWare 6.0 SP2 or later. However, Novell does not support it as a standalone NLM on these NetWare versions" (Wiltbank, 2003).

Alternatives to RSync

Lessening RSync Disconnects:

RSYNC timeout issues can be helped by increasing the Winsock buffer.

You will need the newer Winsock (ws2_32.nlm) in order to increase this buffer. http://support.novell.com/filefinder/ put in ws2_32.nlm and search for a newer ws2_32.nlm

You will need to meet the minimum service pack level documented in the readme of the patch.

This feature should be in the next release after wsock6e.exe

Default buffer is 2MB, do NOT go over 16MB!

How to tell if your Winsock has this feature?
NovellRocks-FS1: ws2_32 help

Once you have the updated ws2_32.nlm in memory type the following:

for 8 MB:
ws2_32 MAX_PENDING_SEND_BUFFER_SIZE 8192000
for 4 MB:
ws2_32 MAX_PENDING_SEND_BUFFER_SIZE 4096000

Set the same buffer on the source and destination server.

Conclusion

This paper shows the reader how to install, configure, and use RSync with step-by-step instructions.

The following topics were covered in this paper:

RSync is a powerful utility for synchronizing remote files to/from a central office.

This paper satisfies the need to document the setup of RSync on NetWare.

Appendix A: Configuring the CO server without RSYNCNRM.NLM

  1. Obtain the RSync binary from Novell's open source collaboration site: http://forge.novell.com. In the search text box, type RSync. Once you get to the RSync project page you can download the RSync binary. Currently the exact URL is: http://forge.novell.com/modules/xfmod/project/?RSync


  2. SETTING UP THE DESTINATION SERVER (RSYNC SERVER):

  3. Copy the rsync directory to sys:\ (after extracting it from the above URL)


  4. Add the following to the system\autoexec.ncf

    SEARCH ADD SYS:\RSYNC
    SEARCH ADD SYS:\RSYNC\SYS\RSYNC
    RSYNCSTR.NCF


  5. Modify RSYNCSTR.NCF to have the CO (Central Office) rsync server listen for incoming rsync traffic.

    Also, if one does not need SSL that can be removed too. You want it to look like:
    rsync -v --progress --port=873 --daemon
  6. Before starting rsync daemon for the first time, configure the conf file.

    Copy sys:\rsync\rsyncd.conf to the sys:\etc directory.
    Modify the rsync server's \etc\rsyncd.conf file
    You will need an entry in the etc\rsyncd.conf file for each source server's info:
    Example /etc/rsyncd.conf:
    uid = nobody 
    gid = nobody 
    max connections = 0 
    syslog facility = local5 
    pid file = SYS:/rsync/rsyncd.pid 
    log file = SYS:/rsync/rsyncd.log 
    motd file = SYS:/rsync/rsyncd.motd 
    #The following line identifies the source server, this is case sensitive. 
    [NW60-FS1] 
    # The following line tells the destination server where to put the files. This path is on the
    destination server's volume and the top directory must be created. 
    path = VOL1:/rsync/NW60-FS1
    comment =  
    read only = no 
    use chroot = no 
    #sometimes depending on your lan/wan link you may need to increase the timeout value 
    timeout = 3600 
    transfer logging = yes 
    
    #here is another rsync source server 
    [NW60-FS2] 
    path = VOL1:/rsync/NW60-FS2
    comment = 
    read only = no 
    use chroot = no 
    timeout = 3600 
    transfer logging = yes 
  7. On the destination server create the path, for example: vol1\rsync\NW60-FS1
  8. Now type the following on the console.

    SEARCH ADD SYS:\RSYNC
    SEARCH ADD SYS:\RSYNC\SYS\RSYNC
    RSYNCSTR.NCF

    Then switch to the RSync Console to confirm the server is listening for RSync traffic.

References


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell