ADSM-L

DumpDB and Volume Change

1997-04-02 09:47:45
Subject: DumpDB and Volume Change
From: "Moir,Elizabeth" <Elizabeth.Moir AT VM.SSW.ABBOTT DOT COM>
Date: Wed, 2 Apr 1997 08:47:45 -0600
To: OAS     --LMS1

FROM: Betsy Moir (TTCEDM) Ext 85020
      VM Tech Services
      email:  elizabeth.moir AT vm.ssw.abbott DOT com
Subject: DumpDB and Volume Change

I hope somebody can help me with this question.  We are running Version 1 of
the ADSM server on VM.  We 10 volumes of varying sizes being used by the
ADSM database.  The storage administrator here wants to consolidate these
10 volumes into 4 much larger volumes.  In studying the documentation we
think the DUMPDB and LOADDB commands are what we should use...Dump the
database, define the new volumes, delete the old volumes and Load the
database back on.

In all my reading, however, it seems to be that in order to use the Dump
DB Load DB scenario, the volumes that the database is being loaded back
onto have to be the same size.  Is this true?  If so, does anyone have
any ideas on what we CAN do in order to achieve our ultimate goal of fewer,
larger volumes for the database.

Thanks in advance for any and all suggestions.

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