ADSM-L

V3-clients and backup-domain

1999-03-11 17:59:55
Subject: V3-clients and backup-domain
From: Tom Tann{s <tom.tannas AT USIT.UIO DOT NO>
Date: Thu, 11 Mar 1999 23:59:55 +0100
I have some problems on the solaris and DEC UNIX V3-clients.

In dsm.opt I define each filesystem/filespace to be processed with
a domain <filespace> statement.
One statement for each.

This has worked for years, but with V3 I see that after some time, the
scheduler seems to ignore this, and backs up all the local filesystems.

When this happens, all the filespaces from my dsm.opt are backed up first,
then the scheduler continues with the rest of the filespaces on the
client.

I've checked the access-times on the dsm.opt, and it is read. Have also
run a trace at scheduler startup to see if the backup-domain is set
correct, and it is.

I plan to run a client with a trace over the weekend, to try and see
what's going on. However, I'm not quite sure which flag to turn on. Guess
I will start with config or option, to see if the scheduler keeps its
backup-domain correct..


Anyone else seen similar problems after migrating to V3?
Any suggestions on which traceflags to use to catch this?



(The clients in question so far are the solaris 2.6 3.1.0.6 and the
Digital UNIX 3.1.0.6 clients. Server is AIX, 3.1.2.13)
<Prev in Thread] Current Thread [Next in Thread>