How to Access a Backup When the Password is Not Known or Forgotten

  • 7019390
  • 05-Nov-2008
  • 29-Aug-2017


All versions of Reload


How can I log into a Reload backup if I have forgotten my password at the time the backup was made. 


One way to access a backup without the password is to use Restore Mode.  In Restore Mode, the user is connected to the live post office while still accessing the backup.  The underlying architecture and setup varies depending on whether the production post office is on Linux or NetWare/Windows. 

If on NetWare/Windows, the Restore Mode POA must be configured.  On Linux, Reload leverages the GroupWise Restore Area Management feature.

For some customers with post offices on Windows Server 2008 R2, Restore Mode won't work (Restore Mode POA won't load and returns segmentation faults).  Under such circumstances, there are two other ways but they are only as a last resort.  The first is the least risky to the production GroupWise system and is the preferred method of the two Marverick options.


Take the production POA down.Enable disaster recovery mode and then make the user password change within ConsoleOne on the production domain. 

1.  The agents' "Network Address" settings should all reference DNS names rather than IP addresses, which is the recommended way to configure the system for DR

2.  Change the IP address for the post office agent in the DNS "A" record to reflect the IP address of the Reload DR POA.

3.  Enable DR on Reload for that post office.  This will also load the DR POA.

4.  Restart the MTA on the production system. Now the MTA should be communicating with the DR POA.

5.  Change the user password in ConsoleOne. It puts an admin message into the WPCSIN/2 directory for the domain. The MTA picks it up and sends it over to the DR POA, which writes the change to the user db. Now the user can access the mailbox with the new password

Obviously, DR can't be enabled without affecting all of the other users on the post office.  If you choose to do this during production hours, you'll also have to migrate ALL of the users' messages that were created during the DR period; otherwise, this should be done during non-production work hours. It really is the cleanest way to do it, but if that isn't feasible, then you'll need to go into a full DR mode that includes running the MTA and ConsoleOne on the Reload server.

Why does it have to be done this way?  Because the user's GroupWise password is stored in the user database and not in the domain nor the post office database.  You have to make the change in ConsoleOne and then allow the MTA to pass the change onto the POA, which writes the new password in the user database.


This step makes changes to the backed up domain and post office databases, so it is the least preferred method.  If those databases ever had to be migrated or restored to production, then it would wreak some havoc until they were re-configured within the production ConsoleOne with the production domain and post office paths.

But, if desperate times calls for desperate measures, here is what you do:

1. Install ConsoleOne on the Reload server.

2. Install the GroupWise administration on the Reload server.

3. Configure the domain profile for disaster recovery.

4. Configure the post office profile for disaster recovery. Make sure the POA's "MTA" setting is pointing to the DR MTA's IP address and not the production MTA.

5. Go into ConsoleOne that you installed on your Reload server and connect it with the domain database that is loaded in DR.

6. Edit the Domain object. Change its directory path to point to /[domain profile]/connect/current.

7. Edit the Post Office object. Change its directory path to point to /[post office profile]/connect/live.

8. Edit the MTA object. Change the MTA network address to the Reload DR MTA's IP address.

9. Edit the POA object. Change the POA network address to the Reload DR POA's IP address.

10. Enable DR on the domain and PO profile, which should load the MTA and the POA for them.

11. Go back into ConsoleOne and change the user password.

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 692.