Re: [Veritas-ha] upgrade VCS 5.1 with many zones Part II
Hello all! II. Using Solaris Live Upgrade from Veritas. It may seem to you rhat this is the only practical way to upgrade Veritas & Solaris. But this is not quite simple as you may think of. There are no problems with "high level steps". It is always right with them. But the devil is in details. 1. Local zone root is on zfs. Zone has some vxfs f.s. which are in zone configuration file. If you switch SG to second node all your vxfs f.s. are switched as well. It means that all veritas diskgroups are deported on the first node. After that this is not possible to mount ABE to patch it. Error messages look like this: ERROR: unable to mount zones. Error message follows. ERROR: Unable to mount zone in . could not verify fs /oracle: could not access /dev/vx/rdsk/mymtrdg/mymtrvol: No such file or directory zoneadm: zone mymtr-zone failed to verify ERROR: unmounting partially mounted boot environment file systems ERROR: cannot mount boot environment by name 2. Global zone is on ZFS as well. Vxlustart demands to use the whole second disk. This is natural for SVM. But ZFS uses snapshots , not mirrors to create ABE. If you want to use vxlustart in that case you must first split your zfs root pool (usually mirror ) into two different pools. I don't see any practical reason to do it. Because it takes much space and much time to create ABE. Summary: 1. Do not use vxfs inside zones. 2. Do not use vxlustart if you use ZFS on global root. What to do ? To be continued on Part III . From: Venkata Reddy Chappavarapu [mailto:venkatareddy_chappavar...@symantec.com] Sent: Monday, April 16, 2012 2:51 PM To: Цветков Павел Анатольевич Cc: veritas-ha@mailman.eng.auburn.edu; mamatec...@mamatec.com Subject: RE: [Veritas-ha] upgrade VCS 5.1 with many zones Hi Pavel, Here are the high level steps which you can use to perform live upgrade with zones to upgrade your cluster from 5.1RP1 to 6.0 with OS upgrade from Solaris 10 Update 9 to Solaris 10 Update 10. 1. Switch the SG to the second node in the cluster and Freeze the SG so that it does not failover during upgrade of first node. 2. Upgrade the SUNWlucfg SUNWluu SUNWlur packages to match the target OS version. 3. Set the ChkZFSMounts attribute of the Zpool resource to false. This is because during the LU Process, it creates snapshot of the zfs file system which are not mounted and the Zpool VCS resource monitor throws warning/erros when any ZFS file system is not mounted with ChkZFSMount attribute is set to True. 4. Begin the Live upgrade process on the first node using vxlustart. This is the process where the OS is upgraded in the ABE. 5. Unfreeze the Application SG. Switch the Application SG from the second node in the cluster to the first node in the cluster where the OS LU upgrade process has been completed. Freeze the APP SG again and begin the LU process on the second node. 6. Start the OS upgrade on ABE for second node using vxlustart 7. Once the OS upgrade process is completed for all the cluster nodes, upgrade the Veritas (SFHA) packages onto the ABE from 5.1RP1 to 6.0. Ensure that the ABE is mounted on the same location on all the nodes in the cluster. 8. Once the upgrade is completed on the ABE, check whether the Veritas packages are upgraded in the ABE on both nodes in the cluster. 9. Now complete the upgrade process by running the vxlufinish script on both (all) the nodes in the cluster. 10. Take a maintenance windows to shutdown all the running applications and the cluster and then reboot all the nodes in the cluster. The Nodes will now boot from the upgraded OS (Solaris 10 Update 10) disk partitions. Check the OS release version once the node comes up. 11. Check the Zone path of the zones after the upgrade. If they are changed to a new path, modify the zone path to reflect the old zone path. 12. Ensure that VCS is running and cluster membership has been formed. 13. Bring the required VCS resources to mount the Zone root on one of the system. Perform the below steps on the nodes where the resources to mount the zone root are brought online. a. Upgrade the local zone to bring it in sync with the global zone b. Ignore the AMF error if any c. Bring the zone into running state manually. d. The zone may not go into multi-user/multi-user-server state as the vxfsdlic service that has been added in SF 6.0 is in disabled state. Enable the vxfsdlic SMF service by logging into the zone. #svcadm enable vxfsldlic e. Probe the zone resource in the cluster and it will come online now. 14. Offline the zone and related resources. Perform step 13 on the other node(s) in the cluster. 15. Now bring the APP SG online on any node. 16. You may see some AMF rela
Re: [Veritas-ha] upgrade VCS 5.1 with many zones Part I
Hello all! Thank you, colleagues, for your suggestions. I have done the upgrade of SF HA 5.1 to RP2P2 HF3 as well as Solaris Update 9 to Update 10 last Sunday on four domains with more than 40 zones in total. This is was not quite simple but it is possible . I can give you my option of doing it but first of all just a few notes... I.No Solaris Live Upgrade. 1.Local zone root on shared storage on veritas volume (vxfs) How to upgrade? Zone must be in installed or running state to get upgraded. But installrp cannot run if it "sees" mounted veritas volume. 2. Local root is on zfs. Local Zone root on shared storage variant using VXFS as its local file . ZFS is under DMP control (dmp native support is on) Yes, this is not difficult to upgrade SFHA only. There are no many patches in the bundle. But if you must upgrade Solaris version? But if you have 16 local zones for example? it takes time to upgrade them all. Sure , you can perform the upgrade process in parallel (/etc/patch/pdo.conf num_proc =16). But if you get any problem with new patches (getting some new bugs) or if you get any error during upgrade (and this is quite possible) you won't be able to roll back quickly. This is because you must upgrade all nodes of your cluster after upgrading local zones on one node. Summary. 1. There is no phase upgrade in that case. This can be unsafe. 2. Installrp does not work if it sees dmp native support switched on. (with 5.1. SP1 RP1/RP2) 3. It can take much time if you have many zones and many patches. 4.If you have six nodes in cluster youmust switch all of your tasks to a single node. This is not always possible because of lack of resources (cpu, memory etc) 3. Zone root on local storage using VXFS If you have six nodes you must have 6 downtimes! This is unreal plan! This is not suitable. plus 1-2-3-4 from above. The only practical way to upgrade the cluster is to use Solaris Live Upgrade. To be continued in part II.. Regards, Pavel. From: Anish Vaidya [mailto:anish_vai...@symantec.com] Sent: Saturday, March 31, 2012 3:10 AM To: Anish Vaidya; Цветков Павел Анатольевич; Venkata Reddy Chappavarapu; mamatec...@mamatec.com <mailto:mamatec...@mamatec.com> Cc: veritas-ha@mailman.eng.auburn.edu <mailto:veritas-ha@mailman.eng.auburn.edu> Subject: RE: [Veritas-ha] upgrade VCS 5.1 with many zones Pavel, We strongly encourage using CPI installer for upgrading the stack in an SFHA cluster involving zones. Anyway, if you want to know the manual procedure, here is the high level procedure. 1. Zone root on shared storage using VXFS You need to patch the zone only once. a. Move all service groups containing Zone resource to one system (preferably). b. Bring down all the APP resources on top of the Zone. Keep the Zone running. c. Stop VCS (hastop -local -force). Upgrade the SFHA packages. At this time, SFHA packages are upgraded in the global and local zones. You may have to reboot this node as the VXFS driver loaded in kernel is still of the lower version. d. Upgrade the other node in the cluster after stopping VCS (using "hastop -local -force"). Upgrade the SFHA packages. Please note, no zone is installed/running on this node. e. Start VCS on 2nd node. Bring up the relevant Zone service groups. 2. Zone root on local storage using VXFS You need to perform the procedure similar to 1a, 1b and 1c on all nodes in the cluster. This is because, each individual zone needs to be patched on all nodes in the cluster. Hope this helps. Regards, Anish ___ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
Re: [Veritas-ha] upgrade VCS 5.1 with many zones
Hi Pavel, Here are the high level steps which you can use to perform live upgrade with zones to upgrade your cluster from 5.1RP1 to 6.0 with OS upgrade from Solaris 10 Update 9 to Solaris 10 Update 10. 1. Switch the SG to the second node in the cluster and Freeze the SG so that it does not failover during upgrade of first node. 2. Upgrade the SUNWlucfg SUNWluu SUNWlur packages to match the target OS version. 3. Set the ChkZFSMounts attribute of the Zpool resource to false. This is because during the LU Process, it creates snapshot of the zfs file system which are not mounted and the Zpool VCS resource monitor throws warning/erros when any ZFS file system is not mounted with ChkZFSMount attribute is set to True. 4. Begin the Live upgrade process on the first node using vxlustart. This is the process where the OS is upgraded in the ABE. 5. Unfreeze the Application SG. Switch the Application SG from the second node in the cluster to the first node in the cluster where the OS LU upgrade process has been completed. Freeze the APP SG again and begin the LU process on the second node. 6. Start the OS upgrade on ABE for second node using vxlustart 7. Once the OS upgrade process is completed for all the cluster nodes, upgrade the Veritas (SFHA) packages onto the ABE from 5.1RP1 to 6.0. Ensure that the ABE is mounted on the same location on all the nodes in the cluster. 8. Once the upgrade is completed on the ABE, check whether the Veritas packages are upgraded in the ABE on both nodes in the cluster. 9. Now complete the upgrade process by running the vxlufinish script on both (all) the nodes in the cluster. 10. Take a maintenance windows to shutdown all the running applications and the cluster and then reboot all the nodes in the cluster. The Nodes will now boot from the upgraded OS (Solaris 10 Update 10) disk partitions. Check the OS release version once the node comes up. 11. Check the Zone path of the zones after the upgrade. If they are changed to a new path, modify the zone path to reflect the old zone path. 12. Ensure that VCS is running and cluster membership has been formed. 13. Bring the required VCS resources to mount the Zone root on one of the system. Perform the below steps on the nodes where the resources to mount the zone root are brought online. a. Upgrade the local zone to bring it in sync with the global zone b. Ignore the AMF error if any c. Bring the zone into running state manually. d. The zone may not go into multi-user/multi-user-server state as the vxfsdlic service that has been added in SF 6.0 is in disabled state. Enable the vxfsdlic SMF service by logging into the zone. #svcadm enable vxfsldlic e. Probe the zone resource in the cluster and it will come online now. 14. Offline the zone and related resources. Perform step 13 on the other node(s) in the cluster. 15. Now bring the APP SG online on any node. 16. You may see some AMF related messages logged into the logs. You can safely ignore them. Thanks & Regards, Venkata Reddy Chappavarapu From: veritas-ha-boun...@mailman.eng.auburn.edu [mailto:veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of p.tsvet...@inform.gazprom.ru Sent: Friday, March 30, 2012 10:57 AM To: Venkata Reddy Chappavarapu; mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Any kind of. Please, give any practical way to upgrade Solaris and/or Veritas when you have zones in service groups. From: Venkata Reddy Chappavarapu [mailto:venkatareddy_chappavar...@symantec.com] Sent: Friday, March 30, 2012 9:22 AM To: Цветков Павел Анатольевич; mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: RE: [Veritas-ha] upgrade VCS 5.1 with many zones Hi Pavel, Could you let me know which upgrade method you want to use? Phased upgrade or Live upgrade? The process to upgrade depends on the method you would use for upgrade. Thanks & Regards, Venkata Reddy Chappavarapu From: veritas-ha-boun...@mailman.eng.auburn.edu [mailto:veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of p.tsvet...@inform.gazprom.ru Sent: Friday, March 30, 2012 10:24 AM To: Venkata Reddy Chappavarapu; mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hello Venkata! You say "you can upgrade the zone from one node keeping it in running state". How can I keep the zone in running state if I must do a failover of a service group to another node to perform phase upgrade? How can I upgrade my OS on a giving node if some of my zones are in running state (service groups are online) but some other zones a in "configured" state (services groups are offline on the node)? How can I upgrade my zone if it has shared resources online on another node? How can I use Solaris Live Upgrade wi
Re: [Veritas-ha] upgrade VCS 5.1 with many zones
Pavel, We strongly encourage using CPI installer for upgrading the stack in an SFHA cluster involving zones. Anyway, if you want to know the manual procedure, here is the high level procedure. 1. Zone root on shared storage using VXFS You need to patch the zone only once. a. Move all service groups containing Zone resource to one system (preferably). b. Bring down all the APP resources on top of the Zone. Keep the Zone running. c. Stop VCS (hastop -local -force). Upgrade the SFHA packages. At this time, SFHA packages are upgraded in the global and local zones. You may have to reboot this node as the VXFS driver loaded in kernel is still of the lower version. d. Upgrade the other node in the cluster after stopping VCS (using "hastop -local -force"). Upgrade the SFHA packages. Please note, no zone is installed/running on this node. e. Start VCS on 2nd node. Bring up the relevant Zone service groups. 2. Zone root on local storage using VXFS You need to perform the procedure similar to 1a, 1b and 1c on all nodes in the cluster. This is because, each individual zone needs to be patched on all nodes in the cluster. Hope this helps. Regards, Anish From: veritas-ha-boun...@mailman.eng.auburn.edu [mailto:veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of p.tsvet...@inform.gazprom.ru Sent: Thursday, March 29, 2012 10:27 PM To: Venkata Reddy Chappavarapu; mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Any kind of. Please, give any practical way to upgrade Solaris and/or Veritas when you have zones in service groups. From: Venkata Reddy Chappavarapu [mailto:venkatareddy_chappavar...@symantec.com] Sent: Friday, March 30, 2012 9:22 AM To: Цветков Павел Анатольевич; mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: RE: [Veritas-ha] upgrade VCS 5.1 with many zones Hi Pavel, Could you let me know which upgrade method you want to use? Phased upgrade or Live upgrade? The process to upgrade depends on the method you would use for upgrade. Thanks & Regards, Venkata Reddy Chappavarapu From: veritas-ha-boun...@mailman.eng.auburn.edu [mailto:veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of p.tsvet...@inform.gazprom.ru Sent: Friday, March 30, 2012 10:24 AM To: Venkata Reddy Chappavarapu; mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hello Venkata! You say "you can upgrade the zone from one node keeping it in running state". How can I keep the zone in running state if I must do a failover of a service group to another node to perform phase upgrade? How can I upgrade my OS on a giving node if some of my zones are in running state (service groups are online) but some other zones a in "configured" state (services groups are offline on the node)? How can I upgrade my zone if it has shared resources online on another node? How can I use Solaris Live Upgrade with Storage Foundation HA? Is it possible or not? I tried to explain the problem and give the resolution the way I see it. I wish Symantec could give all the required explanations... Regards, Pavel From: Venkata Reddy Chappavarapu [mailto:venkatareddy_chappavar...@symantec.com] Sent: Wednesday, March 28, 2012 11:08 AM To: Цветков Павел Анатольевич; mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: RE: [Veritas-ha] upgrade VCS 5.1 with many zones Hi Fred, While upgrading the SFHA you have to keep the zones in the running state and all the applications running inside the zone should be stopped. If you have a zone with root on shared storage, you can upgrade the zone from one node keeping it in running state and in configured state on all other nodes. All this information is documented in the installation guide for both SFHA and VCS products. Please feel free to contact us if you are facing any specific issues while upgrading the product to 5.1SP1 or 6.0. Thanks & Regards, Venkata Reddy Chappavarapu From: veritas-ha-boun...@mailman.eng.auburn.edu<mailto:veritas-ha-boun...@mailman.eng.auburn.edu> [mailto:veritas-ha-boun...@mailman.eng.auburn.edu]<mailto:[mailto:veritas-ha-boun...@mailman.eng.auburn.edu]> On Behalf Of p.tsvet...@inform.gazprom.ru<mailto:p.tsvet...@inform.gazprom.ru> Sent: Tuesday, March 27, 2012 5:39 PM To: mamatec...@mamatec.com<mailto:mamatec...@mamatec.com> Cc: veritas-ha@mailman.eng.auburn.edu<mailto:veritas-ha@mailman.eng.auburn.edu> Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hi! Hi Fred! Just a few questions: 1. Are your mount resources monitored from local zone or global zone? 2. Do you have them in local zone xml file or you mount them directly from global zone or using loopback mounts? 3. Do you plan to offline your local zone or your localzones are running in
Re: [Veritas-ha] upgrade VCS 5.1 with many zones
Any kind of. Please, give any practical way to upgrade Solaris and/or Veritas when you have zones in service groups. From: Venkata Reddy Chappavarapu [mailto:venkatareddy_chappavar...@symantec.com] Sent: Friday, March 30, 2012 9:22 AM To: Цветков Павел Анатольевич; mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: RE: [Veritas-ha] upgrade VCS 5.1 with many zones Hi Pavel, Could you let me know which upgrade method you want to use? Phased upgrade or Live upgrade? The process to upgrade depends on the method you would use for upgrade. Thanks & Regards, Venkata Reddy Chappavarapu From: veritas-ha-boun...@mailman.eng.auburn.edu [mailto:veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of p.tsvet...@inform.gazprom.ru Sent: Friday, March 30, 2012 10:24 AM To: Venkata Reddy Chappavarapu; mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hello Venkata! You say "you can upgrade the zone from one node keeping it in running state". How can I keep the zone in running state if I must do a failover of a service group to another node to perform phase upgrade? How can I upgrade my OS on a giving node if some of my zones are in running state (service groups are online) but some other zones a in "configured" state (services groups are offline on the node)? How can I upgrade my zone if it has shared resources online on another node? How can I use Solaris Live Upgrade with Storage Foundation HA? Is it possible or not? I tried to explain the problem and give the resolution the way I see it. I wish Symantec could give all the required explanations... Regards, Pavel From: Venkata Reddy Chappavarapu [mailto:venkatareddy_chappavar...@symantec.com] Sent: Wednesday, March 28, 2012 11:08 AM To: Цветков Павел Анатольевич; mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: RE: [Veritas-ha] upgrade VCS 5.1 with many zones Hi Fred, While upgrading the SFHA you have to keep the zones in the running state and all the applications running inside the zone should be stopped. If you have a zone with root on shared storage, you can upgrade the zone from one node keeping it in running state and in configured state on all other nodes. All this information is documented in the installation guide for both SFHA and VCS products. Please feel free to contact us if you are facing any specific issues while upgrading the product to 5.1SP1 or 6.0. Thanks & Regards, Venkata Reddy Chappavarapu From: veritas-ha-boun...@mailman.eng.auburn.edu [mailto:veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of p.tsvet...@inform.gazprom.ru Sent: Tuesday, March 27, 2012 5:39 PM To: mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hi! Hi Fred! Just a few questions: 1. Are your mount resources monitored from local zone or global zone? 2. Do you have them in local zone xml file or you mount them directly from global zone or using loopback mounts? 3. Do you plan to offline your local zone or your localzones are running in parallel on two nodes? Regards, Pavel Hi, all Ok ...so I'm very familiar with live upgrade but, my problem is how to upgrade Veritas Cluster when all zones are shares with failover and every zone has multiple vxfs file systems for example: Mount mount_oracleCCPsapdata1 Critical = 0 MountPoint = "/oracle/CCP/sapdata1 BlockDevice = " /dev/vx/dsk/oraccp_dg/oraccp_data1 FSType = vxfs FsckOpt = "-y " Zpool root_CCP ( Critical = 0 PoolName = root_CCP AltRootPath= " / " ZoneResname = zone_root_CCP If I put the application service group offline and only zone_root_CCP is online, it'a good idea? Thanks Fred 2012/3/27 Hi! Something more to it. It is important to note, that vxfs patch must be installed in local zones. It means that local zones must be in running or booted state. If you make failover a zone to another node before upgrade than your local zone cannot be in running state on the first node. It can be in installed state. But when you start patching your local zone on the first node , the zone must change its state from "installed" to "booted" to be patched. There is no problem if the local zone does not have in its configuration any veritas volumes and file systems which have been started up on the second node. If so your local zone on the first node cannot "see" its resources and cannot go from "installed" into "booted" state to be patched up. That is the reason why "failover resources" must not be present in local zone configuration. They must be mounted from global zone directly. Regards, Pavel
Re: [Veritas-ha] upgrade VCS 5.1 with many zones
Hi Pavel, Could you let me know which upgrade method you want to use? Phased upgrade or Live upgrade? The process to upgrade depends on the method you would use for upgrade. Thanks & Regards, Venkata Reddy Chappavarapu From: veritas-ha-boun...@mailman.eng.auburn.edu [mailto:veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of p.tsvet...@inform.gazprom.ru Sent: Friday, March 30, 2012 10:24 AM To: Venkata Reddy Chappavarapu; mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hello Venkata! You say "you can upgrade the zone from one node keeping it in running state". How can I keep the zone in running state if I must do a failover of a service group to another node to perform phase upgrade? How can I upgrade my OS on a giving node if some of my zones are in running state (service groups are online) but some other zones a in "configured" state (services groups are offline on the node)? How can I upgrade my zone if it has shared resources online on another node? How can I use Solaris Live Upgrade with Storage Foundation HA? Is it possible or not? I tried to explain the problem and give the resolution the way I see it. I wish Symantec could give all the required explanations... Regards, Pavel From: Venkata Reddy Chappavarapu [mailto:venkatareddy_chappavar...@symantec.com] Sent: Wednesday, March 28, 2012 11:08 AM To: Цветков Павел Анатольевич; mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: RE: [Veritas-ha] upgrade VCS 5.1 with many zones Hi Fred, While upgrading the SFHA you have to keep the zones in the running state and all the applications running inside the zone should be stopped. If you have a zone with root on shared storage, you can upgrade the zone from one node keeping it in running state and in configured state on all other nodes. All this information is documented in the installation guide for both SFHA and VCS products. Please feel free to contact us if you are facing any specific issues while upgrading the product to 5.1SP1 or 6.0. Thanks & Regards, Venkata Reddy Chappavarapu From: veritas-ha-boun...@mailman.eng.auburn.edu<mailto:veritas-ha-boun...@mailman.eng.auburn.edu> [mailto:veritas-ha-boun...@mailman.eng.auburn.edu]<mailto:[mailto:veritas-ha-boun...@mailman.eng.auburn.edu]> On Behalf Of p.tsvet...@inform.gazprom.ru<mailto:p.tsvet...@inform.gazprom.ru> Sent: Tuesday, March 27, 2012 5:39 PM To: mamatec...@mamatec.com<mailto:mamatec...@mamatec.com> Cc: veritas-ha@mailman.eng.auburn.edu<mailto:veritas-ha@mailman.eng.auburn.edu> Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hi! Hi Fred! Just a few questions: 1. Are your mount resources monitored from local zone or global zone? 2. Do you have them in local zone xml file or you mount them directly from global zone or using loopback mounts? 3. Do you plan to offline your local zone or your localzones are running in parallel on two nodes? Regards, Pavel Hi, all Ok ...so I'm very familiar with live upgrade but, my problem is how to upgrade Veritas Cluster when all zones are shares with failover and every zone has multiple vxfs file systems for example: Mount mount_oracleCCPsapdata1 Critical = 0 MountPoint = "/oracle/CCP/sapdata1 BlockDevice = " /dev/vx/dsk/oraccp_dg/oraccp_data1 FSType = vxfs FsckOpt = "-y " Zpool root_CCP ( Critical = 0 PoolName = root_CCP AltRootPath= " / " ZoneResname = zone_root_CCP If I put the application service group offline and only zone_root_CCP is online, it'a good idea? Thanks Fred 2012/3/27 mailto:p.tsvet...@inform.gazprom.ru>> Hi! Something more to it. It is important to note, that vxfs patch must be installed in local zones. It means that local zones must be in running or booted state. If you make failover a zone to another node before upgrade than your local zone cannot be in running state on the first node. It can be in installed state. But when you start patching your local zone on the first node , the zone must change its state from "installed" to "booted" to be patched. There is no problem if the local zone does not have in its configuration any veritas volumes and file systems which have been started up on the second node. If so your local zone on the first node cannot "see" its resources and cannot go from "installed" into "booted" state to be patched up. That is the reason why "failover resources" must not be present in local zone configuration. They must be mounted from global zone directly. Regards, Pavel From: Fred [mailto:mamatec...@mamatec.com<mailto:mamatec...@mamatec.com>] Sent: Tuesday, March 27, 2012 12:38 AM To: Цветков Павел Анатольевич Cc: colin.y...@gmail.com<mailto:colin.y..
Re: [Veritas-ha] upgrade VCS 5.1 with many zones
Hello Venkata! You say "you can upgrade the zone from one node keeping it in running state". How can I keep the zone in running state if I must do a failover of a service group to another node to perform phase upgrade? How can I upgrade my OS on a giving node if some of my zones are in running state (service groups are online) but some other zones a in "configured" state (services groups are offline on the node)? How can I upgrade my zone if it has shared resources online on another node? How can I use Solaris Live Upgrade with Storage Foundation HA? Is it possible or not? I tried to explain the problem and give the resolution the way I see it. I wish Symantec could give all the required explanations... Regards, Pavel From: Venkata Reddy Chappavarapu [mailto:venkatareddy_chappavar...@symantec.com] Sent: Wednesday, March 28, 2012 11:08 AM To: Цветков Павел Анатольевич; mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: RE: [Veritas-ha] upgrade VCS 5.1 with many zones Hi Fred, While upgrading the SFHA you have to keep the zones in the running state and all the applications running inside the zone should be stopped. If you have a zone with root on shared storage, you can upgrade the zone from one node keeping it in running state and in configured state on all other nodes. All this information is documented in the installation guide for both SFHA and VCS products. Please feel free to contact us if you are facing any specific issues while upgrading the product to 5.1SP1 or 6.0. Thanks & Regards, Venkata Reddy Chappavarapu From: veritas-ha-boun...@mailman.eng.auburn.edu [mailto:veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of p.tsvet...@inform.gazprom.ru Sent: Tuesday, March 27, 2012 5:39 PM To: mamatec...@mamatec.com Cc: veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hi! Hi Fred! Just a few questions: 1. Are your mount resources monitored from local zone or global zone? 2. Do you have them in local zone xml file or you mount them directly from global zone or using loopback mounts? 3. Do you plan to offline your local zone or your localzones are running in parallel on two nodes? Regards, Pavel Hi, all Ok ...so I'm very familiar with live upgrade but, my problem is how to upgrade Veritas Cluster when all zones are shares with failover and every zone has multiple vxfs file systems for example: Mount mount_oracleCCPsapdata1 Critical = 0 MountPoint = "/oracle/CCP/sapdata1 BlockDevice = " /dev/vx/dsk/oraccp_dg/oraccp_data1 FSType = vxfs FsckOpt = "-y " Zpool root_CCP ( Critical = 0 PoolName = root_CCP AltRootPath= " / " ZoneResname = zone_root_CCP If I put the application service group offline and only zone_root_CCP is online, it'a good idea? Thanks Fred 2012/3/27 Hi! Something more to it. It is important to note, that vxfs patch must be installed in local zones. It means that local zones must be in running or booted state. If you make failover a zone to another node before upgrade than your local zone cannot be in running state on the first node. It can be in installed state. But when you start patching your local zone on the first node , the zone must change its state from "installed" to "booted" to be patched. There is no problem if the local zone does not have in its configuration any veritas volumes and file systems which have been started up on the second node. If so your local zone on the first node cannot "see" its resources and cannot go from "installed" into "booted" state to be patched up. That is the reason why "failover resources" must not be present in local zone configuration. They must be mounted from global zone directly. Regards, Pavel From: Fred [mailto:mamatec...@mamatec.com] Sent: Tuesday, March 27, 2012 12:38 AM To: Цветков Павел Анатольевич Cc: colin.y...@gmail.com; veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hi all my SF-HA origin is 5.1rp1 for Solaris and I should to upgrade to 5.1 SP1 or 6.0, NOT upgrade Solaris but only SFHA. What about rolling upgrade, it's possible doing on two node cluster? How to? Thanks Fred 2012/3/26 Hello all! What about using Solaris LiveUpgrade ? It is possible to use it with VCS. There are some tricks though ... You should keep in mind the following. 1. Do not use zpool cluster resource if you don't failover zpools. This is because of the fact, that Offline entry point for zpool does zpool export. This is a not a good thing for "init 6" which must be run after activating New Boot Environment. If you have questions about this point just ask me. 2. main.cf t
Re: [Veritas-ha] upgrade VCS 5.1 with many zones
Hi Fred, While upgrading the SFHA you have to keep the zones in the running state and all the applications running inside the zone should be stopped. If you have a zone with root on shared storage, you can upgrade the zone from one node keeping it in running state and in configured state on all other nodes. All this information is documented in the installation guide for both SFHA and VCS products. Please feel free to contact us if you are facing any specific issues while upgrading the product to 5.1SP1 or 6.0. Thanks & Regards, Venkata Reddy Chappavarapu From: veritas-ha-boun...@mailman.eng.auburn.edu<mailto:veritas-ha-boun...@mailman.eng.auburn.edu> [mailto:veritas-ha-boun...@mailman.eng.auburn.edu]<mailto:[mailto:veritas-ha-boun...@mailman.eng.auburn.edu]> On Behalf Of p.tsvet...@inform.gazprom.ru<mailto:p.tsvet...@inform.gazprom.ru> Sent: Tuesday, March 27, 2012 5:39 PM To: mamatec...@mamatec.com<mailto:mamatec...@mamatec.com> Cc: veritas-ha@mailman.eng.auburn.edu<mailto:veritas-ha@mailman.eng.auburn.edu> Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hi! Hi Fred! Just a few questions: 1. Are your mount resources monitored from local zone or global zone? 2. Do you have them in local zone xml file or you mount them directly from global zone or using loopback mounts? 3. Do you plan to offline your local zone or your localzones are running in parallel on two nodes? Regards, Pavel Hi, all Ok ...so I'm very familiar with live upgrade but, my problem is how to upgrade Veritas Cluster when all zones are shares with failover and every zone has multiple vxfs file systems for example: Mount mount_oracleCCPsapdata1 Critical = 0 MountPoint = "/oracle/CCP/sapdata1 BlockDevice = " /dev/vx/dsk/oraccp_dg/oraccp_data1 FSType = vxfs FsckOpt = "-y " Zpool root_CCP ( Critical = 0 PoolName = root_CCP AltRootPath= " / " ZoneResname = zone_root_CCP If I put the application service group offline and only zone_root_CCP is online, it'a good idea? Thanks Fred 2012/3/27 mailto:p.tsvet...@inform.gazprom.ru>> Hi! Something more to it. It is important to note, that vxfs patch must be installed in local zones. It means that local zones must be in running or booted state. If you make failover a zone to another node before upgrade than your local zone cannot be in running state on the first node. It can be in installed state. But when you start patching your local zone on the first node , the zone must change its state from "installed" to "booted" to be patched. There is no problem if the local zone does not have in its configuration any veritas volumes and file systems which have been started up on the second node. If so your local zone on the first node cannot "see" its resources and cannot go from "installed" into "booted" state to be patched up. That is the reason why "failover resources" must not be present in local zone configuration. They must be mounted from global zone directly. Regards, Pavel From: Fred [mailto:mamatec...@mamatec.com<mailto:mamatec...@mamatec.com>] Sent: Tuesday, March 27, 2012 12:38 AM To: Цветков Павел Анатольевич Cc: colin.y...@gmail.com<mailto:colin.y...@gmail.com>; veritas-ha@mailman.eng.auburn.edu<mailto:veritas-ha@mailman.eng.auburn.edu> Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hi all my SF-HA origin is 5.1rp1 for Solaris and I should to upgrade to 5.1 SP1 or 6.0, NOT upgrade Solaris but only SFHA. What about rolling upgrade, it's possible doing on two node cluster? How to? Thanks Fred 2012/3/26 mailto:p.tsvet...@inform.gazprom.ru>> Hello all! What about using Solaris LiveUpgrade ? It is possible to use it with VCS. There are some tricks though ... You should keep in mind the following. 1. Do not use zpool cluster resource if you don't failover zpools. This is because of the fact, that Offline entry point for zpool does zpool export. This is a not a good thing for "init 6" which must be run after activating New Boot Environment. If you have questions about this point just ask me. 2. main.cf<http://main.cf> types.cf<http://types.cf> must be in synclist file. 3. zfs file systems must NOT have mountpoint=legacy. Mountpoint must stay default. 4. Zone resources . Check DetachZone = false (Zone must stay in installed state while it is offlined. This is required to create ABE for zones as well as to patch zones). ForceAttach must be true if you use Veritas ODM for Oracle DB. 5. If you have vxfs mounted inside zones mount them from outside. It means that vxfs file systems must not be present in zone configuration files , they must be mounted with mount command from global zone. 6. You should have the following clus
Re: [Veritas-ha] upgrade VCS 5.1 with many zones
Hi! Hi Fred! Just a few questions: 1. Are your mount resources monitored from local zone or global zone? 2. Do you have them in local zone xml file or you mount them directly from global zone or using loopback mounts? 3. Do you plan to offline your local zone or your localzones are running in parallel on two nodes? Regards, Pavel Hi, all Ok ...so I'm very familiar with live upgrade but, my problem is how to upgrade Veritas Cluster when all zones are shares with failover and every zone has multiple vxfs file systems for example: Mount mount_oracleCCPsapdata1 Critical = 0 MountPoint = "/oracle/CCP/sapdata1 BlockDevice = " /dev/vx/dsk/oraccp_dg/oraccp_data1 FSType = vxfs FsckOpt = "-y " Zpool root_CCP ( Critical = 0 PoolName = root_CCP AltRootPath= " / " ZoneResname = zone_root_CCP If I put the application service group offline and only zone_root_CCP is online, it'a good idea? Thanks Fred 2012/3/27 Hi! Something more to it. It is important to note, that vxfs patch must be installed in local zones. It means that local zones must be in running or booted state. If you make failover a zone to another node before upgrade than your local zone cannot be in running state on the first node. It can be in installed state. But when you start patching your local zone on the first node , the zone must change its state from "installed" to "booted" to be patched. There is no problem if the local zone does not have in its configuration any veritas volumes and file systems which have been started up on the second node. If so your local zone on the first node cannot "see" its resources and cannot go from "installed" into "booted" state to be patched up. That is the reason why "failover resources" must not be present in local zone configuration. They must be mounted from global zone directly. Regards, Pavel From: Fred [mailto:mamatec...@mamatec.com] Sent: Tuesday, March 27, 2012 12:38 AM To: Цветков Павел Анатольевич Cc: colin.y...@gmail.com; veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hi all my SF-HA origin is 5.1rp1 for Solaris and I should to upgrade to 5.1 SP1 or 6.0, NOT upgrade Solaris but only SFHA. What about rolling upgrade, it's possible doing on two node cluster? How to? Thanks Fred 2012/3/26 Hello all! What about using Solaris LiveUpgrade ? It is possible to use it with VCS. There are some tricks though ... You should keep in mind the following. 1. Do not use zpool cluster resource if you don't failover zpools. This is because of the fact, that Offline entry point for zpool does zpool export. This is a not a good thing for "init 6" which must be run after activating New Boot Environment. If you have questions about this point just ask me. 2. main.cf types.cf must be in synclist file. 3. zfs file systems must NOT have mountpoint=legacy. Mountpoint must stay default. 4. Zone resources . Check DetachZone = false (Zone must stay in installed state while it is offlined. This is required to create ABE for zones as well as to patch zones). ForceAttach must be true if you use Veritas ODM for Oracle DB. 5. If you have vxfs mounted inside zones mount them from outside. It means that vxfs file systems must not be present in zone configuration files , they must be mounted with mount command from global zone. 6. You should have the following cluster configuration: SapTaskGroup (monitored from local zone - sap & oracle resources without mount points for sap and oracle f.s.) |online local firm | Mount_SapGroup (monitored from global zone - sap & oracle mount points on vxfs f.s. - mounted from global zone ) |online local HARD | Zone_SapGroup ( only zone resource itself - monitored from local zone) If you have dialog instances than you can have them as parallel service groups in local zones. This is about all. After that you can do the following: 1. lucreate -n MyNewBoot 2. Upgrade Solaris version with command luupgrade -u -n MyNewBoot -s /mnt/iso -k /var/tmp/sysidcfg 2. Install Recommended Patch Cluster on MyNewBOOT with all zones in parallel (check /etc/patches/pdo.conf num_proc > 1) /installcluster -B MyNewBoot --s10patchset 3. install veritas patches for i in `cat /sample/patch_order` do luupgrade -t -n MyNewBoot -s /sample $i done 4. Luactivate MyNewBoot 5. init 6 This is not easy to do everything without errors. Please, create your test environment and see first. Good luck! Pavel -Original Message- From: veritas-ha-boun...@mailman.eng.auburn.edu [mai
Re: [Veritas-ha] upgrade VCS 5.1 with many zones
Hi, all Ok ...so I'm very familiar with live upgrade but, my problem is how to upgrade Veritas Cluster when all zones are shares with failover and every zone has multiple vxfs file systems for example: Mount mount_oracleCCPsapdata1 Critical = 0 MountPoint = "/oracle/CCP/sapdata1 BlockDevice = " /dev/vx/dsk/oraccp_dg/oraccp_data1 FSType = vxfs FsckOpt = "-y " Zpool root_CCP ( Critical = 0 PoolName = root_CCP AltRootPath= " / " ZoneResname = zone_root_CCP If I put the application service group offline and only zone_root_CCP is online, it'a good idea? Thanks Fred 2012/3/27 > Hi! > > Something more to it. > > ** ** > > It is important to note, that vxfs patch must be installed in local > zones. It means that local zones must be in running or booted state. > > If you make failover a zone to another node before upgrade than your local > zone cannot be in running state on the first node. It can be in installed > state. > > But when you start patching your local zone on the first node , the zone > must change its state from "installed" to "booted" to be patched. There is > no problem if the local zone *does not have* in its configuration any > veritas volumes and file systems *which have been started up on the > second node*. If so your local zone on the first node cannot "see" its > resources and cannot go from "installed" into "booted" state to be > patched up. That is the reason why "failover resources" must not be present > in local zone configuration. They must be mounted from global zone > directly. > > ** ** > > ** ** > > Regards, Pavel > > ** ** > > *From:* Fred [mailto:mamatec...@mamatec.com] > *Sent:* Tuesday, March 27, 2012 12:38 AM > *To:* Цветков Павел Анатольевич > *Cc:* colin.y...@gmail.com; veritas-ha@mailman.eng.auburn.edu > > *Subject:* Re: [Veritas-ha] upgrade VCS 5.1 with many zones > > ** ** > > Hi all my SF-HA origin is 5.1rp1 for Solaris and I should to upgrade to > 5.1 SP1 or 6.0, NOT upgrade Solaris but only SFHA. > What about rolling upgrade, it's possible doing on two node cluster? How > to? > > Thanks > > Fred > > 2012/3/26 > > Hello all! > > What about using Solaris LiveUpgrade ? It is possible to use it with VCS. > There are some tricks though ... > > You should keep in mind the following. > > 1. Do not use zpool cluster resource if you don't failover zpools. This is > because of the fact, that > Offline entry point for zpool does zpool export. This is a not a good > thing for "init 6" which must be run after activating New Boot Environment. > If you have questions about this point just ask me. > > 2. main.cf types.cf must be in synclist file. > 3. zfs file systems must NOT have mountpoint=legacy. Mountpoint must stay > default. > 4. Zone resources . Check DetachZone = false (Zone must stay in installed > state while it is offlined. This is required to create ABE for zones as > well as to patch zones). ForceAttach must be true if you use Veritas ODM > for Oracle DB. > 5. If you have vxfs mounted inside zones mount them from outside. It > means that vxfs file systems must not be present in zone configuration > files , they must be mounted with mount command from global zone. > 6. You should have the following cluster configuration: > > > > > SapTaskGroup (monitored from local zone - sap & oracle > resources without mount points for sap and oracle f.s.) > > |online local firm > | > > >Mount_SapGroup (monitored from global zone - sap & > oracle mount points on vxfs f.s. - mounted from global zone ) > > |online local HARD > | > >Zone_SapGroup ( only zone resource itself - monitored > from local zone) > > > If you have dialog instances than you can have them as parallel service > groups in local zones. > > > > This is about all. After that you can do the following: > > 1. lucreate -n MyNewBoot > 2. Upgrade Solaris version with command > luupgrade -u -n MyNewBoot -s /mnt/iso -k /var/tmp/sysidcfg > > > 2. Install Recommended Patch Cluster on MyNewBOOT with all zones in > parallel (check /etc/patches/pdo.conf num_proc > 1) > >/installcluster -B MyNewBoot --s10patchset > > 3. install veritas patches > > for i in `cat /sample/patch_order` > > do > luupgrade -t -n MyNewBoot -s /sample $i > done > > 4. Luactivate MyNe
Re: [Veritas-ha] upgrade VCS 5.1 with many zones
Hi! Something more to it. It is important to note, that vxfs patch must be installed in local zones. It means that local zones must be in running or booted state. If you make failover a zone to another node before upgrade than your local zone cannot be in running state on the first node. It can be in installed state. But when you start patching your local zone on the first node , the zone must change its state from "installed" to "booted" to be patched. There is no problem if the local zone does not have in its configuration any veritas volumes and file systems which have been started up on the second node. If so your local zone on the first node cannot "see" its resources and cannot go from "installed" into "booted" state to be patched up. That is the reason why "failover resources" must not be present in local zone configuration. They must be mounted from global zone directly. Regards, Pavel From: Fred [mailto:mamatec...@mamatec.com] Sent: Tuesday, March 27, 2012 12:38 AM To: Цветков Павел Анатольевич Cc: colin.y...@gmail.com; veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hi all my SF-HA origin is 5.1rp1 for Solaris and I should to upgrade to 5.1 SP1 or 6.0, NOT upgrade Solaris but only SFHA. What about rolling upgrade, it's possible doing on two node cluster? How to? Thanks Fred 2012/3/26 Hello all! What about using Solaris LiveUpgrade ? It is possible to use it with VCS. There are some tricks though ... You should keep in mind the following. 1. Do not use zpool cluster resource if you don't failover zpools. This is because of the fact, that Offline entry point for zpool does zpool export. This is a not a good thing for "init 6" which must be run after activating New Boot Environment. If you have questions about this point just ask me. 2. main.cf types.cf must be in synclist file. 3. zfs file systems must NOT have mountpoint=legacy. Mountpoint must stay default. 4. Zone resources . Check DetachZone = false (Zone must stay in installed state while it is offlined. This is required to create ABE for zones as well as to patch zones). ForceAttach must be true if you use Veritas ODM for Oracle DB. 5. If you have vxfs mounted inside zones mount them from outside. It means that vxfs file systems must not be present in zone configuration files , they must be mounted with mount command from global zone. 6. You should have the following cluster configuration: SapTaskGroup (monitored from local zone - sap & oracle resources without mount points for sap and oracle f.s.) |online local firm | Mount_SapGroup (monitored from global zone - sap & oracle mount points on vxfs f.s. - mounted from global zone ) |online local HARD | Zone_SapGroup ( only zone resource itself - monitored from local zone) If you have dialog instances than you can have them as parallel service groups in local zones. This is about all. After that you can do the following: 1. lucreate -n MyNewBoot 2. Upgrade Solaris version with command luupgrade -u -n MyNewBoot -s /mnt/iso -k /var/tmp/sysidcfg 2. Install Recommended Patch Cluster on MyNewBOOT with all zones in parallel (check /etc/patches/pdo.conf num_proc > 1) /installcluster -B MyNewBoot --s10patchset 3. install veritas patches for i in `cat /sample/patch_order` do luupgrade -t -n MyNewBoot -s /sample $i done 4. Luactivate MyNewBoot 5. init 6 This is not easy to do everything without errors. Please, create your test environment and see first. Good luck! Pavel -Original Message- From: veritas-ha-boun...@mailman.eng.auburn.edu [mailto:veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of Colin Yemm Sent: Monday, March 26, 2012 5:13 AM To: Fred Cc: veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Short version: Um, something is wrong. Once you figure out what VCS version you are running, you should be able to do a rolling upgrade (node-by-node) if it is 5.1. I haven't been able to find a definitive statement about 5.0 (except how to upgrade from 5.0MP3RP2 to 5.1SP1), but I seem to remember it can be done, but is a somewhat manual process. Are you running 5.1 or 5.0? I ask, because while 5.0 has MP3, the latest VCS version for 5.1 on UNIX is 51SP1 (actually 51SP1RP2, aka SFHA 5.1 Service Pack 1 Rolling Patch 2). (There are Point Patches for some packages as well - the VRTSvxvm on my Clariion-attached servers is 51SP1RP2PP2 ;-) By my math the next thing to be released on 5.1 will be either 51SP1RP3, or they may just jump straight to 51SP2, depending on how many bug fixes are included. Check the patch finder on SORT (sort.symantec.com)
Re: [Veritas-ha] upgrade VCS 5.1 with many zones
Hello Fred! I am not sure about rolling upgrade. Never did it. I think you can use phase upgrade .( I did it recently on AIX without any problem) Or you can try Solaris New Boot Environment to install veritas patches only. This is possible. But if you have no experience with LiveUpgrade you should do phase upgrade. Regards, Pavel From: Fred [mailto:mamatec...@mamatec.com] Sent: Tuesday, March 27, 2012 12:38 AM To: Цветков Павел Анатольевич Cc: colin.y...@gmail.com; veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Hi all my SF-HA origin is 5.1rp1 for Solaris and I should to upgrade to 5.1 SP1 or 6.0, NOT upgrade Solaris but only SFHA. What about rolling upgrade, it's possible doing on two node cluster? How to? Thanks Fred 2012/3/26 Hello all! What about using Solaris LiveUpgrade ? It is possible to use it with VCS. There are some tricks though ... You should keep in mind the following. 1. Do not use zpool cluster resource if you don't failover zpools. This is because of the fact, that Offline entry point for zpool does zpool export. This is a not a good thing for "init 6" which must be run after activating New Boot Environment. If you have questions about this point just ask me. 2. main.cf types.cf must be in synclist file. 3. zfs file systems must NOT have mountpoint=legacy. Mountpoint must stay default. 4. Zone resources . Check DetachZone = false (Zone must stay in installed state while it is offlined. This is required to create ABE for zones as well as to patch zones). ForceAttach must be true if you use Veritas ODM for Oracle DB. 5. If you have vxfs mounted inside zones mount them from outside. It means that vxfs file systems must not be present in zone configuration files , they must be mounted with mount command from global zone. 6. You should have the following cluster configuration: SapTaskGroup (monitored from local zone - sap & oracle resources without mount points for sap and oracle f.s.) |online local firm | Mount_SapGroup (monitored from global zone - sap & oracle mount points on vxfs f.s. - mounted from global zone ) |online local HARD | Zone_SapGroup ( only zone resource itself - monitored from local zone) If you have dialog instances than you can have them as parallel service groups in local zones. This is about all. After that you can do the following: 1. lucreate -n MyNewBoot 2. Upgrade Solaris version with command luupgrade -u -n MyNewBoot -s /mnt/iso -k /var/tmp/sysidcfg 2. Install Recommended Patch Cluster on MyNewBOOT with all zones in parallel (check /etc/patches/pdo.conf num_proc > 1) /installcluster -B MyNewBoot --s10patchset 3. install veritas patches for i in `cat /sample/patch_order` do luupgrade -t -n MyNewBoot -s /sample $i done 4. Luactivate MyNewBoot 5. init 6 This is not easy to do everything without errors. Please, create your test environment and see first. Good luck! Pavel -Original Message- From: veritas-ha-boun...@mailman.eng.auburn.edu [mailto:veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of Colin Yemm Sent: Monday, March 26, 2012 5:13 AM To: Fred Cc: veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Short version: Um, something is wrong. Once you figure out what VCS version you are running, you should be able to do a rolling upgrade (node-by-node) if it is 5.1. I haven't been able to find a definitive statement about 5.0 (except how to upgrade from 5.0MP3RP2 to 5.1SP1), but I seem to remember it can be done, but is a somewhat manual process. Are you running 5.1 or 5.0? I ask, because while 5.0 has MP3, the latest VCS version for 5.1 on UNIX is 51SP1 (actually 51SP1RP2, aka SFHA 5.1 Service Pack 1 Rolling Patch 2). (There are Point Patches for some packages as well - the VRTSvxvm on my Clariion-attached servers is 51SP1RP2PP2 ;-) By my math the next thing to be released on 5.1 will be either 51SP1RP3, or they may just jump straight to 51SP2, depending on how many bug fixes are included. Check the patch finder on SORT (sort.symantec.com) for more info. Colin Who is having all kinds of fun right now dealing with SFHA versions going all the way back to 3.5 ;-) On Sun, Mar 25, 2012 at 4:36 PM, Fred wrote: > Hi all, > How is the best practice to upgrade VCS 5.1 to 5.1MP3? > > the global zone is ZFS, the VCS sg are a lot of zone (with zfs), with > sap apllication over vxvfs file systems. > Is it possibile to upgrade one node at time without offline of > services groups but for example only application? > > thanks in advance > > Laura > ___ > Veritas-ha maillist - Veritas-ha@mailman
Re: [Veritas-ha] upgrade VCS 5.1 with many zones
Hi all my SF-HA origin is 5.1rp1 for Solaris and I should to upgrade to 5.1 SP1 or 6.0, NOT upgrade Solaris but only SFHA. What about rolling upgrade, it's possible doing on two node cluster? How to? Thanks Fred 2012/3/26 > Hello all! > > What about using Solaris LiveUpgrade ? It is possible to use it with VCS. > There are some tricks though ... > > You should keep in mind the following. > > 1. Do not use zpool cluster resource if you don't failover zpools. This is > because of the fact, that > Offline entry point for zpool does zpool export. This is a not a good > thing for "init 6" which must be run after activating New Boot Environment. > If you have questions about this point just ask me. > > 2. main.cf types.cf must be in synclist file. > 3. zfs file systems must NOT have mountpoint=legacy. Mountpoint must stay > default. > 4. Zone resources . Check DetachZone = false (Zone must stay in installed > state while it is offlined. This is required to create ABE for zones as > well as to patch zones). ForceAttach must be true if you use Veritas ODM > for Oracle DB. > 5. If you have vxfs mounted inside zones mount them from outside. It > means that vxfs file systems must not be present in zone configuration > files , they must be mounted with mount command from global zone. > 6. You should have the following cluster configuration: > > > > > SapTaskGroup (monitored from local zone - sap & oracle > resources without mount points for sap and oracle f.s.) > > |online local firm > | > > >Mount_SapGroup (monitored from global zone - sap & > oracle mount points on vxfs f.s. - mounted from global zone ) > > |online local HARD > | > >Zone_SapGroup ( only zone resource itself - monitored > from local zone) > > > If you have dialog instances than you can have them as parallel service > groups in local zones. > > > > This is about all. After that you can do the following: > > 1. lucreate -n MyNewBoot > 2. Upgrade Solaris version with command > luupgrade -u -n MyNewBoot -s /mnt/iso -k /var/tmp/sysidcfg > > > 2. Install Recommended Patch Cluster on MyNewBOOT with all zones in > parallel (check /etc/patches/pdo.conf num_proc > 1) > >/installcluster -B MyNewBoot --s10patchset > > 3. install veritas patches > > for i in `cat /sample/patch_order` > > do > luupgrade -t -n MyNewBoot -s /sample $i > done > > 4. Luactivate MyNewBoot > 5. init 6 > > > > This is not easy to do everything without errors. Please, create your test > environment and see first. > > Good luck! Pavel > > > > -----Original Message----- > From: veritas-ha-boun...@mailman.eng.auburn.edu [mailto: > veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of Colin Yemm > Sent: Monday, March 26, 2012 5:13 AM > To: Fred > Cc: veritas-ha@mailman.eng.auburn.edu > Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones > > Short version: > > Um, something is wrong. Once you figure out what VCS version you are > running, you should be able to do a rolling upgrade (node-by-node) if > it is 5.1. I haven't been able to find a definitive statement about > 5.0 (except how to upgrade from 5.0MP3RP2 to 5.1SP1), but I seem to > remember it can be done, but is a somewhat manual process. > > Are you running 5.1 or 5.0? > > I ask, because while 5.0 has MP3, the latest VCS version for 5.1 on > UNIX is 51SP1 (actually 51SP1RP2, aka SFHA 5.1 Service Pack 1 Rolling > Patch 2). (There are Point Patches for some packages as well - the > VRTSvxvm on my Clariion-attached servers is 51SP1RP2PP2 ;-) > > By my math the next thing to be released on 5.1 will be either > 51SP1RP3, or they may just jump straight to 51SP2, depending on how > many bug fixes are included. > > Check the patch finder on SORT (sort.symantec.com) for more info. > > Colin > Who is having all kinds of fun right now dealing with SFHA versions > going all the way back to 3.5 ;-) > > On Sun, Mar 25, 2012 at 4:36 PM, Fred wrote: > > Hi all, > > How is the best practice to upgrade VCS 5.1 to 5.1MP3? > > > > the global zone is ZFS, the VCS sg are a lot of zone (with zfs), with > > sap apllication over vxvfs file systems. > > Is it possibile to upgrade one node at time without offline of > > services groups but for example only application? > > > > thanks in advance > > > > Laura > > ___ > > Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu > > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha > ___ > Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha > ___ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
Re: [Veritas-ha] upgrade VCS 5.1 with many zones
Hello all! What about using Solaris LiveUpgrade ? It is possible to use it with VCS. There are some tricks though ... You should keep in mind the following. 1. Do not use zpool cluster resource if you don't failover zpools. This is because of the fact, that Offline entry point for zpool does zpool export. This is a not a good thing for "init 6" which must be run after activating New Boot Environment. If you have questions about this point just ask me. 2. main.cf types.cf must be in synclist file. 3. zfs file systems must NOT have mountpoint=legacy. Mountpoint must stay default. 4. Zone resources . Check DetachZone = false (Zone must stay in installed state while it is offlined. This is required to create ABE for zones as well as to patch zones). ForceAttach must be true if you use Veritas ODM for Oracle DB. 5. If you have vxfs mounted inside zones mount them from outside. It means that vxfs file systems must not be present in zone configuration files , they must be mounted with mount command from global zone. 6. You should have the following cluster configuration: SapTaskGroup (monitored from local zone - sap & oracle resources without mount points for sap and oracle f.s.) |online local firm | Mount_SapGroup (monitored from global zone - sap & oracle mount points on vxfs f.s. - mounted from global zone ) |online local HARD | Zone_SapGroup ( only zone resource itself - monitored from local zone) If you have dialog instances than you can have them as parallel service groups in local zones. This is about all. After that you can do the following: 1. lucreate -n MyNewBoot 2. Upgrade Solaris version with command luupgrade -u -n MyNewBoot -s /mnt/iso -k /var/tmp/sysidcfg 2. Install Recommended Patch Cluster on MyNewBOOT with all zones in parallel (check /etc/patches/pdo.conf num_proc > 1) /installcluster -B MyNewBoot --s10patchset 3. install veritas patches for i in `cat /sample/patch_order` do luupgrade -t -n MyNewBoot -s /sample $i done 4. Luactivate MyNewBoot 5. init 6 This is not easy to do everything without errors. Please, create your test environment and see first. Good luck! Pavel -Original Message- From: veritas-ha-boun...@mailman.eng.auburn.edu [mailto:veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of Colin Yemm Sent: Monday, March 26, 2012 5:13 AM To: Fred Cc: veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] upgrade VCS 5.1 with many zones Short version: Um, something is wrong. Once you figure out what VCS version you are running, you should be able to do a rolling upgrade (node-by-node) if it is 5.1. I haven't been able to find a definitive statement about 5.0 (except how to upgrade from 5.0MP3RP2 to 5.1SP1), but I seem to remember it can be done, but is a somewhat manual process. Are you running 5.1 or 5.0? I ask, because while 5.0 has MP3, the latest VCS version for 5.1 on UNIX is 51SP1 (actually 51SP1RP2, aka SFHA 5.1 Service Pack 1 Rolling Patch 2). (There are Point Patches for some packages as well - the VRTSvxvm on my Clariion-attached servers is 51SP1RP2PP2 ;-) By my math the next thing to be released on 5.1 will be either 51SP1RP3, or they may just jump straight to 51SP2, depending on how many bug fixes are included. Check the patch finder on SORT (sort.symantec.com) for more info. Colin Who is having all kinds of fun right now dealing with SFHA versions going all the way back to 3.5 ;-) On Sun, Mar 25, 2012 at 4:36 PM, Fred wrote: > Hi all, > How is the best practice to upgrade VCS 5.1 to 5.1MP3? > > the global zone is ZFS, the VCS sg are a lot of zone (with zfs), with > sap apllication over vxvfs file systems. > Is it possibile to upgrade one node at time without offline of > services groups but for example only application? > > thanks in advance > > Laura > ___ > Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha ___ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha ___ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
Re: [Veritas-ha] upgrade VCS 5.1 with many zones
Short version: Um, something is wrong. Once you figure out what VCS version you are running, you should be able to do a rolling upgrade (node-by-node) if it is 5.1. I haven't been able to find a definitive statement about 5.0 (except how to upgrade from 5.0MP3RP2 to 5.1SP1), but I seem to remember it can be done, but is a somewhat manual process. Are you running 5.1 or 5.0? I ask, because while 5.0 has MP3, the latest VCS version for 5.1 on UNIX is 51SP1 (actually 51SP1RP2, aka SFHA 5.1 Service Pack 1 Rolling Patch 2). (There are Point Patches for some packages as well - the VRTSvxvm on my Clariion-attached servers is 51SP1RP2PP2 ;-) By my math the next thing to be released on 5.1 will be either 51SP1RP3, or they may just jump straight to 51SP2, depending on how many bug fixes are included. Check the patch finder on SORT (sort.symantec.com) for more info. Colin Who is having all kinds of fun right now dealing with SFHA versions going all the way back to 3.5 ;-) On Sun, Mar 25, 2012 at 4:36 PM, Fred wrote: > Hi all, > How is the best practice to upgrade VCS 5.1 to 5.1MP3? > > the global zone is ZFS, the VCS sg are a lot of zone (with zfs), with > sap apllication over vxvfs file systems. > Is it possibile to upgrade one node at time without offline of > services groups but for example only application? > > thanks in advance > > Laura > ___ > Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha ___ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
