ADSM-L

Re: New server migration

2001-02-27 04:35:29
Subject: Re: New server migration
From: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT NL>
Date: Tue, 27 Feb 2001 10:35:33 +0100
Hi Denis
Your scenario should work.
You should indeed do a format db. The database and recovery log should be
formatted before TSM can fill them by using the restore db command.
You will however have to do a upgrade db. This is only done automatically if
you perform an in-place upgrade from ADSM to TSM, but since you are moving
to a new server, you will have to do it manually. Don't worry, it takes
about 5 to 10 minutes or less.
You've answered your questions about the log and database name yourself! The
q logvol showed /lgaa1dk2/lg and /lgaa1dk6/lg which means that you have one
recovery log, mirrored by ADSM across two volumes. The first file is called
lg and is located in /lgaa1dk2 and the second file (also called lg) is
located in the /lgaa1dk6 filespace. About the same goes for the database as
far as I could remember for the 3466.
You will have to allocate the database and log files on your new host by
issuing the following commands:
Create the log and db:
dsmfmt -m -log /lgaa1dk2/lg 1980 /lgaa1dk6/lg 1980
dsmfmt -m -db /dbaa1dk2/db 1980 /dbaa1dk6/db 1980
Format the database and log files :
dsmserv format 2 /lgaa1dk2/lg /lgaa1dk6/lg 2 /dbaa1dk2/db /dbaa1dk6/db
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


<Prev in Thread] Current Thread [Next in Thread>