Cluster Switch Version - Minimizing Downtime

Hi guys,
We are due to do a switch version for a customer with a PUB/SUB configuration. Both have had the update installed and sitting in the inactive partition.
In the past, what I would have done is to disconnect the SUB from the network, switch version on the PUB, allow it time to come up and for the phones to upgrade and re-register. After this, I would switch version on the SUB, allow it to come up, and then re-connect it to the network.
In this case, there is no time when the business is completely closed so the customer is worried about minimizing the amount of dowtime. Reading the documentation, I have found:
All servers in a cluster must run the same release of Cisco Unified Communications Manager. The only exception is during a cluster software upgrade, during which a temporary mismatch is allowed.
Does this mean I can switch version on the PUB whilst leaving the SUB connected and have the phones failover to it, then wait for the PUB to come back up again before performing the switch version on the SUB? To me this seems a bit dangerous as there will be a version of the database on two different version numbers?
Thanks
Sean

Hi Sean,
Your process is spot on! Make sure you leave lots of time for the Pub
to fully come back online after doing the switch version before starting the Sub.
Other than that you look good to go;
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cucos/7_1_2/cucos/iptpch7.html#wp1179637
Cheers!
Rob
PS: +5 for Will, Java & Aaron for their great work here
"Clocks go slow in a place of work
Minutes drag and the hours jerk"
-The Clash

Similar Messages

Major version upgrade of WebLogic with zero/minimal downtime

From what I can tell, the recommended approach for supporting minimal downtime during major version upgrades (e.g. WL 9 -> WL 10) is to have 2 domains available in the production environment.
Leave one running to support existing users, upgrade the other domain, then swap to perform the upgrade on the first domain.
We are planning on starting out with WL 9.1, but moving forward we require very high availability...(99.99%).
Is this my only option?
According to BEA marketing literature, service pack upgrades can be applied with "zero" downtime...but if this isn't reality, I'd like to hear more...
Thanks...
Chuck

Have gotten as far as upgrading all of the software, deleting /var/db/.AppleSetupDone, and rebooting. It brought me back in to Setup Assistant and let me choose "migrate from another mac os x server" and is now sitting waiting for me to take the old server down and boot it into target disk mode. Which we can probably do Sunday at about 2am or so...
You know, Setup Assistant should really let you run Software Update BEFORE migrating from another machine. We have servers that can't be down for SoftwareUpdates in the middle of the day...

Upgrading Cluster without switch version

Hello, I just want to be clear to an upgrade I will be performing in future. We have CUCM cluster and want to know if it is possible to do the upgrade on the publisher (without switch version) and then continue to upgrade the subscribers, then switch version on all - or do I need to switch version on publisher before I can continue to update subscribers?
Also, I think that in the past, the upgrade takes a copy of the database when you upgrade, so you need to switch version soon after upgrade or you will loose any changes. Is this remain the case? Is this also the case for UCCX? I remember maybe reading in the past that it does the database differently.
Thanks to you all

