Getting back up after failure

14 Ways To Pick Yourself Back Up After A Major Failure

We all face failure at one point or another, whether it’s at work or in our personal lives. When you’ve experienced a major failure, finding the strength to move forward can be one of the most difficult parts of the process.

The members of Forbes Coaches Council have experienced their fair share of setbacks—and they've learned how to recover and keep going. If you’re facing a major failure, all hope is not lost. Read on for their best advice on picking yourself back up, then coming back stronger and better than before.

Photos courtesy of the individual members.

1. Create A Contingency Team

You don't know who your friends are until you face real adversity. Find out who is willing to serve during the most difficult times. Setbacks often reveal this, but you can ask someone and help define what you will need before the setback occurs. Ask them about scenarios and situations where they may be needed. Tell them you are setting up a "contingency team" and ask them to help and belong. - John M. O'Connor, Career Pro Inc.

2. Develop Your Personal Resilience Statement

Gain perspective and build personal resilience by asking yourself: What was outside of my control? What was within my control? What could I have done to improve the outcome? What lesson(s) did I learn? From there, turn your answers into a powerful thought process and actionable behavior that you can leverage down the road. “The next time I am faced with [this experience], I will [action/behavior].” - Morgan Massie, Avion Consulting

Forbes Coaches Council is an invitation-only community for leading business and career coaches. Do I qualify?

3. Look Back At How You Did It Before

Look back and remember a time when you were able to move past a significant challenge. What motivated you? What kept you going? What made you resilient? What learning from this past experience can you apply to this current situation? Identify a few words to describe how you felt in that past situation and keep them in mind as a source of inspiration as you move forward. - Antonia Bowring, ABstrategies LLC

4. View Failure As A Part Of The Learning Process

When you begin to see failure as part of your learning process, it opens your eyes to opportunities. With every failure, there's always an opportunity to turn it around. You mustn't miss the opportunity while wallowing in your grief. Instead, get ready for the next opportunity by focusing on establishing a plan to apply the lessons you've learned. - Janette Braverman, Leaders Leaving Legacies, LLC

5. Remember That An Action Failed, Not You

Experiencing a major failure comes with emotional turmoil—often combined with judging ourselves. The first step to come out of it is to acknowledge that it is not you, but an action that did not work out. And this feels very uncomfortable. Instead of blaming yourself, ask what kind of actions you could take right now. This helps you to shift from helplessness into resourcefulness. - Silke Glaab, SilkCelia

6. Fast Forward And Think About Your Future 'Comeback Story'

When I look back on my life now, I know when I have been proud of my response and when I wish I handled things differently. So now when I have a setback, I want to look back and have a great comeback story in the face of a setback. That's what I remind myself in the face of adversity and failure. - Lisa Rangel, Chameleon Resumes LLC

7. Keep Believing In Yourself And Your Abilities

You have just faced a major failure. The world seems bleak. How do you move forward? There are several keys, but it usually starts with remembering to still believe in yourself. Yes, this was a setback. But you are still just as talented and just as knowledgeable as before, maybe even more so! So, maybe this just wasn't the right situation. Maybe change was required. Believe—and then restart! - Ash Varma, Varma & Associates

8. Accept, Forgive And Move Forward

As wrenching as personal or professional failures can be, we have the choice as to whether we get stuck in that failure or move forward. I've only been able to move forward after a failure if I embraced my vulnerability, forgave myself (and others if they had a role), then accepted in my heart that these circumstances will move me toward an even greater future. - Lisa Walsh, Bridgepath Career Advisors, LLC

9. Shift Away From A 'Winning Versus Losing' Mindset

The story isn't written with what we're facing, but how we respond to it. After the first shock and some reflection, changing the mindset from winning versus losing to winning versus learning helps to gain our confidence back. This might help to change the mindset: What should I do and what actions should I take now, so that two years later I can say I'm happy that I've had this experience? - Elif Suner, Elif Suner MBA, M.Ed, PCC - Consulting, Training, Coaching

10. Stay Focused On Your Goal

