Novell Home

My Favorites

Close

Please to see your favorites.

FAQ: Backing up GW 6.5 with TSAFS.NLM instead of GWTSA.NLM (FAQ-Frequently Asked Questions)

(Last modified: 14Jun2005)

This document (10095203) is provided subject to the disclaimer at the end of this document.

goal

Answer the following Frequently Asked Questions (FAQ)s about the GroupWise-enabled file system TSA (TSAFS)

fact

Novell GroupWise 6.5 Support Pack 3

TSAFS.NLM

Backing up and restoring GroupWise data that resides on a NetWare file server

Q1  What advantages can I gain by using the GroupWise-enabled file system TSA (TSAFS)?
Q2  What platforms are supported by the GroupWise-enabled TSAFS?
Q3  Where can I get the GroupWise-enabled TSAFS?
Q4  How do I enable/disable GroupWise backup support in the TSAFS?
Q5  What features of the GroupWise TSA (GWTSA) have been integrated into the file system tsa (TSAFS)?
Q6  Where can I get the GroupWise 6.5.3 agents so I can take advantage of automatic timestamping?
Q7  How does this affect GroupWise restore procedures?
Q8  What are the differences between the GWTSA and the GroupWise-enabled TSAFS?
Q9  What do I do about differences between the GWTSA and the GroupWise-enabled TSAFS
Q10 What gets put in the temporary working directory that is pointed to using the /tempdir- switch?
Q11 Does GWTSA give the backup software all of the GW database files in a synchronized state?

Q1 What advantages can I gain by using the GroupWise-enabled file system TSA (TSAFS)?

A1 GroupWise customers will benefit from the increased performance, stability, and support that the TSAFS provides.
The TSAFS and the GroupWise TSA (GWTSA) are both file-based backup agents. The current file system TSA has been improved to take advantage of the performance gains of higher-end hardware and clustering.
Adding GroupWise functionality to the existing file system TSA provides customers with ability to harness all its improvements in a live GroupWise environment.

Q2 What platforms are supported by the GroupWise-enabled TSAFS?

A2 The GroupWise-enabled TSAFS runs on NetWare versions 6.0 and forward. Customers wishing to back up GroupWise data residing on NetWare servers older than version 6.0 may continue to use the GWTSA to back up their data.

Q3 Where can I get the GroupWise-enabled TSAFS?

A3 The GroupWise-enabled TSAFS is available for download from the Novell Support Website.  The TSAFS.NLM needs to be dated December 14, 2004 or later.

Q4 How do I enable/disable GroupWise backup support in the TSAFS?

A4 To enable the GroupWise enhancements, type the following at the command line

MYSERVER:unload tsafs
Module TSAFS.NLM unloaded
MYSERVER:tsafs /EnableGW=yes

To disable the GroupWise enhancements, type the following at the command line

MYSERVER:unload tsafs
Module TSAFS.NLM unloaded
MYSERVER:tsafs /EnableGW=no


The GroupWise enhancements to the TSAFS are disabled by default. The EnableGW command line switch is a TSAFS startup switch, so the TSAFS must be unloaded and re-loaded with the switch to enable/disable the functionality. Once enabled, the GroupWise functionality will remain enabled until explicitly disabled.
To determine the state of the EnableGW switch, simply type 'tsafs' at the command line while the tsafs is loaded. Hit any key to scroll down until the EnableGW status appears on the screen.

Q5 What features of the GroupWise TSA (GWTSA) have been integrated into the file system tsa (TSAFS)?

A5 The GWTSA features that have been integrated into the TSAFS are:

  • File level backup/restore
  • GroupWise database lock/backup/unlock
  • Backup/restore timestamping of user databases (TSAFS needs GroupWise 6.5.3 engine or later in server search path for this functionality. The gwtmstmp utility may be used to manually timestamp the databases when the GroupWise 6.5.3 engine is not available. Load gwtmstmp with no parameters to print usage details to the NetWare logger screen.)

Q6 Where can I get the GroupWise 6.5.3, or later,  agents so I can take advantage of automatic timestamping?

A6 The current GroupWise 6.5. agents are available available for download from the Novell Support Website.  The GWMTA.NLM and GWPOA.NLM need to be dated December 1, 2004 or later

Q7 How does this affect GroupWise restore procedures?

A7 GroupWise restore procedures are not affected by this change, other than the fact that the TSAFS can be used to restore the GroupWise data. To restore items that have been deleted to a live system, the entire GroupWise post office must be restored to a separate area, and ConsoleOne used to configure the post office restore area. The user may then use the client to restore deleted items.
In no case should backed up GroupWise data be restored over the top of an existing GroupWise data area.

