From:	SMTP%"hopson_thomas_h@lilly.com" 29-JUL-1993 14:31:13.60
To:	EVERHART
CC:	
Subj:	Re: Oh Give me a ... break (re: snapshots)

X-Newsgroups: comp.os.vms
Subject: Re: Oh Give me a ... break (re: snapshots)
Message-ID: <1993Jul29.075828.331@inet.d48.lilly.com>
From: rz85728@mcvax0.d48.lilly.com (Thomas H. Hopson)
Date: 29 Jul 93 07:58:28 EST
Reply-To: hopson_thomas_h@lilly.com
Sender: rz85728@mcvax0.nohost.nodomain (Thomas H. Hopson)
Distribution: world
Organization: Eli Lilly and Company, LCC Indianapolis
Nntp-Posting-Host: mcvax2.d48.lilly.com
Lines: 38
To: Info-VAX@KL.SRI.COM
X-Gateway-Source-Info: USENET


In article <1993Jul29.061319.6663@spcvxb.spc.edu>,
terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.) writes:
>In article <28JUL199320305566@spades.aces.com>,
>gavron@spades.aces.com (Ehud Gavron) writes:
>> With BIG KUDOS to Edward J. Los of DEC, Snapshot does indeed work
>> on VAXcluster systems of various configurations (excluding those
>> with non-motif DECwindows).  If you want "supported" vs.
>"unsupported"
>> or like the other whiner who wrote "if it aint' gonna be supported
>> then why have it?" just shut the hell up.

[...]

>  I haven't looked at the V6.0 release yet. Can you simply run the
>snapshot
>prep utility on a clustered system, or are special steps involved? If
>so, can
>you tell us what those steps are?

The SYS$MANAGER:SNAPSHOT.COM procedure explicitly checks for cluster
membership and, by default, disallows the snapshot if the machine is
clustered.

You can force it to take the snapshot anyway, by issuing a

	$ DEFINE/SYSTEM SNAPSHOT$ALLOW_UNSUPPORTED "TRUE"

This would indicate to me that it's unsupported.  But it might work,
too.  I haven't tried it, myself.  I gather that Ehud has.

						- Tom

--
Thomas H. Hopson                   thh@lilly.com
Eli Lilly and Company
Lilly Corporate Center
Indianapolis, IN  46285