Delta copy is a cool program that allows you to copy data from one computer to another for backup. It works great! The documentation says that it's just a wrapper program that really runs rsync.
It uses port 873, so I had to open that port on the firewall on Jupiter which is the computer that I'm using as the server right now.
-------------------------------------------------------------------------------------------------
1. See if rsync.exe is running through the Task Manager. DeltaCopy server spawns this process in the back-ground
2. If it is running and still you cannot connect using the telnet command, it could mean that the OS is not letting the server listen on a priviledged port (873). Ensure you are running the server under "Administrators" account.
3. Suggestion: By pass DeltaCopy server and try starting rsync daemon on its own. This is by by using the following command.
rsync.exe -v --daemon --config=deltacd.conf --no-detach
See if this runs on its own.
----------------------------------------------------------------------------------
8-may-09 You can screw things up by not having the proper permissions on the target folder on the deltacopy server. I am currently using jupiter as the deltacopy server.
I discovered after much experimentation that (duh!) you have to have the correct permissions to view files on jupiter that were copied there from Blackhawk by deltacopy. When I tried to view files on jupiter that were copied there by deltacopy, it would always say "permission denied". So I would change the owner of the folder to tayloe and then give tayloe full control. But what I did not realize that this made the folder inaccessable from blackhawk because user tayloe on blackhawk had no rights to the folder. So the solution was to give use everyone full control of the folder.
The reason deltacopy worked at first was that when I made a new folder on blackhawk to copy files to jupiter using deltacopy, deltacopy itself would create the folder on jupiter, and so deltacopy (the system user??) had access to that folder on jupiter. But then it would stop working when I changed the owner to JUPITER\tayloe because deltacopy no longer had rights to the folder.
----------------------------------------------------------------------------------------
9-may-09
rsync on linux
The command that successfully copied the folder (and contents) called "varsity_to_legacy" on varsity to legacy is:
rsync -vrt /home/tayloe/varsity_to_legacy 192.168.1.20:/home/tayloe
If you put a trailing slash at the end of the source, it will not create the folder on legacy,it will just dump the files into /home/tayloe on legacy.
----------------------------------------------------------------------------------------
13-may-09
At first I could not get the Deltacopy server to run on Blackhawk after the wipe out of Windows XP Home and the installation of Windows XP Pro. It said there was a login failure. It was set to log in under the name tayloe which should certainly work. I fixed it by going into Control Panel --> system --> services and scrolling to Deltacopy and wiping out the name tayloe and choosing tayloe again from the name picker and retyping in the password. Then the deltacopy server started fine. I don't know why that fixed it.
----------------------------------------------------------------------------------------
15-may-09
I was able to successfully copy files from jupiter to legacy by typing the following command at a command prompt on jupiter:
rsync -vrt /cygdrive/e/aaa 192.168.1.20:/home/tayloe
This is the first time I've copied files from Windows to Linux. The command copies all the files on the e:\aaa folder on jupiter to the /home/tayloe folder on legacy.
----------------------------------------------------------------------------------------
According to http://everythinglinux.org/rsync/, a single colon in the remote path specification means "use ssh". A double colon means "use rsh" (rsh means that no encrytion will be used). So apparently the above command I used to copy from jupiter to legacy uses ssh.
In the next to last line of script below (from http://finmath.uchicago.edu/~wilder/Security/rsync/), the term "mach3::rsync" means backup files FROM a remote computer called mach3 and use the specifications found in the section entitled "rsync" in the file on mach3 called /etc/rsyncd.conf. The double colon implies that ssh encryption will NOT be used.
#!/bin/bash
# The argument this script is called with, either 1 or 2
ext=$1
# The full paths of the programs used in this script
rsync=/usr/bin/rsync
mount=/bin/mount
umount=/bin/umount
# Good rsync options for backups.
rsync_opts="-av --delete --delete-excluded"
# The name of the file containing the rsync connection password
password="--password-file=/etc/.rs_pass"
# A list of files and directories that do not need to be backed up
exclude_list="noback/ core .kde/ .gnome/ .netscape/cache/ Cookies/ backup/"
excludes=""
for exclude in $exclude_list; do
excludes="$excludes --exclude=$exclude"
done
# Backup /home on mach1 to /backup/mach1_1/home or
# /backup/mach1_2/home depending on the argument the script
# was called with. Dump any output and error messages to
# /etc/backup/mach1_home_1 or /etc/backup/mach1_home_2
$rsync $rsync_opts $excludes /home /backup/mach1_${ext}/ > \
/etc/backup/mach1_home_${ext} 2>&1
# Backup /profiles on mach1
$rsync $rsync_opts $excludes /profiles /backup/mach1_${ext}/ > \
/etc/backup/mach1_profiles_${ext} 2>&1
# Backup /etc on mach1
$rsync $rsync_opts /etc /backup/mach1_${ext}/ > \
/etc/backup/mach1_etc_${ext} 2>&1
# Backup mach2 and mach3 according to the [rsync] sections
# of the rsyncd.conf files on the two machines. Use the
# password given in /etc/.rs_pass.
$rsync $rsync_opts $excludes $password mach2::rsync \
/backup/mach2_${ext}/home/ > /etc/backup/mach2_${ext} 2>&1
$rsync $rsync_opts $excludes $password mach3::rsync \
/backup/mach3_${ext}/home/ > /etc/backup/mach3_${ext} 2>&1
No comments:
Post a Comment