Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    7
  • Subscribers subscribers
    6
  • Views views
    668
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Migrating & Upgrading the GroupWise server from Reload/GWDR perspective

Andy Konecny
 

Up to-date Reload/GWDR appliance for a GroupWise 14R2 system, preparing to migrate GroupWise to a new box as GW 18.4

and I haven't played with Reload much yet.

I've done plenty of GroupWise migrations like this without reload, so I could do the traditional dbcopy route and then update the Domain&PO, but then how do I get Reload working towards the new box?

or I would assume there is a way to use the DR part, but I'm not seeing in the Docs for Live to Live, only the Kaboom recovery angle.  
    I see KB 7019446 that appears to address most of it, though it is a bit old, and I'm not seeing anything about the Domain migration which I need to do in the same time frame as well.

Any general ideas of pointers for either/both paths?

________________________

Andy of KonecnyConsulting.ca in Toronto
Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0  

    Andy - if you use dbcopy to copy GW from the current server to the new one and then get it all up and running, you would just need to go into GWDR and change the IP addresses / paths to the new server.  Sadly I am not sure how to "recover" from GWDR to a new server. - Pam

  • 0   in reply to   

    So DBcopy to new box, and then install newer version of GW code onto Retain?   IP is getting moved, though I see a mount point on the GW server that likely needs to be created as well.  The Docs really have a gap here.

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0   in reply to   

    Ok, now you have confused me.  How did Retain get into this mix?  If you mean Reload, yes that is the case.  The reload server could even still use the older version of GW to back up your newer install on the other box, I believe.

  • 0   in reply to   

    Sorry, me juggling too much today.  R thing vs the other R thing and I just mixed it up.  Both are involved, but I think I have Retain side figured out.  The names start having us sound like pirates,  arr

    I take it we will still need to update the GroupWise software installed on the Reload(not Retain) box before long, perhaps after getting the OS a little more up to date.

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0   in reply to   

    LOL  I have the same problems with those pesky R products.  Yeah it can't hurt to update the GW software on the Reload box.

  • 0   in reply to   
    Unknown said:
    pesky R products

    The real reason they renamed them?  Too much pirate talk?

    In meeting with that client as you responded, with your first response being After I had emailed them about not getting an answer and time to discuss our options. Academic licensing, so more involved if we were to open a case.

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0   in reply to   

    To bring them into the GroupWise family is the reason we were given.  To confuse the heck out of everyone I think is the real reason  :-)

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.