Kbase P125076: How to restore a 10.1A database to another server with OpenEdge 10.1B
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/07/2008 |
|
Status: Verified
GOAL:
How to restore a 10.1A database to another server with OpenEdge 10.1B
GOAL:
How to restore an online probkup of a database to OpenEdge 10.1B environment
GOAL:
Can I restore an online probkup to an OE 10.1B environment
GOAL:
How to restore an online probkup to a remote device
GOAL:
How to restore an online probkup to mapped drives on a remote device
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Versions
FIX:
Due to the 'complex' nature of this environment, the instructions below are formatted by way of example for a sports2000 database.
assume:
\\server1\db is where the OpenEdge 10.1A backup file volumes are, mapped-drive Y:\
\\server2\Oe10 is where the OpenEdge 10.1B installation is
\\server3\tt is where the database needs to be restored as a 10.1B database, mapped-drive X:\.
Note: If this were an OFFLINE probkup, it would not be necessary to truncate the bi with 101a utilities.
1.) Start by cleaning down the past failure to restore. This includes all instances of .db and database files.
[\\server2\Oe10 ]
2.) Create a structure file (dbname.st) LOCAL to server2 that includes all extents to be restored and their full path-name
# dbname.st
b X:\tt.b1
d "Schema Area":6,32;1 X:\dbname.d1
d "Employee":7,32;1 X:\dbname_7.d1
d "Inventory":8,32;1 X:\dbname_8.d1
d "Cust_Data":9,32;1 X:\dbname_9.d1 f 10240
d "Cust_Data":9,32;1 X:\dbname_9.d2
d "Cust_Index":10,32;1 X:\dbname_10.d1 f 512
d "Cust_Index":10,32;1 X:\dbname_10.d2
d "Order":11,32;1 X:\dbname_11.d1
d "Misc":12,32;1 X:\dbname_12.d1
3.) create a multivolume backup file feeder: dbname.rst is also LOCAL to server2
Y:\dbname1.bak
Y:\dbname2.bak
Y:\dbname3.bak
.. etc
4.) STEPS (please verify each step)
a.) create the database structure on the X drive, with 101a utilites
proenv> %DLC%\bin\101dbutils\101a_dbutil prostrct create X:\dbname dbname.st
b.) RENAME dbname.st dbname0.st
c.) restore backup
proenv> %DLC%\bin\101dbutils\101a_dbutil prorest X:\dbname Y:\dbname0.bak < dbname.rst
d.) truncate bi file
proenv> %DLC%\bin\101dbutils\101a_dbutil X:\dbname -C truncate bi
5.) start the remote database, with the 10.1B executables:
proserve X:\dbname [+ parameters]
NOTE in the dbname.lg file the messages:
BROKER 0: (9466) File X:\dbname.db is on a remote device.
BROKER 0: (333) Multi-user session begin.