There are many different paths to a destination. Just because one pathway didn't work doesn't mean you're off target. Reflect on what caused the misstep and explore new ways to continue moving toward the ultimate goal. You may discover that the so-called "failure" was actually a sign that you are moving out of alignment with your true goal to begin with—failure can be a wake-up call. - Tonya Echols, Vigere

11. Give Yourself Permission To Grieve

After my last failure, I made the mistake of "just pushing through it" without giving myself time to grieve. I got advice from a coach to allow myself to feel bad about it. Don't avoid the feelings—lean into them so they may wash over you and pass. Once I did, I found the natural energy and drive for a fresh start, knowing failure doesn't define me, it's how I choose to move forward afterward. - Sheryl Lyons, Culture Spark LLC

12. Focus On The Facts, Not Your Emotions

Have the humility to admit you were wrong or made some bad decisions. Be sure to separate what actually happened from the story and emotion you are wrapping around it to make yourself feel right, justified or better. Stay focused on the facts and don't feel too bad for yourself for too long, don't blame others for your situation and don't try to make like it never happened. - Lee Eisenstaedt, Leading with Courage Academy

13. Empower Yourself To Adjust Your Actions

Instead of wallowing in the misery of what went wrong, empower yourself. Make a decision to take action to ensure that mistake doesn't repeat. Assess what went wrong, and be brutally honest about what you could have done differently. Then chart a plan of action to make the needed adjustments. - Kimberly A. Ferguson, K-Ferg Training

14. Practice Gratitude

Gratitude is the No. 1 weapon to deal with failure. Most people's brains don't jump straight to how lucky they are to be able to learn from such a failure, so it's better to start small. What are the things you appreciate about your work, your personal life and the opportunities available to you? The more you look for things to be grateful for, the more you see, and soon you're back on your feet. - Scott Swedberg, The Job Sauce

7 Ways To Bounce Back Stronger After Failure

Entrepreneurs Elon Musk and Jeff Bezos actively encourage failure amongst their inner circles. Musk said, “If you’re not failing, you are not innovating,” and Bezos famously hires people who have failed. Failure has become somewhat of a cultural fetish amongst the business elite, with countless podcasts and biographies providing reassuring tales of success after darker times.

7 ways to bounce back stronger after failure

getty

But is this failure narrative fit-for-purpose for every entrepreneur, or just part of a PR campaign for a select few? Amanda Perry is an e-commerce entrepreneur and investor who knows about failure. Perry experienced public bankruptcy before proceeding to scale and sell three businesses. She now runs SOUP, a performance marketing agency, and says that failure should be recognised along the way and not just when you’re back at the top.

I interviewed Perry to learn the seven ways that anyone can bounce back from rock bottom.

Keep going

As the Winston Churchill saying goes, “if you’re going through hell, keep going.” Working through and coming out the other side of a (perceived) failure gives you the valuable element of perspective. By then you’ll be more resilient, more resourceful, and ready for your next stage.

“Regardless of the type of failure you’ve had, recognise that you have been through a traumatic event and there’s a grieving process to follow,” said Perry, who added there isn’t a right or wrong way to go through failure, but recommends that you lean into your feelings to work out what they are telling you. “You might feel ready to bounce-back quicker than you expected, but first take a step back and process what’s happened.”

MORE FROMFORBES ADVISOR

Take time to plan your next move

Perry describes the time when her chain of bakeries went into liquidation, leaving her bankrupt and at the mercy of negative local media headlines, as her wilderness years. “Going through bankruptcy is tough, even more so when the business you’ve built is actually really successful. I knew that I had it in me to do it again.”

Perry felt a strong temptation to dive straight into a new project, but she took her time. “As with relationships, rebound businesses rarely work out.” Rebound businesses can go wrong for a multitude of reasons, and they can put founders in a position to repeat previous mistakes. “Even if something seems like the ideal next step, nothing bad will happen if you don’t move straight away. So, take your time.”

Lean on your real friends

