Dear Eduardo,

many thanks! Due to your guidance everything worked successful! 
Remarks:
1. The new server architecture was different from the old servers one but 
no problem came up (there was no LONG-Column in any table defined)
2. I changed some of the parameters (e.g. CAT_CACHE_SUPPLY, MAXUSERTASKS, 
_MAXDEVSPACES, _TAB_RGNS,... ) during the installation of the target 
instance - without any problem. What is really important is to use the 
same DATE_TIME_FORMAT - parameter! 

regards
Heidi Rufer

-Entwicklung-
Kern AG
Hildastr. 66
D-79102 Freiburg

Fon:  +49-761-791 878-150
Fax:  +49-761-791 878-9
mailto: [EMAIL PROTECTED]
http://www.kern.ag






Hi there,

Is the arquitecture diferent in the new server?. Otherwise, you can use a 
homogenous system copy of your database instance for example to test new 
applications, to check the database structures without affecting operation 
or to set up a new standby database.

Prerequisites
Different prerequisites apply depending on the type of database instance 
that you want to copy:

· Database instance type OLTP: the processor architecture of the source 
and target computers have to be compatible.
· Database instance type liveCache: both the processor architectures and 
the operating systems of the source and target computers have to be 
identical, and the same database procedures have to be used on both 
computers.

Process Flow
Use the Database Manager.
       1.      Create a complete data backup of the original instance to a 
backup medium.
       2.      Initialize an existing target instance, or create a new 
target instance using the for recovery option.
The target instance has to be the of the same database instance type as 
the original instance and use the same database software version.

¡ You are using the original parameters of the original database instance 
for the target instance.
¡ In the target instance, create volumes that are large enough for 
importing the data backup from the original instance.
¡ In the target instance, define a backup medium that is compatible with 
the backup medium on which you created the data backup of the original 
instance.
       3.      Import the complete data backup of the original instance in 
the target instance.
You can transport the data backup using pipes.

With the database manager GUI, proceed as described in Recovery Without a 
Backup History.

You must not transfer the target instance to the operational state ONLINE 
before you import the data backup from the original instance. If the 
target instance has already been in operational state ONLINE, you have to 
reinitialize the target instance.

       4.      Transfer the target instance to the operational state 
ONLINE.
       5.      Update the system tables in the target instance. You will 
need the database system administrator and the domain user?s password for 
this.
       6.      If necessary, restore indices that are no longer up-to-date 
in the target instance (BAD INDICES).

Eduardo Vega Torres
Projection Core Consulting Ltda.
Tel. +571-3131060
Bogotá, Colombia.

-----Mensaje original-----
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Enviado el: Mié 27/07/2005 07:04 a.m.
Para: maxdb@lists.mysql.com
Asunto: copy a complete database to a different server

Reply via email to