TID: GroupWise-enabled File System TSA (TSAFS) FAQ

Q1:

A1:

Q2:

A2:

Q3:

A3:

Q4:

A4:

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:

A5:

• 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:

A6:

Q7:

A7:

Q8:

A8:

• 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:

A9:

• 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