You can use the GroupWise Database Copy Utility to back up your GroupWise system if you would prefer not to purchase a third-party backup solution, as recommended in Section 31.0, Backing Up GroupWise Databases.
IMPORTANT:If you want to move domains and post offices from NetWare or Windows to Linux, see the GroupWise Server Migration Guide. The migration process includes DBCopy startup switches that are not described in this GroupWise 2012 Administration Guide because they are used only for migration.
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. DBCopy is a multi-threaded application that provides highly efficient copying of large quantities of data.
DBCopy copies only GroupWise-recognized directories and files, as illustrated in Post Office Directory
and Domain Directory
in Directory Structure Diagrams
in GroupWise 2012 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, gateway files are copied, but no gateway subdirectories are copied.
When planning disk space for your backups, you should plan to have at least three times the size of a post office. This accommodates the post office itself, the backup of the post office, and extra space for subsequent growth of the post office.
Typically, domains grow less than post offices, so domain backups should occupy somewhat less 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 in the downloaded GroupWise 2012 software image.
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 /destination_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.
To remind yourself of these options when you are at your Linux server, view the dbcopy man page.
DBCopy creates a log file named mmddgwbk.nnn. The first four 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:\Program Files\Novell\GroupWise Server\Agents).
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 \destination_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 four 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 when you are preparing to back up GroupWise data:
|
Linux DBCopy |
Windows DBCopy |
Explanation |
|---|---|---|
|
Backup of BLOB files in a document storage area |
||
|
Incremental backup |
||
|
DBCopy priority control |
||
|
Number of threads |
||
|
Verbose logging |
||
|
Continuous logging to the screen |
Indicates that DBCopy is copying a document storage area, which includes BLOB (binary large object) files. Use this switch only when you need to copy BLOB 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.
|
Linux DBCopy |
Windows DBCopy |
|
|---|---|---|
|
Syntax: |
-i mm-dd-yyyy |
/i mm-dd-yyyy |
|
Example: |
-i 5-18-2012 |
/i 10-30-2012 |
Raises the priority of DBCopy processing. By default, if DBCopy detects that a POA is running, it lowers its own priority so that it does not interfere with POA processing. If DBCopy runs at night, when GroupWise users are not active, use the -j switch so that DBCopy does not lower its own priority. This speeds up DBCopy processing.
Specifies the number of threads that you want DBCopy to start for copying data. The default number of threads is 5. Valid values range from 1 to 10.
|
Linux DBCopy |
Windows DBCopy |
|
|---|---|---|
|
Syntax: |
-t number |
/t number |
|
Example: |
-t 10 |
/t 10 |
Specifies verbose logging, which provides more detail than the default of normal logging. DBCopy creates a log file named mmddgwbk.nnn. The first four 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.
Turns on continuous logging to the screen.