Re: [Bacula-users] job records have gone after database move

[Andras Horvai]

Hi,

Thank you for your answer. I think it is not the problem... Fileset has 2
months retention period it means files are gone from
the Catalog after 2 months... this is perfectly ok for me. But the volume
has 100 years retention period and job records also
inherit this retention period, the problem is that after database restore
these job records have gone from the catalog after
about 2 weeks usage of the new server or so, honestly I cannot tell you
this precisely because I have not checked the presence
of archive jobs in catalog.

This is how I planned the restore from archive:
I would have expected that I had the archive job records id in catalog, so
using those
I would have been able to do a full job restore (this would have perfectly
worked for me).
And this would have worked if I should not had to move the catalog to
another server :( since I checked with the old db and
I was able to see the old archive records...

I am going to double check the logs on the new server but I do not think so
I would find any useful :(

Thanks for any help,

Andras



Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Fri, Aug 4, 2017 at 10:02 PM, Dan Langille  wrote:

> > On Aug 3, 2017, at 4:44 AM, Andras Horvai 
> wrote:
> >
> > Hi,
> >
> > I had to move my bacula backup server from one server to another because
> of hardware
> > failure. I am using mysql server as my catalog backend. Before
> installing the new server
> > I did a mysql dump on the old and then I did a mysql restore on the new.
> > Seemed everything was fine. Then recently I had to restore from Archive.
> >
> > I have archive jobs which are copy jobs.
> > I do weekly full backup to a file storage. Then these copy jobs move the
> last full backup from
> > file storage to tape (worm) storage.
> >
> > The retention period of the volume of archive is 100 years. This
> retention
> > time is inherited by the jobs. The file retention time of these jobs is
> 2 months. So in theory,
> > when I have to restore something from archive what is 2 years old I
> would be able to do
> > a full job restore... of that full backup which would be perfectly fine
> for me but the problem:
>
> As I understand it, and perhaps other can correct/confirm:
>
>  - when the first retention period is met, the data can be purged from the
> Catalog.
>
> Perhaps this data has been purged from the new database server after it
> was copied it.  It was
> there, but now it has been purged. Has the 2 month period been met since
> that move?
>
> > It seemed that after the move of the backup server I lost my archive job
> records from the catalog.
> > bacula did not find the archive jobs of the client in the catalog. I had
> to use bscan on the tape
> > volume, so I was able to restore.
> >
> > Fortunately, I did not wipe the old system so I was able to run bconsole
> and I checked
> > that the archive records are present... in the old database
> >
> > Can anybody advise what to check in this case? What did I wrong?
>
> I think you did nothing wrong.
>
> --
> Dan Langille - BSDCan / PGCon
> d...@langille.org
>
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] job records have gone after database move

[Dan Langille]

> On Aug 3, 2017, at 4:44 AM, Andras Horvai  wrote:
> 
> Hi,
> 
> I had to move my bacula backup server from one server to another because of 
> hardware
> failure. I am using mysql server as my catalog backend. Before installing the 
> new server
> I did a mysql dump on the old and then I did a mysql restore on the new.
> Seemed everything was fine. Then recently I had to restore from Archive.
> 
> I have archive jobs which are copy jobs. 
> I do weekly full backup to a file storage. Then these copy jobs move the last 
> full backup from
> file storage to tape (worm) storage. 
> 
> The retention period of the volume of archive is 100 years. This retention
> time is inherited by the jobs. The file retention time of these jobs is 2 
> months. So in theory,
> when I have to restore something from archive what is 2 years old I would be 
> able to do
> a full job restore... of that full backup which would be perfectly fine for 
> me but the problem:

As I understand it, and perhaps other can correct/confirm:

 - when the first retention period is met, the data can be purged from the 
Catalog.

Perhaps this data has been purged from the new database server after it was 
copied it.  It was
there, but now it has been purged. Has the 2 month period been met since that 
move?

> It seemed that after the move of the backup server I lost my archive job 
> records from the catalog.
> bacula did not find the archive jobs of the client in the catalog. I had to 
> use bscan on the tape
> volume, so I was able to restore.
> 
> Fortunately, I did not wipe the old system so I was able to run bconsole and 
> I checked
> that the archive records are present... in the old database 
> 
> Can anybody advise what to check in this case? What did I wrong?

I think you did nothing wrong.

-- 
Dan Langille - BSDCan / PGCon
d...@langille.org



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users