When Perry’s business was failing, she “struggled to find someone who’d been in [her] shoes. ” She wasn’t sure if no one she knew had messed up in a big way, or if they just hadn’t shared that they had. Instead of waiting for friends to reach out to her, she was open about needing help.

A strong support network is crucial for ambitious entrepreneurs, but failure can lead to pushing people away. Perhaps you feel embarrassed or, in Perry’s case, “I assumed at first that friends and family wouldn’t understand because they didn’t own their own businesses.” As she did eventually, Perry urges entrepreneurs in trouble to lean on a small circle of trusted confidantes, who “love and care for you, so they’ll learn how to support you” even if their experience isn’t shared. Don’t figure things out alone, collect advice and help from people who know you well and have your best interests at heart.

7 ways to bounce back stronger after failure

getty

Leverage your failure

Reframing your failures as great content can help you bounce back. Rather than trying to forget or gloss over mishaps, use them in the story of your career. Experiencing failure and sharing your lessons humanises you. It can help you find common ground with others. Once you’re bouncing out of a dip, look for ways to tell your story in an inspirational way, perhaps one that boosts your personal brand. Not only does this help your cause, it helps others too. “It would definitely have been an easier process if more people shared their failure along the way,” Perry adds.

The most successful people have learnt (or been media trained) to tell their story in an endearing way. “It will take time, but the story of what you’re going through really will become your greatest asset,” explained Perry. “When you’re going through tough times, this will probably be inconceivable, but when you’ve come through the worst, you’ll realise that you can use your experience as a force for good.”

Find the lessons

In every downturn, mistake or piece of bad luck there is an opportunity to learn. Perry advises to ignore that which was out of your control and instead learn how you could do better next time. “Forget the external factors that played a part and focus on the things you can change.”

Start with a fresh piece of paper and write about your struggle. Write what happened and why, the big components and the small details. Write down everything that went well and didn’t go well and make yourself some learning points and an action plan for improvement. Whatever got you down this time needn’t beat you again. Next time you’ll be prepared.

Move beyond shame

Failure is part of success and demonstrates that you have tried. The alternative is to strive for no great achievement and never experience either. 20% of businesses in the UK and USA fail within their first year. Failure isn’t a big deal, so don’t carry the shame. See success and failure through the same eyes, with as much objectivity as possible, and take neither to heart.

Whilst it’s easy to let any previous failure be a dark cloud over your every future step, the past is the past. “Don’t let any failure stop you from moving forward.” Perry admitted she lost sleep and spent hours thinking about the business that she built and the team members and suppliers who were lost along the way. “When you’ve had a failure, especially in public, you feel guilty when things are better or when you go on to achieve something else, but you have to draw a line under the past and celebrate new successes.”

Let go of others’ opinions

The key to overcoming your feeling of failure is to simply stop caring about what other people think. “Although you remember the hardest, darkest days and assume that everyone else holds them in the same regard, the reality is, they don’t.” Don’t spend your life worrying about what others might be thinking. “They have likely moved on and probably aren’t thinking about you at all.”

Don’t let pretend fear hold you back. Perry added, “The people who know you will love you regardless and the people who matter will applaud your bouncebackability and be there for your success. ”

Failure is neither glamorous nor desirable but experiencing it can be the catalyst for doing and achieving more than ever. What if your biggest failure turned out to be the best thing that ever happened to you? Following these seven steps can make that a reality.

Follow me on Twitter or LinkedIn. Check out my website or some of my other work here.

Failover and replication—Portal for ArcGIS (10.4.1)

Web GIS can be replicated by creating a standby redundancy. If the primary deployment fails or becomes unavailable, you can switch to a standby deployment.

The standby deployment typically runs on a different network or subnet, or may even be physically removed from the primary deployment location. Wherever the standby deployment is located, ensure that web GIS clients can access it when needed.

Geographical duplication

Geographical duplication can be used if the primary and secondary data centers are located in geographically distant locations. If one of the data centers is in a disaster zone, such as a hurricane or other natural disaster, you can bring the standby data center to an active state and continue working.

