The GroupWise Database Copy utility (DBCopy) copies files from a live GroupWise post office or domain to a static location for backup. During the copy process, DBCopy prevents the files from being modified, using the same locking mechanism used by other GroupWise programs that access databases. This ensures that the backed-up versions are consistent with the originals even when large databases take a substantial amount of time to copy. Starting with Support Pack 2, DBCopy is a multi-threaded application for greater efficiency.
DBCopy copies only GroupWise-recognized directories and files, as illustrated in Post Office Directory
and Domain Directory
in Directory Structure Diagrams
in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure.
DBCopy does not copy some directories:
Post office queue directories (wpcsin and wpcsout): Only post office data files and directories are copied. Queue directories are not copied.
All domain subdirectories: Only domain files are copied. Queue directories are not copied.
All subdirectories under each gateway directory in wpgate: Only gateway files are copied from each gateway directory. Queue directories of gateway directories are not copied. For example, under gwia and webac70a, gateway files are copied, but no gateway subdirectories are copied.
IMPORTANT:Starting with GroupWise 7, TSAFSGW is provided as a robust backup solution on NetWare and Linux, as described in Section 34.2, Target Service Agents. However, if you do not want to use TSAFSGW, you can use DBCopy in conjunction with your backup software of choice to back up your GroupWise system.
DBCopy can also be useful for moving domains and post office from NetWare or Windows to Linux. For more information, see Migration
in the GroupWise 7 Installation Guide.
At a command prompt, change to the directory where you installed the GroupWise agents (typically sys:\system).
Use the following command to back up a post office:
dbcopy.nlm \post_office_directory \destination_directory
or
Use the following command to back up a domain:
dbcopy.nlm \domain_directory \destination_directory
or
Use the following command to back up a remote document storage area:
dbcopy.nlm /b \storage_area_directory
You can include the /i switch in any of these commands to provide the date (mm-dd-yyyy) of the previous copy. This causes DBCopy to copy only files that have been modified since the previous copy, like an incremental backup.
DBCopy creates a log file named mmddgwbk.nnn. The first 4 characters represent the date. A three-digit extension allows for multiple log files created on the same day. The log file is created at the root of the destination directory. Include the /v switch in the dbcopy command to enable verbose logging for the backup.
After DBCopy has finished copying the post office, domain, or remote document storage area, use your backup software of choice to back up the static copy of the data.
After the backup has finished, delete the static copy of the data to conserve disk space.
Change to the directory where the DBCopy RPM is located or copy it to a convenient location on your workstation.
The DBCopy RPM (groupwise-dbcopy-version-mmdd.i386.rpm) is located in the /admin directory in your GroupWise software distribution directory if you have created one or on the GroupWise 7 Administrator for Linux CD.
Install DBCopy.
rpm -i groupwise-dbcopy-version-mmdd.i386.rpm
Change to the /opt/novell/groupwise/agents/bin directory.
Use the following command to back up a post office:
./dbcopy /post_office_directory /destination_directory
or
Use the following command to back up a domain:
./dbcopy /domain_directory /destination_directory
or
Use the following command to back up a remote document storage area:
./dbcopy -b /storage_area_directory
You can include the -i switch in any of these commands to provide the date (mm-dd-yyyy) of the previous copy. This causes DBCopy to copy only files that have been modified since the previous copy, like an incremental backup.
DBCopy creates a log file named mmddgwbk.nnn. The first 4 characters represent the date. A three-digit extension allows for multiple log files created on the same day. The log file is created at the root of the destination directory. Include the -v switch in the dbcopy command to enable verbose logging for the backup.
After DBCopy has finished copying the post office, domain, or remote document storage area, use your backup software of choice to back up the static copy of the data.
After the backup has finished, delete the static copy of the data to conserve disk space.
You might find it helpful to set up a cron job to run DBCopy regularly at a time of day when your system is not busy.
At a command prompt, change to the directory where you installed the GroupWise agents (typically c:\grpwise).
Use the following command to back up a post office:
dbcopy.exe \post_office_directory \destination_directory
or
Use the following command to back up a domain:
dbcopy.exe \domain_directory \destination_directory
or
Use the following command to back up a remote document storage area:
dbcopy.exe /b \storage_area_directory
You can include the /i switch in any of these commands to provide the date (mm-dd-yyyy) of the previous copy. This causes DBCopy to copy only files that have been modified since the previous copy, like an incremental backup.
DBCopy creates a log file named mmddgwbk.nnn. The first 4 characters represent the date. A three-digit extension allows for multiple log files created on the same day. The log file is created at the root of the destination directory. Include the /v switch in the dbcopy command to enable verbose logging for the backup.
After DBCopy has finished copying the post office, domain, or remote document storage area, use your backup software of choice to back up the static copy of the data.
After the backup has finished, delete the static copy of the data to conserve disk space.
The following startup switches can be used with DBCopy:
Indicates that DBCopy is copying a document storage area that includes BLOB (binary large object) files.
Specifies the date of the previous copy of the data. This causes DBCopy to copy only files that have been modified since the previous copy, like an incremental backup. There is no default date; you must specify a date.
Specifies the number of threads that you want DBCopy to start for copying data. The default number of threads is 5; valid values range for 1 to 10. The default value typically provides optimum performance.
Specifies verbose logging. DBCopy creates a log file named mmddgwbk.nnn. The first 4 characters represent the date. A three-digit extension allows for multiple log files created on the same day. The log file is created at the root of the destination directory. By default, DBCopy provides a normal level of logging.