Hi Ess,
In addition to the great tips from my friend Manish (+5)
You didn't mention the to/from CUCM versions but here is an example
User Provisioning
For upgrades from Cisco Unified Communications Manager Release 6.x, changes that are made to the following user-facing features get preserved after the upgrade completes:
•Call Forward All (CFA)
•Message Waiting Indication (MWI)
•Privacy Enable/Disable
•Do Not Disturb Enable/Disable (DND)
•Extension Mobility Login (EM)
•Hunt Group Logout
•Device Mobility
•CTI CAPF status for end users and application users
•Credential hacking and authentication
•Recording enabling
•Single Number Reach enabling
Upgrading a Cluster in Parallel
When you upgrade a cluster that is running a supported version of Cisco Unified Communications Manager 6.x to Cisco Unified Communications Manager 8.5(1), begin upgrading the first node first. You can begin upgrading subsequent nodes in parallel after the first node reaches a specified point in the upgrade.
During the upgrade of the first node, view the installation log, install_log_.log, by using the Software Installation/Upgrade window in Cisco Unified Communications Operating System Administration or the command line interface (CLI). You can begin the upgrade of the subsequent nodes after the following information displays in the log:
PRODUCT_TARGET is
PRODUCT_NAME is
PRODUCT_VERSION is
You can also use the CLI to search for the relevant information in the install log by following this procedure:
Procedure
Step 1 List the install logs; for example:
file list install install_* date
install_log_2008-10-01.09.41.57.log install_log_2008-10-08.12.59.29.log
install_log_2008-10-14.09.31.06.log
dir count = 0, file count = 3
Step 2 Search the most recent install log for the string PRODUCT_VERSION; for example:
file search install install_log_2008-10-14.09.31.06.log PRODUCT_VERSION
Searching path: /var/log/install/install_log_2008-10-14.09.31.06.log
Searching file: /var/log/install/install_log_2008-10-14.09.31.06.log
10/14/2008 09:52:14 upgrade_os.sh|PRODUCT_VERSION is 7.1.0.39000-97|
Search completed
Step 3 When the file search command finds the PRODUCT_VERSION string in the install log, you can start the upgrade of the subsequent nodes.
Caution If you want to upgrade the subsequent nodes in parallel with the first node, do not choose the Reboot to upgraded partition on either first node or subsequent nodes while configuring the upgrade options. If selected, the first node may complete its upgrade and reboot while the subsequent nodes are upgrading, which causes the upgrade of the subsequent nodes to fail.
When you are ready to activate the new version, you must activate the new software on the first node before activating it on all other nodes. .
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cucos/8_5_1/cucos/iptpch7.html#wp1076243
Cheers!
Rob
"Seek it out and ye shall find "
- OneRepublic

Schema changes, minimal downtime

We are a software development company, using Oracle 10g (10.2.0.2.0). We need to implement schema changes to our application, in a high traffic environment, with minimal downtime. The schema changes will probably mean that we have to migrate data from the old schema to new or modified tables.
Does anyone have any experience with this, or a pointer to a 'best practices' document?

It really depends on what "minimal" entails and how much you're willing to invest in terms of development time, testing, hardware, and complexity in order to meet that downtime requirement.
At the high end, you could create a second database either as a clone of the current system that you would then run your migration scripts against or as an empty database using the new schema layout, then use Streams, Change Data Capture, or one of Oracle's ETL tools like Warehouse Builder (which is using those technologies under the covers) to migrate changes from the current production system to the new system. Once the new system is basically running in sync with the old system (or within a couple of seconds), you can shut down the old system and switch over to the new system. If the application front end can move seamlessly to the new system, and you can script everything else, you can probably get downtime to the 5-10 second range, less if both versions of the application can run simultaneously (i.e. a farm of middle-tier application servers that can be upgraded 1 by 1 to use the new system).
Of course, at this high end, you're talking about highly non-trivial investments of time/ money/ testing and a significant increase in complexity. If your definition of 'minimal' gets broader, the solutions get a lot easier to manage.
Justin

Migrate entire database to ASM on another server via RMAN minimal downtime

Hi
I was looking for a procedure to migrate non ASM production databases to ASM via RMAN on a separate server with minimal downtime (backup as copy/switch database to copy technique). We have TDPO for tape backup and I normally rman clone test databases between servers but this involves too much downtime for production. The procedure in the ASM Admin Guide (Chapter 8) assumes the databases are on the same server.
Thanks
Tom Cullen

tcullen wrote:
Hi
I was looking for a procedure to migrate non ASM production databases to ASM via RMAN on a separate server with minimal downtime (backup as copy/switch database to copy technique). We have TDPO for tape backup and I normally rman clone test databases between servers but this involves too much downtime for production. The procedure in the ASM Admin Guide (Chapter 8) assumes the databases are on the same server.
Thanks
Tom CullenDear Tom. Why you think you'll have downtime in the production database? The database will be running while the clone will be processing. Check the following link:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmdupdb.htm#BGBDCDGJ
RMAN DUPLICATE DATABASE From ASM to ASM: Example
Kamran Agayev A.
Oracle ACE
My Oracle Video Tutorials - http://kamranagayev.wordpress.com/oracle-video-tutorials/

