[BackupPC-users] Question about transient inodes
I'm adding systems in earnest to my new BackupPC 4.1.2 installation, and
I've encountered an interesting problem.
My current pool uses a decent number of inodes:
cpool:7864978
pc:11504955
For a total of 19,369,933 objects.
However, my NFS filesystem, which had 50M pre-allocated inodes, and a max
of 80M inodes briefly ran out of inodes! I increased the max, and it
finally settled at 88M inodes allocated, but currently reports ~20M used.
A number of double checks confirms the current useage. I was never able
to show that the file system actually had 80M+ inodes, making me think they
were quickly allocated and then released before I could catch the state.
Since BackupPC is the only process pointed at this file system, the
conclusion is that BackupPC is, as some point in the process, requesting
far more inodes for a short time, than it is using.
It looks like, based on the numbers, that BackupPC is attempting to
temporarily allocate a guess at the number of inodes needed to store
the $Conf{FullKeepCnt} which in my case was [4, 0, 4, 0, 0, 2] or 10.
Can a developer comment on under what conditions BackupPC might be
temporarily allocating a lot of extra inodes, and then quickly releasing
them?
Thanks.
--
Time flies like an arrow, but fruit flies like a banana.
Ray Frush
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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/
Re: [BackupPC-users] Backing up Windows 7 Pro, not enough permissions
Hi Michael Huntley, Michael Stowe, and everybody, I overlooked your reply and only now saw it in the archives - also, I don't have your private mail address visible there, to reach out for a "thanks" privately: > Stowe has been around forever. I suggest you read his entire blog - > very entertaining. > > Here's his BackupPC stuff: > > http://www.michaelstowe.com/backuppc/ Thanks a lot for the pointer; testing soon! Cheers, Alexander On 2017-05-17 09:07 AM, Alexander Kobel wrote: > Hi Michael, > > On 2017-05-15 06:32 PM, Holger Parplies wrote: >> Hi, >> >> Michael Stowe wrote on 2017-05-15 09:58:08 -0500 [Re: [BackupPC-users] >> Backing up Windows 7 Pro, not enough permissions]: >> [...] >>> At any rate, these reasons are why I personally switched to a >>> combination of rsync and vshadow (to handle open files) and put together >>> a package to install the proper files on the client side. [...] > > would you mind to share that package, in whatever state it is? I use a > similar setup (Cygwin + rsync over SSH), but getting it to run is less > than intuitive. > > I yet have to find a simple and fool-proof way of installing (don't talk > about keeping up-to-date even) that combination. It takes me less and > less time every time I do it (every few months), but it's still a pain. > IIRC, last time I had to refresh my mind on > - how to enable a cyg_server (appx. a.k.a. root) account with the proper > access rights > - how to open port 22 on the firewall, and (if need be) respond to pings, > - how to make the SSH server accept the BackupPC server pubkey (because > cyg_server has no home by default). > And that's even without vshadow. > > Certainly not an approach that I can load off to the average Joe user, > say, "download and install ..., and I do the BackupPC server setup > remotely". > > > Cheers, > Alexander -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ 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/
Re: [BackupPC-users] Replication
Hello, Currently I use a proprietary solution for backing up my vmware VMs: arc serve UDP. Creating a backup job is split into several sub-tasks. Example for a simple backup: - Choice of source; - Type of backup to make (complete, incremental ...); - Destination; Then I can add other tasks: - Choice of source; - Type of backup to make (complete, incremental ...); - Local destination; - Replication on another datastore; - ... Each subtask can have an action time range. - | - Choice of source; From 10pm to 5am | - Type of backup to make (complete, incremental ...); | - Local destination; - - From 8 am to 3 pm | - Replication on another datastore; - Then it's up to the engine to launch tasks at the right time. The replication on another medium (local or datacenter) with the certainty of the consistency of this one seems to me necessary. In case of crash of the main site the recovery plan of activity to rely on the copy in datacenter for with the most recent data and not as is the case with a differentiation of a day because the latest backup Is not consitante. Philippe. Le 22/05/2017 à 15:04, Johan Ehnberg a écrit : > Hi, > > Indeed that is currently not implemented in BackupPC, since this would > require all backups to stop. That in turn is not may not feasible in a > large environment or where backup schedules are tight. But as an > optional feature, it is interesting. > > Basically any previous backup will be coherent, so snapshoting at any > time is fine when you are aware of this limit. > > Of course you can always check for running processes in a while loop and > wait until there are no backups running. > > This is the kind of details I might be interested in documenting. > > Best regards, > Johan -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ 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/
