backup and recovery

[#1]

While running the backup command for apigee components, except apigee-cassandra & PostgresSQL all other components are being stopped first and backup and then restart the component.

How to refrain stopping apigee component during backup?

For example: While backup of edge-management-server (or) edge-ui, and backup stops these services then it would be causing big trouble.

Do we have any standard procedure to bounce the servers for backup process?

[latheefdudakula]

Hi Suresht,

Are you worried about the API traffic being interrupted during the backup ?

If so , components impacting the API traffic are router and message processor, Cassandra based on your traffic management policies.

To avoid any traffic interruption, you can do as follows(considering your on private cloud)

Disable the reach-ability of the router components you intend to take a back-up , by this the traffic will not be routed to this router and no interruption to API traffic. Re-enable it once the backup is completed. Do it for all other router node one after the other.

For message-processor, stopping the message processor will solve the problem because from 4.17.05 reach-ability is disabled when we stop message processor and most importantly ; message processor will stop only after processing in-flight transactions.

For Cassandra or other components , do it in rolling fashion where at-least one node (respective components) is running so you'll not see bring any outage to the components as the others are running.

Hope this answers your question.

Thanks.

[#3]

Thanks Latheef!!