Switch version fail. CCX 8.5.1SU4 - 9.0.2

Hey All.
When i try to switch-version from version 8.5.1su4 to 9.0.2 then after app. 30 min, the cli says "Sync after switch version failed" and then stops.
I have tried to reinstall the 9.02 on the inactive partion, but still the same issue. all network connectivity (DNs, NTP etc.) is running så they should not be any network issue that causes this.
I have also tried to force a switch-version thru the recovery CD, and the swtich version goes ok, and the 9.02 comes up, but no services will start (Waited 45 min - and monitor the utils services list on the console)... so im back on 8.51su4.
Installation is on vmware version 5.0 and is SA
On the console, i can se 1 error in the startup,
But the interface is actually answering from remote.
Anyone have any idea what i could be??
(the refresh file was install before the the upgrade file...)
Best Regards
Thomas Johannesen

Hey Aaron
Here is the log files.
As i can se in the files it comes with this error :
WARNING: server initialization failed, or possibly timed out (if -w was used).
Check the message log, online.log, for errors.
2013-01-28 12:40:30,501 - uccxdb.util - CRITICAL - Error in executing the cmd [su -c 'source /opt/cisco/uccx/bin/uccx_ids.env ; oninit -wyv' informix], retCode [1]
Mon Jan 28 12:40:30 CET 2013 :: Error while installing files for UCCX DB instance
Mon Jan 28 12:40:30 CET 2013 :: -------------------------------------------------------------------
Mon Jan 28 12:40:30 CET 2013 :: Moving sysadmin db to sadmin dbspace
Mon Jan 28 12:40:30 CET 2013 :: sadmin_exist 2
Mon Jan 28 12:40:30 CET 2013 :: Moving sysadmin database
1809: Server rejected the connection.
Mon Jan 28 12:41:00 CET 2013 :: Error moving sysadmin DB
Mon Jan 28 12:41:00 CET 2013 :: Stopping DB
Mon Jan 28 12:41:00 CET 2013 :: ------Stopping uccx database-------
Mon Jan 28 12:41:05 CET 2013 :: Waiting for port to be released
Mon Jan 28 12:41:05 CET 2013 :: The port is released
Mon Jan 28 12:41:05 CET 2013 :: ------UCCX database stopped--------
Mon Jan 28 12:41:05 CET 2013 :: DB upgrade script failed
Mon Jan 28 12:41:05 CET 2013 :: Restoring repicaition status of the databse
At least two servers must be defined for replication.
The requested operation will not be performed.
Mon Jan 28 12:41:05 CET 2013 :: ./uccx_sv_db.sh 8.5.1.11004-25 9.0.2.10000-71 8.5.1.11004 rpmdb: Program version 4.2 doesn't match environment version error: db4 error(22) from dbenv->open: Invalid argument error: cannot open Packages index using db3 - Invalid argument (22) error: cannot open Packages database in /partB/var/lib/rpm package UCCX02_lib is not installed /var/log/active/platform/log/cli.log
Script uccx_sv_db.sh failed with exit code 255.
in the uccx_install.log file. and after that i runs the rollback script.
Have no idea why this error is showing.
Best regards
Thomas

UCCX 8.0 to 8.5 Switching Versions

Will there be data lost between versions if I decided to switch version (reboot to inactive partition) later? I got UCCX on 8.0 now and installed 8.5 on the inactive partition but due to scheduling constraints, we're holding off on rebooting to the new one. I'm talking about days or even a weeks. Will changes done to UCCX from here on as well as reporting data be lost after switching?

