guntbert
New Around Here
my Systems
Prerequisite: get Telnet/ssh access with root/sudo privileges on both systems
use Web-PASM on both systems to start the replication, be patient
and wait for
- NS4300N, Firmware SR5.2 v01.05.0000.08 (http://firstweb.promise.com/upload/Support/Firmware/ns4300_010508_P3.upg) as receiving server (i.e. backup, I don't want to have it running all the time)
- NS4600, Firmware SR2.1 02.01.0000.18 (http://www.promise.com/support/download_file.aspx?rsn=931&m=205®ion=en-US) as sending server
Prerequisite: get Telnet/ssh access with root/sudo privileges on both systems
- NS4300N: I got dropbear from http://www.16paws.com/projects/NS4300N/dropbear.html (if you scroll down you will find the link for the complete plugin within the text). That plugin made it possible to login with the "admin" account (via telnet (port 2380) and ssh) and gave "admin" sudo permission (sudo -s will give you a root shell if needed )
- NS4600: I followed http://savoryape.com/2009/10/nasaga-or-pwng-the-promise-smartstor-4600/, I do not care very much about the problem to have repeat step (7) after every reboot, the system runs 24/7
- edit the rsync-configuration on at least one system (so that they match, obviously if only one system acts as primary server and the other as backup server not all settings are relevant)
- /etc/rsync.conf: leave alone, gets its content from PASM
- /etc/rsync.passwd: used in the server that initiates the replication
- /etc/rsyncd.conf: only important on the receiving (=backup) server. Begins with a common part, then follow the "modules", handled by WebPASM again, really important is the "auth users" line, it can contain more names too...
- /etc/rsyncd.secrets: thats the place where promise likes to change things, only important on the receiving server, the format is nameassword
# RSYNC Authentication File
promiseromise
use Web-PASM on both systems to start the replication, be patient
and wait forin the system log
Last edited:
