Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!apple!mrspoc!itkin
From: itkin@mrspoc.Transact.COM (Steven M. List)
Newsgroups: comp.databases
Subject: Re: moving unify and file.db to different system
Keywords: unify
Message-ID: <1989Oct3.184225.17467@mrspoc.Transact.COM>
Date: 3 Oct 89 18:42:25 GMT
References: <34964@apple.Apple.COM>
Reply-To: itkin@guinan.UUCP (Steven List)
Organization: Transact Software, Inc.
Lines: 54

ric@Apple.COM (Ric Urrutia) writes:

>Could someone please help me with a problem I'm having porting a unify 
>database to a different hardware platform.  Here is the scenario:

>1.  Existing file.db is on two raw partitions of 65 meg each
>2.  I need to put file.db on a single raw partition on new system
>3.  I tried backup and restore unify utitlities (BUDB and REDB) but
>    the backup program apparently backs up the unify.db first including
>    volume information.
>4.  When I go to restore on target system, it restores unify.db first and
>    attempts to restore to old partition names.  I really don't want or need
>    two volumes for this database.

>My question is this

>1.	Can I dd file.db onto a cartridge tape and dd onto the new single
>	raw partition on target system.

Yup.  Just like cat, except you'll use tapes as the intermediate step.
Actually, you'll need to dd each part of the database separately, since
file.db will be a device node pointing to the first volume.  So you will
need to dd the entire contents of each disk partition (database volume)
onto a tape, set up the new database (see below) and then retrieve the
contents of each of the old volumes and put them into the new database.
The second tape will be restored with dd seek=nnnn.

>2.	Can I then restore unify.db from a cpio backup, modify volume 
>	maintenance and tell set it to a single volume db.

The trick here will be to set up the new database with two volumes that
correspond in size to the originals.  Since each volume (other than volume
zero) may start at an offset within its disk partition, the second volume
in the new database should be set to start immediately after the first.
Both volumes should be defined to be on the same disk partition.  Once
you've restored the database by copying in the tapes (remembering to
seek for the second volume), you can then change the volume information in
the database header to have only one volume.  Since the reconfiguration
process dumps and reloads the database, the change in volumes should work
fine.

>3.	Do I have to modify anything in the file.db header to tell
>	it there is only one volume.  If so, is there a UNIFY utility
>	that will do this for me.

No, and no.

Call me, Ric, if you need anything more.
-- 
 +----------------------------------------------------------------------------+
 :                Steven List @ Transact Software, Inc. :^>~                  :
 :           Chairman, Unify User Group of Northern California                :
 :     {apple,coherent,limbo,mips,pyramid,ubvax}!itkin@guinan.Transact.COM    :