To successfully use geographic redundancy, certain requirements must be met.

Primary and secondary media must be identical. Each data center must contain the same number of computers that are part of the web GIS, the computer names must be the same.
Geographic redundancy typically uses an active-passive approach; therefore, data and resources must be constantly copied to the web GIS on duty.
Successful use of geographic redundancy requires third-party components. For example, a GSS or DNS server is important because it ensures a seamless experience for web GIS users when switching from a primary to a secondary deployment.

To minimize downtime in the event of a failure or disaster, you can deploy a fault-tolerant geographically dispersed web GIS. This is the most complex deployment system, requiring a large number of computers and careful maintenance. Set up two separate datacenters, each with its own resilient web GIS deployment. In each data center, all computer names must be identical, there must be no single point of failure, including with respect to data, whether it is on a failover file server or in a failover database, all web servers and load balancers, and web components. -GIS. Archives of the primary web GIS must be created continuously, and their recording in the standby web GIS in a separate data center can occur immediately or when the primary web GIS fails.

Planning a replication deployment

First determine the number of computers required. Then, plan for the following requirements to restore the duplicated web GIS:

Duplication - make sure both datacenters and both web GIS deployments have the same architecture.
Replication - create an archive of resources and data of the primary data center and restore it to the duty one.
Monitoring - Check logs to determine if a failure occurs and whether the failure requires a failover to the standby data center.
Failover - Decide whether to migrate to a different component within this web GIS or completely migrate to a web GIS in another datacenter.

Computer requirements

The number of computers depends on the web GIS setup. At a minimum, two computers are required. If your web GIS does not store much data and services and is used by a small number of employees, you can set up an initial deployment to an ArcGIS Server site from a single machine and install Portal for ArcGIS and ArcGIS Data Store on the same machine. You will need a second computer to store the standby deployment.

If web GIS is used more intensively—for example, a large number of users, a large number of items, heavy editing—an ArcGIS Server site from one or more machines will be required, and Portal for ArcGIS and ArcGIS Data Store should be installed on separate machines. If you are publishing many hosted scene layers, you may need to set up ArcGIS Data Store to store the scene cache databases on another machine. In this case, determine the required number of computers using the following formula:

 ( + 1 Portal for ArcGIS machine + ) X 2

Note that no additional ArcGIS licenses are required for a standby deployment because it is not being accessed; you will make it active only if the primary fails.

Duplicate deployments

Web GIS has various dependencies that need to be taken into account to resolve access issues. Map services access data in public folders or work through a database connection. Machines within a web GIS communicate with each other through specific URLs, such as how ArcGIS Server and Portal for ArcGIS communicate in a federated environment. Therefore, the web GIS must be completely duplicated so that all components (hostname, folder location, database name, and URL) of the web GIS in each data center are identical. Network-attached storage (NAS) locations that store file geodatabases or configuration files for Portal for ArcGIS and ArcGIS Server must have the same name in order for the on-duty web GIS to connect to the content. All web GIS components must be installed in the same directory on each web GIS. Finally, the number of computers in the data centers must be identical, because with fewer computers, performance may be degraded. Keep in mind that you can use DNS records or edit host files on computers to ensure host name consistency.

Web GIS replication

Portal for ArcGIS includes a tool - webgisdr - that allows you to export portal content, federated GIS servers, and ArcGIS Data Store resources (relational and tile cache) to a file that can be transferred to a standby computer for restoration. The tool processes Portal for ArcGIS, ArcGIS Server, and ArcGIS Data Store settings and copies all content from the portal, as well as data copied to the GIS server and data store when publishing. Keep in mind that the tool does not copy data from databases or folders registered with the GIS server, such as data from a database or file geodatabase. Replication of this data to the on-site web GIS depends on the decision of the organization.

You can run the webgisdr tool on a schedule from the Windows Task Scheduler or as a cron in a Linux environment. Additionally, the tool can be moved and run from a computer other than the one where the portal is installed, as long as it has access to the web GIS components.

