Groupwise 7 Documentation:
http://www.novell.com/documentation/gw7/gw7_admin/index.html?page=/documentation/gw7/gw7_admin/data/bqpw8ct.html 

A link to a cool solutions article for adding dbcopy script to te crontab:
http://www.novell.com/communities/node/2611/incremental-groupwise-database-backups

A Novell forum post on dbcopy I found helpful:
http://forums.novell.com/novell-product-support-forums/groupwise/groupwise-7x/gw7-install-setup-admin/108420-dbcopy-cron-oes-linux.html#post443320

groupwise 7.01 one Suse 9 the gwdva randomly crashes or begins using 99% system utilization, and also renders web access non functional. users attempt to login and receive an error stating unable to communicate with GroupWise WebAccess Agent.

 Restarting the gwdva temporarily elevates the problem.

Stop gwdva with the following:

/opt/novell/groupwise/agents/bin/grpwise stop gwdva.groupwise

 Start gwdva with the following:

/opt/novell/groupwise/agents/bin/grpwise start gwdva.groupwise

I have not found anywhere in the novell documentation (honestly I haven’t looked very hard) yet but apparently when using Universal Password, and configuring Groupwise to authenticate using LDAP it uses two concurrent logins.

 So in other words in this configuration if you limit concurrent logins to 1 your users cannot login to both EDirectory and Groupwise at the same time. GWIA will give you a wonderful error:53 which according to the TID I saw leads you to beleive the users password is expired, and I do suppose that LDAP returns the same error code for expired and concurrent logins? MAYBE??

Not that it’s a huge deal but so much for limiting your users to kly logging into one comptuer at a time. Well they are limited to two now! NICE!