Messaging Server includes a backup API that provides an interface with third-party backup tools, such as Legato Networker. The physical message store structure and data format are encapsulated within the backup API. The backup API interacts directly with the message store. It presents a logical view of the message store to the backup service. The backup service uses the conceptual representation of the message store to store and retrieve the backup objects.
Messaging Server provides an Application Specific Module (ASM) that can be invoked by the Legato Networker’s save and recover commands to back up and restore the message store data. The ASM then invokes the Messaging Server imsbackup and imsrestore utilities.
This section provides information about how to use Legato Networker with the Messaging Server message store. To understand the Legato Networker interface, see your Legato documentation.
Create a symbolic link from /usr/lib/nsr/imsasm to msg-srv-base/lib/msg/imsasm
From Sun or Legato, obtain a copy of the nsrfile binary and copy it to the following directory:
Note that this is required only if you are using an older version of Networker (5.x). With Networker 6.0 and above, nsrfile is automatically installed under /usr/bin/nsr.
If you want to back up users by groups, perform the following steps:
Create a backup group file as described in 20.12.2 To Create Backup Groups
To verify your configuration, run mkbackupdir.sh.
Look at the directory structure created by mkbackupdir.sh.The structure should look similar to that shown in Table 20–4.
Note that if you do not specify a backup-groups.conf file, the backup process will use the default backup group ALL for all users.
In the directory /nsr/res/, create a res file for your save group to invoke the mkbackupdir.sh script before the backup. See Table 20–4 for an example.
Earlier versions of Legato Networker have a limitation of 64 characters for the save set name. If the name of this directory plus the logical name of the mailbox (for example, /primary/groupA/fred) is greater than 64 characters, then you must run mkbackupdir.sh -p. Therefore, you should use a short path name for the -p option of mkbackupdir.sh. For example the following command will create the backup image under the directory /backup:
mkbackupdir.sh -p /backup
Important: The backup directory must be writable by the message store owner (example: mailsrv).
Table 20–6 shows a sample backup groups directory structure.
/backup/primary/groupA/amy /bob /carly /groupB/mary /nancy /zelda /groupC/123go /1bill /354hut
The example below shows a sample res file named IMS.res in the /nsr/res directory:
type: savepnpc; precmd: "echo mkbackupdir started", "/usr/siroe/server5/msg-siroe/bin/mkbackupdir.sh -p /backup"; pstcmd: "echo imsbackup Completed"; timeout: "12:00 pm";
You are now ready to run the Legato Networker interface as follows:
Create the Messaging Server save group if necessary.
Create a backup client using savepnpc as the backup command:
Set the save set to the directory created by mkbackupdir.
For a single session backup, use /backup
For parallel backups, use /backup/server/group
Be sure you’ve already created group as defined in 20.12.2 To Create Backup Groups
You must also set the parallelism to the number of backup sessions.
Select Group Control | Start to test your backup configuration.
Example. Creating A Backup Client in Networker:
To create a backup client in Networker. From nwadmin, select Client | Client Setup | Create
Name: siroe Group: IMS Savesets:/backup/primary/groupA /backup/secondary/groupB /backup/tertiary/groupC . . Backup Command:savepnpc Parallelism: 4
To recover data, you can use the Legato Networker nwrecover interface or the recover command-line utility. The following example recovers user a1’s INBOX:
recover -a -f -s siroe /backup/siroe/groupA/a1/INBOX
The next example recovers the entire message store:
recover -a -f -s siroe /backup/siroe