Problem
How do I set up file replication from one SCO AFPS 3.5.2 system to another?
Solution
The following example details how to set up file replication between two SCO AFPS systems.
As an example only, two systems are set up as follows:
PDC BDCASU1_DOM domain+-------------+ +------------+
| | | |
| | | |
| SCOTEST | - - - - > - - - | SCORE |
| | | |
| | | |
+-------------+ +------------+OpenServer 5.0.4 OpenServer 5.0.4
AFPS 3.5.2n AFPS 3.5.2n
.
.
. +---------------+
. | |
. . . . . | Windows PC |
| NT User |
| Manager |
+---------------+The two OpenServer 5 systems are loaded with SCO Advanced File and Print Server Release 3.5.2n. They are configured to be a Primary and Secondary Domain Controllers, respectively, in the same overall LAN Manager/NT domain, "ASU1_DOM".
The AFPS PDC is then configured to be an "export" server and replicate its files to the BDC system, the "import" server. Make sure you are familiar with the system's UNIX "root" and AFPS "administrator" passwords.
(1) A special user account is created so that the import systems can use it to log on (as in domain rather than UNIX logon) to the export server. This user account can ONLY be created using the NT Server Tools "User Manager for Domains" utility, as the option for setting a non-expiring password is not available with the UNIX command line "net user" command. In this case, a Microsoft Windows for Workgroups 3.11 system configured with the Windows NT Server Tools (supplied in the "ASTOOLS" share on the AFPS server) is used to configure the user.
Choose User Manager and pick:User, New User;Username: scorepNote: You can choose any name so it's a good idea to have "rep" as part of it.
Full Name: Replication User
Description: same
Password: scorep
Confirm: scorepNow click the "Password Never Expires" check box AND clear all the other check boxes. Leave the other settings as default.
(2) Next, the import server is set up to receive the files from the export server. Choose the "Server Manager" from the Windows NT Server Tools utilities. Click on the BDC, in this case "SCORE", which appears as a Windows NT 3.51 Backup Advanced Server which highlights the properties of the server.
Choose "Replication", set the "Import Directories" by clicking the check box which then should set the default Path to:
c:\usr\net\servers\lanman\shares\asu\repl\importfrom the List: SCOTEST.NOTE: At the bottom of the screen you will see the "Logon Script Path" set to:
c:\usr\net\servers\lanman\shares\asu\repl\import\scriptsClick "OK" and exit.In this case, the system "SCORE" is configured only to receive files, whereas it can be configured to both receive and send out files.
The services running on the BDC may be examined using the Server
Manager by choosing "Computer" and "Services". The "Directory
Replicator" status is listed as Started and Manual. This can be
altered by double-clicking on the entry and setting it to
"Automatic". In the bottom box of this screen, click on the square
button on the right side of the "This Account" line. Add the user
that was created earlier, "scorep". This adds "ASU1_DOM\scorep".
Confirm the user password again and click "OK". You should see the
message:The account ASU1_DOM\scorep has been granted the Log On As A service right and added to the Replicator local group
The "Replicator" service should now be started on the BDC. This
can be confirmed from the UNIX prompt using the command:# net start
These Advanced Server services are started:
BROWSER EVENTLOG REPLICATOR
NETLOGON ALERTER SERVERThe "imports" directory on this server will contain a flag file to indicate that no replication has taken place at the moment:
# pwd
/var/opt/K/SCO/asusrv/3.5.2n/usr/net/servers/lanman/shares
/asu/repl/import/scripts
# ls -al
-rw-rw-rw- 1 lmxadmin DOS---- 55 Dec 7 17:38 no_mastr.rp$In this example, the export server should copy its files to this directory.
(3) Next, configure the export server. Create a few test files in the export directory that should appear in the import directory, as mentioned in part (2). The default export directory already has some files there:
$ pwd
/var/opt/K/SCO/asusrv/3.5.2n/usr/net/servers/lanman/shares
/asu/repl/export/scripts
$ ls
netlogon.bat
netlogon.cmdThe "netlogon.bat" file can, for example, be altered to be replicated throughout your servers so that a standard logon script can be presented to your PC clients upon logon to the domain.
Create or place some test files into this directory to confirm replication to the import server. In this case, the files "test1.txt" and "test2.txt" are created.
The default import and export directories are used in this example but you can specify any replication directory you may require.
Next, configure the export replicator service.Assign the "scorep" logon account to the replicator service. From the NT Server Manager, highlight the export server and choose "Computer", "Services", "Directory Replicator", "Startup", set startup type to Automatic, and the "Log on As:" account name under "This Account" as (again by browsing by clicking on the square button option) "ASU1_DOM\scorep". Confirm the password again and click "OK".
Start the export replicator service via the Server Manager. This can be seen running on the UNIX system as:
# net start
These Advanced Server services are started:
SNMP BROWSER EVENTLOG
REPLICATOR NETLOGON ALERTER
SERVER# ps -ef |grep lmx
...
root 17588 1 0 07:52:11 ? 00:00:01 /usr/net/servers/lanman
/service/lmx.repl
..(4) The replicator services on both systems should now wait until stabilized and then transfer the files. Check the import server import directory for the test files.
While no replication is occurring, the flag file:
no_sync.rp$will be present. The replicator services on both servers can be stopped and restarted as a clean restart. Shortly thereafter, the files should appear in:
# pwd
/var/opt/K/SCO/asusrv/3.5.2n/usr/net/servers/lanman/shares
/asu/repl/import/scripts# ls
netlogon.bat
netlogon.cmd
ok.rp$
test1.txt
test2.txtThe contents of the "ok.rp$" flag file specifies where the files were successfully transferred.
(5) The replicator mechanism progress can be monitored by examining the creation of 3 files within the import first-level directory. These are:
no_mastr.rp$
no_sync.rp$
ok.rp$The first flag file, 'no_mastr.rp$', will appear when the import replicator service first starts. The directory is not yet receiving exports.
If the flag file 'no_sync.rp$' appears, the directory is receiving
updates from the export server but the data is not up-to-date. One
cause is that the import server does not have access permission at
the export server, that is, the replicator user account has not been
set up.When file replication succeeds, the file 'ok.rp$' should appear.
The behavior of the replication services on the systems (such things as under what conditions will the contents of an export directory be re-exported, or what subtrees will be copied) can be altered using the NT Server Tools Server Manager. Highlight the system and choose "Properties", "Replication", and the "Manage" options on the directories.
NOTES: File replication is handled by the AFPS "replicator" process. It is
different from AFPS account replication which transfers user account
details from PDCs to systems in the domain and is handled by the
AFPS "netlogon" process.File replication will work from AFPS to a LAN Manager BDC but you cannot replicate from a LAN Manager system to AFPS.
The default replication directories have changed from LAN Manager. These used to be "/usr/net/servers/lanman/repl/export" or "import".
While AFPS does support long filenames for file sharing, file replication does not support them and is limited to the transfer of files adhering to the 8.3 DOS naming convention.
See also
SCO Advanced File and Print Server System Guide, P124-137.