The error messages in #4 are due to the inability to set
the TCP/IP window size. You might want to try
TCPWINDOWSIZE 8
in the client options file to set up a windows size
requiring less buffer space.
Barry Fruchtman
ADSM Development
On Wed, 15 Jan 1997, Hilton Tina wrote:
> We also have ADSM on an SP2. Our server is at 2.1.5.10. We also purchased
> the Disaster Recovery Module. I don't know if that's available on 2.1.0.1
> or not.
>
> 1. Our procedure (untested so far, but we're not production yet) is to
> restore the server node from a mksysb image, restore the other volume groups
> (including the ones used for the adsm database, log, storage pool, etc.)
> from a savevg, then following the instructions & running the scripts so
> wonderfully prepared by DRM. The DRM script knows everything about the
> database size, volhist, which volumes were considered offsite, etc.
>
> 2. I was "thrown" into ADSM too, and am very glad we purchased DRM so I
> don't have to figure out how to do it manually. We make backup our storage
> pools and database every day and those tapes are taken offsite. If we ever
> need to restore our database locally, we'll just call for the tape to be
> returned.
>
> 3. Sorry. Can't answer this one.
> ----------
> From: Wood, Darren
> To: Multiple recipients of list ADSM-L
> Subject: ADSM Newbie questions
> Date: Tuesday, January 14, 1997 5:19AM
>
>
> Hello everybody,
> Having been thrown in at the deep end and given
> the task of implementing ADSM ( with only the manuals to read ) I've
> finally come up gasping for air and with a few questions.
>
> Please forgive me if these questions are basic but any help/pointing me
> in the right direction for answers would be gratefully appreciated.
>
> 1. Am I right in assuming that the procedure for a 'Bare metal restore'
> of the ADSM server after a disaster is as follows :-
> i) Re-install the ADSM server onto new system.
> ii) Increase the size of the d/b & recovery log to that of the
> original.
> iii) Restore the volhist, dev config & server option files.
> iv) Restore the ADSM d/b.
> v) Change status of all stg volumes not off-site to destroyed.
> vi) Change status of all off-site volumes to readwrite.
> vii) Restore Primary stg volumes.
>
> 2. Would the import/export be useful in a disaster recover position ?
>
> 3. Once a ADSM d/b backup has been performed can a copy of this backup
> be taken to enable a copy to be sent off-site ?
>
> 4. While testing I got the following message every time I made a client
> to server connection.
> TcpOpen() : setsockopt (SO_SNDBUF) : errno = 74
> TcpOpen() : setsockopt (SO_RCVBUF) : errno = 74
> TcpOpen() : setsockopt failed to open on one or more options
> Does anybody know why this is happening ?
>
> My set up is
> ADSM server & client V2.1.0.1
> IBM SP2 all nodes AIX 4.1.4 connected through a High speed switch.
>
> Thanks in advance.
>
> Darren
>
|
