ADSM-L

Client backup with two different policy domains

2004-07-29 08:48:34
Subject: Client backup with two different policy domains
From: Kevin Kinder <Admin AT WVADMIN DOT GOV>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 29 Jul 2004 08:32:21 -0400
Tivoli Server MVS 5.1.7.0
NetWare Client 5.2.0.0 on NetWare 5.10 server

On this server, I need to back up one directory (called admbrim) and all of its 
subdirectories with seven days' retention.  The rest of the directories (across 
two volumes) need to have 30 days' retention.

I set up two nodes:

BRIMSERVER2MAIL: For the admbrim directory
BRIMSERVER2: for everything else.

I have two BA directories with separate DSM.opt files.  (DSMMAIL.OPT and 
DSM.OPT) respectively.

Here are the pertinent differences in the .OPT Files:

DSMMAIL.OPT
�--------------
*  Setting Nodename
*  -------------------------------------------------------

   NODENAME           brimserver2mail

*  Includes/Excludes
*  ---------------------------------------------------------

INCLUDE brim_server2\data:admbrim/*
INCLUDE brim_Server2\data:admbrim
EXCLUDE brim_server2\data:*

DSM.OPT

*  Setting Nodename
*  -------------------------------------------------------

   NODENAME           brimserver2

*  Includes/Excludes
*  ---------------------------------------------------------

EXCLUDE brim_server2\*:/.../vol$log.err
EXCLUDE brim_server2*:/.../tts$log.err
EXCLUDE brim_server2*:/.../sys$log.err
EXCLUDE brim_server2*:/.../events.log
EXCLUDE brim_server2*:/.../secaudit.log
EXCLUDE brim_server2*:/.../system.log
EXCLUDE brim_server2\sys:system/cmaster.dba
EXCLUDE brim_server2\sys:system/btrieve.trn
EXCLUDE brim_server2\sys:system/tsa/tsa$temp.*
EXCLUDE brim_server2\sys:_SWAP_.MEM
EXCLUDE.dir brim_server2\sys:\queues
EXCLUDE.DIR brim_server2\data:admbrim


Both nodes are using the same schedule, but with a different policy domain. I 
used the -optfile parameter to point each schedule to its correct .OPT file.

This a.m., only one scheduler, for the BRIMSERVER2 node, was running.  However, 
info in the schedlog for that node appeared to include both nodes.  For example:

Time remaining until execution: Querying server for next scheduled event.
07/28/2004 19:18:58 Node Name: BRIMSERVER2
07/28/2004 19:18:58 Session established with server SERVER1: MVS
07/28/2004 19:18:58   Server Version 5, Release 1, Level 7.0
07/28/2004 19:18:58   Data compression forced off by the server
07/28/2004 19:18:58   Server date/time: 07/28/2004 19:19:16  Last access: 
07/28/2004 15:19:16

07/28/2004 19:18:58 --- SCHEDULEREC QUERY BEGIN
07/28/2004 19:18:58 --- SCHEDULEREC QUERY END
07/28/2004 19:18:58 Next operation scheduled:
07/28/2004 19:18:58 ------------------------------------------------------------
07/28/2004 19:18:58 Schedule Name:         NORMAL_DAILY_10PM_START
07/28/2004 19:18:58 Action:                Incremental
07/28/2004 19:18:58 Objects:               
07/28/2004 19:18:58 Options:               
07/28/2004 19:18:58 Server Window Start:   22:00:00 on 07/28/2004
07/28/2004 19:18:58 ------------------------------------------------------------
07/28/2004 19:18:58 Command will be executed in 3 hours and 48 minutes.
07/28/2004 19:18:58 
Time remaining until execution: Querying server for next scheduled event.
07/28/2004 19:20:29 Node Name: BRIMSERVER2MAIL
07/28/2004 19:20:29 Session established with server SERVER1: MVS
07/28/2004 19:20:29   Server Version 5, Release 1, Level 7.0
07/28/2004 19:20:29   Server date/time: 07/28/2004 19:20:47  Last access: 
07/28/2004 15:20:47

07/28/2004 19:20:29 --- SCHEDULEREC QUERY BEGIN
07/28/2004 19:20:29 --- SCHEDULEREC QUERY END
07/28/2004 19:20:29 Next operation scheduled:
07/28/2004 19:20:29 ------------------------------------------------------------
07/28/2004 19:20:29 Schedule Name:         NORMAL_DAILY_10PM_START
07/28/2004 19:20:29 Action:                Incremental
07/28/2004 19:20:29 Objects:               
07/28/2004 19:20:29 Options:               
07/28/2004 19:20:29 Server Window Start:   22:00:00 on 07/28/2004
07/28/2004 19:20:29 ------------------------------------------------------------
07/28/2004 19:20:29 Command will be executed in 2 hours and 53 minutes.
07/28/2004 19:20:29 

Then, when the backup kicked off, I got this:


Executing scheduled command now.
07/28/2004 22:13:29 Node Name: BRIMSERVER2MAIL
07/28/2004 22:13:29 Session established with server SERVER1: MVS
07/28/2004 22:13:29   Server Version 5, Release 1, Level 7.0
07/28/2004 22:13:29   Server date/time: 07/28/2004 22:13:47  Last access: 
07/28/2004 19:20:47

07/28/2004 22:13:29 --- SCHEDULEREC OBJECT BEGIN NORMAL_DAILY_10PM_START 
07/28/2004 22:00:00
07/28/2004 22:13:29 Please enter NetWare user for "BRIM_SERVER2": 
Executing scheduled command now.
07/28/2004 23:06:58 Node Name: BRIMSERVER2
07/28/2004 23:06:58 Session established with server SERVER1: MVS
07/28/2004 23:06:58   Server Version 5, Release 1, Level 7.0
07/28/2004 23:06:58   Data compression forced off by the server
07/28/2004 23:06:58   Server date/time: 07/28/2004 23:07:16  Last access: 
07/28/2004 19:19:16

07/28/2004 23:06:58 --- SCHEDULEREC OBJECT BEGIN NORMAL_DAILY_10PM_START 
07/28/2004 22:00:00
07/28/2004 23:06:58 Incremental backup of volume 'BRIM_SERVER2\SYS:'
07/28/2004 23:06:58 Incremental backup of volume 'BRIM_SERVER2\DATA:'
07/28/2004 23:07:20 ANS1898I ***** Processed     2,500 files *****
07/28/2004 23:07:20 Directory-->                   0 SYS:/ [Sent]      
etc etc

The BRIMSERVER2MAIL node's logs are empty.  I've obviously messed up somewhere, 
but I can't figure it out.  I searched the archives and FAQs, but I can't seem 
to find the correct procedure.  Help[ much appreciated!

<Prev in Thread] Current Thread [Next in Thread>