ADSM-L

Re: Backup of all-local -systemonject

2004-01-09 11:50:01
Subject: Re: Backup of all-local -systemonject
From: Bill Kelly <kellywh AT AUBURN DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 9 Jan 2004 10:49:35 -0600
On Fri, 9 Jan 2004, Prather, Wanda wrote:

> (You probably don't remember me, but I'm sure you've stumbled across some of
> my old code there at some point...:>)

Wanda,

(Actually, I think I remember meeting at SHARE or something...in any case,
rest assured you're still talked about in reverent tones around here :-)

> But, if you don't want to store the data, you could bind the System Object
> (via include.systemobject in a CLOPTSET) to a management class that trashes
> it immediately.

That's exactly what I wound up finally doing.  The data goes to a disk
pool and is deleted from there, so that at least it doesn't tie up space
on tapes, etc.

> Hm... wonder what happens if you bind it to a management class with no
> backup copy group?  ....something else to put on my to-test list...

I tested that.  If in the GUI, the user gets a 'server out of data storage
space' message and the backup fails.  I was willing to live with that,
even though if, for example, a user selects a local drive and the System
Object, then clicks 'Backup', the backup fails without having backed up
even the local drive.  (Apparently the client attempts to back up the
System Object first.)

But we also have some pre-v5 clients still out there (hey, there's only so
much control one has in at least this university setting), which don't
support the 'domain -systemobject', and their scheduled incremental
backups fail altogether when I impose an 'include.systemobject ALL
blackhole' on them.

So, I went with the 'let them back it up, then throw it away' approach,
which has its obvious drawbacks in terms of wasted resources.

*sigh*

Regards,
Bill

> -----Original Message-----
> From: Bill Kelly [mailto:kellywh AT AUBURN DOT EDU]
> Sent: Friday, January 09, 2004 10:58 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Backup of all-local -systemonject
>
>
> On Fri, 9 Jan 2004, Lambelet,Rene,VEVEY,GL-CSC wrote:
>
> > could you help me, I'd like to backup all local volumes like C., D: etc.
> BUT
> > without the system state !
> >
> > We did not succceed with  "Domain all-local -systemobject"
>
> How exactly is the backup being done?  With the 'incremental' command
> (scheduled or via command line) or 'on-demand' via the GUI?  If
> incremental, then the 'domain -systemobject' (or 'domain all-local
> -systemobject', which is the same thing) should work.  However, the
> 'domain' statement doesn't affect 'on-demand' backups, so if the user
> selects the System Object in the GUI and then clicks 'Backup', it will be
> backed up even if you have a 'domain -systemobject'.
>
> I've recently been through all of this; as far as I can tell, there is no
> way to absolutely prevent a client from backing up the System Object if
> the user really wants to.  No 'exclude.systemobject', no nothing.
>
> I hope I'm wrong on this, and if so, I'd love for someone to correct me!
>
> Thanks,
> Bill
>
> Bill Kelly
> Auburn University OIT
> 334-844-9917
>

<Prev in Thread] Current Thread [Next in Thread>