Technical data

Moving a Server to Another Machine
Administration Guide 15-7
For detailed information on monitoring and logging values and attributes, see the
Server topic in the Administration Console Online Help.
Moving a Server to Another Machine
When an applications server is moved to another machine, it must be able to locate the
transaction log files on the new disk. For this reason, we recommend moving the
transaction log files to the new machine before starting the server there. By doing so,
you can ensure that recovery runs properly. If the pathname is different on the new
machine, update the
TransactionLogFilePrefix attribute with the new path before
starting the server.
When migrating transaction logs after a server failure, make all transaction log files
available on the new machine before starting the server there. You can accomplish this
by storing transaction log files on a dual-ported disk available to both machines. As in
the case of a planned migration, update the
TransactionLogFilePrefix attribute
with the new path before starting the server if the pathname is different on the new
machine. Ensure that all transaction log files are available on the new machine before
the server is started there. Otherwise, transactions in the process of being committed at
the time of a crash might not be resolved correctly, resulting in application data
inconsistencies.