This ought to happen because your volumes have not been marked in the
database as being offsite. "upd v * stg= acc=offsite" will
do the trick.
If a copypool volume is offsite, the server is reading from primary pool
volumes and is making new copies on new volume. Then the new volume is
sent offsite
RESOURceutilization is an option which can be defined in a client option
set on the server.
The other possibility is that Node_B is indeed connecting and is having
NODename=Node_A in some dsm.sys stanza.
In fact I cannot recall when address seen in Nodes table is updated -
during client operations
Koen,
The answer is yes, you can do what you want. Library partitioning may be
easier, however, depending on your configuration.
What do you plan to do with the restored server after the move? If you are
going to access data tapes for the branch database at HQ, are there any
cartridges with dup
Dear listers,
I am setting up the following config:
HQ:
1 3584 with 9 fibre drives
2 AIX tsm servers on 1 690 lpar with disk and tape on 2109-f16 switches and
ess
tdp for sap
Brache office:
1 tsm server on a remote location.
1 AIX tsm server with disk and tape on 2109-f16 switches and ess
tdp fo
>Can anyone share some info on TSM managed services to address a Unix memory
>leak. i.e. have dsmcad start scheduler prior to backup and stop it after
>backup. My understanding is that the memory leak is actually a short coming of
>the Unix operating system architecture. Apparently the scheduler
On Fri, Sep 19, 2003 at 10:17:45PM -0400, Wholey, Joseph (IDS DM&DS) wrote:
> Can anyone share some info on TSM managed services to address a Unix memory leak.
> i.e. have dsmcad start scheduler prior to backup and stop it after backup. My
> understanding is that the memory leak
> is actually a
