Kern Sibbald schrieb:
> It is quite possible that Bacula will re-create all the pools the next time
> the Director is restarted.
Indeed. And the pool id's now are different too. Is there any way that I can
prevent bacula to re-create the deleted pools? I'm sure at some point someone
(maybe me) will add a volume to the MyCatalog Archiv pool instead of the
ArchiveCatalog's pool.
*use
The defined Catalog resources are:
1: MyCatalog
2: ArchiveCatalog
Select Catalog resource (1-2): 1
Using Catalog "MyCatalog"
Using Catalog name=MyCatalog DB=bacula
*list pool
+--------+--------------+---------+---------+----------+-------------+
| poolid | name | numvols | maxvols | pooltype | labelformat |
+--------+--------------+---------+---------+----------+-------------+
| 1 | Default | 0 | 0 | Backup | * |
| 2 | CleaningPool | 0 | 0 | Backup | * |
| 4 | Full | 8 | 0 | Backup | * |
| 5 | Differential | 4 | 0 | Backup | * |
| 6 | Incremental | 4 | 0 | Backup | * |
| 7 | Scratch | 7 | 0 | Backup | * |
| 8 | Archiv | 0 | 0 | Backup | * |
+--------+--------------+---------+---------+----------+-------------+
*use
The defined Catalog resources are:
1: MyCatalog
2: ArchiveCatalog
Select Catalog resource (1-2): 2
Using Catalog "ArchiveCatalog"
Using Catalog name=ArchiveCatalog DB=bacula_archive
*list pool
+--------+--------------+---------+---------+----------+-------------+
| poolid | name | numvols | maxvols | pooltype | labelformat |
+--------+--------------+---------+---------+----------+-------------+
| 2 | CleaningPool | 0 | 0 | Backup | * |
| 3 | Archiv | 1 | 0 | Backup | * |
| 7 | Scratch | 0 | 0 | Backup | * |
| 8 | Default | 0 | 0 | Backup | * |
| 9 | Full | 0 | 0 | Backup | * |
| 10 | Differential | 0 | 0 | Backup | * |
| 11 | Incremental | 0 | 0 | Backup | * |
+--------+--------------+---------+---------+----------+-------------+
> > It is a bit confusing that the pools exist in both catalogs, but not the
> > volumes. What about the scratch pool, is there a way to share the volumes
> > between the catalogs/pools?
>
> No. Maybe it is something to think about for the future though.
>
> By the way, handling of two catalogs is, for the most part, significantly
> improved in version 2.0.x compared to 1.38.11.
I'm using 2.0.2.
> Pool definitions are currently "global". At some point in the future, they
> will need to be attached to a particular catalog ...
That would be great, at the moment it's a bit tricky to use 2 catalogs.
Ralf
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