You can restore archives to a standby web GIS deployment at any time. If you restore archives immediately after exporting from the primary web GIS, in the event of a primary deployment failure, the loss of data and work time will be reduced to a minimum. If archives are not restored immediately, there may be additional overhead when restoring data and switching to a standby web GIS. Also remember that if there are errors in the web GIS at the time of data archiving and the process of importing data into the standby version is automated, these errors and incorrect parameters will also be imported into the standby web GIS.

For instructions on how to replicate a web GIS deployment, see Configure failover.

Web GIS monitoring

Monitoring is very important, both in a replicated environment and in a fault tolerant environment. In a fault-tolerant environment, some parts of the deployment are able to fail over without user intervention. For example, if the primary web GIS portal fails, the software immediately switches to standby without user intervention. Similarly, the GIS server and ArcGIS Data Store components may fail, but the system will continue to function normally because there is no single point of failure. Assuming that there may be no visible disruption to the web GIS, mechanisms should be used to notify administrators of failures of individual web GIS components. For example, you can set up Python scripts to periodically query Portal for ArcGIS and ArcGIS Server logs to check for messages that indicate a failure of a particular component. If a failure occurs, the script can send an email or notify administrators to intervene. Querying logs through the Portal for ArcGIS Administration API and the ArcGIS for Server Administration API is an effective way to check for errors.

In a replicated environment, fallback requires user input; therefore, it is necessary to monitor the deployment to determine if there is a failure and make a decision to failover.

Resiliency

Web GIS, Portal for ArcGIS, ArcGIS for Server, and ArcGIS Data Store have their own recovery mechanisms. In fault-tolerant configurations, the failure of each component can be corrected without significant disruption to the web GIS.

Failing a replicated deployment from primary to standby data center typically requires the involvement of the organization's IT department, and can be done through the GSS server or global DNS. Members of an organization typically access a web GIS through multiple URLs, such as https://my.organization.com/arcgis for the public portal URL and https://my.organization.com/server for the URL public services. The GSS or the global DNS may assign an IP address to the my.organization.com hostname. If it is necessary to switch to another datacenter, GSS or the global DNS will redirect the my.organization.com hostname to the IP address associated with the standby datacenter. Clients and users will not be affected, but all requests will be sent to the data center on duty. When the primary datacenter is restored, the my.organization.com IP address may be redirected back to the original datacenter IP. You will need to reconcile the call center and primary data center so that the primary data center has all the new resources and data created while working with the call center.

If the data in any database registered with the GIS server (enterprise geodatabase or database) has been edited, use database replication tools to ensure that the original primary web GIS contains updated data. If the data in the file data sources registered with any web GIS server has changed, copy the changed files to the original folder. Finally, use the webgisdr utility to export the web GIS archive from the standby deployment and restore it to the primary deployment. The tool replicates the portal's resources, including associated hosted feature layer data and new unhosted services registered with the portal, to the original primary web GIS.

Feedback on this section?

Failover and replication—Portal for ArcGIS

An ArcGIS Enterprise deployment can be replicated by creating a standby deployment. If the primary deployment fails or becomes unavailable, you can switch to a standby deployment.

Geographical duplication

To successfully use geographic redundancy, the following requirements must be met:

The primary and secondary environments must be identical. Each datacenter must contain the same number of machines participating in the ArcGIS Enterprise deployment, and the URLs to access the components must be the same.
ArcGIS Server directories must have the same name. The directory paths can be different, but the folder name itself must be the same for the primary and secondary environments.
Folders registered with ArcGIS Server sites in primary and secondary environments can have different paths, but the folder names must be the same and they must contain exact copies of the same source data.
Geographic redundancy typically uses an active-passive approach; therefore, data and resources must be backed up to the backroom of ArcGIS Enterprise at all times.
Third-party components are required to successfully use geographic redundancy. For example, a GSS or DNS server is important because it keeps ArcGIS Enterprise users up and running when switching from a primary to a secondary deployment.

