[BackupPC-users] considerations on i-nodes

[fi]

Dear List, 

running BackupPC v4 I sometimes ran out of i-nodes. 

I have about twelve servers to backup with a total amount of about 2
TB and aboz 20 million files. I keep about 50 backups.  

On an ext4 file system it is likely to run out of i-nodes rather than
to run out of disk space (this holds if the file system was created
using the default parameters). In my situation I have only used half
the space but almost all i-nodes available. 

Because I prefer ext4 for it's robustness and reliability I have to
consider i-nodes. 

We have the pool (or cpool) storing the actual files. And we have the
pc directory storing the structure. The most files in pc are small or
even empty, but they are many (in my case ten times more than the
actual files in pool). They waste an enourmous amount of disk
space. 

So I created a separate (logical) partition of only 200 GB in size and
formatted with 1024 bytes per inode and per block (mkfs.ext4 -b 1024
-i 1024 ...). I later use it for pc.

Then I simply copied the pc entries (note: only the entries, not the
complete directory) to the new partition using cp -a. This took about
50 hours but worked correctly (this also shows, that BackupPC v4 can be
replicated). Afterwards I removed the entries from the original pc
directory and mounted the new partition there. 

I started BackupPC once again and it works like a charm. 

In this constellation remarkable space for the future backup space was
released. If I ever would run out of space or i-nodes again I will
simply increase either of the partitions.

As a suggestion I would recommend an information about i-nodes
consumption in the server status page. 


Finally I am looking for a formula that could be used to estimate the
required disk space and i-nodes depending on the number  and size of
files and the number of backups kept. 


Best regards


Torsten



-- 

Torsten Finke
f...@igh.de
 
Ingenieurgemeinschaft IgH
Gesellschaft für Ingenieurleistungen mbH
Heinz-Bäcker-Str. 34
D-45356 Essen



--
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] Serious error: last backup ... directory doesn't exist!!! - reason found

[fi]

Dear Holger, 

> f...@igh.de wrote on 2018-03-08 16:59:37 +0100 [Re: [BackupPC-users] Serious 
> error: last backup ... directory doesn't exist!!! - reason found]:
> > [...]
> > Meanwhile I found the reason: the partition ran out of inodes. As you
> > wrote under "How much disk space do I need?" one has to have "plenty
> > of inodes". But what does that mean? 
> 
> as has been said, that depends directly on what you are backing up.

yes of course, but there are other signicant influences. I have
counted the number of inodes in the cpool and in the pc
directories. The latter was about 100 times higher. Obviously the
number of kept backups is a factor to consider. It seems, the number
n_i of inodes required is about 

   n_i = n_f (2 n_b + 1), 

where 
  n_b: number of backups kept 
  n_f: number of files to backup
  
could anyone confirm or disconfirm this? 



> > May I ask the following:
> > 
> > - in the "General Server Information" you give some statistical
> >   information about disk usage; would it be a good idea also to give
> >   information about inode consumption? 
> 
> You mean 'df -i'?

yes exactly! 

I have created a post backup notification e-mail which now contains
also the output of "df -i". 

BTW.: such a post backup notification I would recommend as
default. It is not a good idea to conclude a successful backup from a
missing message...


> > - is it possible and would it make sense to separate the "pc" and the
> >   "pool/cpool" directories into different partitions? I just did an
> >   rsync of a BackupPC-directory and found that the files on "pc" are
> >   mostly empty or small. The file sizes in "pool/cpool" are remarkable
> >   bigger - I assume these are the "real" files. So one could create
> >   one partition for "pool/cpool" having about e.g. 64kB per inode and
> >   another partition having a block size of 1 kB and also 1 kB per
> >   inode. Maybe this would reduce disk space consumption and also allow 
> >   rsyncing somewhat faster. 
> 
> My first thought is to avoid the issue altogether by using a file system
> that doesn't statically allocate inodes (e.g. XFS or reiserfs, the latter
> I wouldn't recommend for other reasons, though; I don't know about ext4,
> btrfs and ZFS, but my guess would be that ext4 has static allocation and
> the others dynamic). Why worry about a problem modern file systems simply
> don't have?

I have made several tests with different file systems (xfs, reiserfs,
jfs). After some time of operation I had different kinds of trouble with
all of them; especially xfs seems to be sensitive against power
blackout (I know UPS could help, but this increases the effort of battery
life cycle management; sometimes I found UPS caused more trouble than solved). 

