Backup Central

Dear Nathan,

The rsnapshot.conf file for your kind inspection:-

---
##################################
# rsnapshot.conf - rsnapshot configuration file #
#################################################

###########################
# SNAPSHOT ROOT DIRECTORY #
###########################

# All snapshots will be stored under this root directory.
snapshot_root /.snapshots/

#################################
# EXTERNAL PROGRAM DEPENDENCIES #
#################################

# LINUX USERS: Be sure to uncomment "cmd_cp". This gives you extra features.
# EVERYONE ELSE: Leave "cmd_cp" commented out for compatibility.
#
# See the README file or the man page for more details.
#
cmd_cp /bin/cp

# uncomment this to use the rm program instead of the built-in perl routine
cmd_rm /bin/rm

# rsync must be enabled for anything to work.
cmd_rsync /usr/local/bin/rsync

# Uncomment this to enable remote ssh backups over rsync.
cmd_ssh /usr/bin/ssh

# Comment this out to disable syslog support.
cmd_logger /bin/logger

#########################################
# BACKUP INTERVALS #
# Must be unique and in ascending order #
# i.e. hourly, daily, weekly, etc. #
#########################################

interval hourly 2
interval daily 7
interval weekly 4
#interval monthly 3

############################################
# GLOBAL OPTIONS #
# All are optional, with sensible defaults #
############################################

#link_dest 0

verbose 4

# Same as "verbose" above, but controls the amount of data sent to the
# logfile, if one is being used. The default is 3.
loglevel 3

# If you enable this, data will be written to the file you specify. The
# amount of data written is controlled by the "loglevel" parameter.
logfile /var/log/rsnapshot

# Default rsync args. All rsync commands have at least these options set.
#
rsync_short_args -a
rsync_long_args --delete --numeric-ids --rsync-path=/usr/local/bin/rsync

# ssh has no args passed by default, but you can specify some here.
#
ssh_args -i /root/.ssh/suse-rsync-key

# If this is enabled, rsync won't span filesystem partitions within a
# The default is 0 (off).
#
#one_fs 0

# If you enable the lockfile, make sure the lockfile directory is
# not world writable. Otherwise anyone can prevent the program from running.
#
#lockfile /var/run/rsnapshot

###############################
### BACKUP POINTS / SCRIPTS ###
###############################

# LOCALHOST
backup root < at > 10.1.1.228:/home/ home/
backup root < at > 10.1.1.228:/usr/d/ usr/d/
---

Wednesday, August 18, 2004, 7:49:36 AM, you wrote:

Can you please post a copy of your rsnapshot.conf file?

It appears the 'dest' key isn't getting initialized in the backup point
hash ref passed to the create_backup_point_dir() and
rsync_backup_point() subroutines. I'd like to know why, since the config
file validation is supposed to catch that.

Thanks!
-Nathan

Hi,

During my testing on rsync over ssh for one suse 9.1 box to pull data
from redhat 9, I got 2 errors:

[SuSE /home/test]/usr/local/bin/rsnapshot hourly
/bin/rm -rf /.snapshots/hourly.1/
/bin/cp -al /.snapshots/hourly.0/ /.snapshots/hourly.1/
/usr/local/bin/rsync -a --delete --numeric-ids \
--rsync-path=/usr/local/bin/rsync --rsh=/usr/bin/ssh -i \
/root/.ssh/suse-rsync-key root < at > 10.1.1.228:/home/ \
/.snapshots/hourly.0/home/
root < at > 10.1.1.228's password: [<<- I've to enter password]
[Rsync runs for some times...]
Use of uninitialized value in split at /usr/local/bin/rsnapshot line 2636.
Use of uninitialized value in concatenation (.) or string at
/usr/local/bin/rsnapshot line 2399.
[SuSE /home/test]

Can someone enlighten me with explanations?

Thanks!


Regards,
YM




-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss





-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss



--
Regards,

YM TAN

= A Quote A Day =
"Nearly all men can stand adversity, but if you want to test a man's character, give him power." (Abraham Lincoln)

Dear Nathan,

Thanks!! Did you receive the rsnapshot.conf file I sent?

Wednesday, August 18, 2004, 12:20:55 PM, you wrote:

It appears the outgoing SMTP server you're using is an open proxy:

<<< 550-[<http://dsbl.org/listing?ip=219.95.229.236>]
<<< 550-1.2 RCVD_IN_NJABL_PROXY RBL: NJABL: sender is an open proxy
<<< 550-[219.95.229.236 listed in combined.njabl.org]
<<< 550-0.1 RCVD_IN_SORBS_MISC RBL: SORBS: sender is open proxy server

If you follow that link, it can tell you (or your ISP) what to do
aboutgetting off that list. It seems it's likely that spammers can use
thatbox to relay mail through, and SourceForge's mail server has
subscribedto a blacklist that knows of such reported servers.

This URL will tell you more (from the DSBL site): http://dsbl.org/sender

Google "RBL" or "realtime blackhole list" if you want to find out more.

It seems you will have to either take this up with your
serviceprovider, or (if it's your server) secure the machine so it
can't beused as a spam relay.

Good luck!
-Nathan



--
Regards,

YM TAN

= A Quote A Day =
"Ideas are funny little things, they won't work unless you do. "