Bacula-users

Re: [Bacula-users] Preserving data of decommissioned Bacula client

2011-12-22 02:40:47
Subject: Re: [Bacula-users] Preserving data of decommissioned Bacula client
From: Geert Stappers <Geert.Stappers AT vanadgroup DOT com>
To: "bacula-users AT lists.sourceforge DOT net" <bacula-users AT lists.sourceforge DOT net>
Date: Thu, 22 Dec 2011 08:36:21 +0100
Op 20111221 om 18:12 schreef Win Htin:
> On Wed, Dec 21, 2011 at 12:03 PM, John Drescher <drescherjm AT gmail DOT com> 
> wrote:
> >> If I want to retire an old server but need to keep the backup data for
> >> several years, what is the best option? Just disable the job? What
> >> happens if the old server is deleted from the clients list?
> >>
> >
> > The big problem is volume recycling. Does this server use volumes that
> > any other server uses or separate volumes?
> >
> > John
> 
> Yes, the volumes are shared with other servers/Bacula clients but the
> monthly full backups are kept off-site for the requisite period, i.e.
> the tapes/volumes are not re-cycled.
> 
> Thanks,
> Win


on this mailinglist a few days ago ...

| Op 20111220 om 17:15 schreef Bill Arlofski:
| > On 12/19/11 21:31, Gary R. Schmidt wrote:
| > > Hi,
| > > Bacula 3.0.3.
| > > 
| > > I've had some machines be removed from use, but I don't want their 
| > > backups to go away until we are sure their replacements are complete.
| > > 
| > > I can disable them individually from the console, but is there something 
| > > I can do in the .conf file that will turn them off?
| > 
| > Hi Gary...
| > 
| > If you are talking about not having the DATA on your volumes being
| > over-written then I would create a pool called something like
| > "Archive" with a very long retention period. Then determine which
| > volumes have the jobs on them that you do not want to lose and move
| > them into that pool.
| >
| > Also, since you probably don't want the jobs running any more,
| > what I normally do is create a schedule called "Manual"  with no
| > run definitions like so:
| >
| > Schedule {
| >   Name = Manual
| > }
| >
| > and set the Job's schedule to Manual.  This way, I can start any of
| > these jobs manually (they are not disabled) any time I want/need,
| > but they will no longer run on the nightly schedule.
| >
| > Hope this helps.
| >
| > --
| > Bill Arlofski
| > Reverse Polarity, LLC
| > http://www.revpol.com/
| > 


Groeten
Geert Stappers
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users