I consider ext[3/4] the far most robust file system. So if I know how
to calculate the required number of inodes it will stay my favorite. 


Best regards


Torsten


-- 

Torsten Finke
f...@igh.de

Ingenieurgemeinschaft IgH
Gesellschaft für Ingenieurleistungen mbH
Heinz-Bäcker-Str. 34
D-45356 Essen



--
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] Serious error: last backup ... directory doesn't exist!!! - reason found

[fi]

Craig,

again I return to my issue "No space left on device". 

Meanwhile I found the reason: the partition ran out of inodes. As you
wrote under "How much disk space do I need?" one has to have "plenty
of inodes". But what does that mean? 

May I ask the following:

- in the "General Server Information" you give some statistical
  information about disk usage; would it be a good idea also to give
  information about inode consumption? 

- is it possible and would it make sense to separate the "pc" and the
  "pool/cpool" directories into different partitions? I just did an
  rsync of a BackupPC-directory and found that the files on "pc" are
  mostly empty or small. The file sizes in "pool/cpool" are remarkable
  bigger - I assume these are the "real" files. So one could create
  one partition for "pool/cpool" having about e.g. 64kB per inode and
  another partition having a block size of 1 kB and also 1 kB per
  inode. Maybe this would reduce disk space consumption and also allow 
  rsyncing somewhat faster. 


Best regards


Torsten



