{"id":39427,"date":"2025-04-09T21:30:21","date_gmt":"2025-04-09T20:30:21","guid":{"rendered":"https:\/\/fos.consulting\/?page_id=39427"},"modified":"2025-04-09T21:39:00","modified_gmt":"2025-04-09T20:39:00","slug":"plan-de-contingencia","status":"publish","type":"page","link":"https:\/\/fos.consulting\/en\/plan-de-contingencia\/","title":{"rendered":"Contingency plan"},"content":{"rendered":"
<\/div><\/div><\/div>
\n\t
\n\t\t
\n\t\t\t
\n\t\t\t\t\n
\n\t
\n\t\t

1. Introduction<\/h3>\n

The purpose of this Plan is to guarantee the operability of the Agora software in situations of contingency or infrastructure failure.<\/p>\n

2. Outreach<\/h3>\n

This plan applies to the following components:<\/p>\n

    \n
  • \n

    Software<\/strong>\u00c1gora POS (both cloud and hybrid versions)<\/p>\n<\/li>\n

  • \n

    Infrastructure<\/strong>: Servers, databases, communications, POS devices<\/p>\n<\/li>\n

  • \n

    Points of sale<\/strong>: Owned, franchised or mixed model shops<\/p>\n<\/li>\n

  • \n

    Services<\/strong>: Backend, Frontend, API, integrations (Sihot, Delivery, payments, etc.)<\/p>\n<\/li>\n<\/ul>\n

    3. Critical risk analysis<\/h3>\n
    \n
    \n\n\n\n\n\n\n\n\n\n\n
    Risk<\/th>\nImpact on operation<\/th>\nLevel of criticality<\/th>\nMitigation strategy<\/th>\n<\/tr>\n<\/thead>\n
    Failure in the main cloud<\/td>\nTotal standstill<\/td>\nHigh<\/td>\nHA, replication and automatic migration<\/td>\n<\/tr>\n
    Local POS failure<\/td>\nPartial shutdown<\/td>\nMedium<\/td>\nOffline mode enabled, remote support<\/td>\n<\/tr>\n
    Cyber-attack (ransomware, DDoS)<\/td>\nHigh<\/td>\nHigh<\/td>\nFirewall, immutable copies, segmentation<\/td>\n<\/tr>\n
    Internet outage in premises<\/td>\nMedium<\/td>\nHigh<\/td>\nOffline operation, subsequent synchronisation<\/td>\n<\/tr>\n
    Database corruption<\/td>\nVery high<\/td>\nUnder<\/td>\nBackups + automatic validation<\/td>\n<\/tr>\n
    Human failure at headquarters<\/td>\nMedium<\/td>\nMedium<\/td>\nStandard Operating Procedures<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

    4. Backup strategy<\/h3>\n
      \n
    • \n

      Frequency<\/strong>:<\/p>\n

        \n
      • \n

        Full daily + hourly incremental<\/p>\n<\/li>\n<\/ul>\n<\/li>\n

      • \n

        Retention<\/strong>:<\/p>\n

          \n
        • \n

          30 days for premium SLA customers<\/p>\n<\/li>\n<\/ul>\n<\/li>\n

        • \n

          Location<\/strong>:<\/p>\n

            \n
          • \n

            Local + remote ( S3)<\/p>\n<\/li>\n<\/ul>\n<\/li>\n

          • \n

            Immutable backups<\/strong>:<\/p>\n

              \n
            • \n

              Activated with minimum retention of 7 days<\/p>\n<\/li>\n<\/ul>\n<\/li>\n

            • \n

              Verification<\/strong>:<\/p>\n

                \n
              • \n

                Daily automated recovery test<\/p>\n<\/li>\n

              • \n

                Quarterly complete restorations<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n

                5. High availability infrastructure (HA)<\/h3>\n
                  \n
                • \n

                  Cloud<\/strong>Redundant architecture in different availability zones<\/p>\n<\/li>\n

                • \n

                  Database<\/strong>Cluster with automatic failover<\/p>\n<\/li>\n

                • \n

                  Load balancers<\/strong><\/p>\n<\/li>\n

                • \n

                  Proxmox + Ceph<\/strong>: node, network or storage fault tolerance<\/p>\n<\/li>\n

                • \n

                  UPS and electrical switching<\/strong> in physical facilities<\/p>\n<\/li>\n

                • \n

                  Proactive monitoring<\/strong> 24\/7 (Prometheus)<\/p>\n<\/li>\n<\/ul>\n

                  6. Recovery targets<\/h3>\n
                  \n
                  \n\n\n\n\n\n\n\n
                  Type of incident<\/th>\nRTO (Recovery Time)<\/th>\nRPO (Maximum Data Loss)<\/th>\n<\/tr>\n<\/thead>\n
                  Total cloud service failure<\/td>\n\u2264 1 hour<\/td>\n\u2264 15 minutes<\/td>\n<\/tr>\n
                  Local impact on POS<\/td>\n\u2264 30 minutes<\/td>\n\u2264 1 hour<\/td>\n<\/tr>\n
                  Restore from backup<\/td>\n\u2264 4 hours<\/td>\nLast copy available<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

                  7. Recovery procedures<\/h3>\n
                    \n
                  • \n

                    Partial failure (local)<\/strong>Remote intervention in <15 min. Activation of offline mode.<\/p>\n<\/li>\n

                  • \n

                    Total failure (cloud)<\/strong>automatic switchover to the contingency environment.<\/p>\n<\/li>\n

                  • \n

                    Restore from backup<\/strong>: snapshot upload + synchronisation of subsequent changes.<\/p>\n<\/li>\n

                  • \n

                    Crisis communication<\/strong>:<\/p>\n

                      \n
                    • \n

                      Email, telephone and direct channel to our technical team.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n

                      8. Validation and revision of the plan<\/h3>\n
                        \n
                      • \n

                        Scheduled tests<\/strong>:<\/p>\n

                          \n
                        • \n

                          Full restoration: Quarterly<\/p>\n<\/li>\n

                        • \n

                          Infrastructure crash drill: Annual<\/p>\n<\/li>\n<\/ul>\n<\/li>\n

                        • \n

                          Security audits and backups<\/strong>Monthly<\/p>\n<\/li>\n

                        • \n

                          Review of the plan<\/strong>Annual or in case of critical changes<\/p>\n<\/li>\n<\/ul>\n

                          9. Additional information for the customer<\/h3>\n
                            \n
                          • \n

                            Access to the fos.consulting technical portal (FAQs, updates, service status)<\/p>\n<\/li>\n

                          • \n

                            Possibility of specific training for the client's team<\/p>\n<\/li>\n<\/ul>\n\t<\/div>\n<\/div>\n\n\n\n\n\t\t\t<\/div> \n\t\t<\/div>\n\t<\/div> \n<\/div><\/div>","protected":false},"excerpt":{"rendered":"1. Introducci\u00f3n El presente Plan tiene como finalidad garantizar la operatividad del software \u00c1gora en situaciones de contingencia o fallo de infraestructura. 2. Alcance Este...","protected":false},"author":162,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-39427","page","type-page","status-publish"],"jetpack_sharing_enabled":true,"jetpack-related-posts":[],"jetpack_shortlink":"https:\/\/wp.me\/PfY7gm-afV","_links":{"self":[{"href":"https:\/\/fos.consulting\/en\/wp-json\/wp\/v2\/pages\/39427","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fos.consulting\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/fos.consulting\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/fos.consulting\/en\/wp-json\/wp\/v2\/users\/162"}],"replies":[{"embeddable":true,"href":"https:\/\/fos.consulting\/en\/wp-json\/wp\/v2\/comments?post=39427"}],"version-history":[{"count":4,"href":"https:\/\/fos.consulting\/en\/wp-json\/wp\/v2\/pages\/39427\/revisions"}],"predecessor-version":[{"id":39434,"href":"https:\/\/fos.consulting\/en\/wp-json\/wp\/v2\/pages\/39427\/revisions\/39434"}],"wp:attachment":[{"href":"https:\/\/fos.consulting\/en\/wp-json\/wp\/v2\/media?parent=39427"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}