Sleeping Beauty

Reload / GroupWise Disaster Recovery is a Sleeping Beauty.

I have checked discussions entries - older than 6 months.

If I check the version number, then we are still on a low 18 number ... And of course still old Microfocus information.

No discussions? It seems to work ..

No new version? Nothing to repair or to enhance ...

A real Sleeping Beauty!


Use "Verified Answers" if your problem/issue has been solved!

  • 0  

    Hello Diethmar,

    I have very good experience with Reload. Because it is no longer maintained, I have developed my own procedures to be able to restore GroupWise quickly.

    For many OT products there is also a lack of best practice instructions. There is a task on SMT 2.0 in the forum right now, just thinking that www/root writes to / the repos and nowhere does it say to unmount the Apache path with bind mount or whatever. The same applies to Reload, GroupWise, Mobility, Vibe and many other applications.

    Ergo a best practice guide for Reload even if it is old should be written, fingers are pointing at me right now. Incidentally, I still use something with Reload or my scripts. The whole thing ultimately runs into a Ceph and is only flagt read after a snap to prevent ransomware attacks. A recovery can still take place from a read only. Only what the wizard has put into the hat can be pulled out of the hat later in the performance. George

    “You can't teach a person anything, you can only help them to discover it within themselves.” Galileo Galilei

  • 0  

    Hello Diethmar,

    I have very good experience with Reload. Because it is no longer maintained, I have developed my own procedures to be able to restore GroupWise quickly.

    For many OT products there is also a lack of best practice instructions. There is a task on SMT 2.0 in the forum right now, just thinking that www/root writes to / the repos and nowhere does it say to unmount the Apache path with bind mount or whatever. The same applies to Reload, GroupWise, Mobility, Vibe and many other applications.

    Ergo a best practice guide for Reload even if it is old should be written, fingers are pointing at me right now. Incidentally, I still use something with Reload or my scripts. The whole thing ultimately runs into a Ceph and is only flagt read after a snap to prevent ransomware attacks. A recovery can still take place from a read only. Only what the wizard has put into the hat can be pulled out of the hat later in the performance. George

    “You can't teach a person anything, you can only help them to discover it within themselves.” Galileo Galilei

  • 0  

    Diethmar - look for the prince to come along sometime in the next week or so and wake Sleeping Beauty with a kiss.   -  Pam

  • 0   in reply to   

    Diethmar - GWDR 24.4 is in the SLD  :-)

  • 0 in reply to   

    And Where are the List of Changes and new Features?

    or it is only cosmetical, the Text change from 23.4 to 24.4, OT had this Reputation on our beautiful planet with beautiful Software and the Best Integrators and Multiplikators that May be Resignate (some times)

  • 0   in reply to 

    Claude - there were only 2 fixes along with the OT branding.  Check out the readme https://www.novell.com/documentation/groupwise-disaster-recovery-24-4/gwdr24-4_release_notes/data/gwdr24-4_release_notes.html

  • 0   in reply to   

    In the next few days I will check if Reload is still Sleepy .. ah, sorry a Beauty. And what kind of prince awakened the princess ...


    Use "Verified Answers" if your problem/issue has been solved!

  • 0   in reply to   

    LOL!  The kind of prince who was able to fix 2 defects, as well as making some security fixes and added SLES15 support.