> Thanks for the additional info, but I can't explain the behavior your are
> seeing.  Sending to the user-list to see if others have suggestions.
> 
> BackupPC seems to be unable to create directories and files below
> /vol/bpc4/BackupPC.  The "No space left on device" errno seems inconsistent
> with the output of df.
> 
> Although it won't address any of your problems, I pushed a fix
> 
> for the error caused by the failure to open a directory.
> 
> Craig
> 
> On Sat, Feb 3, 2018 at 3:56 AM,  wrote:
> 
> > Dear Craig,
> >
> > On Fri, Feb 02, 2018 at 09:19:02AM -0800, Craig Barratt via BackupPC-users
> > wrote:
> > > Here are a few things to check:
> > >
> > >- can you manually create files and directories below
> > /vol/bpc4/BackupPC
> > >as the backuppc user (eg, "su backuppc; cd /vol/bpc4/BackupPC; mkdir
> > foo;
> > >rmdir foo; touch foobar; rm foobar")
> >
> > yes, works as expected.
> >
> > >- is the file system mounted readonly?
> >
> > no, mount says:
> > ... /vol/bpc4 type ext4 (rw,noatime,data=ordered)
> >
> > >- has the backuppc user lost permissions?
> >
> > in what sense? All BackupPC processes run as user backuppc; all files
> > and directories /vol/bpc4/BackupPC and below are owned by
> > backuppc:backuppc.
> >
> >
> > df says
> > Filesystem Size  Used Avail Use% Mounted on
> > /dev/mapper/data-bpc4  1.6T  955G  535G  65% /vol/bpc4
> >
> > The file system lives on a mirror raid, which seems to be ok:
> >
> > md127 : active raid1 sdb1[1] sdc1[0]
> >   2930266432 blocks [2/2] [UU]
> >
> > There are no SMART errors logged on the disks (even after SMART test).
> >
> > I have copied several GB to the file system and removed them again -
> > no errors.
> >
> > I have launched a forced fsck. It succeeded without any errors:
> > Durchgang 1: Inodes, Blöcke und Größen werden geprüft
> > Durchgang 2: Verzeichnisstruktur wird geprüft
> > Durchgang 3: Verzeichnisverknüpfungen werden geprüft
> > Durchgang 4: Referenzzähler werden überprüft
> > Durchgang 5: Zusammengefasste Gruppeninformation wird geprüft
> > /dev/data/bpc4: 104312919/104505344 Dateien (0.0% nicht
> > zusammenhängend), 256909
> > 738/417993728 Blöcke
> >
> >
> > I went through the logs. There are more error messages from a backup
> > which was presented as "running" in the summary. Rather strange sound
> > the messages "IO error encountered" and "No space left on device "
> > (please see below). I cannot figure out the origin of these messages.
> >
> > ...
> > G bpc_fileReadAll: can't open
> > /vol/bpc4/BackupPC/cpool/20/9a/219b13a5a32e6cd66ab3cf139bd8d35c (from
> > alternatives/pg_config)
> > file has vanished: "alternatives/pg_config"
> > ...
> >
> > ...
> > IO error encountered -- skipping file deletion
> > G bpc_attrib_dirRead: can't open
> > /vol/bpc4/BackupPC/cpool/26/24/27243e59e0d4404f14ddc7ebb0202ce6
> > G bpc_attribCache_loadPath:
> > bpc_attrib_dirRead(/vol/bpc4/BackupPC/pc/zuse/169, fetc/fapache2/attrib)
> > returned -1
> > ...
> >
> > ...
> > R bpc_attrib_dirRead: can't open
> > /vol/bpc4/BackupPC/cpool/1e/aa/1eab8cca5e477b6fe2530e955cca3978
> > R bpc_attribCache_loadPath:
> > bpc_attrib_dirRead(/vol/bpc4/BackupPC/pc/zuse/169,
> > fetc/fcups/fssl/attrib) returned -1
> > [ skipped 6 lines ]
> > ...
> >
> >
> > ...
> > R
> > R
> > bpc_sysCall_checkFileMatch(.cpan/build/DateTime-Locale-1.
> > 05-GcMGii/pm_to_blib):
> > file doesn't exist
> > ...
> >
> > ...
> > R bpc_poolWrite_write: can't open/create
> > /vol/bpc4/BackupPC/cpool/18801.736.0 for writingIOdone: pool
> > .cpan/build/DateTime-Locale-1.05-GcMGii/blib/lib/DateTime/
> > Locale/.en_NR.pod.00
> > ...
> >
> > ...
> > R
> > bpc_poolWrite_unmarkPendingDelete(/vol/bpc4/BackupPC/cpool/50/02/
> > 50032f7b52be451f6a6c396067253906)
> > failed; errno = 2
> > R Couldn't unmark candidate matching file
> > 

Re: [BackupPC-users] Serious error: last backup ... directory doesn't exist!!!

[fi]

Dear Craig, 

> Thanks for the additional info, but I can't explain the behavior your are
> seeing.  Sending to the user-list to see if others have suggestions.
> 
> BackupPC seems to be unable to create directories and files below
> /vol/bpc4/BackupPC.  The "No space left on device" errno seems inconsistent
> with the output of df.

Indeed it sounds crazy. 

I would try to do some kind of roll back to a date before this
trouble. Would it be safe to remove:
- all numbered directories which have been created after the
  first errors,
- the per-host directories "refCnt"
- files: XferLOG.NNN.z, backups, backups.old, LOG., LOCK?

After that I would try to restart BackupPC hoping it would set up on
the state before the error. Could that work? 



> Although it won't address any of your problems, I pushed a fix
> 
> for the error caused by the failure to open a directory.


I am going to set up another Backup server. I will do that with the
newest version available. 



Best regards


Torsten




> On Sat, Feb 3, 2018 at 3:56 AM,  wrote:
> 
> > Dear Craig,
> >
> > On Fri, Feb 02, 2018 at 09:19:02AM -0800, Craig Barratt via BackupPC-users
> > wrote:
> > > Here are a few things to check:
> > >
> > >- can you manually create files and directories below
> > /vol/bpc4/BackupPC
> > >as the backuppc user (eg, "su backuppc; cd /vol/bpc4/BackupPC; mkdir
> > foo;
> > >rmdir foo; touch foobar; rm foobar")
> >
> > yes, works as expected.
> >
> > >- is the file system mounted readonly?
> >
> > no, mount says:
> > ... /vol/bpc4 type ext4 (rw,noatime,data=ordered)
> >
> > >- has the backuppc user lost permissions?
> >
> > in what sense? All BackupPC processes run as user backuppc; all files
> > and directories /vol/bpc4/BackupPC and below are owned by
> > backuppc:backuppc.
> >
> >
> > df says
> > Filesystem Size  Used Avail Use% Mounted on
> > /dev/mapper/data-bpc4  1.6T  955G  535G  65% /vol/bpc4
> >
> > The file system lives on a mirror raid, which seems to be ok:
> >
> > md127 : active raid1 sdb1[1] sdc1[0]
> >   2930266432 blocks [2/2] [UU]
> >
> > There are no SMART errors logged on the disks (even after SMART test).
> >
> > I have copied several GB to the file system and removed them again -
> > no errors.
> >
> > I have launched a forced fsck. It succeeded without any errors:
> > Durchgang 1: Inodes, Blöcke und Größen werden geprüft
> > Durchgang 2: Verzeichnisstruktur wird geprüft
> > Durchgang 3: Verzeichnisverknüpfungen werden geprüft
> > Durchgang 4: Referenzzähler werden überprüft
> > Durchgang 5: Zusammengefasste Gruppeninformation wird geprüft
> > /dev/data/bpc4: 104312919/104505344 Dateien (0.0% nicht
> > zusammenhängend), 256909
> > 738/417993728 Blöcke
> >
> >
> > I went through the logs. There are more error messages from a backup
> > which was presented as "running" in the summary. Rather strange sound
> > the messages "IO error encountered" and "No space left on device "
> > (please see below). I cannot figure out the origin of these messages.
> >
> > ...
> > G bpc_fileReadAll: can't open
> > /vol/bpc4/BackupPC/cpool/20/9a/219b13a5a32e6cd66ab3cf139bd8d35c (from
> > alternatives/pg_config)
> > file has vanished: "alternatives/pg_config"
> > ...
> >
> > ...
> > IO error encountered -- skipping file deletion
> > G bpc_attrib_dirRead: can't open
> > /vol/bpc4/BackupPC/cpool/26/24/27243e59e0d4404f14ddc7ebb0202ce6
> > G bpc_attribCache_loadPath:
> > bpc_attrib_dirRead(/vol/bpc4/BackupPC/pc/zuse/169, fetc/fapache2/attrib)
> > returned -1
> > ...
> >
> > ...
> > R bpc_attrib_dirRead: can't open
> > /vol/bpc4/BackupPC/cpool/1e/aa/1eab8cca5e477b6fe2530e955cca3978
> > R bpc_attribCache_loadPath:
> > bpc_attrib_dirRead(/vol/bpc4/BackupPC/pc/zuse/169,
> > fetc/fcups/fssl/attrib) returned -1
> > [ skipped 6 lines ]
> > ...
> >
> >
> > ...
> > R
> > R
> > bpc_sysCall_checkFileMatch(.cpan/build/DateTime-Locale-1.
> > 05-GcMGii/pm_to_blib):
> > file doesn't exist
> > ...
> >
> > ...
> > R bpc_poolWrite_write: can't open/create
> > /vol/bpc4/BackupPC/cpool/18801.736.0 for writingIOdone: pool
> > .cpan/build/DateTime-Locale-1.05-GcMGii/blib/lib/DateTime/
> > Locale/.en_NR.pod.00
> > ...
> >
> > ...
> > R
> > bpc_poolWrite_unmarkPendingDelete(/vol/bpc4/BackupPC/cpool/50/02/
> > 50032f7b52be451f6a6c396067253906)
> > failed; errno = 2
> > R Couldn't unmark candidate matching file
> > /vol/bpc4/BackupPC/cpool/50/02/50032f7b52be451f6a6c396067253906
> > (skipped; errno = 2)
> > ...
> >
> >
> > The following is very strange:
> > ...
> > rsync_bpc: recv_generator: mkdir
> > "/.cpan/build/Dist-CheckConflicts-0.11-RNgNPa/t/lib" failed: No space
> > left on device (28)
> > ...
> >
> > dumpe2fs says:
> >
> > ...
> > Inode count:  104505344
> > Block count:  417993728
> > Reserved block count: 20899686
> > Free blocks:  243883988
> > Free inodes:

[BackupPC-users] Serious error: last backup ... directory doesn't exist!!!

[fi]

Dear BackupPC Users, 
 

I am running BackupPC-4.1.3 for several months without problems
(really a great piece of software).

About a week ago a strange type of error occured and keeps staying,
which I cannot understand. The error messages are like this ("fs" is
the name of one of my systems to be backed up; I did some linebreaks
to increase readability):


2018-01-28 23:43:34 Can't create /vol/bpc4/BackupPC/pc/fs/149/refCnt
2018-01-29 02:09:34 Serious error: last backup
  /vol/bpc4/BackupPC/pc/fs/149 directory doesn't exist!!!  Need to
  remove back to last filled backup
2018-01-29 02:09:34 Deleting backup 147
2018-01-29 02:09:35 BackupPC_backupDelete: removing #147
2018-01-29 02:09:35 BackupPC_backupDelete: No prior backup for merge
2018-01-29 02:09:52 BackupPC_refCountUpdate: doing fsck on fs #149
  since /vol/bpc4/BackupPC/pc/fs/149/refCnt doesn't exist
2018-01-29 02:09:52 Can't use an undefined value as an ARRAY reference
  at /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380.
2018-01-29 02:09:52 BackupPC_backupDelete: got 1 errors
2018-01-29 02:09:52 Finished BackupPC_backupDelete, status = 256
  (running time: 18 sec)
2018-01-29 02:09:52 Deleting backup 148
2018-01-29 02:09:52 BackupPC_backupDelete: removing #148
2018-01-29 02:09:52 BackupPC_backupDelete: No prior backup for merge
2018-01-29 02:09:55 BackupPC_refCountUpdate: doing fsck on fs #149
  since /vol/bpc4/BackupPC/pc/fs/149/refCnt doesn't exist
2018-01-29 02:09:55 Can't use an undefined value as an ARRAY reference
  at /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380.
2018-01-29 02:09:55 BackupPC_backupDelete: got 1 errors
2018-01-29 02:09:55 Finished BackupPC_backupDelete, status = 256
  (running time: 3 sec)
2018-01-29 02:09:55 Deleting backup 149
2018-01-29 02:09:56 BackupPC_backupDelete: removing #149
2018-01-29 02:09:56 BackupPC_backupDelete: No prior backup for merge
2018-01-29 02:38:20 BackupPC_refCountUpdate: host fs got 0 errors
  (took 1704 secs)
2018-01-29 02:38:20 Finished BackupPC_backupDelete, status = 0
  (running time: 1705 sec)
2018-01-29 03:16:29 dump failed: unable to open/create
  /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
2018-01-29 03:55:15 dump failed: unable to open/create
  /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
2018-01-29 04:15:15 dump failed: unable to open/create
  /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
2018-01-29 23:43:54 dump failed: unable to open/create
  /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
2018-01-30 01:24:02 dump failed: unable to open/create
  /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
2018-01-30 02:36:01 dump failed: unable to open/create
  /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
2018-01-30 03:42:01 dump failed: unable to open/create
  /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
2018-01-30 04:12:01 dump failed: unable to open/create
  /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
2018-01-30 23:57:53 Copying backup #146 to #147

2018-01-31 01:05:38 Can't mkpath
  /vol/bpc4/BackupPC/pc/fs/147/./fsysbak/f.../fLocked/f00
2018-01-31 01:05:38 Can't copy
  ./fsysbak/f.../fLocked/f00/attrib_dc793dc4650baa1a8cc3b69d211573c1
  to 
/vol/bpc4/BackupPC/pc/fs/147/./fsysbak/f.../fLocked/f00/attrib_dc793dc4650baa1a8cc3b69d211573c1
...

The last pair of messages is then repeated for thousands of files. 


It seems, that there is an error concerning the sequence. 

I had checked for several default reasons:
- No files or directories have been manipulated manually
- BackupPC is almost the only task running on my backup server (there
  should be no side effects from other services; no user is normally
  working on that machine)
- the file system has about 1.6 TB at a usage of 65% (this rate was
  never exceeded)
- the system had no crash (uptime is 217 days, since setup of
  BackupPC). 
- /vol/bpc4 is a mount point of an ext4 file system (normally very reliable)
- Kernel 4.1.39, OpenSuSE 42.1 - not really outdated




Any advice to repair this error is highly appretiated. 


Best regards


Torsten Finke



-- 

Torsten Finke
f...@igh.de

Ingenieurgemeinschaft IgH
Gesellschaft für Ingenieurleistungen mbH
Heinz-Bäcker-Str. 34
D-45356 Essen



--
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] mistake during server migration - how to prevent trash cleanup from file removal?

[fi]

Dear Craig, 
 
On Sun, Aug 13, 2017 at 07:30:00PM -0700, Craig Barratt via BackupPC-users 
wrote:
> I would like to understand the steps you took.
> 
> First, by "server A" and "server B" you mean clients that BackupPC backs up?

yes - from my point of view they are file servers, but you are right:
they are BackupPC clients. 

Also one information ahead: The system I talked about was a
BackupPC-3.3.1. 

> When you said "on my BackupPC I deleted "A:data"" did you mean you simply
> removed that share from the config.pl for server A, or did you actually
> delete files below the BackupPC store (eg,
> /data/BackupPC/pc/serverA/NNN/fdata)?

I deleted the share from the config.pl. My intention was to migrate
the share from one "client" to another keeping it's backup history. I
have not removed any files expilicitely.

> If it was just a config change, then all the old backups of the data share
> on server A should still be present (until they otherwise expire based on
> the config settings).

During nightly cleanup BackupPC started removal of the "deleted" share
of client A. Unfortunately I noticed this after about 20 hours of
removal (I have an amount of about 4 million files at about 30
snapshots, lasting about 5 years back). 

I understand that if a share is deleted (from config.pl),
BackupPC assumes that the share is not needed any more and thus
starts removal. Actually it started to remove hard links from the snap
shots. Many of them are empty now and I am afraid that the pooled
files also have been deleted, because their hard link counter has
decremented to 1. Anyway I am afraid that I would not be able to
reestablish the removed links. 

So my question is, how can I tell BackupPC to "move" a share
(including it's history) from one client to another?


Meanwhile I noticed your release of Version 4 and I did a complete new
setup. My hope would be that in case of damage there would be at least
a chance to recover files from my old V3-Backup. I kept it and mounted
the volume read only, because BackupPCv3 insists in doing cleanup as
soon as I start it on I writeble volume. So my other question was, how
to disable cleanup. 

The last question in this story then is how to merge another backup
into the "clean-upped" one. I found that this question was discussed
several times but it seems to be complicated. 

After all I want to state, that I am very excited about your
project. I have used it for many years now and it has helped in many
cases of file damage or loss. Also your project is a prime example of
very good software design.


Thanks for any advice and best regards


Torsten


> On Sun, Aug 6, 2017 at 8:01 AM,  wrote:
> 
> > Dear BackupPC Users,
> >
> > recently I made a mistake:
> >
> > I moved a share "data" from an old server A to a new server B. Then on
> > my BackupPC I deleted "A:data", created the new host B and added a
> > share "data" to the new one, having "B:data". Naively I assumed that
> > this would keep also the history from "A:data" ...
> >
> > Because some other shares on A have still to be backed up, I started
> > BackupPC. This resulted in file removal inside the history snapshots
> > of "A:data" via trash cleaning. As soon as I have detected this, I
> > stopped BackupPC. Because the amount of files is rather huge, the
> > removal was not completed.
> >
> > Now my questions:
> > - how can I temporarily prevent BackupPC from deleting files?
> > - how can I find out, which files have been deleted?
> > - what would have been the correct way of migrating a share from one
> >   host to another?
> > - I have another BackupPC-service running which holds several of the
> >   presumably removed files; how could I merge them to reconstruct my
> >   backup?
> >
> > Thanks for any advice and best regards
> >
> >
> > T. Finke
> >
> >
> >
> > 
> > --
> > 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/
> >

> --
> 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/


-- 

Dr.-Ing. Torsten Finke
f...@igh.de

Ingenieurgemeinschaft IgH
Gesellschaft für 

[BackupPC-users] mistake during server migration - how to prevent trash cleanup from file removal?

[fi]

Dear BackupPC Users, 

recently I made a mistake: 

I moved a share "data" from an old server A to a new server B. Then on
my BackupPC I deleted "A:data", created the new host B and added a
share "data" to the new one, having "B:data". Naively I assumed that
this would keep also the history from "A:data" ... 

Because some other shares on A have still to be backed up, I started
BackupPC. This resulted in file removal inside the history snapshots
of "A:data" via trash cleaning. As soon as I have detected this, I
stopped BackupPC. Because the amount of files is rather huge, the
removal was not completed. 

Now my questions:
- how can I temporarily prevent BackupPC from deleting files? 
- how can I find out, which files have been deleted? 
- what would have been the correct way of migrating a share from one
  host to another? 
- I have another BackupPC-service running which holds several of the
  presumably removed files; how could I merge them to reconstruct my
  backup? 

Thanks for any advice and best regards


T. Finke



--
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/