John Huttley wrote:
> No DNS, no connect, no bacula, no restoring dns files!
Tip #1: All infrastructure needed for a correct backup/restore should go in
/etc/hosts on all clients beeing backed up. Make this a documented routine
as you roll out your backup software on all the clients.
Tip #2: If
On Monday 09 July 2007 06:10:57 Dan Langille wrote:
> On 9 Jul 2007 at 14:45, John Huttley wrote:
> > Yes that would have been an option.
> > The real issue was simply realising what the problem was.
> > I had a sweaty period of thinking "Oh no, i've buggered the DNS and
> > bacula both", help help
On 9 Jul 2007 at 14:45, John Huttley wrote:
> Yes that would have been an option.
> The real issue was simply realising what the problem was.
> I had a sweaty period of thinking "Oh no, i've buggered the DNS and
> bacula both", help help!
Yep. Experience will help that situation.
--
Dan Langi
sses in the config
> files temporally?
>
> Robert LeBlanc
>
>
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:bacula-users-
>> [EMAIL PROTECTED] On Behalf Of John Huttley
>> Sent: Sunday, July 08, 2007 8:16 PM
>> To: bacula-users@lists.sour
o: bacula-users@lists.sourceforge.net
> Subject: [Bacula-users] Nasty Gotcha with bacula
>
> Hi,
>
> I've just recovered from blitzing my /etc/bind/named.conf file.
> I must have done it weeks ago but not restarted the server until now.
>
> Bacula could not restore this file be
Hi,
I've just recovered from blitzing my /etc/bind/named.conf file.
I must have done it weeks ago but not restarted the server until now.
Bacula could not restore this file because the console would not connect
to the director.
Why? because all the bacula conf files use dns host names.
No DNS,