The common understanding is that configuration is migrated during the upgrade, this is a CUCM concept.
UCCX and Unity only migrates the configuration data when you switch version.
There is no changes to the Historical data as it sits on the common partition is avaliable to both the active/inactive partition.
This is somthing that requires a documentation update, I am still looking through the avaliable documents wither its already avaliable. Should I not beable to find it, I'll look at filing for a documentation update assuming this information is also avaliable for CUCM.
Hoai

What are the rules about switching versions?

I thought projects created in iMovie 9 showed up in iMovie 10, but I just tried creating a new project in iMovie 9 this morning and it is not showing up in iMovie 10, even though I see projects from 2013 and before in there.
Also, what are the rules about switching versions? I know iMovie 9 much better, so can I start a project there and finish it in iMovie 10? I would like to gradually learn iMovie 10, but not all at once.
I assume that once a project is edited in iMovie 10, it can't be worked on in iMovie 9 anymore.

You have to update iMovie 9 projects to iMovie 10 from within iMovie 10 before they will appear in iMovie 10 as iMovie 10 uses a completely different project/event file system. After updating you can still work on projects in iMovie 9 but you won't see any changes made in iMovie 10 and you can't transfer them back.
I would have a good look at the iMovie 10 help files first since a lot is changed and some features have been discontinued that might be important to you.
In order to try out iMovie 10 on just one of your iMovie 9 projects, put the folders just for that project in a separate iMovie Projects and iMovie Events folder and hide the project and event folders containing the projects you don't want to update from iMovie 10 by enclosing them in a higher level folder (only projects and events folders in the Movies folder of the boot drive or at the root level of another drive or partition will be visible to iMovie).
I did it this way and I'm glad I didn't try to update evrything at once!
Geoff.

Migrating Hyper-V 2008 R2 HA Clustered to Hyper-V 2012R HA Clustered with minimal downtime to new hardware and storage

Folks:
Alright, let's hear it.
I am tasked with migrating an existing Hyper-V HA Clustered environment from v2008R2 to new server hardware and storage running v2012R2.
Web research is not panning out, it seems that we are looking at a lot of downtime, I am a VMware guy and I would do likely a V2V migration at this point with minimal downtime.
What are my options in the Hyper-V world? Help a brother out.

Merging does require some extra disk space, but not much.
In most cases the data in the differencing disk is change, and not additional files.
The absolute worst case is that the amount of disk space necessary would be the total of the root plus the snapshot.
Quite honestly, I have seen merges succeed with folks being down to 10 GB free.
But, low disk free space will cause the merge to take longer. So you always want to free up storage space to speed up the process.
Merge is designed to not lose data. And that is really what takes the time in the background. To ensure that a partial merge will still allow a machine to run, and a full merge has everything.
Folks have problems when their free space hits that critical level of 10GB, and if they have some type of disk failure during the process.
It is always best to let the merge process happen and do its work. You can't push it, and you cannot stop it once it starts (you can only cause it to pause). That said, you can break it by trying to second guess or manipulate it.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

Question on switch-version and data loss

Hi,
In reading info around the web, I do find and understand that any changes made to configuration of an upgraded CUCM node will be lost if they were made after upgrade but before switch-version. I was wondering if CDR files/database were also grouped into this, or if those are copied over when switch-version is executed.

Hi,
CDR records will be lost, only user facing features are preserved. Please check the following post
https://supportforums.cisco.com/discussion/11117171/cucm-upgrade-and-cdr-records#3293654
HTH
Manish

Migrating SQL Server Published databases with minimal downtime

All,
I have a requirement in which databases in Server A has to be mirated to Server B. Server A has two databases in Merge replication and one with Transactional replication. Server A act as the distributor itself.
My question is how can I migrate all these production databases which are also publishers to new sever B with minimal downtime, and with out breaking replication.
I read that if the Server B is renamed as Server A then replication will continue with out any errors.Please suggest how to migrate the publisher to Server B with minimal downtime.
Also I would like to know if the replication is Server A->Server C->Server D, then if I can migrate Server A to Server B with out dropping replication, will it affect the replication setup from Server C to Server D. Does it cause any replication errors.
Thanks in advance!

