51.2 GroupWise Database Copy Utility

You can use the GroupWise Database Copy Utility (DBCopy) to back up your GroupWise system if you would prefer not to purchase a third-party backup solution. For more information, see Backing Up GroupWise Databases.

51.2.1 DBCopy Functionality

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 folders and files in domain and post office folders. DBCopy does not copy some folders:

Post office queue folders (wpcsin and wpcsout): Only post office data files and folders are copied. Queue folders are not copied.
All domain subfolders: Only domain files are copied. Queue folders are not copied.
All subfolders under each GWIA folder in wpgate: Only GWIA files are copied from each GWIA folder. Queue folders of GWIA folders are not copied. For example, under gwia, GWIA files are copied, but no GWIA subfolders 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.

51.2.2 Using DBCopy on Linux

To use DBCopy on Linux:

Change to the following folder:
```
/opt/novell/groupwise/agents/bin
```
Use the following command to back up a post office:
```
./dbcopy /post_office_folder /destination_folder
```
or

Use the following command to back up a domain:
```
./dbcopy /domain_folder /destination_folder
```
or

Use the following command to back up a remote document storage area:
```
./dbcopy -b /storage_area_folder /destination_folder
```
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 folder. 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.

IMPORTANT:If you are planning on running dbcopy in a script outside of the /opt/novell/groupwise/agent/bin directory, then you need to add the following export to your script:

export LD_LIBRARY_PATH=/opt/novell/groupwise/agents/lib

51.2.3 Using DBCopy on Windows

To use DBCopy on Windows:

At a command prompt, change to the folder 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_folder \destination_folder
```
or

Use the following command to back up a domain:
```
dbcopy.exe \domain_folder \destination_folder
```
or

Use the following command to back up a remote document storage area:
```
dbcopy.exe /b \storage_area_folder \destination_folder
```
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 folder. 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.

51.2.4 Using DBCopy Startup Switches

The following startup switches can be used with DBCopy when you are preparing to back up GroupWise data:

Linux DBCopy	Windows DBCopy	Explanation
--b	/b	Backup of BLOB files in a document storage area
-i	/i	Incremental backup
-j	/j	DBCopy priority control
-t	/t	Number of threads
-v	/v	Verbose logging
-w	/w	Continuous logging to the screen

-b

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.

-i

Specifies the date of the previous copy of the data. This causes DBCopy to copy only files that have the specified date or newer, such as an incremental backup. There is no default date; you must specify a date or an increment backward from today. Valid increments are -1 to -31.

	Linux DBCopy	Windows DBCopy
Syntax:	-i mm-dd-yyyy -i -days	/i mm-dd-yyyy /i -days
Example:	-i 5-18-18 -i -1	/i 10-30-2015 /i -7

Linux DBCopy

Windows DBCopy

Syntax:

-i mm-dd-yyyy

-i -days

/i mm-dd-yyyy

/i -days

Example:

-i 5-18-18

-i -1

/i 10-30-2015

/i -7

-j

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.

-t

Specifies the number of threads for 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

-v

Turns on 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 domain, post office, or document storage area folder. In addition to status and error messages, it lists any remote document storage areas associated with a post office.

-w

Turns on continuous logging to the screen.