To minimize downtime in the event of a failure or disaster, you can deploy a fault-tolerant geographically remote ArcGIS Enterprise. This is the most complex deployment system, requiring a large number of computers and careful maintenance. Set up two separate datacenters, each with its own fault-tolerant ArcGIS Enterprise deployment. In each datacenter, all computer names must be identical, there must be no single points of failure, including with respect to data, whether it is on a failover file server or in a failover database, all web servers and load balancers, and components ArcGIS Enterprise. Initial deployment archives must be created continuously, and they can be written to a standby deployment in a separate datacenter immediately or when the initial deployment fails.

Planning a replication deployment

First determine the number of computers required. Then plan for the following requirements to restore a replicated ArcGIS Enterprise deployment:

Duplication—Make sure both datacenters and both ArcGIS Enterprise deployments have the same architecture.
Replication: back up the resources and data of the primary data center and restore it to the backup.
Monitor: Check logs to determine if a failure occurs and whether the failure requires a failover to a backup datacenter.
Failover - Decide whether to migrate to a different feature within ArcGIS Enterprise or migrate entirely to your ArcGIS Enterprise deployment in another datacenter.

Also, when planning a replicated deployment, remember:

The webgisdr utility does not move map service cache tiles. If you are enabling a map service or hosted tile layer caches that are used by the current deployment's GIS Server site, back up any directories where cache tiles are stored (for example, the entire arcgiscache directory in C:\arcgisserver\directories\ or /arcgis/server/usr/directories). Manually place copies in the appropriate arcgiscache directory or as a standalone deployment.
Multiple ArcGIS Server clusters are not supported when using the webgisdr utility to replicate ArcGIS Enterprise on a disabled standby deployment.
All computers in both deployments must use the same operating system. For example, a primary deployment cannot be hosted on Windows machines, while a standby deployment cannot be hosted on Linux.
The webgisdr utility records versions of ArcGIS Enterprise software components when creating a backup file. The fallback deployment into which you import the file must be the same version as the main deployment.

Machine requirements

The number of machines you need depends on your ArcGIS Enterprise setup. At a minimum, two computers are required. If your ArcGIS Enterprise deployment contains very few data and services, does not include a spatiotemporal big data store, does not include a graph store, and is used by a small number of employees, then you can set up a primary deployment on a single machine GIS Server site and Install Portal for ArcGIS and ArcGIS Data Store on the same machine. You will need a second computer to store the standby deployment.

If your ArcGIS Enterprise deployment is used more intensively—for example, a large number of users, a large number of items, heavy editing—you will need a single-machine or multi-machine GIS Server site, and install Portal for ArcGIS and ArcGIS Data Store on separate machines, also separating them from GIS Server computers. If you are publishing many hosted scene layers, you may need to set up an ArcGIS Data Store (tile cache data store) to store the scene cache databases on another machine. If you use graph storage, you will need at least one additional computer. If you will be using a spatiotemporal big data store, you will need at least one additional computer. In this case, determine the required number of computers using the following formula:

 ( + 1 Portal for ArcGIS machine + ) X 2

Note that additional ArcGIS licenses are not required for a fallback deployment because it is not accessed; you will make it active only when the primary fails.

Required settings for duplicated deployments

To provide effective disaster recovery for a replicated ArcGIS Enterprise deployment, a fallback deployment must duplicate the range of system settings, security configurations, and storage locations found in the primary deployment. Frequent backups and keeping replicated deployments in sync are the best ways to minimize downtime in the event of a failure. These considerations should be applied to all aspects of your deployment. Some examples are given below:

The following system and security settings must be configured on each deployment prior to importing webgisdr as they are different for each deployment and cannot be the same:

Proxy information transfer, including server names
privatePortalURL used for the portal and administration URL used for any federated servers portal proxy
Identify storage configuration properties for user or group storages, if applicable
SAML and LDAP authentication provider settings

Starting with version 10. 4, the list of items and parameters that must be identical in the source and target deployments when running the webgisdr utility was shortened. These changes in the latest versions of Portal for ArcGIS and ArcGIS Server are summarized in the following table:

