I do not know will this work in ADSM 3.1 (but it ought to). At least it works in my TSM 4.1. 1. (optional) Format log volume files - if on Windows or prefer to use files instead of raw devices 2. Mirror the volume(s) in question using "DEFine LOGCopy" command (in my test "def logc /dev/rtsm_log0 /dev/rtsm_log1") 3. Delete old copy using "DELete LOGVolume" command (in my test "del logv /dev/rtsm_log0") If you wish to have DB and LOG mirrored on different disks on the end repeat steps 1&2 (i.e. "def logc /dev/rtsm_log1 /dev/rtsm_log2" or something similar).
Zlatko Krastev IT Consultant "Ward, Stuart" <[EMAIL PROTECTED]> on 26.12.2001 21:29:20 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Moving Log Volumes on 3.1 Hi I have recently taken over an ADSM implementation. It is not configured the way I believe it should be and I want to make some adjustments. At some point I hope to have the necessary funds to upgrade the version too as I believe we are out of date here. Anyhow, I have ADSM 3.1 at level 2.9 and a configuration such that I have logs and database on same hard drive. I have another hard drive I wish to put in the machine and ultimately want to end up with some semblance of correct configuration. I wish to have a duplicate copy of DB and logs on both hard drives. At present there is no ADSM mirroring set up and such, if I can move the logs I think I'm golden. My question therefore, is how I go about moving the log volumes safely without jeopardising the installation. Once they are moved I will implement a mirror of the respective DB/LOGS on the opposing disks. Any and all help is appreciated. Thanks Stu