Just to throw some thoughts out there.
It sounds like the "blocker" in the overall migration strategy is the Distribution database and the fact that it is local to a Publisher.
Once you have migrated the Distributor, the remainder of the problem
is more straightforward, using solutions such as Database Mirroring to failover to a new server with minimal downtime for example.
If I were performing this migration project, I would agree with the business that there was to be a
short replication service interruption whilst we migrated to a new Distribution database/server. I would also apply Hillary's recommendation to use the opportunity to split-out the Distribution database to a dedicated server.
Using this approach, you could build and configure the new Distribution database before the migration "cut over" phase. The cut-over would require that you Drop the replication topology and re-create it, using the new Distributor DB/Server. You can script
ALL the steps required for this ahead of time, resulting in the actual cut-over to the new Distributor being completed in a couple of minutes max (the database involved are already in Synch).
Once done, you can proceed ahead with the remainder of the migration.
Overall this is not a trivial project you have on your hands and in my opinion you absolutely must perform the process in a test environment before attempting to do so in Production.
Good luck.
John Sansom | SQL Server MCM
Blog |
Twitter | LinkedIn |
SQL Consulting

CUPS upgrade switch version fails

Hello,
I'm upgrading CUPS 6.0.5.10000-13 to 7.0.2.10000-36 which I have downloaded from CCO.
I restarted the server and when I apply switch version command from CLI to swtich to ver 7, it doesn't do anything.
Has any body experience this kind of issue? This is a standalone lab installation so physically there's no CUCM connected. I have restored production CUPS backup on it and wants to upgrade to ver 7.
Thanks in advance,
Sak

This is most likely CSCsl59162.
I might be wrong, but I don't think nodatasync would fix the problem.
"nodatasync" parameter is used on CUCM to turn off UFF (User Faced Feature) synchronization. UFF means, MWI, Call Forwarding, etc.. Since CUPS does not have UFF, this parameter shouldn't make any difference on switch-version command.
If "nodatasync" didn't fix the problem, you may open a TAC case and provide bug ID CSCsl59162. TAC engineer should be able to apply workaround per the bug.
Michael
http://htluo.blogspot.com

How do I move databases using RMAN with minimal downtime ?

How can I do the following using RMAN ?
DB version 10.2.0.4
Redhat 5.2
I am not using an rman catalogIn the past I have moved large databases from 1 server to another with 5 minutes downtime using backups done the old way by putting tablespaces in backup mode and making copies of the datafiles.
I used the following method :
========> Part 1
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE set DATABASE "VPMY" RESETLOGS ARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 3
....etc
LOGFILE
......... log file names
DATAFILE
... list of datafiles
CHARACTER SET US7ASCII;
========> Part 2
Up until the scheduled downtime, I would copy the archive logs from the production server to the new and run the following to apply the latest archive logs:
RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
->AUTO<-
========> Part 3
After applying the last archive log while in restrict mode -
ALTER DATABASE OPEN resetlogs;
My question is, how do I do Part 2 in RMAN. I have managed to duplicate databases and restore databases using rman to a different server, but this obviously only covers the data upto the backup point. How can I do the above parts 1 -3 with downtime of about 5 minutes like I have done using old methods ?
Any help is much appreciated/

you should be able to recover as you go with rman as well..
copy the archived logs from A to B and apply them as they come in.
run
set until sequence x thread 1;
recover database;
if you're not opening the database after recovery you can just increment the set until sequence as the logs come in and do a new recovery.

Migrate Data from one SAN to other in AlwaysON configuration with no/minimal downtime

