ADSM-L

Re: DumpDB and Volume Change

1997-04-02 14:33:15
Subject: Re: DumpDB and Volume Change
From: "Pittson, Timothy ,HiServ/US" <tpittson AT HIMAIL.HCC DOT COM>
Date: Wed, 2 Apr 1997 14:33:15 -0500
Betsy,
        It's easier to format, then define the 4 new database volumes to ADSM,
then delete the old ones... ADSM will automagically move the database
entries from the deleted db volumes to the new database volumes.  When
you do this, make sure the 4 new db vols are the same size or larger
than the existing databases, otherwise this won't work.  If the sum of
the space on the 4 volumes is greater than the 10 volumes, you can
always extend your database after the old db vols are deleted.

Tim Pittson
tpittson AT himail.hcc DOT com

>----------
>From:  Moir,Elizabeth[SMTP:Elizabeth.Moir AT VM.SSW.ABBOTT DOT COM]
>Sent:  Wednesday, April 02, 1997 9:47 AM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       DumpDB and Volume Change
>
>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>