> 
> I have developed a catalogue snapshot facility in python to snapshot
one
> job's catalogue and dump it to disk. The snapshot provides a bacula
> database schema file, a database dump of the job's data, and a file
> listing of files showing info such as the tape number, path, file, md5
> and lstat.
> 
> We intend to include the catalogue in compressed format on CDs
> accompanying tape sets to assist our clients retrieve data in future
if
> required.
> 
> At present the system works only for Postgresql, and for our setup
which
> has the director, storage and file daemons on the same Linux server.
> 
> How it works:
> 
>     * A temporary schema is made in postgres, named job_%d % (jobid)
>     * Relevant data is selected from the public schema to the
temporary
>       schema
>     * The file listing is ouput
>     * The public schema is dumped
>     * The temporary schema is dumped
>     * The temporary schema is removed
> 
> I'm considering making an sqlite database from the temporary schema to
> obviate the need for the public schema file and file listing.
> 
> This is fairly simple stuff, but if this functionality is useful to
you,
> do let me know and I can share the programme with you.
> 

How much smaller is the catalogue subset vs the full catalogue?

James

------------------------------------------------------------------------------
Virtualization is moving to the mainstream and overtaking non-virtualized
environment for deploying applications. Does it make network security 
easier or more difficult to achieve? Read this whitepaper to separate the 
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users