Re-Creating the Domain Administration Server (DAS)

For mirroring purposes, and to provide a working copy of the DAS, you must have:

One host (olddashost) that contains the original DAS.
A second host (apphost) that contains a cluster with server instances running applications and catering to clients. The cluster is configured using the DAS on the first host.
A third host (newdashost) where the DAS needs to be re-created in a situation where the first host crashes or is being taken out of service.

Note - You must maintain a backup of the DAS from the first host using the backup-domain(1) subcommand as described in To Back Up a Domain. You can automatically maintain a backup of the DAS using the automatic backups feature of Oracle GlassFish Server.

To Migrate the DAS

The following steps are required to migrate the DAS from the first host (olddashost) to the third host (newdashost).

Install GlassFish Server on newdashost just as it was installed on olddashost.
This is required so that the DAS can be properly restored on newdashost without causing path conflicts.
Use the restore-domain subcommand to restore the latest backup file onto newdashost.
For example:
```
asadmin> restore-domain --backupdir /net/backups.example.com/glassfish
```
This example assumes that backups are stored in a network-accessible location. If this is not the case, manually copy the latest backup file from offline storage to a directory on newdashost.
If you have both configuration-only and full backups, restore the latest full backup first. Then, restore the latest configuration-only backup if it is newer than the latest full backup. Use the --backupconfig option of the restore-domain subcommand to specify the appropriate full and configuration-only backups.
You can backup any domain. However, while re-creating the domain, the domain name should be same as the original.
Stop the domain on olddashost, if it is running.
Start the domain on newdashost by using the start-domain(1) subcommand.
For example:
```
asadmin> start-domain domain1
```
If the domain on olddashost was centrally administered, set up centralized administration on newdashost.
See Chapter 2, Setting Up SSH for Centralized Administration, in Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide for instructions.
Verify that instances on other hosts are visible to the new DAS on newdashost:
```
asadmin> list-instances --long
```
Update instances on apphost to communicate with the new DAS.
If the domain uses centralized administration, use the update-admin-server-coordinates subcommand on newdashost:
```
asadmin> update-admin-server-coordinates
```
If the domain does not use centralized administration, use the update-admin-server-local-coordinates subcommand on apphost:
```
asadmin> update-admin-server-local-coordinates
--adminhost host3 --adminport port-number node-name
```
Use the new DAS to restart clusters and standalone instances on apphost:
Restarting the clustered and standalone instances on apphost triggers their recognition of the new DAS on newdashost.
1. Use the list-clusters subcommand to list the clusters in the domain.
2. Use the stop-cluster subcommand to stop each cluster.
3. Use the list-instances subcommand to list the instances in the domain.
4. Use the restart-instance subcommand to restart each standalone instance.
5. Use the start-cluster subcommand to start each cluster.
  If the domain does not use centralized administration, use the start-local-instance subcommand to start the cluster instances on apphost.
Verify that instances on apphost are running:
```
asadmin> list-instances --long
```
Decommission and discontinue use of the DAS on olddashost.

Skip Navigation Links
Exit Print View
	Oracle GlassFish Server 3.1 Administration Guide