Team,
There is a requirement to move the current DBs from existing SAN to new IBM SAN disks. I have outlined the below steps. Request you to please add your inputs/challenges/risks.
This is in Always ON and We have 3 Nodes.
Server A , Server B and Server C
A and B are Synchronous
C is hosting Async replica.
Note: The SQL binaries are installed on E: drive which is a SAN drive. Whether is this going to be impacted based on my steps below?
Present the new SAN of same size on all the nodes in the Availability Cluster.
Break the secondary replica. On Secondary replica, Migrate the data by physically moving the DB files from old SAN to new SAN.
Rename the new SANs back to the original filenames as it was present earlier. Bring up the services and join to Availability Group. Check whether the DBs are Synchronized with Primary.
Now, Failover the Primary to Secondary replica- This will be a short outage.
Follow the same steps on Primary as mentioned in Steps 1-3.
Check the Synchronization of the DBs and perform all the sanity checks.
Thanks!
Sharath
Best Regards, Sharath

Hi Sharath,
This can be easily achieved by storage migration by storage Vendor, In your case IBM should be able to do it, since they have sophisticated tools
(one of these tools is Storage Virtualization for Data Migration and Consolidation) to this SAN migration they don't need downtime during the storage sync process. your downtime will be only the Cutoff Time, If SAN Vendor does the Data Migration for you. <o:p></o:p>
Otherwise,
1. Take out read-only replica out of Always on Group.
2. Since SQL is also installed on SAN drive, I strongly suggest you to rebuild the SQL Server as new. (No Copy of Data from SAN to SAN)
Note: Drive allocation and drive letters should be identical
3. Once you rebuild the SQL Server, One Challenge here is to migrate the SQL Logins (You must migrate users using same SID, to avoid permission issues).
4. then Add it Always on Group, and wait for the databases to sync.
5.
Then manually move the always on group read/write replica to new node.
6. follow the steps 1 ,2,3 and 4 in sequence.
Hope this will help you.

SQL SERVER Failover Cluster switch failure because the passive node automatically reassign drive letter

I switch the sql server resource group to the standby node , when the disk resource ready bring online in the passive node ,then occur exception. because the original dependency disk resource the drive letter is 'K:' , BUT when the disk bring online , it
automatically reassign new drive letter 'H:' , So the sql server resource couldnot bring online . And After Manual modify the drive letter to 'K:' in the passive node , It Works ! So my question is why it not use the original drive letter
and reassign a new one . what reasons would be cause it ? mount point ? Some log as follows:
00001cbc.000004e0::2015/03/12-14:41:11.377 WARN [RES] Physical Disk <FltLowestPrice_K>: OnlineThread: Failed to set volguid \??\Volume{e32c13d5-02e6-4924-a2d9-59a6fae1a1be}. Error: 183.
00001cbc.000004e0::2015/03/12-14:41:11.377 INFO [RES] Physical Disk <FltLowestPrice_K>: Found 2 mount points for device \Device\Harddisk8\Partition2
00001cbc.00001cdc::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: PNP: Update volume exit, status 1168
00001cbc.00001cdc::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: PNP: Updating volume
\\?\STORAGE#Volume#{1a8ddb8e-fe43-11e2-b7c5-6c3be5a5cdca}#0000000008100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
00001cbc.00001cdc::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: PNP: Update volume exit, status 5023
00001cbc.000004e0::2015/03/12-14:41:11.377 ERR [RES] Physical Disk: Failed to get volname for drive H:\, status 2
00001cbc.000004e0::2015/03/12-14:41:11.377 INFO [RES] Physical Disk <FltLowestPrice_K>: VolumeIsNtfs: Volume
\\?\GLOBALROOT\Device\Harddisk8\Partition2\ has FS type NTFS
00001cbc.000004e0::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: Volume
\\?\GLOBALROOT\Device\Harddisk8\Partition2\ has FS type NTFS
00001cbc.000004e0::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: MountPoint H:\ points to volume
\\?\Volume{e32c13d5-02e6-4924-a2d9-59a6fae1a1be}\

Sounds like you have an cluster hive that is out of date/bad, or some registry settings which are incorrect. You'll want to have this question transferred to the windows forum as that's really what you're asking about.
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

Cluster Switch Version - Minimizing Downtime

Similar Messages

Maybe you are looking for