ADSM-L

Re: [ADSM-L] export node writing to spacemgpool

2010-04-12 12:42:05
Subject: Re: [ADSM-L] export node writing to spacemgpool
From: "Prather, Wanda" <wPrather AT ICFI DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 12 Apr 2010 11:12:30 -0500
You've got management class(es)/backup copy group(s) on the source
server that do not match in some respect the management class(es)/backup
copy group(s) on the target server.  (And remember the old gotcha,
directories are bound to the mgmt class with the highest RETONLY
setting....)

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Keith Arbogast
Sent: Monday, April 12, 2010 11:40 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] export node writing to spacemgpool

I am seeing surprising behavior from a process exporting a node
directly to another server.  Most of the exported files are being
written to an HSM disk pool and HSM tape pool, but some to the primary
disk and tape poosl. All the filespaces being exported are dong this.
I see this by running 'q occ <nodename>' on the target server.  The
same command on the source server does not show any files in an HSM
pool.

The node being exported is running Windows 5.0.2 and TSM version
5.5.2.6.  It is not running HSM, to my knowledge.   The source TSM
server is at Linux version 5.5.2.1.  The target TSM server is at Linux
version 5.5.4.1.

What circumstances could be causing this?  I am baffled. The primary
disk pool is not hitting HighMig, and it wouldn't migrate to
SPACEMGPOOL if it were.

Thank you,
Keith Arbogast

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