ginal Message-
From: Derek Stevens via BackupPC-users
Sent: Friday, November 8, 2019 2:33 PM
To: marki ;
backuppc-users@lists.sourceforge.net
Cc: Derek Stevens
Subject: Re: [BackupPC-users] Host key verification failed
Marki,
When I say "to the client from the server" I mean that am ini
Marki,
When I say "to the client from the server" I mean that am initiating SSH
and Rsync from the BackupPC server to the backup client.
I agree that it makes no sense, that's why I'm stumped and I'm writing you.
Here's an ssh into the backup client:
# su b
Hello BackupPC users,
I am coming to you guys with a problem I've been having trying to set up
a client backup with the Rsync method and an SSH key.
I am able to SSH and Rsync to the client from the server on the command
line using the SSH key, and the server is in the client's k
Hello,
Do I understand correctly there's no answer to this?
I have "solved" this problem by pinging a different IP. I still can't
understand why hping response doesn't suit BackupPC. Does it expect the
exact string format in ping command output?
Sincerely,
Konsta
Hello,
While running BackupPC 3.2.1 (CentOS), I found I can't set up backups
for a host that can't be reached via ICMP Ping.
I have hping installed, and modified default PingCmd for the host in
question with
/usr/bin/sudo /usr/sbin/hping $host -p 80 -c 1 -S
When I run it unde
compression required isn't very
large: only new files not already in the pool need to be compressed. It's
not likely compression is a bottleneck.
Craig
On Mon, Sep 30, 2019 at 5:33 PM wrote:
> Hey guys,
>
>
> Is there such a setting or is backuppc genuinely single threaded when it
On 11.09.2019 18:19, Robert Trevellyan wrote:
I'm letting ZFS do the compression (using the default of LZ4) with BackupPC
handling deduplication. I think you'll find a reasonable consensus that ZFS
compression is always a win for storage space (it will store un-compressible
data
t 2:56 PM, Mike Hughes wrote:
>
> No responses. Too much detail? Let me rephrase it:
>
> Windows rsync backup no worky!
> plz halp!!!
> :-D
>
> On Thu, 2019-08-15 at 14:44 -0500, Mike Hughes wrote:
>
> Working to add a few Windows clients to our BackupPC system. I have
>
port for SMB3 with version 4.0.0. I don't
> have any CentOS boxes, but it looks like CentOS 7 has Samba 4.8.3
>
> The notes I made back when I updated our BackupPC servers to support
> Windows 10 tell me that I had trouble with Samba 4.8.0+, so I'm using
Dear all Users,
I have a running copy of BackupPC v4.21 on my Oracle Linux 7.?? It is
running well even though I don't need it to backup anything.
Now, my question is: how do I update my BackupPC to v4.31 from the tar
ball file?
Thanks for any opinion.
ged from 23 to 027. Does anybody
> know exactly which files and folders this relates to and what if anything I
> need to chmod after the change?
>
>
>
> From what I can see, the data dirs and files created are already 760 and
> 540.
>
>
> Kind regards,
>
> Jamie
> _
ome
> so fixing that means I have to coordinate with the user to meet him when
> he's at the office and not busy using the host. It's just easier to
> change the ping setting. And, since Windows defaults to disallowing
> ping, perhaps this change is a good choice for all W
Please look in the LOG files (main BackupPC LOG and per-host LOG) to see
whether backups were started or not, and whether that matches what your
configuration specifies.
Craig
On Tue, Aug 6, 2019 at 8:01 AM Norman Goldstein wrote:
> Haven't seen your config.pl file, but this might expl
Hello again,
On Sat, 3 Aug 2019, Ted Toal wrote:
I am NOT sure whether bandwidth limitation is what I want. ... only
backing up our lab?s small portion of the data ... only backing up
files less than 1 MB ...
BackupPC shines, I think, in less well-constrained situations.
Given the
Hi there,
On Fri, 26 Jul 2019, Ted Toal wrote:
Is it easy to make updates to the documentation?
I haven't seen a reply to this so I'll take a stab at it, although I
don't really know the proper procedure. Mr. Barratt will know.
It's not clear to me where you saw the &qu
Yes, that bug is fixed in the latest versions of BackupPC (4.3.1) and
rsync_bpc (3.1.2.1). It sounds like you have the latest BackupPC, but you
will need to upgrade to the latest rsync_bpc.
Craig
On Mon, Jul 29, 2019 at 12:29 PM Alexander Kobel wrote:
> Hi,
>
> On 29.07.19 18:30, Pi
Could your backup be trying to backup large virtual or sparse files, eg, in
/proc or /var/wtmp?
Craig
On Mon, Jul 29, 2019 at 4:48 AM Mariano Sanfilippo
wrote:
> Hello, i have connected backuppc to my client server through ssh keys and
> rsync, on the client i had a user backuppc th
Hi there,
On Thu, 25 Jul 2019, Ted Toal wrote:
...What about filename and file directory, do these have to match
for a pair of files to be identical?
They wouldn't be identical files. They'd be the same file. :)
--
73,
Ged.
___
Back
Also Centos 7, just upgraded to 4.3.1 via the hobbes1069 copr repo.
Here's your problem:
>
> Alias /backuppc//usr/share/BackupPC/html/
> Alias /BackupPC/ /usr/share/BackupPC/html/
> ScriptAlias /BackupPC_Admin /usr/share/BackupPC/sbin/Ba
p correctly
> without an error message. I tried this with rsync_bpc 3.0.9.13 and
> rsync_bpc 3.1.2.0 (although these have the the BPC_FTYPE_DELETED fix
> <https://github.com/backuppc/rsync-bpc/commit/07b18a3469caefc72c01546515973dd1dc21deb4>
> I committed last week).
>
Hello again,
On Wed, 17 Jul 2019, David Koski wrote:
I suspect there are over ten million files but I don't have a good
way of telling now.
This indicates to me an issue more fundamental than not being able to
back up a few files using BackupPC. You need to have *some* kind of a
hand
Raoul Bhatia wrote at about 08:07:34 +0200 on Tuesday, July 16, 2019:
> I'd actually recommend rolling proper Debian packages instead of using a
> script to manually compile software on a production server.
>
> My HOWTO and pre-built packages can be found here:
> https:/
04 LTS and I installed originally from the
> > script on this page.
> >
> >
> https://github.com/backuppc/backuppc/wiki/Installing-BackupPC-4-from-tarball-or-git-on-Ubuntu
> >
> > Thanks
> > Mark
>
> It's unfortunately not that simple as you ne
Mark Wass wrote at about 13:20:24 +1000 on Tuesday, July 16, 2019:
> Hi Guys
>
> Is there a How-To on upgrading from 4.3.0 to 4.3.1?
>
> I'm running 4.3.0 on Ubuntu 18.04 LTS and I installed originally from the
> script on this page.
>
> https://gith
BackupPC 4.3.1 <https://github.com/backuppc/backuppc/releases/tag/4.3.1> has
been released on Github. This release has a number of bug fixes.
In addition, rsync-bpc 3.0.9.14
<https://github.com/backuppc/rsync-bpc/releases/tag/3.0.9.14> and rsync-bpc
3.1.2.1 <https://github.com/bac
In addition to the helpful suggestions, are you sure you are not backing up
any sparse or virtual files (eg, /var/log/lastlog, /proc etc)?
Craig
On Tue, Jul 9, 2019 at 5:43 AM G.W. Haywood via BackupPC-users <
backuppc-users@lists.sourceforge.net> wrote:
> Hi there,
>
> On
Hi there,
On Mon, 8 Jul 2019, David Koski wrote:
I am trying to back up about 24TB of data that has millions of files.?
It takes a day or to before it starts backing up and then stops ...
Your post is a little light on detail.
BackupPC installations routinely back up that kind of data
Is rsync running as root on the client side? If not, it won't have
permission to chown files to root. An example setting would be:
$Conf{RsyncClientPath} = 'sudo /usr/bin/rsync';
This requires the backuppc user to have sudo privileges. You should
exercise some caution in doin
(cannot
convert filename). But when ClientCharset is empty, it backs up correctly
without an error message. I tried this with rsync_bpc 3.0.9.13 and
rsync_bpc 3.1.2.0 (although these have the the BPC_FTYPE_DELETED fix
<https://github.com/backuppc/rsync-bpc/commit/07b18a3469caefc72c01546515973dd1dc2
Pete Geenhuizen wrote at about 12:43:58 -0400 on Thursday, July 4, 2019:
>
>
> On 07/04/2019 11:27 AM, backu...@kosowsky.org wrote:
> > Pete Geenhuizen wrote at about 06:09:04 -0400 on Wednesday, July 3, 2019:
> > > I upgraded BackupPC from V3 to V4 sever
Pete Geenhuizen wrote at about 06:09:04 -0400 on Wednesday, July 3, 2019:
> I upgraded BackupPC from V3 to V4 several months ago which went
> relatively smoothly.
>
> I have been able to successfully restore system files and presumed that
> all was running well. Yester
Thank you both very much for your answer an explanation. after checking
with the ls -i command the two files are indeed on the same inode.
Le 01/07/2019 à 04:22, Adam Goryachev a écrit :
On 28/6/19 9:46 pm, Jean-Louis Biasini via BackupPC-users wrote:
Hi all,
I have a working installation
Hi Craig!
Thanks for your answer. I'm running the version from epel repository,
tagged as: 3.3.1-5.el7
jean-louis
Le 30/06/2019 à 19:58, Craig Barratt a écrit :
Jean-Louis,
What version of BackupPC are you running?
Craig
On Fri, Jun 28, 2019 at 5:11 AM Jean-Louis Biasini via Bac
Jean-Louis,
What version of BackupPC are you running?
Craig
On Fri, Jun 28, 2019 at 5:11 AM Jean-Louis Biasini via BackupPC-users <
backuppc-users@lists.sourceforge.net> wrote:
> Hi all,
>
> I have a working installation on a centos7 server. I'm backing up 30+
> linux
ain on the second backup. I also checked
the hard link limit that I increased from 32000 to 64000 (ext4
file-system here) with no improvement. Am I missing something?
Many thanks
jean-louis
___
BackupPC-users mailing list
BackupPC-users@lists.sourc
ain on the second backup. I also checked
the hard link limit that I increased from 32000 to 64000 (ext4
file-system here) with no improvement. Am I missing something?
Many thanks
jean-louis
___
BackupPC-users mailing list
BackupPC-users@lists.sourc
al Physics)
wrote:
> Hi Craig,
>
>
>
> Thanks for your reply.
>
>
>
> Is there a file size limit on the output zip or tar from BackupPC?
>
>
>
> It’s a bit odd that it’s able to create the folder it’s going to write to
> and then just stops.
>
>
>
ig Barratt wrote at about 21:43:38 -0700 on Monday, June 24, 2019:
> > Jeff,
> >
> > I suspect you'll get the same error if you use native rsync and tell it
> to
> > convert utf8 to utf8 (eg, add '--iconv=utf8,utf8' to your native rsync
> > command).
>
ot;","user.rsync.%aacluser.rsync.%aacl",0)
failed: No such file or directory (2)
Not sure why this error is happening suddenly when most of these files
haven't changed.
Now that being said, I don't have SELinux turned on for my system but
the error never occurred
e rsync to no longer attempt any charset
conversion.
Craig
On Sun, Jun 23, 2019 at 6:13 PM wrote:
> Craig Barratt via BackupPC-users wrote at about 13:59:46 -0700 on Sunday,
> June 23, 2019:
> > The error you are getting is when rsync_bpc is trying to use iconv to
> > convert
Jeff,
You are correct that the $vars and %Conf options are missing. I just committed
a fix
<https://github.com/backuppc/backuppc/commit/357e8376f6f659a1b2281f9172c8b62e8f4e21e7>
.
Craig
On Sat, May 18, 2019 at 9:29 PM wrote:
> backu...@kosowsky.org wrote at about 23:19:58 -0400 on
nut on the most recent backup (eg, use
BackupPC_attribPrint)?
Craig
On Sun, Jun 16, 2019 at 3:44 PM wrote:
> backu...@kosowsky.org wrote at about 22:09:29 -0400 on Saturday, June 15,
> 2019:
> > I am using backuppc 4.3.0 to backup an Ubuntu 18.04 Linux server using
> > rsy
The error you are getting is when rsync_bpc is trying to use iconv to
convert the client file name encoding to utf8 (which is the native format
that BackupPC on the server).
What is $Conf{ClientCharset} set to for this host? If it is empty then
rsync_bpc should skip any charset conversion, so I
’ve got that working.
>
>
>
> However, I appear to be back to a similar error as before.
>
>
>
> Running: /usr/bin/smbclient restoredestination\\D\$ -U account -E -d
> 1 -c tarmode\ full -mSMB3 -Tx -
>
> Running: /usr/local/BackupPC/bin/BackupPC_tarCreate -h restoresource -
You definitely shouldn't do that. BackupPC isn't aware that they point to
the same real host. Currently you have 6 "different" hosts, each with
their own configuration and backups.
With your proposed change, only one host ("A") would be visible (duplicate
lines w
nteresing. Thanks for the troubleshooting!
>
> --
> Carl Soderstrom
> Systems Administrator
> Real-Time Enterprises
> www.real-time.com
>
>
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> Lis
Hi there,
On Sat, 22 Jun 2019, Carl Soderstrom wrote:
On 06/21 06:07 , Patrick B?gou wrote:
I'm using BackupPC 3 for many local PCs. I would like now to backup some
data from a remote server, located in another entity and where I need to
go throught a frontend
BackupPC <<---
backu...@kosowsky.org wrote at about 22:09:29 -0400 on Saturday, June 15, 2019:
> I am using backuppc 4.3.0 to backup an Ubuntu 18.04 Linux server using
> rsync.
>
> 1 get the following (unexplainable) rsync errors:
>
> [1] file has vanished: "/etc/apt/
Michael Stowe wrote at about 03:35:13 + on Sunday, June 16, 2019:
> On 2019-06-15 19:20, backu...@kosowsky.org wrote:
> > I am running backuppc 4.3.0 on Linux Ubuntu 18.04
> >
> > I have a file copied over from an old Windows installation to my Linux
> > server
I am using backuppc 4.3.0 to backup an Ubuntu 18.04 Linux server using
rsync.
1 get the following (unexplainable) rsync errors:
[1] file has vanished: "/etc/apt/apt.conf.d/20archive.~1~
This file which seemingly refers to an emacs backup file, has not
existed on my server for m
David Wynn via BackupPC-users wrote at about 15:53:25 -0600 on Friday, June 7,
2019:
> -Original Message-
> From: G.W. Haywood via BackupPC-users
> Looks like you might have installed BackupPC from more than one, er, source.
> In the interests of their own san
-Original Message-
From: Adam Goryachev [mailto:mailingli...@websitemanagers.com.au]
Sent: June 10, 2019 5:54 PM
To: backuppc-users@lists.sourceforge.net
Subject: Re: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to
client
Apologies, the last email was truncated...
Hi David,
id Wynn
Subject: RE: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to
client
Hi, David.
Try commenting out "HostName 192.168.1.6" from your ssh.conf, AND adding
"192.168.1.6" (without "" marks, when done via the gui) to the
ClientNameAlias for the host nbox, and
t often be pulled in
to another Perl script very early in the script's code (it's common to
see a few 'use' statements at the top of a script) - something like:
use BackupPC::Lib;
which in this example, assuming that the paths are set up properly so
that Perl can find it, would pull
doneInit = 1
Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0
sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 2 inode
Parsing done: nFilesTotal = 0
rsync error: remote command not found (code 127) at io.c(226)
[Receiver=3.1.2.0]
rsync_bpc exited with fatal status 127 (
went back
to your OP and that prompted me to grab the version of BackupPC that
you're using - or at least try to. I grabbed BackupPC-4.3.0 from link
https://github.com/backuppc/backuppc/releases/download/4.3.0/BackupPC-4.3.0.tar.gz
near the bottom of
https://github.com/backuppc/backuppc/rel
BEERS/*'
]
};
$Conf{RsyncClientPath} = 'rsync';
...
You need the full pathname for $Conf{RsyncClientPath}, not just the
name of the executable.
--
73,
Ged.
___
BackupPC-users mailing list
BackupPC-users@lists.source
ling at the same place . somehow getting the IP address stuck
in the command being sent ..
DW
From: Michael Stowe [mailto:michael.st...@member.mensa.org]
Sent: June 7, 2019 4:44 PM
To: General list for user discussion, questions and support
Cc: m...@visionary.com; David Wynn
Subject: Re: [Ba
-Original Message-
From: G.W. Haywood via BackupPC-users
[mailto:backuppc-users@lists.sourceforge.net]
Sent: June 7, 2019 7:34 AM
To: backuppc-users@lists.sourceforge.net
Cc: G.W. Haywood
Subject: Re: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to
client
Hi there,
On
r to it.
Looks like you might have installed BackupPC from more than one, er,
source. In the interests of their own sanity, package maintainers for
the likes of Debian, Ubuntu and derivative distributions do (shall we
say) interesting things with the files and directories used 'upstream&#x
I’ve just noticed that there are two directories on the new servier – both for
‘backuppc’! One of the directories is ‘BackupPC’ (note the caps) and the other
is simply ‘backuppc’. The latter contains a config.pl (2016/12/14) file as
well as Apache.conf (2019/5/29), hosts (2016/12/14
… aaarrrggghh (I almost hate
technology!)
From: Dave Wynn [mailto:dewyn...@yahoo.ca]
Sent: June 5, 2019 1:19 PM
To: m...@visionary.com
Subject: Re: [BackupPC-users] BACKUPPC V4 - rsync-bpc error connecting to client
Sent from Yahoo Mail on Android
<https://go.onelink.me/107872968?pid=InProduc
Hi there .. I have a small home network and have been using Backuppc for the
past 5 years. The last system was based on Ubuntu 16.04.6 LTS and Backuppc
V3.3.1. I was originally using SMB for backing up our PC's and NETSTORE
device but recently switched to using RSYNC/RSYNCD - and everythi
).
Craig
On Tue, May 28, 2019 at 5:45 AM Sriram ARUN EXCELLO
wrote:
> Dear Team,
>
> Kindly guide us how to upgrade the backuppc from version 4.2.1 to 4.3.0
> please.
>
> Regards,
>
> Sriram.p
> ___
> BackupPC-users
ther passed in the above code nor are they inherited (as
per my previous post).
Note that even if $vars and %Conf were passed as the 3rd argument to
$bpc->cmdSystemOrEval, the arguments would be ignored when passed on
to cmdSystemOrEvalLong as per my earlier post...
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
is later
eval'd?
Note, the same problem occurs for any of the variables defined in BackupPC_dump.
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
list-form of exec(), ie: no shell even for 1 arg
#
exec { $cmd->[0] } @$cmd;
print(STDERR "Exec failed for @$cmd\n");
POSIX::_exit(1);
}
}
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge
BackupPC uses sendmail to send emails. See the documentation
<https://backuppc.github.io/backuppc/BackupPC.html#Step-8:-Checking-email-delivery>
for how to test sending of emails.
Craig
On Wed, May 8, 2019 at 5:37 AM Gopal Dhapa wrote:
> Hello Team,
> Please share link or docume
to /home/raman/x and it worked just fine. I forgot to mention I
> > also have another BackupPC server, backing up the same client with the
> > same configuration, and it backs up all of these files from this
> > client without any issue, so the issue is definitely on the server
>
Hi,
I am using BackupPC 3 on Debian 9.
I use this configuration (only relevant parts)
$Conf{WakeupSchedule} =
[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24];
$Conf{BackupPCNightlyPeriod} = 1;
$Conf{MaxBackups} = 2;
$Conf{FullPeriod} = '6.97';
$Conf{IncrPeriod} = &#x
ugh... my backups have
> been running nightly for years. However, in late 2017 I updated
> BackupPC on my Fedora box, and `--one-file-system` was added to the
> rsync args without me realizing. This caused all backups from that
> point forward to a few days ago to be missing all the new fi
ertain directories (and their contents) on one of my hosts are not
> getting backed up at all, even with a “Full” backup.
>
> I use rsync as my Xfer method, with BackupPC 4.3.0 on Fedora (rpms
> BackupPC-4.3.0-1.fc29.x86_64, BackupPC-XS-0.58-1.fc29.x86_64).
>
> Looking at the backup
Craig Barratt via BackupPC-users wrote at about 11:21:29 -0700 on Sunday, May
5, 2019:
> >
> > - Is this just a concatenation of different command-line options sent to
> > rsync?
>
>
> Yes - rsync passes along short versions of the command-line arguments the
&
syncClientPath.
> We also have a DumPreShareCmd that makes the actual snapshot and then a
> DumpPostShareCmd that removes the snapshot. Our scripts are pretty crappy
> Perl (I can say that because I wrote them) but they work. As far as BackupPC
> is concerned, the share name
iLsf --iconv=UTF-8
>
> - What is the meaning of the (option?) string: -slHogDtpAXrcxe.iLsf
> - Is this just a concatenation of different command-line options sent
> to rsync?
> - If so, what is the meaning of the period?
> - Also, are these options fixed or do they vary with the setting of
>
Yes, that's the best workaround. Since BackupPC 4.x uses rsync_bpc on the
host (which is native rsync, modified to access the BackupPC storage),
unfortunately this is internal to how rsync specifies and executes the
remote command.
The problem, as you observed, is that rsync adds the host
a redirection that I
could for example set in DumpPreShareCmd to redirect the rsync source.
Jeff
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http
$conf{SshPath} = '';
The resulting command is of form:
usr/bin/sudo -h /usr/bin/rsync --server --sender
-slHogDtpAXrcxe.iLsf --iconv=UTF-8
Since 'host' is the localhost (by choice), adding the '-h ' switch to
sudo doesn't do anything different...
Still a bit klugey but at least it's simple...
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
sr/bin/rsync --server --sender
-slHogDtpAXrcxe.iLsf --iconv=UTF-8
I could presumably write a short shell script like:
#!/bin/bash
shift
exec $*
Then set SshPath to the above script (with RsyncSshArgs = '').
But even if that would work, it seems klugey.
-line options sent
to rsync?
- If so, what is the meaning of the period?
- Also, are these options fixed or do they vary with the setting of
rsync args in config.pl?
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https
access to
RsyncClientCmd but instead can only specify:
RsyncClinetPath
RsyncSshArgs
SshPath
i.e., I don't see how to eliminate the use of ssh...
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.
Jeff,
BackupPC forces the host names to lower case when it reads the host file,
so everywhere they are lower case. It's been that way from the
very beginning.
I think the reason I did it that way is that host names are generally
treated as case insensitive. But I agree it would have
Any reason why capital letters don't work?
Specifically, I found that renaming the 'pc' directory name to a name
with capital letters (along with the corresponding change in the hosts
file), causes backuppc to fail to recognize the machine backups.
In terms of linux and windows,
otal 1
drwxr-xr-x 16 root root 1024 Dec 12 2010 c/
This occurs whether I run as root or other user...
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/bac
to manually convert an incremental/unfilled to a
> full/filled backup under v4?
>
>
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinf
I have 2 separate v3 backup trees, that have been run on 2 separate v3
BackupPC servers, say A and B.
I would like to migrate both of them to a new combined v4 backup tree,
say C.
I believe the following will work based on looking at the code for
BackupPC_migrateV3toV4.
1. Migrate A to v4 using
t; > but otherwise I am still here.
> >
> > Any suggestions better than my renaming of the backup tree itself?
> >
> > Jeff
> >
> >
> > ___
> > BackupPC-users mailing list
>
I just converted some old v3 backups to v4.
Is there any way to manually convert an incremental/unfilled to a
full/filled backup under v4?
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists
,
> would it be reasonable for a future version of BackupPC to pre-duplicate the
> last backup during one of the maintenance operations? Then it would be
> possible to simply update that when the time comes.
>
> Or am I misunderstanding this?
>
> On 04/21 05:15 , Crai
eltas. Another minor advantage
of only having filled backups is deleting any one of them is easier, as you
note. Currently BackupPC needs to merge deltas into the immediate prior
backup (if unfilled) when you deleted a backup.
Craig
On Thu, Apr 11, 2019 at 9:50 AM wrote:
> Presumably in a
Thanks Craig.
Craig Barratt wrote at about 16:54:09 -0700 on Sunday, April 14, 2019:
> Jeff,
>
> I've pushed fixes to backuppc-xs, rsync-bpc 3.0.9 and rsync-bpc 3.1.2 for
> making mtime signed and correctly writing and reading negative mtimes.
> That should fix things
Jeff,
I've pushed fixes to backuppc-xs, rsync-bpc 3.0.9 and rsync-bpc 3.1.2 for
making mtime signed and correctly writing and reading negative mtimes.
That should fix things for v4. However, I haven't released new versions
yet, since I haven't decided whether (or how) to deal wi
I use noatime,nodiratime on my BackupPC store (ext4). Since in the
steady-state most BackupPC operations on the pool should be reads, it
should definitely make a difference. However, I don't have benchmark data
to show how much.
Craig
On Thu, Apr 11, 2019 at 3:28 PM wrote:
> Mad
407-925-7030
www.riptidesoftware.com
*From:* dan aneas
*Sent:* Saturday, April 13, 2019 1:17 PM
*To:* BackupPC-users@lists.sourceforge.net
*Subject:* [BackupPC-users] Cant Rsync between Freenass and Win10
Dear all,
I have been trying many things (during 2 weeks now) to make it works
with
materially faster by eliminating at
least the first atime write?
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
ental tree to see if there are changes -- all presumably much
slower than just writing the attrib file to each directory.
Said another way, in v4, why not just make all backups filled while
still mixing incrementals between filled to overall speed up average
backup time.
__
had
> a negative mtime file (especially given that both macs and windows
> have an epoch before 1/1/1970)
>
> Jeff
>
> Craig Barratt wrote at about 23:30:34 -0700 on Tuesday, April 9, 2019:
> > Jeff,
> >
> > Thanks for the detective work and proposed
2019 at 7:38 PM wrote:
>
> > So, the problem seems to be that backuppc treats mtime as an unsigned
> > integer -- meaning that any file created before Jan 1, 1970 is not
> > representable.
> >
> > v3 represents treats the number as an unsigned integer a
So, the problem seems to be that backuppc treats mtime as an unsigned
> integer -- meaning that any file created before Jan 1, 1970 is not
> representable.
>
> v3 represents treats the number as an unsigned integer and basically
> shows it's 2's complement (in 32 bits) - i.e
So, the problem seems to be that backuppc treats mtime as an unsigned
integer -- meaning that any file created before Jan 1, 1970 is not
representable.
v3 represents treats the number as an unsigned integer and basically
shows it's 2's complement (in 32 bits) - i.e. it's packed as
701 - 800 of 1302 matches
Mail list logo
