Non-production environment restarts
You can restart the tiers or just a specific tier in your dev/test and staging
environments using the My Pega Cloud self-service portal. This ability
helps you and your clients continue using environments with minimal disruption. To use the My Pega Cloud portal, have the following: Restarts should occur gracefully, without data loss, while maintaining high
availability of the environment. During environment restarts, users, both clients
and their customers, can continue to access and use their applications in the
client's Pega Cloud environments with minimal disruption. Depending on the version of Pega Platform running in your Pega Cloud environment, the management of background processing changes. Depending on the version of Pega Platform running in your
Pega Cloud environment, clients will see the following types
of impact to search functionality as a result of restarting the background
processing tiers or all of the tiers in your environment: When restarting your environment is available, depending on the type of environment,
you can use the self-service function to restart or you can restart your environment
by making a request to support. For information about when to plan a restart, see Environment availability during a restart. For information about who completes the various restart tasks, see Restart task responsibilities To self-service restart your selected non-production Pega Cloud
environment tier(s), see Restarting
your Pega Cloud environment. To request a restart of your production environment,
select New request in My
Support Portal. For information about how to submit a request, see Requesting support
services. Restarts should occur gracefully, without data loss, while maintaining high
availability of the environment. To avoid unnecessary disruption and potential conflicts,
plan your restarts for when your environment is available. Use this information to help you
understand when it makes sense to restart. You want to ensure that during an environment restart, users, both clients and their
customers, can continue to access and use their applications in the client Pega Cloud environments with minimal disruption. Restart considerations Here are some things to consider when planning your restart: You cannot restart an environment in the following cases: For a successful restart of any Pega Cloud environment, certain
tasks must be performed. During the Pega Cloud restart process, Pegasystems Inc has the responsibility for completing some tasks and you,
the client, have the responsibility for completing other tasks. Use this information to help
you to understand who is responsible for which restart action and why the actions are
necessary. Pega performs certain restart tasks and you perform
others. To ensure the following: To ensure that a restart occurs with near-zero downtime impact to
their environment, perform the following: To ensure a restart occurs with minimal impact to their environment,
perform the following: If a client
must reschedule a production restart, they should call
the Pegasystems Global Client Support contact information
listed for their region. When you want to restart your Pega Cloud environment, be sure you
understand the implications and then follow the instructions in this topic. Before you can use the portal, have the following: To restart your selected Pega Cloud environment tier, complete the
following steps: After a successful restart, you receive a notification with details
about the restart.Before you begin
Considerations for any Pega Cloud restarts
Background processing differences
Pega Cloud restart processing differences
Item Description Pega Platform 8.3 and later Tiers restart without affecting the Pega software. The
restart process includes automated stopping and restarting of
background processing. Clients must follow the recommended best
practices for using background processing as described in the
section Client responsibilities. The restart process waits up to
30 minutes for an activity that is running in the background to
finish its work; if it is not finished within 30 minutes, the
background process is terminated and the restart proceeds.
Pega Platform 8.2 and earlier Tier restarts may require client involvement as listed in the
recommended best practices for using background processing as
described in the section Client responsibilities. Impact on Search availability
Pega Cloud post-restart search differences
Item Description Pega Platform 8.1.4 and later Search is highly available throughout a restart and does not
require re-indexing Pega Platform 8.1 through 8.1.3 Search is not available until automated Search re-indexing
completes. Pegasystems Inc. applies cumulative patch releases
for the latest Pega Platform 8.x software to the environment.
For details, see Pega Cloud Services maintenance and types of
system updates. Pega Platform 7.4 and earlier Search is not available during a restart and requires clients
to re-index the search. Restarting a Pega Cloud environment
Environment availability during a restart
Restart task responsibilities
Pega Cloud restart task responsibilities
Item Description Pegasystems Inc. responsibilities Client responsibilities for Pega Platform 8.3.x and
later Client responsibilities for Pega Platform 8.2.x and
earlier Restarting your Pega Cloud environment
Previous topic Working with your environments Next topic Managing hibernated environments