---------- X-Sun-Data-Type: text X-Sun-Data-Description: text X-Sun-Data-Name: text X-Sun-Charset: us-ascii X-Sun-Content-Lines: 110 HI Sun managers, Thanks to Erwin Fritz, Marina Daniels, and Dennis Martens. The questions and answers are as following: > I am going to upgrade a data server from Solaris 2.4 to Solaris 2.6 this > weekend (also replacing the 1GB system disk to 2GB disk), and has a few > questions hopefully you can help me. > > My current configuration consists 4 disk controllers with several disks per > controller. It works really well in the past few years. DiskSuite in this > system has 4 metaDB spread out in 4 disks respectively. The system disk has > only the metaDB which I think it is much easier to do the upgrade without much > concern of accidentally damage the disk array. My procedure is: > > 1. The new 2GB disk will first put inside the other system, and will be > partitioned to 600MB for /, 600MB for /var, 600MB for /opt, and 256MB for > the swap. Then I will restore the / and /var from yesterday backup tape. > > 2. After the backup is done, I will replaced the 1GB disk with 2GB disk into > the system, then comment out the RAID 5 mounting point (/export/local and > /export/home0) in vfstab (note: none of the slice of RAID 5 are in system > disk). Afterward, I rebooted the system and do the system upgrade from > Solaris 2.4 to 2.6. > > 3. After the Solaris upgrade, then I will restore the original vfstab so > that after further reboot, the system will mount the RAID 5 disks. > > 4. lastly I will apply recommended cluster patch for Solaris 2.6 and find > if I need to apply further patch for Y2k and disksuite. > > My question are: > > 1. I don't think I need to 'newfs' the 5MB partition of the new 2GB disk > which is reserved for the MetaDB, right? Correct. > > 2. after I replaced the system disk from 1GB to 2GB disk and before doing > the commenting out the RAID 5 mounting points for purpose of doong the OS > upgrade, the metaDB is not in the 2GB disk, will the system automatically > created it in the system disk? I actually get an better answer from Sun T.S. engineer. Since I have 4 MetaDB and the minimum requirement is 3, I just went ahead and deleted the MetaDB in the system disk: metadb -d c0t3d0s7 (ie. slice 7 has the MetaDB) Other suggestion is to use 'metainit' to do this trick. > > 3. after the OS upgrade from 2.4 to 2.6, do I need to re-install the disksuite > from 2.6 CD? Or the upgrade includes disksuite upgrade? And what is the > procedure? The current version of the disksuite is 4.0 of my Solaris 2.4, so after upgrading to Solaris 2.6, I need to install disksuite 4.1 from CDROM. I haven't really did the upgrade yet because I burned my 1GB Solaris disk! I am going to buy a new 4GB disk, then copy the 2GB disk to the 4GB disk, keep the 2GB for emergency fallback backup. And here is the procedure I will do in near future: a. save important information: metastat -p > metastatp.systemname metastat > metastat.systemname metadb -i > metastat.systemname b. take out the metaDB of the system disk (see the answer of the step 2), so my sysetm disk is not part of any Meta device (no MetaDB on it, and it was originally designed none of the slice in system disk is part of RAID 5 configuration) c. - mv /etc/rsS.d/S35SUNWmd.init & /etc/rc2.d/S95SUNWmd.sync to notused- - comment out the disksuite stuff in vfstab then reboot the 2.4 system, and do 2.4 to 2.6 upgrade. (make sure you have at least 2GB disk or else you may be at risk of running out disk space) d. someone suggest me to read "Solaris Server Intranet Extension Installaion and Release Notes 2.6" that come wtih 2.6 software. e. upgrade disksuite 4.0 to 4.1 from the other CDROM. - caution: need to answer "n" to some question so that my original disksuite configuration file is still being used by the new disksuite 4.1. - the Sun T.S. engineer actually email some of the advise including the above (see the 3 attachments) f. apply disksuite patch 104172-xx g. undo C., then reboot. h. use metastat or metatool to check the health of the disksuite. i. apply 2.6 cluster patch and do h. again. As I said before, I didn't really try the above yet, and will do it after the 4GB disk arrive. I do think I cover a lot but one must do some more research and don't follow my exact step because different people has different disksuite configuration. > > 4. In case something unexpected happened and I need to put back the original > 1GB disk, do I need to do anything after rebooted? > I think it should be Okay to put back the 2GB disk if the 4GB disk has problem. Rgds, Lincoln Chang Philips Semiconductors ---------- X-Sun-Data-Type: default X-Sun-Data-Description: default X-Sun-Data-Name: sds_4.0_4.1 X-Sun-Charset: us-ascii X-Sun-Content-Lines: 46 SCRIPTURE READING: Proverbs 17:1-28 Please pray for God's intervention in the situation in Yugoslavia. Pray for peace and the welfare of all in the world. I. PRAYER FOCUS FOR THIS WEEK: English Ministries 1. Pray for the development of a good prayer foundation and that God may be praised and glorified in all that we do. 2. Pray for spiritual renewal in the English Congregation. 3. Pray for a consistent and growing welcoming/follow-up/visitation ministry. 4. Pray for strong and growing Fellowships: Emmanuel (Adult), Lighthouse Koinonia (College/Career), El-Shaddai (High School), River of Life (Jr, High. 5. Pray for our outreach opportunities that people may come to know Christ: Emmanuel Fellowship Pot Luck (Sunday April 18th), El-Shaddai Friends Nite (Saturday April 24th) 6. Pray for our English Ministry Team: Steve Chiu, Dixie Chu, Sarah Lee, Danny Ma, Steve Tam, John and Jennie Wong, Jim Woo. 7. Pray for equipping opportunities, especially the start of a seekers class in Sunday School. II. CHURCH CALENDAR 4/16 Cook Chow's Evangelistic Meeting 4/23 (Fri) - Missions to Muslim and Arab Nations, Speaker: Mary Lai 4/25 (Sun) - Fellowship Sunday 4/25 (Sun) - Choir singing at Milpitas Arts Festival, outreach opportunity 4/30 (Fri) - "Singleness, Courtship and Marriage" Seminar, Speaker: Mimi Leung-Pang 5/2 (Sun) - Prayer Sunday 7/17-26 - Short Term Mission Trip to Panama 7/30-8/7 - Short Term Mission trip to Arizona III. PRAYERS FOR GOD'S HEALING ... 1. Alan Phan - new Christian, both kidneys failing. 2. Mrs. Grace Phipps (EC) - recovering at home after surgery. 3. Catherine Tjio - continued prayer for healing from tumor. 4. Mrs. Tow (lung cancer) - NEEDS much prayer. 5. Mr. Kwok-Yuen Leung (recovering in nursing home after recent stroke) IV. PERSONAL NEEDS 1. Pray for salvation of our non-Christian family members, spouses & relatives. 2. New mothers (Gladys Chan, Daphne Chong, Lian Fong, Rhonda Tung, Anna Wong, Noel Pang, Christina Choi, Olivia Hui, Grace Leung, Monica Ng) 3. Expecting mothers (Diana Lam, Michelle Lo, Linda Li, ok-Hin Yeo, Vivian Yim, Wai-Yee Lai, Katherine Tam) pray for good health and God's protection 4. Pray for those who are still looking for jobs... Pray for each other... ---------- X-Sun-Data-Type: default X-Sun-Data-Description: default X-Sun-Data-Name: sds_solaris_upgrade X-Sun-Charset: us-ascii X-Sun-Content-Lines: 115 Solaris upgrade with regard to Solstice Disksuite 4.x DISCLAIMER: ** THE PROCEDURE DESCRIBED BELOW ASSUMES THAT THE ADMINISTRATOR ** IS FAMILIAR WITH DISKSUITE AND SOLARIS UPGRADES ** IMPORTANT - This assumes that your system drive is NOT under SDS control. If it is, other steps must be taken (e.g., metaroot command). 1) Run: metastat -p and redirect to a file for safe keeping and also print it out. (This shows current SDS configuration) The file that you saved may be used after the upgrade. 2) Run: metadb -i and redirect to a file and print out (this shows replica locations). 3) Backup the entire system using "ufsdump" for safe keeping: a) halt system to the OK prompt b) boot -s (to boot up in maintenance mode) c) fsck all filesystems to check integrity d) perform level 0 dumps of filesystems by writing to tape device 4) Make sure all filesystems that are mounted on metadevices are unmounted. 5) Modify /etc/vfstab file and comment out all metadevice entries. 6) Move (mv) the two SDS startup scripts ( /etc/rcS.d/S35SUNWmd.init and /etc/rc2.d/S95SUNWmd.sync ) to " notused- " so that they will not be executed during subsequent bootups (these get renamed again AFTER Solaris upgrade). 7) If you have multiple controller numbers with disk drives or SPARC Storage Arrays attached - then make a note of the controller #'s. (for the SSA's run: ssaadm display c for each. Print out this info and save aside). 8) Reboot system (and verify that no metadevices are in use) ============================================================================ 9) Perform Solaris Upgrade at this point. ============================================================================ 10) Once upgrade is finished, rename the two startup scripts in /etc back to their original names. 11) Reboot new O.S. to multiuser and run metadb to make sure that the replicas are still intact. Also make a note of controller numbers of external SSAs (if applicable). If controller numbers changed then read appendix A below. If they are exactly the same then proceed with next step. 12) Run metastat to confirm that all metadevices are in the Okay state. (verify that all mirrors are synced-up if applicable). 13) Modify the /etc/vfstab and uncomment metadevice entries. 14) Fsck the filesystems on top of metadevices PRIOR to attempting to mount them. Once they are clean, mount them (or reboot one more time for completeness). NOTE: you shouldn't have to do anything fancy with the SDS configuration. The reason we printed out the metadb and the metastat in steps 1 and 2 were simply for precaution! ========================================================================= Appendix A: A-1) If controller numbers changed during the upgrade and there were metadevices on them - not to worry, the devices are still intact! We simply need to modify your /etc/opt/SUNWmd/md.tab file and change the controller numbers to reflect the new configuration. This would be a good time to run the ssaadm display command again for each SSA and verify controller numbers, etc. A-2) If metareplica databases are affected by the controller number changes, then those affected need to be deleted using "metadb -d -f " and then readded to the SAME slice (but with new controller number) by using "metadb -a -f . A-3) At this point we need to determine which metadevices were affected by the controlle number changes as well. Run metastat and save to hardcopy. Now metaclear every device that will need to be changed. A-4) Cd to /etc/opt/SUNWmd dir and copy md.tab to md.tab.b4upgrade A-5) Copy the saved file in step #1 (prior to upgrade) to md.tab and edit it and make controller number changes. If any of the metadevices are mirrors, comment out the second side of each mirror entry so that SDS will only configure first side initially. Also, if you have RAID5 devices, MAKE SURE THAT the new md.tab file has the "-k" switch after each RAID5 device entry to insure that it won't blow away data. (your metastat -p output should show the "-k" switch after each RAID5 device. CONFIRM THIS!). A-6) Now with second side of mirrors commented out AND RAID5 device verified AND controller numbers reflecting current configuration AND vfstab file still showing metadevice entries commented-out, initialize each affected metadevice (individually) by running the metainit command. metainit reads the md.tab and builds device accordingly. For example: "metainit d20". A-7) When all devices are initialized, reboot. A-8) When system comes up in multiuser mode, run metastat and verify status of devices. If devices are all in the Okay state then modify the md.tab file again and uncomment second side of mirrors. Then run "metattach" to attach second side of each mirror. A-9) Go back to step # 10 above and proceed with upgrade steps. ---------- X-Sun-Data-Type: default X-Sun-Data-Description: default X-Sun-Data-Name: solaris_sds_upgrade X-Sun-Charset: us-ascii X-Sun-Content-Lines: 79 Upgrading Solaris With Solstice DiskSuite -------------------------------------------------------------------- Warning - Before you begin this procedure, back up all file systems. _____________________________________________________________________ 1. Repair any mirrors that have errors. 2. Save /etc/vfstab for later use. 3. Clear any metatrans devices that may be used during the Solaris upgrade (for example, /usr, /var, and /opt). (If you are uncertain which metatrans devices should be cleared, clear all metatrans devices.) 4. Comment out file systems in /etc/vfstab mounted on metadevices that are not simple metadevices or simple mirrors. 5. Convert the remaining (simple) mirrors to one-way mirrors with the metadetach command. (Upgrade will be performed on a single submirror of each mirror. The other submirrors will be synced up with metattach after the upgrade.) 6. If root is mounted on a metadevice or mirror, set the root file system to be mounted on the underlying component of the metadevice or the underlying component of the remaining attached submirror. (Use the metaroot command to do this safely.) 7. Edit the /etc/vfstab file to change any file systems of swap devices still mounted on metadevices or mirrors after Step 3. 8. Remove symbolic links to the DiskSuite startup files so that it is no longer initialized at boot time. demo# rm /etc/rcS.d/S35SUNWmd.init /etc/rc2.d/S95SUNWmd.sync These links will be added back later by reinstalling DiskSuite after the Solaris upgrade. 9. Halt the machine and upgrade Solaris, then reboot the machine. 10. Reinstall DiskSuite, then reboot the machine. This will re-establish the symbolic links removed in Step 7. --------------------------------------------------------------------- Note - Make sure that the version of Solaris you are installing is compatible with DiskSuite 4.0. --------------------------------------------------------------------- 11. If root was originally mounted on a metadevice or mirror, set the root file system to be mounted back on the original metadevice or mirror. (Use the metaroot command to do this safely.) 12. Edit the /etc/vfstab file to change any file systems or swap devices edited in Step 6 to be mounted back on their original metadevice or mirror. 13. Edit the /etc/vfstab file to uncomment the file systems commented out in Step 3. 14. Reboot the machine to remount the file systems. 15. Use the metattach command to reattach and resync any submirrors broken off in Step 4. 16. Recreate the cleared metatrans devices. (See Chapter 6, "UFS Logging" from Solstice DiskSuite 4.0 Administration Guide for information on creating metatrans devices.)