Q8 What are the differences between the GWTSA and the GroupWise-enabled TSAFS?

A8 The differences between the GWTSA and the GroupWise-enabled TSAFS are: 

  • The TSAFS uses multiple threads and read-ahead to boost performance.  The GWTSA does not.
  • In a clustered environment, the TSAFS uses the cluster name rather than the node name to expose backup resources. This facilitates the resuming of a backup job in case of failover, as the backup resource name does not change even when the node does. The GWTSA uses the node name to expose backup resources. A failed-over backup job must be restarted using the resource name based on the new node name.
  • The TSAFS supports the SMS ScanDataSetContine API, which allows a backup job to continue where it left off if interrupted. The GWTSA does not support the ScanDataSetContine API. Backup jobs using the GWTSA must be restarted from the beginning if interrupted.
  • The GWTSA exposes the root directories of domains, post offices, and libraries as high-level backup resources. The TSAFS automatically detects and handles GroupWise data as part of normal file backup.
  • The GWTSA makes multiple passes of certain GroupWise directories to reduce the number of broken links between inbox/library items and their underlying data. The TSAFS does not make multiple passes of any directories.
  • The GWTSA automatically excludes certain files that are not needed in a valid GroupWise data snapshot.
  • The TSAFS only excludes only files that it has been instructed to exclude.
  • The GWTSA can discover the location of remote storage areas, and back them up if they are on the same server. The TSAFS will only back up the data chosen by the creator of the backup job.

Q9 What do I do about differences between the GWTSA and the GroupWise-enabled TSAFS

A9 Here is how to deal with the differences between the GWTSA and the GroupWise-enabled TSAFS:

  • As the TSAFS does not know where GroupWise data resides, the backup job must be configured manually to include the location(s) of the GroupWise data and remote storage areas.
  • Because the TSAFS does not make multiple passes of the GroupWise directories, it is recommended to run GWCheck against the restored image so that broken links can be removed.
  • Because the TSAFS does not automatically skip unnecessary GroupWise files, there may be a number of error messages reported while trying to back up unneeded files which happen to be open. The backup software should provide an exclusion mechanism to allow the TSAFS to skip these files. Common examples of these files are:
    • agent log files (example: 1028mta.001 and 1028poa.001)
    • gwcache.db (WebAccess document management cache database)
    • xNStore files (transitory files used by the GroupWise agents)
    • proc and pulse.tmp files
    • QuickFinder indexes and incrementals (.idx and .inc files) which are being updated during the backup
    • files in OFFILES that are being written during the backup
      Files in the WSPCSOUT and WSPCSIN directories

       

Q10 What gets put in the temporary working directory that is pointed to using the /tempdir- switch?

The /tempdir switch designates an alternate locaction for temporary databases. If the switch is not used, the default is SYS:\SYSTEM\TSA\TEMP.

The GWTSA copies a database to the temp dir, then backs up the copy to tape. This is done to minimize the amount of time needed to hold a flaim lock on a database. The GWTSA obtains the flaim lock, then copies the database to the temp directory, releases the lock on the original, then feeds the copy to tape. That way, the lock only had to be held for the amount of time needed to perform a disk-to-disk copy, rather than a disk-to-tape copy.

Q11 Does GWTSA give the backup software all of the GW database files in a synchronized state?

It has been said in the past the GWTSA gives the backup software all the post office DB files in a synchronized state, meaning that if the backup job started at 1:00 am, the files passed to the backup software would be the files as they looked at 1:00 am and that the changes to the files are being tracked in the /tempdir- location. So this would be a synchronized set of PO files. Is this not the case? 

This is indeed not the case. The process outlined in Q10 takes place on a per-file basis, serially. In order to obtain system-wide synchronization, the GW system would need some kind of global 'bookmark' strategy, or the system would need to be halted for however long it took to back up the interdependent files. No such strategy is currently implemented. Right now, the main concern is to obtain a clean backup of each individual database. We recommend running GWCheck on a restore image to clean up any orphan references that would result due to latency. In fact, the increased performance with the TSAFS will serve to reduce the amount of orphans in a backup image, since they will have a smaller time window in which to occur. 

note

When loading GroupWise in protected memory it is necessary to load a separate instance of the Gwenn4.nlm to address space 0 for the TSAFS to work properly.  When using cluster resources you can add a Gwenn4.nlm load statement to the Resource load script.  When on a non cluster server add a load statement for Gwenn4.nlm to the autoexec.ncf.

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10095203
  • Solution ID: NOVL99547
  • Creation Date: 26Oct2004
  • Modified Date: 14Jun2005
    • NovellGroupWise Client/Admin

Did this document solve your problem? Provide Feedback