-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Poly Video Conferencing
- Collaboration & Conferencing Platforms
- CMA4000: Backup and restore on a different CMA device.
Create an account on the HP Community to personalize your profile and ask a question
02-05-2013 03:23 AM
Hi Guys,
recently a customer approached my company asking to provide redundancy on a CMA 4000 device... (unfortunately they dont want to invest on a CMA5000).
We plan to provide one more CMA 4000 at the same software versionm and to keep it updated uploading system backup weekely... however i never tried to upload a system backup from one CMA to another... does it works? Or it's hardware dependant?
Thanks for your support.
Regards
-dan
Solved! Go to Solution.
02-09-2013 09:04 PM
Unfortunately the restore would work, but after the reset of the CMA, you would brick it. The reason being database user accounts are different in each CMA server. Altough the names are the same, plcmuser for example, SQL does reference the user account by this name. The Master database contains the user accounts and the related GUID - global unique ID. Windows AD uses this same concept. The names are there for us simple human beings. This is why you need sysadmin level rights to create user accounts in SQL, because of the interaction with the Master DB. When you restore the DBs from one SQL server to another, the internal references to the GUIDs are not updated as the Master DB did not change as well.
What I have done in the past is to set one CMA server up and use external SQL for DBs. Then you can use whatever SQL replication or HA feature you like. In my case, we used SQL log shipping to mirror the database to another location. There we have another CMA turned off. If the primary CMA server went down, changes were made to failover to the other SQL server. The we would bring up the passive CMA and configure it for the failed over SQL server. Of course this is a manual process, but this gave us geographic redundancy which was more important.
S.
Didn't find what you were looking for? Ask the community