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
-----Original Message-----
From: Denis L'Huillier [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 26, 2001 17:42
To: [EMAIL PROTECTED]
Subject: New server migration
Hello,
I am planning to migrate my ADSM server to a new Server running TSM.
ADSM 3.1.2.50 RS/6000 R20 (IBM 3466 B03) 3494 Library 3590 B1A drives- OLD
SERVER
TSM 3.7 RS/6000 H70 (IBM 3466 C01) - 3494 Library 3590 E1A drives - NEW
SERVER
AND NEW 3494
Here is my basic plan:
From the old server:
1. Copy devconfig and volhist. Record db and log size from q log and q db
2. Initiate a full db backup then eject from library / insert in new Library
From the new server:
1. Restore devconfig and volhist.
2. Format the db and log via:
dsmserv format 1 <logname> sizeinMB 1 <dbname> sizeinMB
3. Restore the db via:
dsmserv restore db todate=<todays date>
From what I have read I will not have to do a upgrade db because when
running
on AIX this is done automatically.
4. Move all the tapes from the old 3494 to the new 3494.
The part I am not sure of is the format db command. Is this necessary if
I'm
doing a restore db?
How can I find out what my database name and recovery log name is?
This is the output from q logvol:
Volume Name Copy Volume Name Copy Volume Name Copy
(Copy 1) Status (Copy 2) Status (Copy 3) Status
---------------- ------ ---------------- ------ ---------------- ------
/lgaa1dk2/lg Sync'd /lgaa1dk6/lg Sync'd Undef-
ined
This is the output from q log:
Available Assigned Maximum Maximum Page Total Used Pct
Max.
Space Capacity Extension Reduction Size Usable Pages Util
Pct
(MB) (MB) (MB) (MB) (bytes) Pages
Util
--------- -------- --------- --------- ------- --------- --------- -----
-----
1,980 1,980 0 1,976 4,096 506,368 215 0.0
1.1
(Courier New and Font 10 will make the q log,logvol look normal)
Would the command be: dsmserv format db 1 lgaa1dk2 1980 1 <db> <size>?
Would I have to issue this command for each recovery log volume and each db
volume?
I think I'm missing something here... I've spent hours searching the list
and
reading the adsm guides but I am
still unsure.. I'm a new adsmer, sorry for the "dumb" questions..
Thanks in advance,
Denis
**********************************************************************
This e-mail and any attachment may contain confidential and privileged material
intended for the addressee only. If you are not the addressee, you are notified that
no part of the e-mail or any attachment may be disclosed, copied or distributed, and
that any other action related to this e-mail or attachment is strictly prohibited, and
may be unlawful. If you have received this e-mail by error, please notify the sender
immediately by return e-mail, and delete this message. Koninklijke Luchtvaart
Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for
the incorrect or incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
**********************************************************************
