Recovering a Component After Cluster Configuration Change

Recovering Your Environment 18-15

18.2.8 Recovering a Cluster

The following topics describe how to recover a cluster: ■ Recovering a Cluster After Deletion or Cluster-Level Configuration Changes ■ Recovering a Cluster After Membership Is Mistakenly Modified

18.2.8.1 Recovering a Cluster After Deletion or Cluster-Level Configuration Changes

In this scenario, the cluster has been erroneously deleted or the cluster-level configuration, such as the JMS configuration or container-level data sources, was mistakenly changed and committed. The server cannot be started or does not operate properly or the services running inside the server are not starting. You cannot ascertain what was changed. If the configuration changes are few, then the easiest way is to redo the configuration changes. If that is not feasible, use the following procedure to recover the configuration: 1. Stop the cluster. You can use the Oracle WebLogic Server Administration Console or WLST. For example, to use WLST: stopclusterName, Cluster 2. Stop the Administration Server. For example: DOMAIN_HOMEbinstopWeblogic.sh username password [admin_url] 3. Recover the Administration Server configuration by recovering the domain home backup to a temporary location. Then, restore the config directory to the following location: DOMAIN_HOMEconfig 4. Start the Administration Server. For example: DOMAIN_HOMEbinstartWebLogic.sh -Dweblogic.management.username=username -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true 5. Start the cluster. You can use the Oracle WebLogic Server Administration Console or WLST. For example, to use WLST: startclusterName, Cluster

18.2.8.2 Recovering a Cluster After Membership Is Mistakenly Modified

You can recover a cluster when the clusters membership has been mistakenly modified. For example, if you inadvertently delete a member from the cluster, you can restore the member to the cluster. Caution: Performing a domain-level recovery can impact other aspects of a running system and all of the configuration changes performed after the backup was taken will be lost. 18-16 Oracle Fusion Middleware Administrators Guide To recover the cluster membership: 1. Stop all processes, such as the Managed Servers and the Administration Server. For example, to stop the Administration Server on Linux: DOMAIN_HOMEbinstopWeblogic.sh username password [admin_url] 2. Recover the Administration Server configuration by recovering the domain home backup to a temporary location. Then, restore the config directory to the following location: DOMAIN_HOMEconfig 3. Start the Administration Server. For example: DOMAIN_HOMEbinstartWebLogic.sh -Dweblogic.management.username=username -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true The deleted member is now back in the cluster. 4. Start all processes, such as the Managed Servers. For example, to start the Managed Server on Linux, use the following script: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url 5. Start the cluster. You can use the Oracle WebLogic Server Administration Console or WLST. For example, to use WLST: startclusterName, Cluster The deleted member is now part of the cluster. 6. Start all cluster members if they are not started: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url

18.2.9 Recovering Applications

The following topics describe how to recover an application: ■ Recovering Application Artifacts ■ Recovering a Redeployed Application That Is No Longer Functional ■ Recovering an Undeployed Application ■ Recovering a Composite Application Note the following about recovering applications: ■ If the application is staged, the Administration server copies the application bits to the staged directories on the Managed Server hosts. ■ If the deployment mode is nostage or external_stage, ensure that additional application artifacts are available. For example, applications may reside in directories outside of the domain directory. Make your application files available to the new Administration Server by copying them from backups or by using a Caution: Performing a domain-level recovery can impact other aspects of a running system and all of the configuration changes performed after the backup was taken will be lost.