Re: [BackupPC-users] Windows XP reboots while rsyncing
Looks like a filesystem panic. Did you try checkdisk on partitions you backup? Le Wednesday 15 March 2006 10:25, Alain a écrit : Hi all, We have two Windows XP hosts that sometimes reboots while backuppc is backing up datas from these hosts. The backup method chosen on both hosts is rsyncd. It seems that the problem occurs while running a X11 server on these hosts. Has anyone ever seen this problem ? -- Olivier LAHAYE Motorola Labs IT Manager Computer Information Systems European Communications Research --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
[BackupPC-users] ReL rsyncd's problem
Hello, I have backuppc for backupping up my windows pc and linux servers. I have installed cygwin-rsyncd-2.6.2.0 and used rsyncd's method for my windows pc. With one of my windows pc, i have this problem : when i install the rsyncd's package and want to start the rsyncd service , this message appears : the processus is stopped without opnion :error 1067. This pc is a HOTON with Windows XP Pro service Pack2 installed. What is the reason of this message and how to resolve it. Thanks a lot for your help! I had problems installing the rsyncd service on mulitple Windows XP machines. The way I got around it was to install Cygwin on one machine and start removing files from the install until I had the minimum number of files to make it work. I ended up with following files: cygiconv-2.dll cygintl-1.dll cygintl-2.dll cygintl-3.dll cygintl.dll cygrunsrv.exe cygserver-config cygwin1.dll nice.exe rsync.exe rsyncd.conf rsyncd.secrets I also had to create the folder c:\cygwin\var\log. The nice.exe is only needed because I wanted the rsync process to run a lower priority. I then took all these files stuck them in a network share, created a batch file to copy them and add rsync as a service. Let me know I will zip them together and email you the zip Bryan Penney --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
[BackupPC-users] backupPC nightly backups spilling into the day...
Hi All,
I have recently added about 15-20 hosts to the backup system, which was
already backing up about that number of hosts nightly. My $Conf{MaxBackups}
was set to 2 but is now set to 4. Also, hardlinks were not being created in
the cpool because it was on a different filesystem than that of the PCs and
therefore I had corrected these and so hard links are now being created.
Also, an important note, I am using smb to backup windows servers (NT) (to
avoid installing cwrsync) and rsync and ssh to backup all new linux/bsd
boxes since none have rsyncd installed and have endless dependencies when
trying to install it.
I would imagine at first instance that a machine using rsync+SSH is put on
backup but the auto-login setup in .ssh is incorrect and so is prompting for
a password on the server and so delaying the backup...is this possible? But
the logs dont seem to hint at this possiblity.
Ontop of all that my backupPC server has slowed down dramatically...
Now it seems that the consequence of some or all of these actions is a
constant running of backup at night and for most part of the day. Possible
solutions seem to be:
- increase MaxBackups variable further
- decrease the WakeupSchedule variable since the clients are constantly on
the network; currently backupPC wakes up every two hours between 18:00 and
7:00, but I think I can change it to 2 or 3 times in the night(?); I am
assuming here that unneccesary wakeups waste time?!
- increase the BackupPCNightlyPeriod variable from 8 (current) to about 16
to further shorten the time it takes to traverse the pool (keeping in mind
the pool will grow since links have only just been started to be created).
- increase the FullPeriod and IncrePeriod variables so that the server is
not congested every night; current settings are 6.97 and 0.97 respectively,
but how can set incrementals for different machines to happen on alternate
days so I get load balancing on the backupPC server?
Anyway, please could anyone suggest why I am having this problem and how to
overcome my problem and/or comment on the above proposal in terms of
effectiveness, etc.
BTW
1. How can I clear all pending backups other than by going into each host
being backed up and stopping it?
2. At every wakeup, does backupPC reload the per-pc configs? Or do I need to
restart backupPC everytime I update a per-pc config?
Kindest Regards
Khaled
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
[BackupPC-users] FileList Receive failed - problem with version of rsync from yum repository
Just to let you all know, on monday one of my client machines (FC3)
performed an automated yum update and updated the rsync rpm to version
2.6.7-1.1.fc3.rf (provided by the Dag repository). Immediately after
this the next (and all subsequent) backups failed to complete with the
'FileListRecieved failed' error. This version of rsync uses protcol
version 29.
I made some changes to the client config so that $Conf{RsyncShareName}
changed from '/' to a list of each of the directories under '/' that I
wanted backing up. It subsequently failed on /home (the biggest
directory 2GB in size). Removing /home from the list meant that it
completed all the other directories.
Removing /home permanently is not an option, and using individual share
names for each directory under '/' and under '/home' is not ideal (what
happens when the user creates a new directory under '/' or when a new
user account is added - it won't get automatically backed up). So I
needed to go back to backing up '/'. I fixed the problem by reverting to
an older version of rsync (version 2.6.3 protocol version 28). Here are
the steps for anyone interested:
1. Remove the current rsync package:
rpm -e --nodeps rsync
2. Check what other versions of rsync are available:
yum --disablerepo=dag list rsync
If you are happy with the version listed (and the repository it comes
from) then goto step 3, if not add another --disablerepo to remove the
repository that supplies the version listed by the command above.
3. Install the version from another repository:
yum --disablerepo=dag install rsync
In my case all now appears to be going smoothly.
In the long run I should either disable these repositories, or only
allow them to update packages that were explicitly obtained from them.
I do have a question: does anyone know what the rsync options --server
and --sender do? I can't find them documented anywhere.
Hope that's of some use to the list
Dylan
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please reply to this email and then delete it. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Future.
The recipient should check this email and any attachments for the presence of viruses. Future accepts no liability for any damage caused by any virus transmitted by this email.
Future may regularly and randomly monitor outgoing and incoming emails and
other telecommunications on its email and telecommunications systems. By
replying to this email you give your consent to such monitoring.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
Re: [BackupPC-users] Status of Mac OS X tar vs. xtar
On Mar 16, 2006, at 5:41 PM, Ski Kacoroski wrote: Tar on OSX10.4 and later supports resource forks. That said, I do not know how it works with BackupPC which is why I have continued to use xtar (also because I have a mix 10.2, 10.3, and 10.4 client base). I have a pure 10.4 client base and am using tar without issue (that I know of). Tony Del Porto SysAdmin USENIX Association 2560 9th Street, Suite 215, Berkeley CA 94710 [EMAIL PROTECTED] | www.usenix.org | www.sage.org --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
[BackupPC-users] Rsyncing ACLs with Cygwin
Thought I would let folks know that the latest CVS version of the rsync ACLs patch works with Cygwin. My guess is that they will roll it in the next release (2.6.8 I believe). If your interested in being able to rsync and still preserve ACLs when rsyncing between Windows and Linux/Unix, this latest release does the trick. Dont know about you, but this eliminates my need to hang on to bulky ntbackup files and/or using robocopy to fix ACLs after rsyncing. It also makes BackupPC way more powerful a solution for windows backups as you can now preserve security settings when backing up and restoring. Here is the link to the mail list thread if your interested. http://www.mail-archive.com/rsync@lists.samba.org/msg15853.html
