Deprecated: Assigning the return value of new by reference is deprecated in /var/www/ud02_38/html/dokuwiki.en/inc/parserutils.php on line 159 Deprecated: Assigning the return value of new by reference is deprecated in /var/www/ud02_38/html/dokuwiki.en/inc/parserutils.php on line 162 Deprecated: Assigning the return value of new by reference is deprecated in /var/www/ud02_38/html/dokuwiki.en/inc/parserutils.php on line 293 Deprecated: Function split() is deprecated in /var/www/ud02_38/html/dokuwiki.en/inc/auth.php on line 103 Deprecated: Function split() is deprecated in /var/www/ud02_38/html/dokuwiki.en/inc/common.php on line 737
The Intradisk Software Replication Manager (ISRM, more info on www.intradisk.com) is a plugin for all professional Intradisk MiniServers and used for active pulling of backups from Windows network shares using protocol called cifs, smbfs or samba. This plugin is especially designed for professional software distribution and update services e.g. for companies with widespread agency networks. This means saving enormeous network bandwitdth using the intradisk as local software distribution points in every small agency. Intradisk MiniServers are as small (size of pocket book) as economically priced to be the ideal solution for an “all agencies software package station” e.g. for SMS2003, Novell Z.E.N Works or Install.Desk software distribution and update services.
Therefore this system is also designed for high efficient transportation of any backup data throughout lowest bandwidth networks. This means very short synchronisation cycles even over very “slow” uplink channels like DSL internet connections as well as generating very low network impact even when transmission of big files. The high efficient intradisk mini servers are also designed for highest reliability (fanless, passive cooled & shock resistant) are noiseless and running at lowest energy costs ~10$ per year.
This field shows brief status information generated before or during the last active process. If you need more details e.g. for solving of a configuration error, please take a look at the log file using the button or the direkt network SMB-share access to the target directory. All informations are logged in clear text to a file in the target directory called <target>/rsync.status.<hostname>.ddmmyyhhmm.log where the last number indicates the time when the last process was terminated.
default: none #indicates no process has ever been started, e.g. when the plugin was disabled
Parameters in this menu are used for all general source share configurations containing data to be synchronized or backuped to the target directory.
This parameter is the DNS network host name or an IP address providing a Windows/CIFS/Samba network share which is used as the source for replication of pull backup data. In company wide software distribution and update systems, this is normally beeing a Windows-server with a share containing all the software packages like service packs, patches, updates and bugfixes for any clients Workstation.
default: server
This is the name of the source share containing any backup data, packages, updates and service packs. Hidden shares that are not beeing browseable in the network are specified with a trailing ‘$’ like in the default example.
default: package$
This directory specifies the source directory and is a subdirectory of the mounted network share. Special care has to be taken wether using a trailing “/” or not meaning to backup directories or files with or without the prefixed source directory name.
default: /export/server/install.src/packages
The three octal digits refer to read/write/execute permissions for owner, group, and other. The value of each specified digit is subtracted from the corresponding ‘digit’ specified by the system here especially for the source share before copying. For example, syncmask 022 removes write permission for group and other (files normally created with mode 777 become mode 755. Files created with mode 666 become mode 644).
The syncmask variable can be little confusing to use, because it does work as a mask. In other words, you set the permissions that you do not want in the syncmask. To calculate permissions which will result from specific syncmask values, subtract the syncmask from 777 for files and the same for directories.
If you want all files created with permissions of 666, set your syncmask must be set to 111. Alternatively, if you want all files created with permissions of 000, set your UMASK to 777.
A reasonable value for UMASK is 022, which will cause files to be synced with permissions of 644 (rw-r--r--) and directories to be created with permissions of 755 (rwxr-xr-x). A more secure value for UMASK is 066, which will cause files to be synced with permissions of 600 (rw-------) and directories to be created with permissions of 700 (rwx------).
If you set your syncmask to auto we try to determine the value from the target directory but changing a syncmask 0000 to 0111 and 0222 to 0333 to remove the executable flag from files beeing interpreted as hidden + Archive when synchronizing samba shares for backups and otherwise causing trouble using AD/ACL filesystem structures.
default: auto (especially when using AD,ACLs & EAs)
The target parameter is defining the directory used as the reference target and for storing all replicated backup data. The directory is created once if it is not existing. As user and group ID the standard samba users IDs are used or the users AD-Environments data (AD-Plugin required). Last but not least any numeric IDs can be used depending on whatever this directory is beeing changed to later on.
default: /export/server/install.tgt
This is the username having at least read only access to the network source share.
default: workgroup\samba
This parameter is the the password for read only accessing the source network share.
default: pas$word
The rsnetload parameter controls the used network bandwidth. It can be specified ether using a trailing “%” relative to the maximum possible bandwith (9,6MB/s) or in kB/s using a trailing “k”.
default: 100%
This parameter uses a kind of “reverse cron” syntax for defining the time interval when the replication process has to be scheduled. For highest flexibility you can use any cron syntax like in the following reverse order: “WeekDay:Month:MonthDay:Hour:Minute”. Unneeded positions can be replaced with the wildcard “*” or can be completely removed like 7:00 (pm). The default example starts the replication process every day, every month at exactly 8 pm in the evening.
default: 0-6:1-12:*:20:00
the syntax is ecactly the same like of the above parameter. The default example is sending an interrupting stop signal to an unterminated replication process every workdays morning to keep the network impact at a minimum when people are at work.
default: 1-5:1-12:*:8:00
This document describes options and features derived from smbreplicator plugin version V0.9.0.