Re: [BackupPC-users] Question about v4

[Bzzzz]

On Mon, 7 Aug 2017 10:17:41 -0700
Craig Barratt via BackupPC-users 
wrote:

> Sorry that it isn't very clearly stated

Nooo, there's no more sorry in stock… may be a little forgive,
for the lowest rate of $.91 (sub-primed credit allowed) ;-p)

> and it doesn't depend on the real client's inode (and
> inode numbers) on the file system being backed up.

Ahhh, NOW this is crystal clear; however, it wasn't in the
aforementioned doc's page.

I may sound dumb/punctilious, but on my reading I really understood what
I asked about (may be it is because I'm always strive to see things like
a user will.)

>  Therefore it's
> portable across different underlying file systems on the server.

Yeah, now let's port it to the Apple ][ CP/M card, then build a
cluster of 120KB 5"1/4 diskettes and conquer the (known) world
by backuping it ! :))
(yeah, I'm not that young anymore, may be that's what explains the
dumb/punctilious way of live.)

Thanks for your answer, Craig; it is now clear that BPCv4 "inodes
storing" is way different than the OS one.

Jean-Yves

--
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] Question about v4

[Craig Barratt via BackupPC-users]

Sorry that it isn't very clearly stated - yes, v4 does store inode-like
information in the backup tree (and can therefore accurately represent
hardlinks etc), but it uses regular files to do it - it doesn't use real
hardlinks, and it doesn't depend on the real client's inode (and inode
numbers) on the file system being backed up.  Therefore it's portable
across different underlying file systems on the server.

Craig

On Mon, Aug 7, 2017 at 9:00 AM, B  wrote:

> On Mon, 7 Aug 2017 08:50:30 -0600
> Ray Frush  wrote:
>
> > Jean-Yves-
>
> Ray
>
> > I believe you may have been looking at v3 documentation.   BackupPC V4
> >  does _not_ make extensive use of hard links.
> >
> > See: https://backuppc.github.io/backuppc/BackupPC.html#BackupPC-4.0
>
> Na, I'm on: http://backuppc.sourceforge.net/BackupPC-4.1.1.html
>
> searching "inodes" leads to this paragraph:
>
> "Inodes for hardlinked files are stored in each backup tree. This makes
> backing up hardlinks accurate, compared to V3, and provides for
> consistent inode numbering across backups."
>
> As there's a comparison w/ v3, it is of course targeting v4.
> This is why I ask, 'cos it collides with what you said.
>
> Sooo, I don't know what to think 'cos moving a regular hardlink isn't a
> problem as the FS is taking care of inode(s) swapping, but IF v4 is doing
> it's own not-hardlinking-but-much-like-it, moving a file whose inode's
> reference  is contained in another one would break this system (?)
>
> JY
>
> > --
> > Ray Frush
> > Colorado State University.
> >
> >
> > On Sun, Aug 6, 2017 at 6:10 PM, B  wrote:
> >
> > > Hi backuppcers,
> > >
> > > I'm gonna switch from v3 to v4 and have a question about it:
> > >
> > > * doc says hardlinked files inodes are stored in each backup tree,
> > >   I guess that BPC partition being formatted in XFS, any optimization
> > >   (that might move any file) of this partition is out of the
> > > question ?
> > >
> > > Jean-Yves
> > >
> > > 
> > > --
> > > 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/
>
--
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] Question about v4

[Bzzzz]

On Mon, 7 Aug 2017 08:50:30 -0600
Ray Frush  wrote:

> Jean-Yves-

Ray

> I believe you may have been looking at v3 documentation.   BackupPC V4
>  does _not_ make extensive use of hard links.
> 
> See: https://backuppc.github.io/backuppc/BackupPC.html#BackupPC-4.0

Na, I'm on: http://backuppc.sourceforge.net/BackupPC-4.1.1.html

searching "inodes" leads to this paragraph:

"Inodes for hardlinked files are stored in each backup tree. This makes
backing up hardlinks accurate, compared to V3, and provides for
consistent inode numbering across backups."

As there's a comparison w/ v3, it is of course targeting v4.
This is why I ask, 'cos it collides with what you said.

Sooo, I don't know what to think 'cos moving a regular hardlink isn't a
problem as the FS is taking care of inode(s) swapping, but IF v4 is doing
it's own not-hardlinking-but-much-like-it, moving a file whose inode's
reference  is contained in another one would break this system (?)

JY

> --
> Ray Frush
> Colorado State University.
> 
> 
> On Sun, Aug 6, 2017 at 6:10 PM, B  wrote:
> 
> > Hi backuppcers,
> >
> > I'm gonna switch from v3 to v4 and have a question about it:
> >
> > * doc says hardlinked files inodes are stored in each backup tree,
> >   I guess that BPC partition being formatted in XFS, any optimization
> >   (that might move any file) of this partition is out of the
> > question ?
> >
> > Jean-Yves
> >
> > 
> > --
> > 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/

Re: [BackupPC-users] Question about v4

[Ray Frush]

Jean-Yves-

I believe you may have been looking at v3 documentation.   BackupPC V4
 does _not_ make extensive use of hard links.

See: https://backuppc.github.io/backuppc/BackupPC.html#BackupPC-4.0

--
Ray Frush
Colorado State University.


On Sun, Aug 6, 2017 at 6:10 PM, B  wrote:

> Hi backuppcers,
>
> I'm gonna switch from v3 to v4 and have a question about it:
>
> * doc says hardlinked files inodes are stored in each backup tree,
>   I guess that BPC partition being formatted in XFS, any optimization
>   (that might move any file) of this partition is out of the question ?
>
> Jean-Yves
>
> 
> --
> 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/
>



-- 
Time flies like an arrow, but fruit flies like a banana.
--
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/