vCenter to migration issues of device 5.5 to 6.0

Similar Questions

• DTA migration issues

  In order to gain visibility for DTA migration issues I've mentioned several times in other threads, I thought I would post a new thread and kick off the coast with two of my favorites:

  Events of 'no time' 1) recurring are moved to the previous day.  If you look in the .mdb (Microsoft Access) data tables, created by the new Palm Desktop 6.2.2 you will see that these events are stored in GMT, instead of any time you have set.  If you're at (for example) EST/EDT, then a "free time" event in GMT will begin the day previous (GMT 5/4 hours located prior to the EST/EDT).  Palm Desktop 6.2.2 these events appears correctly (maybe corrected 'on the fly' for a few screws previously known upward in previous versions from the Palm Desktop or Palm devices stored these events), but during the migration to the front via DTA, they appear the previous day.

  (2) recurring events which were to "12 months" (instance, father's day, which is the 3rd Sunday of June, is set up by placing the event initial OK Sunday of June and then by setting the recurrence for "3rd Sunday of each month 12") are changed during migration via DTA the Pre, reproduce every month.

  These are both very reproducible and took place during three separate migrations of DTA.  The Calendar database have been verified by the latest version of DbFixIt and found no problem. The Treo 700 p and Palm Desktop 4.1.4 and now 6.2.2 display them correctly.  Only the Pre after migration DTA shows these questions.  The Pre is runnning WebOS 1.0.4 and is configured to only use the Palm profile for the backup.

  I'm ready to ask for a SOLUTION to these two questions, with these workaround solutions:

  (1) to prevent the traffic events "without time" days prior (for those of you at the time of the zones West of GMT/UTC) Please make sure that your pre got your time zone local network, or if not, that you set your time zone manually to match that of your host, before migrating to the DTA.

  (2) If you have each year (in fact any interval of more than 9 'days', 'weeks', 'months', or 'years') "byday" (e.g., 3rd Sunday of June) or events (e.g., May 13) "bymonthday", you will need to:

  (a) after the execution of DTA 1.1, and before unplugging the USB before, open a window File Explorer and move the file migration.mig from PRE USB key to your computer.  After that, you can leave the pre connected or not, depending on your needs.  As long as the migration file is not in the USB when the Pre is disconnected, it does not start a data migration.

  (b) using a suitable text editor (for example, Wordpad on Windows), do a find on (for example) "FREQ = MONTHLY; INTERVAL = 1"(without the quotes).  Inspect the field 'SUMMARY' current record "VCALENDAR" to determine if this is really a monthly event or (for example) "byday" or "bymonthday".  If the latter, change the 'INTERVAL = 1' clause' RANGE = 12' (or whatever the actual range is supposed to be.  Repetition of finding suspicious items until you are satisfied you have found and fixed all.

  (c) save the modified file.  Check the file name to ensure that Windows has not renamed it "migration.mig.txt".  If so, rename it to "migration.mig".

  (d) If you had unplugged the meadow at the end of step one), he re - connect as a USB and copy the file "migration.mig" forwards, in the root of the USB stick.  When you do a "safely removing" pre, it will find the migration.mig file and start the migration.  With WebOS 1.1, the pre now entertains you with a progress indicator.  This is actually very useful, because if you connect the Pre to as a USB key before the migration is complete, it will start a 2nd an and start in double filling your calendar, etc.  So be patient and wait until the migration is completed before making any transfer files USB with the Pre.

  This procedure should be performed with the DTA 1.1 (or a later version, if later versions don't fix this issue) and WebOS 1.1 (which seems to have solved the calendar gray/frozen screens that had suffered me since the day 1 of pre availability (06/06/09 in the United States).) Please note that this is a problem with the program of the DTA, not WebOS, so it cannot be solved with a future WebOS update (Garbage In, Garbage Out or GIGO as say the).  Please note that I am not synchronized with any service, but use the Palm profile as backup.

  Now that I feel I have a pretty good handle on getting a solid migration of DTA, I'll probably then address a Google account instead of the Palm profile synchronization and see what falls from that.

  Thank you, PDAGuy and Anachronistic, for all your help.

  EDIT: I found a new failure in the timing of the front.  I'll start a new thread, so we can more easily track it separately.

  Message edited by theoldmoose on 10/08/2009 21:02

• Suggestion on Vcenter DB migration on the new virtual machine and enhancement vcenter server

  Hello

  I'm looking for any suggestion/plan with Vcenter DB migration steps towards the new virtual machine, and then upgrade the server vcenter

  4.1 for Update1/2

  My plan will be

  (1) creating new virtual machine.

  (2) fresh install 64-bit OS

  (3) migration Vcenter DB of the physical server to the new virtual machine.

  (4) upgrade to Vcenter Server 4.1 update 41 4.1 Update1/2

  Anything else missing then please let me know.

  Thank you

  vmguy

  Hi vmguy

  I agree with this approach

  (3) migration Vcenter DB of the physical server to the new virtual machine.

  As long as you leave the old DB in tact and simply detach and copy the DB to the new Victoria Cross.

  Before you run the upgrade on the new VC and DB.

  This way, you have a restoration plan in case something goes wrong with the upgrade.

  Just to add:

  You must migrate the ADAM database so to maintain the specified permissions vCenter

  See: Migrateing vCenter new host

  Please allow points if you find this useful/correct

• TMS directory failed in the endpoints of series C after the migration of the device to the virtual computer

  Hi all

  We have migrated the 12.8 TMS from the device to the TMS 13.0 on the VM platform. There is no matching TMSPE and mainly used for management and directory service.

  Once the migration is complete on the platform of the VM, we found that endpoint C-series could not receive phonebook of TMS (while 95 MXP endpoints works very well with the TMS directory).

  The end point of series C, we check the Configuration-> directory server 1: URL. The link is converted from http:// /tms/public/external/phonebook/phonebookservice.asmx http:// tms/public/external/phonebook/phonebookservice.asmx.

  (In addition, we check the authorization of the two phone book page, and there is no IIS issue).

  In the 95 MXP endpoint, it can receive the telephone directory unit VM MSD and MSD.

  Best regards

  Ben

  Hi Ben,

  As confirmed by the curl command - you don't have access to the web page as an anonymous user.  You have to fix your permissions.  One of the fastest ways to do would be to try to reinstall the MSDS on the server again - this should reconfigure the IIS settings required for TMS.

  Wayne
  --
  Remember the frequency responses and mark your question as answered as appropriate.

• Cold of Vcenter server migration

  We change architechtures CPU from AMD to Intel.

  I moved all my virtual machines with the exception of the server that is running VirtualCenter 5.01.

  The database is on the machine as well.

  My plan is to:

  1. stop the server

  2. attach to the host, it's on with Vcenter client and remove from the inventory.

  3. using the Vcenter client attached to a host in the cluster I want to move to and save it on the host computer.

  4 cross my fingers and the power on the virtual machine.

  I fear that the center of V server will be confused when it starts on a different host and cluster

  All the world did this with success?

  Don't anticipate any issues... it's one of the benefits of virtualization, because virtual machines are encapsulated in a set of files, they can be easily imported/exported on any standard x 86 architectures. Although an essential part of the management of vSphere, vCenter it wouldn't hurt to keep a clone backup of it on the existing (just in case) host. Post migration you may be prompted with a uuid warning message, take a look at the below URL for the explanation:

  http://techhead.co/VMware-ESX-i-moved-it-or-i-copied-it-whats-the-difference/

• Simple with VM storage Migration issues

  I have a unique virtual machine in my cluster 6.x that is having a problem of migration of storage. If I try to migrate to any other data store, I get "cannot complete the creation of file operation" which gives me virtually no results and I was not able to locate all newspapers host or vcenter which will tell us what is in fact a failure. Migrate from 20 other virtual machines without problems and an another vm has migrated to the data store at several levels, I want this virtual machine. I also tried to move it to just a datastore k 15 directly with the same error. I was not able to get a maintenance window in order to turn off the virtual machine and see if I can migrate it cold. I have migrated to different hosts in my group and get the same errors. VM snapshots and consolidated very well and seems to be about all other related storage containers business as usual and has no irregular performance.

  HP Gen9 blades with 3PAR on FC storage. Using ISO custom and all that Jazz. I have a lot of environments hosts 6.x without any problem. Definitely a problem with the virtual machine.

  Doug

  Unfortunately, the question lies in the damaged files from VM. I'll have to rebuild the virtual machine.

• vCenter license migration.

  Hi all

  I'm n process of installing a new server vCenter and DB. Currently I have a vCenter 5.0 with Sql Express. I want to install new 5.5 vCenter as there is a problem with the Windows operating system. Can anyone provide steps on the migration of the current 5.0 vCenter vCenter license to new vCenter 5.5. And not taking a full backup of the current comics and migration to the new full DB will give me same old vCenter inventory?

  Kind regards

  Vikram kumar

  You must first migrate the database to db express to Full SQL 2008 DB. The steps are lower in the article.

  VMware KB: Migrating the database from the SQL Express vCenter server to full SQL Server

  -Deploy the new operating system and give the same IP address and host name you use for the old operating system.

  -Take the backup of the more secure base for located.

  -Take SSL certificate to the top of the old C:\ProgramData\VMware\VirtualCenter Server\SSL Server

  -Create the system DSN proper connections on the new host to vCenter server. For more information, see displaying and editing of the database server to vCenter Server installation fails with ODBC and DSN errors (1003928).

  -If the new VirtualCenter server using the same hostname and IP address, SSL certificates can be copied to the new server to eliminate the need to reconnect the ESX and ESXi hosts.

  -To copy the VirtualCenter Server SSL certificates:

  1. Create this folder structure on the new server:
  2. C:\ProgramData\VMware\VirtualCenter Server\SSL

  -To copy the VirtualCenter Server SSL certificates:

  -Copy these files from the server, VirtualCenter of origin to the new server, while preserving the folder structure:

  • VirtualCenter Server\SSL\rui.key C:\ProgramData\VMware\VMware
  • VirtualCenter Server\SSL\rui.pfx C:\ProgramData\VMware\VMware
  • VirtualCenter Server\SSL\rui.crt C:\ProgramData\VMware\VMware

  -Launch Virtual center 5.5 installation see the installation guide for 5.5

  -When you are prompted, select use existing databaseand provide the correct credentials for the database.

  -When you are prompted, select this option to not reset the database to keep all your inventory data.

  -Restart the computer after the installation is complete.

  For detail info see the KB article below. http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=5850444

• vCenter Server upgrade issues

  I'm looking to upgrade vCenter Server Application 5.1 to 5.5 and I have a few questions:

  Y would there be a way to migrate the current settings of my instance 5.1 to 5.5 new one?

  -Can I use the appliance of vCenter 5.5 5.1 ESXi?

  -Manage vCenter 5.5 5.1 ESXi hosts?

  Thank you!

  -John

  Y would there be a way to migrate the current settings of my instance 5.1 to 5.5 new one?

  Rep. : Please go through the KB: VMware KB: upgrading vCenter Server Appliance 5.0.x/5.1 to 5.5

  -Can I use the appliance of vCenter 5.5 5.1 ESXi?

  Rep. : Yes, you can.

  -Manage vCenter 5.5 5.1 ESXi hosts?

  Rep. : You can manage vCenter 5.5 5.1 ESXi hosts

  -vChinna

• Migration of raw device to VMDK virtual card reader

  Hi all

  I currently have 3 5.0.0 ESX 504890 hosts.  I have about 12 people who unfortunately have mapped drives of raw device.  I would like to convert VMDK to a data store.  I have VMware Standard, so I vMotion and Storage vMotion at my disposal.

  I tried a migration of guests which has a hard drive of the RDM.  Steps are the following:

  1. Right-click on the client
  2. Select migrate
  3. Select change Datastore
  4. Click on advanced
  5. Select the data store that I want to spend.
  6. Select thin provision
  7. Click next

  Once it's over it's now a VMDK created in the data store but when I go in the settings on the guest he always shows as RDM.  I'm doing something wrong here as the VMDK which was create shows, it has been changed at the end of the procedure.

  Thank you for taking the time to read/post on my question.

  

  

  Just to confirm. You have selected different datastore to where you want to migrate the virtual computer?

  André

• VCenter server migration

  I need to migrate my vCenter Server 5.0 to a more powerful server.

  How can I migrate without having to reconfigure all of my environment vSphere 5.0 from scratch?

  Can I export and import configuration and/or the DB?

  Is there any document or best practices I can refer to?

  Concerning

  Marius

  the items below should be useful

  http://KB.VMware.com/kb/5850444

  http://KB.VMware.com/kb/7960893

• VCenter simple Migration to new hardware

  have a Setup simple vCenter.  A vCenter server with 3 being the hosts managed and about 15-20 ESX servers.  He is currently a virtual machine host as we had no spare parts at the time.

  We do not use the advanced features yet (vMotion, etc.).  Basic host maintenance.  We have new equipment and Win2008/64-bit is installed.

  What moved the easiest way to get the old stuff?  Or I have to actually migrate?  Can I simply unattach the 3 former ESX servers and add it again?  Old server vCenter will be deactivated once all moved or added to the new server.

  Thank you

  Hello

  You need basically install new vcenter and remove all hosts to vcenter (unplug and remove). To add vcenter again.

  Also check http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=5850444

  and this discussion http://communities.vmware.com/thread/139206

  Hope helps

  Good luck

• 4.0U2 > 4.1 server migration issue

  I'm currently experimenting with a VC 4.0u2 & gt; 4.1 migration. I install a new Windows 2008R2 host for the VC and have run the migration tool on the old Victoria Cross, and then again on the new VC to import the configuration. I'm a little confused as to what to do once the migration is completed successfully... I disconnect the old VC, withdraw the AD and then set the parameters of the new Victoria Cross to the former (IP address, host name)? I leave the IP and hostname as new entities and then edit info on the ESX servers and within the view? Which is better?

  Thanks in advance.

  My Blog: http://rebootuser.com

  If you have found this device or any other useful post please consider the use of buttons useful/correct for award points.

  Hello

  Take a look at this thread http://communities.vmware.com/thread/281955

  Kind regards

  Micke

• vCenter Server install issues?

  We plan our migration of VI 3.5 to vSphere 4.  Our current vicenter server is running on Windows 2003 with a SQL 2000 database.

  I want to do the following and know if it is possible.

  1 virtualize our current viserver and wipe the hardware it is running on.

  2. install Windows 2008 R2 Enterprise x 64

  3. install Microsoft SQL Server 2005 x 64

  VCenter will work on Windows 2008 x 64?  I tried searching for this information, but for some reason any cannot arrive at this answer.

  Thank you

  Kris Turner

  Yes vCenter 4.0 is compatible with the 2008 x 64 according to the compatibility guide - http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• migrate the NAS device file system

  Current config: host CentOS; Ubuntu Vm; VMWareServer.

  I'm migrating file systems of a number of Ubuntu VM running on a host of CentOS to a NAS device which is mounted via NFS.  I am running VMWare Server (64-bit)

  Current configuration:

  Release of centOS 5.2 (Final)

  Ununtu VM: 2.6.18 - 92.1.18.el5 #1 SMP Wed Nov 12 09:19:49 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux

  I see some contradictory information, so I would appreciate an idea if you have a similar project.

  Thank you.

  will136 wrote:

  Can I use rsync to copy the virtual host to the NAS disk or do I have to use the vmkfstools command?

  Any guest arrested or Hibernate mode can be reproduced by any tool you like (rsync, unison, cp, mv, no matter).

  No risk of problems with disc ID / Grub?   How do I point to the new location of the virtual disk?

  You didn't play something with raw devices? Haven't you? If this is not the case, the 'virtual' disk is only one (the) (*.vmdk) file that is moved/copied to the new location. Which does not affect its content, nor that it does not change the disk IDS.

  There could be problems with ISO attached hard coded paths for CD/DVD. They can be set by editing the appropriate *.vmx or using the WebGUI of Server 2 for this guest (guest physical or ISO settings based on CD/DVD).

  Is the same for drives, if you specify special data store options, the *.vmx expect to find his 'virtual' disk in the same place as the *.vmx.

  To be sure, take a look inside the appropriate *.vmx (open with a text editor).

• to migration issues

  You can migrate a user file to the same computer more than once?

  Is it an advantage to use to migrate down and assistant rather than simply drag?

  Yes, but MY will does not overwrite anything. It will simply create a new user and renamed such that you will have two or more depending on how ofter you repeat the process. Once you decide which one to use, you can delete one or ones that you don't want.