Does the element or setting match for deployments when running the webgisdr utility?

The utility does not copy data from databases or directories registered with the hosting server or ArcGIS Server federated sites. It is the administrator's responsibility to replicate this data to the backup ArcGIS Enterprise deployment and verify that these services on the backup machine can work with the replicated data.

When you register data sources with ArcGIS Server sites, you provide certain information about the nature of access to the data. This information must be the same on the main and standby deployments. For example, if you are copying the file geodatabases used for source data to a standby deployment, the file geodatabase directory paths must be the same as the main deployment. In addition, the standby deployment must have access to the database using the same connection information that you entered when registering the database with the primary deployment's ArcGIS Server site.

You can run the webgisdr utility as a scheduled task in the Windows Task Scheduler. You can also move this utility and run it from a different machine than the one where the portal is installed, as long as the connection between the machine running the utility and ArcGIS Enterprise components is intact.

You must restore ArcGIS Enterprise backups to the standby deployment as soon as they are exported from the primary. This avoids restoring cumulative backups out of order, and means that if the main deployment fails, there will be minimal data loss or downtime. If the backups are not restored immediately, there may be additional overhead for importing the backup and switching to a standby deployment.

Also be aware that if there are errors when creating a backup in the primary deployment, and the process of importing data into the standby deployment is automated, then these errors and incorrect settings will also be imported into the standby deployment.

Instructions for replicating an ArcGIS Enterprise deployment.

ArcGIS Enterprise Monitor

Monitoring is very important in both replicated and failover environments. In a fault-tolerant environment, some parts of the deployment are able to fail over without user intervention. For example, if the primary ArcGIS Enterprise portal fails, the software immediately switches to standby without user interaction. Likewise, the ArcGIS Server and ArcGIS Data Store components may fail, but the system will continue to function normally because there is no single point of failure. Assuming there may be no visible disruption to ArcGIS Enterprise, mechanisms should be used to notify administrators of failures of individual components of an ArcGIS Enterprise deployment.

You can use ArcGIS Monitor to analyze the health of the Portal for ArcGIS, ArcGIS Server, and relational ArcGIS Data Store components of your deployment. You can also use the Portal Index Task to query the indexer status for the portal's primary machine before replicating the deployment. If you are using a registered PostgreSQL, Oracle, or Microsoft SQL Server database with your deployment, you can use one of the Egdb tasks available in the ArcGIS Monitor gallery to track statistics for those databases.

You will need to use Python or another scripting language for the ArcGIS Server REST API to automate validation of connections to registered folders, big data stores, raster data file shares, tile caches, and spatiotemporal big data stores.

In a replicated environment, fallback requires user input; therefore, it is necessary to monitor the deployment to determine if there is a failure and make a decision to failover.

If you have automatic replication configured from primary to standby, this process must be supervised to ensure that backups, file moves, and restores are successful.

Learn more about failover

ArcGIS Enterprise, Portal for ArcGIS, ArcGIS Server, and ArcGIS Data Store have their own recovery mechanisms. In fault-tolerant configurations, failure of each component can be corrected without significant disruption to ArcGIS Enterprise.

Failing a replicated deployment from primary to standby data center typically requires the involvement of the organization's IT department, and can be done through the GSS server or global DNS. Organization members typically access an ArcGIS Enterprise deployment through multiple URLs, such as https://myportalwa.organization.com/portal for the portal URL and https://myserverwa.organization.com/server for the services URL ArcGIS Server. GSS or global DNS can assign an IP address to any hostname. If it is necessary to switch to another datacenter, GSS or the global DNS will redirect the hostname myportalwa.organization.com and myserverwa.organization.com to the IP addresses associated with the standby datacenter. Clients and users will not be affected, but all requests will be sent to the data center on duty. When the primary datacenter is restored, the IP addresses of the site's primary hosts can be translated back to the IP addresses of the original datacenter. You will need to reconcile the call center and primary data center so that the primary data center has all the new resources and data created while working with the call center.

Learn more