For about half of the year, I develop Reload, and the other half of the year, I work directly with GroupWise and Reload customers. The advantage to this approach is two-fold:

I get a real-world understanding of how customers are using GroupWise and Reload

It's going to hurt saying this . . . , I find bugs and design flaws in my own software

With all the consulting I do, I'm piling up all kinds of stories and factoids from dozens of customer consultations. Here's a few:

[ Did You Know Reload is Fast! ]

I hesitate to talk about other vendor's solutions in a public forum, so I won't. But I have no problem talking about genre's of solutions.

Last week I was consulting with a customer who had recently implemented Reload. The daily Reload backups of their 350 Gigabyte post office are taking about 1 ½ hours. And remember, every Reload backup, is effectively a full backup, but only 12% of the size of the post office.

I asked how long their previous backup product was taking. It was taking over 24 hours to get a backup with their snapshot genre solution from another vendor.

[ A Complete Push-Button Disaster Recovery Solution ]

I have now personally assisted 5 customers in creating their Reload servers into a complete Push-Button DR solution for their GroupWise system. Let me explain. Reload backs up GroupWise Domains and Post Offices. Reload cannot backup GroupWise Gateways however. So in the case of a total GroupWise system failure, or at least the failure of the server housing the GWIA, there's no Internet Mail failover.

But you can do it, and make it push-button. And I'm training a few consultants on how to do this, so you can send me an e-mail and I'll send you contact information for a consultant who can assist you. Here's a high-level look at the steps needed to make this happen:

1.Establish a new GroupWise Secondary domainⁱ in your live GroupWise system that is actually housed on the Reload server.

2.Install a GWIA on the Reload server.

3.Configure the existing GWIA and the domain that owns that GWIA to talk to one another via MTP.

4.Configure the GWIA on the Reload server as the Alternative GWIA for routing Internet mail.

5.Have the GWIA on the Reload server only run at the time that your push the button on the Reload server to run in Disaster Recovery Failover Mode for the domain that houses the actual primary GWIA. This can be done by making a simple Bash Shell Script to start the GWIA, and this script referenced in the Reload Disaster Recovery Failover Configuration menu.

[ Reload Saved My Life! ]

That's what Thys says. Read his message to the NGWListserver:

http://marc.info/?l=ngw&m=120817525625787&w=2

Enjoy