System 800xA 6.1 restore
Hi,
I have system 800xA version 6.1, where application is being currently developed in our cloud environment. When it is finished, it is supposed to be transferred to physical hardware which will be shipped to customer site. To make things more complicated, node setup in cloud and on physical HW is not the same. There are some nodes combined in cloud to save resources (AS/CS combination), but in final setup on physical HW they need to be separate.
I have already build the physical HW, prepared all nodes and did the restore a while ago from earlier version of the application to check if everything is working. Restore went smooth, I just allocated system functions, but did not deploy anything to nodes, exported system config aspects, then I excluded every node except for primary AS, deleted system and restored from full backup. Then I imported aspects, included all nodes and deployed functions as I needed. Finally I corrected service structure so service providers are pointing to proper nodes. All good and green.
But now I need to get newer version of the application from cloud environment to my system on physical HW and I am not sure what is the best way to do it.
Another restore will not work in my opinion, as the functions were already deployed to nodes and node setup do not match.
I was thinking about export/import of the structures from application, but I have no experience with that, and I am not sure what and how export/import to make it work.
I was also thinking about creating another system in cloud, where node setup will match node setup on physical HW, do the restore there firs, then backup and another restore into physical HW with matching nodes. Not sure if that would help as the nodes will still have functions deployed on them.
I would be really grateful for any suggestions how to best do that. I would like to avoid rebuilding nodes from scratch. Thank you in advance.
Kind regards
Ondrej
I have system 800xA version 6.1, where application is being currently developed in our cloud environment. When it is finished, it is supposed to be transferred to physical hardware which will be shipped to customer site. To make things more complicated, node setup in cloud and on physical HW is not the same. There are some nodes combined in cloud to save resources (AS/CS combination), but in final setup on physical HW they need to be separate.
I have already build the physical HW, prepared all nodes and did the restore a while ago from earlier version of the application to check if everything is working. Restore went smooth, I just allocated system functions, but did not deploy anything to nodes, exported system config aspects, then I excluded every node except for primary AS, deleted system and restored from full backup. Then I imported aspects, included all nodes and deployed functions as I needed. Finally I corrected service structure so service providers are pointing to proper nodes. All good and green.
But now I need to get newer version of the application from cloud environment to my system on physical HW and I am not sure what is the best way to do it.
Another restore will not work in my opinion, as the functions were already deployed to nodes and node setup do not match.
I was thinking about export/import of the structures from application, but I have no experience with that, and I am not sure what and how export/import to make it work.
I was also thinking about creating another system in cloud, where node setup will match node setup on physical HW, do the restore there firs, then backup and another restore into physical HW with matching nodes. Not sure if that would help as the nodes will still have functions deployed on them.
I would be really grateful for any suggestions how to best do that. I would like to avoid rebuilding nodes from scratch. Thank you in advance.
Kind regards
Ondrej
Asked 1 year ago
Answers
2
What you normally do is build your final system as you want it the export two configuration aspects from the admin structure. Then you delete the 800xA configuration, restore the backup from the other system and then restore the two aspects back to the admin structure. You might need to delete the configuration aspects from the admin structure which came from the backup. The procedure is described in th upgrade manual search for “node consolidation”.
2
Different geometries in engineering vs production causes trouble until we have the Import System function ready that shall assist with transforming a backup to fit the destination.
Deploy is a one way street... images of non-deployed nodes may become your best friend.
I also suggest exercising in export/import and learn the traditional dependency chains between Object Type Structure, Control Structure and Functional Structure.
With the correct approach and engineering methods, export/import should be an open path saving you from the very disruptive backup/restore alternative.
Deploy is a one way street... images of non-deployed nodes may become your best friend.
I also suggest exercising in export/import and learn the traditional dependency chains between Object Type Structure, Control Structure and Functional Structure.
With the correct approach and engineering methods, export/import should be an open path saving you from the very disruptive backup/restore alternative.
0
Hi!
Hard to tell, depending on what's changed.
Generally do frequent backups as mentioned in this thread.
From the application standpoint it's usually:
PG2 graphics I'll go for Export/Import with the I/E Tool. You can make exports of "old" graphics before importing new and revert if necessary.
Regarding the Control Structure I would investigate the depth of changes before a go-a-head.
(Added applications or controllers are easy to import, revisions and changes to libraries etc could be trickier.)
Always keep a log of changes, it will make your decisions easier and quicker.
Making good use of version-handling of libraries will make life easier...
Testing procedure in a virtual environment before rolling out to production is good pratice.
Regards!
Hard to tell, depending on what's changed.
Generally do frequent backups as mentioned in this thread.
From the application standpoint it's usually:
PG2 graphics I'll go for Export/Import with the I/E Tool. You can make exports of "old" graphics before importing new and revert if necessary.
Regarding the Control Structure I would investigate the depth of changes before a go-a-head.
(Added applications or controllers are easy to import, revisions and changes to libraries etc could be trickier.)
Always keep a log of changes, it will make your decisions easier and quicker.
Making good use of version-handling of libraries will make life easier...
Testing procedure in a virtual environment before rolling out to production is good pratice.
Regards!
Answered 1 year ago
Add new comment