Migrating/Moving to a higher Users OVA template

[shanee420]

Hi,

I am hoping someone can answer this. How can a customer migrate from 2,500 users CUCM OVA template to 7,500 users OVA template if they hit the capacity of the 2,500 users OVA template.

Does it involve a migration, whereby you have backup the system, create a new OVA template and restore or could it be done more simply by changing the RAM/vCPU assignment etc.

Need to this information for a phased deployment for a customer, where we are propsing them to add amore hardware servers in phase 2 when they would need more scalability, while trying to keep the disruption to a minimum.

Any help would be much appreciated.

Regards,

Zeeshan

[dakeller]

Zeeshan,

For your specific question about changing an OVA from a 2500 to a 7500 user, the answer is no, you cannot change this.  The reason is that the disk sizes do not match.  The 2500 user OVA has either an 80GB or a 60GB HDD defined.  The 7500 user OVA has 2x80GB drives.  As such, you cannot change between th 2500 user and 7500 user.  Cisco does allow changing the memory, vCPU, OS and network settings on an OVA, but not hard disk.  The only way to change the HDD size is to do a reinstall and DRS backup/restore to the larger sized OVA. 

Thanks,

Dan Keller

Technical Marketing Engineer

[martin.smith]

Daniel,

Regarding your original comment/response to this queston........ would it be possible to 'down spec'...?!!

We have a C-series that was (mistakenly) deployed with an OVA for 4vCPU, and we would like to change this 'downward' to the 2vCPU spec - so would effectively be over-spec'd for HDD. Would this be a problem?

This woud be preferable to a DRS backup/re-install/restore, even iif it is wasteful of disk space......!

BR,

ms.

(Logicalis UK)

[dakeller]

This principle also applies for backward compatibility.  So taking a 10K OVA down to 2vCPUs and 4GB of memory will change the OVA to a 7500 user OVA.  If you want to drop lower than that (but still fit in the right sized OVA), then you will have to reinstall the server on the new OVA, but all other aspects of the deployment stay the same.

Thanks,

Dan Keller

Technical Marketing Engineer