Chapter 3 - File Layouts and Online Indexes
This chapter provides an overview of the file layouts for StreetTalk for Windows NT, including StreetTalk Directory Assistance (STDA), and Intelligent Messaging (IM) installed on a Windows NT server. General guidelines are included for backup and restore of StreetTalk for Windows NT, STDA, and IM files. This chapter also contains an overview of the NetWorker file and media indexes.
Note: For detailed instructions on backup and restore procedures for Windows NT and VINES servers, refer to Chapter 4 and Chapter 5 of this guide.
StreetTalk for Windows NT File Layout
By default, the StreetTalk for Windows NT file structure is installed on, and therefore resides on, the Windows NT boot drive. If you do not want to install StreetTalk for Windows NT on the boot drive, you can install it on any local drive that you specify. If you accept the default directory structure during installation, the boot drive contains the Program Files directory and the Banyan subdirectory. For example, if drive C:\ is your boot drive, your StreetTalk for Windows NT files reside on:
C:\Program Files\Banyan\...
If you specify another local drive, or a directory structure other than the default, your files reside where you specify.
The directories containing the executable files, log files, and databases for StreetTalk for Windows NT, STDA, and IM reside beneath the Program Files\Banyan directory structure (or other structure that you specify). These directories are:
\BIN
\DATA
\FILE
\SYSERROR
\VFILES
\VNS
Backing Up StreetTalk for Windows NT and the Windows NT Registry
When backing up StreetTalk for Windows NT software, be aware of the following:
If you are doing a scheduled backup with NetWorker and Save Set = All (the default), the Registry is always automatically backed up. If you change the Save Set default, the Registry is not automatically backed up. You can back up the Registry by entering REGISTRY:\ in the Save Set field along with other information to be included in the backup. If you initiate a backup from NetWorker User, the Registry is selectable for backup, but you must mark it. If you do not mark the Registry, it is not included in the backup.
The Windows NT Registry is a database that contains details of your computer's configuration. If you do not back up the Windows NT Registry, you can not restore StreetTalk for Windows NT or StreetTalk groups.
Restoring StreetTalk for Windows NT Files and StreetTalk Groups
When restoring StreetTalk for Windows NT files, you must restore all subdirectories that reside in the Program Files\Banyan directory. In order to restore StreetTalk groups, you must restore:
All subdirectories that reside in the Program Files\Banyan directory The Windows NT Registry.
Perform the restore from the StreetTalk for Windows NT server.
Intelligent Messaging and StreetTalk Directory Assistance File Layouts
When either the STDA service or IM service is created on the Windows NT server, the default VnsData directory is created with a corresponding subdirectory. The following default directory structure is created on the drive you selected when you created the service:
<drive letter>:\VnsData\STDA
Note: If you specified a local drive other than C, that drive appears in the path.
The STDA subdirectory contains STDA service data files.
If the IM service is created before the STDA service, the following default directory structure is created:
<drive letter>:\VnsData\BMS...
The BMS subdirectory contains the mail service data files.
You must back up the entire VnsData directory because the STDA and IM databases reside in the VnsData\STDA and VnsData\BMS subdirectories, respectively. To successfully restore either STDA or IM, you need all the files contained in the STDA or BMS subdirectory.
Note: Do not use File Manager or Windows Explorer to copy files to and from the BMS directory instead of backing up and restoring these files. You cannot use the Copy and Move functions to recover these files.
Restoring StreetTalk Directory Assistance or Intelligent Messaging
To successfully restore Intelligent Messaging, you must restore from the BMS subdirectory and its subdirectories, that is, BMS and all directories that reside beneath it. Likewise, to successfully restore StreetTalk Directory Assistance, you must restore from the STDA subdirectory and its subdirectories, that is, STDA and all directories that reside beneath it. When you restore STDA, you must also restore the Registry in order to restore your StreetTalk groups.
It is necessary to restore the entire BMS directory because NetWorker cannot perform a mail merge. Instead, entire files are replaced. This can create problems if the Envelope.db file is not synchronized with files contained in the mailbox being restored.
Note: Envelope.db contains mail addressing information, attachments, and brief mail messages. The mail client obtains the mail message ID from envelope.db. If the mail client cannot access the correct version of envelope.db, mail messages cannot be accessed, although they may still reside on the disk. The messages use disk space, but they are not accessible.
If you replace only one folder when you should replace the entire mailbox, the information in the envelope.db file will not be correct. Mail will still reside on the disk and will take up disk space, but you will not be able to access that mail.
How to Restore an Intelligent Messaging Service
To perform this procedure, you need to locate and mount the backup media containing the files you want to restore.
Note: You must create the mail service prior to restoring the VnsData\BMS data directory (but do not start the service at that time). When you create the mail service, the VnsData\BMS directory and its files are installed. If an existing BMS directory is detected, a BMS0 (or next incremented number) is created. The mail service then looks for data files in BMS0, not in BMS. The data in BMS is then inaccessible to the mail service. The path VnsData\BMS0 is also included in all registry entries requiring the path to the mail service data files.
Your mail service may require additional disk space if the mail boxes on the mail service have messages with large attachments.
1. Delete the existing mail service from your server.
2. Recreate the mail service. Do not start the service.
3. Open NetWorker User, and locate the BMS data directory.
4. Mark the directories that you are restoring.
5. Unmark folder.db.
6. Click Start.
Note: If there is any chance that your data is damaged, delete all the data and then replace the mail system by re-installing. Refer to the Intelligent Messaging Administrator's Guide for instructions on installing a mail service. Also refer to the printed Release Notice included with your Intelligent Messaging software option.
Redirected Intelligent Messaging Restore
After backing up Intelligent Messaging from one server, you can use NetWorker to restore it to another server. This type of backup and restore is a redirected restore.
How to Perform a Redirected Restore of Intelligent Messaging
To perform a redirected restore, that is, to restore an Intelligent Messaging mail service to a server other than the one it was backed up from, you must have a valid backup of the VnsData\BMS directory and its subdirectories.
1. Create a mail service on the server you are restoring to, but do not start the new mail service.
2. On the client receiving the restored mail service, give NetWorker User administrator's rights. (In the Properties dialog box, enter -s followed by the server name followed by -a.) For example,
-s server-one -a
You can now run NetWorker User in administrator mode. (See the NetWorker User online help system for details on assigning administrator rights.)
3. Access the NetWorker Administrator module and
- Click on the Manage Clients icon. The list of configured clients appears.
- Select the name of the client that is the original owner of the mail service you are restoring. Right-click, and select Edit.
- Click on the Remote tab, and, in the Remote Access field, add the name of the client to which the mail service will be restored.
- Click OK and close the client window.
4. Open the NetWorker User module, and
- On the Operations menu, select Directed Recover. The Source Client dialog box appears.
- Select the name of the client you are receiving the restored mail service from and click OK.
- The Destination Client dialog box appears. Select the name of the client you are restoring the mail service to and click OK.
- In the Index entries, mark the BMS directory.
- Unmark Folder.db
5. On the Options menu, select Recover Options and check the Overwrite Existing File checkbox.
If you are restoring the data to a drive and path name other than the original, on the Recover Options dialog box, enter the location where you are restoring the data to.
Click OK.
6. Click Start.
If a tape needs to be mounted, NetWorker Administrator prompts for tapes. Insert the tapes so the restore can begin.
7. When the Restore is complete, start the mail service.
8. Use MMail to verify that the mail service was restored correctly.
StreetTalk File Services on Windows NT
Access Rights Lists (ARL) and extended attributes (OS/2 clients only) are stored in an ARL database file that resides below the StreetTalk for Windows NT installation directory, for example, Program Files\Banyan\File. You can restore the data file but the associated ARL file is not automatically restored.
On a StreetTalk for Windows NT file service, when you copy or restore a file, StreetTalk for Windows NT uses the ARLs that govern that directory location. If you need a different ARL, modify the ARL using StreetTalk Explorer. See Managing VINES Security.
NetWorker creates indexes of all files that are backed up. Indexes are used to locate saved files and the volumes those files are located in. After using a NetWorker server to back up your network, the indexes reside on your NetWorker server. NetWorker creates two types of online indexes, a file index and a media index. Each has a specific role during the backup and restore processes.
The file index contains information about the individual files backed up by NetWorker. If the file index contains an entry for a particular file, that file can be recovered.
The media index contains entries for the volumes to which the files are backed up. This index does not recognize individual files; it recognizes the save sets to which the files belong. A save set is a group of individual files, or a file system, backed up onto the backup media. The media index contains entries for the backup volumes that contain the backed up save sets. Use the media index to locate a specific portion of the media that you want to recover.
Locating Files and Volumes for Recovery
By default, the online indexes are stored in the following directory on the boot drive of your NetWorker server:
win32app\nsr\index\...
To locate a file that you want to recover, use NetWorker User to browse the file index. See the NetWorker User Online Help System.
To locate a volume that contains a particular save set, browse the media index from the NetWorker Administrator module.
To browse the save sets that contain files, use the NetWorker Administrator module to browse the media index. See the Legato NetWorker Administrator's Guide for details, or see the NetWorker Administrator Help System.
NetWorker maintains one file index for each client and one media index for each server.
Use NetWorker User module to recover indexes for each individual client. See the NetWorker User online help for details.
Note: Always recover the NetWorker indexes to the directory where they originally resided. You cannot successfully recover an index to a directory other than its original directory.
Using Save Sets to Locate Information on Server Backups
With each NetWorker server backup, NetWorker creates a save set called the bootstrap. The bootstrap includes the server indexes and the NetWorker configuration files. The server indexes are the file index and the media index described in "File and Media Indexes" previously. You must have the bootstrap information to recover from a disaster. Configuration files reside on your boot drive in win32app\nsr\res.
Bootstrap information is automatically saved only during scheduled backups; it is not saved during manual backups.
You should keep a written record of how each disk on your network is partitioned and formatted. You will need this information when it is necessary to restore one or more disks after a disk failure. You will need to recreate the same size (or larger) disk partitions, the same formatting methods and the exact drive letters. See the Legato NetWorker Disaster Recovery Guide for an example of bootstrap information.
