Retain archives best when archiving the items directly. However, as an alternative to archiving messages directly from GroupWise, GroupWise Disaster Recovery can run a POA that Retain can archive from. This is useful for archiving data from unstable GroupWise servers or dealing with archiving from tape backups. This is different from the GroupWise Disaster Recovery for Retain product which backs up the Retain server to the GroupWise Disaster Recovery server.
This feature sets up a POA that is active almost all the time for Retain to connect to archive from, except for short periods as GroupWise Disaster Recovery switches to the latest backup.
Since this requires running a POA, it is best to bind an extra IP address to the server for the Retain POA or you will need to make sure to change the POA settings in such a way that it does not interfere with the Access Mode POA or Disaster Recovery POA.
There must be an existing Post Office Profile and backup in place.
Retain Integration is set up on a per profile basis. Each post office profile will have to be configured to use this feature.
On the GroupWise Disaster Recovery server, go to GroupWise Disaster Recovery Administration by running:
reload
Then, navigate to Profiles > Post Office Profile, and do the following:
Select the desired profile.
Select Advanced Profile Configuration Menu.
Select Retain Integration Settings.
Select Retain to Reload Integration Configuration Wizard.
Enter the GroupWise post office name.
Enter the GroupWise domain name.
Enter the Retain Worker Password (This can be set in the Retain Console, which by default is the Retain administrator password).
Enter the IP address and ports the Retain POA will bind to. If this POA will be sharing the IP address with any other GroupWise Disaster Recovery POA, the Client, SOAP, and HTTP connection ports must be unique to avoid port conflicts. GroupWise Disaster Recovery should be installed on a machine other than the live POA server, but the standard ports are usually best used for one of the other GroupWise Disaster Recovery POAs, (Disaster, Restore, and Access). Pick a port for each connection which you know is open. Retain will pull all necessary connection information from the GroupWise Disaster Recovery server. There is no need to enter these settings into the Retain Server.
To mitigate the chances of getting Retain Worker archive errors while working against a GroupWise Disaster Recovery POA, it is STRONGLY recommended that GroupWise Disaster Recovery is set to create highly consistent backups. This setting is located at Main menu > Profiles > (select profile) > Standard > Advanced > Consistency: Set to highest.
To configure Retain:
Set the worker password on the Retain Web Console.
This can be set in the Retain Web Console under Workers > desired worker > Connection tab. By default, it is the Retain administrator password.
If the password is changed, the Worker bootstrap will need to be updated.
To remove an existing Worker bootstrap:
On the Retain server, stop tomcat.
Navigate to /opt/beginfinite/retain/RetainWorker/WEB-INF/cfg/ or wherever the worker is stored and remove RetainWorker2.cfg
Start tomcat.
Create a Profile for use with GroupWise Disaster Recovery:
Set the Scope Date Range to Scan.
If using Retain 4.1 or higher: set to New Items stores which items have been archived internally.
If using Retain 4.0.3.1 or lower: set to Publish all messages newer than last stored message (fast) and the Set Storage Flags must be set to Item Store Flag.
Create a Job as normal with Schedule, Profile, and Worker:
Under the Reload tab:
Set Enable Reload Integration.
Set Server Protocol http or https.
Set Server Host Name to the Reload server host name or IP address.
Set Server Port, default 5555.
Select Mailboxes to dredge.
Now the job will dredge the GroupWise Disaster Recovery server rather than the GroupWise server.