On Wed, Mar 02, 2011 at 10:57:18PM -0800, Craig Barratt wrote:
] Tino wrote:
> > The downside of this is that I cannot easily peek into a backup on
> > command line any more. :-( It's been very helpful to quickly figure out
> > which files have bee backed up (e.g. to determine unneccessarily backed
> > up stuff). Now I'll lose that capability and have to resort to web page
> > clicking...
>
> That's true. Maybe I could add an "ls" facility?
That would be great especially if it can list across multiple backups
to allow me to search for a file.
> > or us that FUSE FS part of the release?
>
> Not currently planned, but it's a good idea. The new set up will
> make FUSE more faithful (in particular, getting nlinks right).
Will the fuse filesystem be runnable on Solaris, or *bsd or is it a
linux only solution?
> > > Inodes attributes (for client hardlinks) are stored in an additional
> > > tree of directories below each backup directory. The attribute hash key
> > > is the inode number. 128 directories are used to store up to 128 attrib
> > > files. The lower 14 bits of the inode number are used to determine the
> > > directory (bits 13 to 7) and the file name within that directory
> > > (bits 0-6). These two 7 bit values are encoded in hex (XX and YY):
> > >
> > > $TOPDIR/pc/HOST/NNN/inode/XX/attribYY.
> > >
> > > where NNN is the backup number.
> >
> > Oh, or do you mean: The inode number is made up by BackupPC? Then please
> > don't call it inode number, but rather hardlink-ID or so.
>
> Right. It's made by BackupPC on the server side. But it would be
> the inode number exposed by FUSE, so I'd like to call it that.
I got the impression that the pc tree will no longer have any
indication of the the (mangled) names of the original files.
We run is an automatic build server and rely on backups to recover
prior builds of software as a last fallback to recover from a bad
software build/install. Without actual files located under the pc tree
is there a way to search (cf. gnu locate or find) for a file matching
a particular regular expressions (e.g. python-orif.*.rpm) so I can go
to that backup and restore the file?
A directory history does some of that if the directory name remains
constant, but in some cases even the directory name changes from
release to release. Plus on a busy directory the history takes a long
time to load.
--
-- rouilj
John Rouillard System Administrator
Renesys Corporation 603-244-9084 (cell) 603-643-9300 x 111
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
BackupPC-devel mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
