Migrations

[Gill, Geoffrey L.]

I have a disk pool that is set Migration Continue=no, High Migration=80, Low
Migration=60. This disk pool is 390GB in size and every morning when I come
in migration is running, and would run till it is empty, I've seen it. I've
verified the settings during the migration and I see no reason that this
should be happening. The disk fills with SAP R/3 data each evening and some
other regular stuff.

Has anyone else come across this? I haven't seen the other disk pools I have
do this.

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail: [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 905-7154

Canceling Migrations

[Coats, Jack]

Does someone have a script (Unix is ok, Windows is preferred) that can
cancel currently running migrations?



My script doesn't seem to work just right.  Any suggestions (or a script
that works for you :-)  ) would really help!



Here is my attempt:



@Echo Off

REM c:\SBIB\TSMKillReclaimation.cmd - 20040916 jcoats - based a thread in
the ADSM-L list

REM requires command line e-mail client BLAT to send reprots



set PATH=%PATH%;c:\Progra~1\tivoli\tsm\baclient

set PDSM="C:\Program Files\Tivoli\tsm\baclient\"

set DSMC=dsmadmc.exe -ID=MYTSMADMIN -PASS=XX -OUTFILE=C:\SBIB\TEMP2.TXT

cd \sbib

del /q KillRec.txt

del /q temp.txt

del /q temp2.txt

del /q temp3.txt

del /q temp4.txt



Echo TSM Kill Reclaimation > temp.txt

date /t >>temp.txt

time /t >>temp.txt



cd %PDSM%

%DSMC% UPDATE STG TAPEDATA REC=100

%DSMC% UPDATE STG COPYPOOL REC=100

%DSMC% select * from processes where PROCESS like '%%Reclamation%%'

cd \sbib



REM save a copy of the reclaimations that are running

echo *** Reclaimations Running *** >temp4.txt

type temp2.txt >> temp4.txt



cd %PDSM%

%DSMC% select PROCESS_NUM from processes where PROCESS like
'%%Reclamation%%'

cd \sbib

copy TEMP2.TXT TEMP3.TXT

for /F "eol=A tokens=1* skip=8 " %%i in (TEMP3.TXT) do (

 %DSMC% KILL PROC %%i

)



copy temp.txt+temp4.txt KillRec.txt

date /t >>KillRec.txt

time /t >>KillRec.txt

for /F "tokens=2-4 delims=/, " %%i in ('Date /t') do (

  copy KillRec.txt Logs\KillRec%%k%%i%%j.txt

)

blat KillRec.txt -Subject TSM-KillReclaimation -to [EMAIL PROTECTED]





del /q KillRec.txt

del /q temp.txt

del /q temp2.txt

del /q temp3.txt

del /q temp4.txt

Re: Migrations

[David Longo]

I suspect what is happening is that as you say the SAP "fills" the disk
pool.  So when migration starts and after it gets below the
lowmig point, it will keep going bascially till it migrates the data
for
the current node's data it was working on when it hit the lowmig
point.
So if this was a large amount of data, essentially it would empty the
disk pool.


David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5509
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 10/22/02 10:00AM >>>
I have a disk pool that is set Migration Continue=no, High
Migration=80, Low
Migration=60. This disk pool is 390GB in size and every morning when I
come
in migration is running, and would run till it is empty, I've seen it.
I've
verified the settings during the migration and I see no reason that
this
should be happening. The disk fills with SAP R/3 data each evening and
some
other regular stuff.

Has anyone else come across this? I haven't seen the other disk pools I
have
do this.

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail: [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 905-7154


"MMS " made the following
 annotations on 10/22/2002 11:28:48 AM
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==

Re: Migrations

[Prather, Wanda]

Yep, this tends to happen when you have only a small number of large clients
in a disk pool.

When the disk pool fills above the HIGHMIG value and triggers a migration,
TSM picks the LARGEST CLIENT (or maybe the largest filespace, I forget) in
the pool and migrates that WHOLE chunk out.  Then TSM checks to see it's
below LOWMIG yet.  If not, it picks the next largest client and migrates
that one.

So if all the remaining data in the disk pool belongs to one client, it can
go down to 0.

Working as designed.

-Original Message-
From: Gill, Geoffrey L. [mailto:GEOFFREY.L.GILL@;SAIC.COM]
Sent: Tuesday, October 22, 2002 10:01 AM
To: [EMAIL PROTECTED]
Subject: Migrations


I have a disk pool that is set Migration Continue=no, High Migration=80, Low
Migration=60. This disk pool is 390GB in size and every morning when I come
in migration is running, and would run till it is empty, I've seen it. I've
verified the settings during the migration and I see no reason that this
should be happening. The disk fills with SAP R/3 data each evening and some
other regular stuff.

Has anyone else come across this? I haven't seen the other disk pools I have
do this.

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:<mailto:gillg@;saic.com> [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 905-7154

Re: Migrations

[Mark D. Rodriguez]

Gill, Geoffrey L. wrote:


I have a disk pool that is set Migration Continue=no, High Migration=80, Low
Migration=60. This disk pool is 390GB in size and every morning when I come
in migration is running, and would run till it is empty, I've seen it. I've
verified the settings during the migration and I see no reason that this
should be happening. The disk fills with SAP R/3 data each evening and some
other regular stuff.

Has anyone else come across this? I haven't seen the other disk pools I have
do this.

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail: [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 905-7154



Geoff,

Based on the information your are giving me I might offer this
explanation.  First of all "MIGContinue" only has meaning if you have
"MIGDelay" set to something other than 0, but I don't think that is a
factor here.  The way migration works is as follows:

  1. Once stg_pool utilization exceeds the "HIghmig" value a migration
 process or processes are started.
  2. ITSM will pick the largest single filespace backup (or archive
 package) in the stg_pool and move it AND all of the other
 filespaces for that node.
  3. Once all data for that node has been moved for that node ITSM
 checks to see if stg_pool utilization is below the  "LOwmig" value
 if not then go back to step 2.

There is a bit of a difference in this process if you use "MIGDelay" and
"MIGContinue", I have posted on that process several times before so I
want go through it all again.

I am guessing that since this stg_pool is for your SAP data which is
probably quite large that what you are seeing is a single node with data
that is a very large portion of the stg_pool space.  And therefore, once
ITSM starts to migrate it's data it will continue way past the low
threshold.  As you can see above, ITSM does not check "LOwmig" until
after it moves all data for a given node.  I beleive this is waht you
are seeing.

--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.

===
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education
IBM Certified Advanced Technical Expert, CATE
AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
Red Hat Certified Engineer, RHCE
===

Re: Canceling Migrations

[Mark D. Rodriguez]

Jack,
I think your problem is with these lines:
for /F "eol=A tokens=1* skip=8 " %%i in (TEMP3.TXT) do (
%DSMC% KILL PROC %%i
)
They should read:
for /F "eol=A tokens=1* skip=8 " %%i in (TEMP3.TXT) do (
%DSMC% /*_CANCEL_ */PROC %%i
)
There is no TSM server command of KILL PROC, but there is a CANCEL PROC!
Try that.
--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.
===
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education
IBM Certified Advanced Technical Expert, CATE
AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
Red Hat Certified Engineer, RHCE
===

Coats, Jack wrote:
Does someone have a script (Unix is ok, Windows is preferred) that can
cancel currently running migrations?

My script doesn't seem to work just right.  Any suggestions (or a script
that works for you :-)  ) would really help!

Here is my attempt:

@Echo Off
REM c:\SBIB\TSMKillReclaimation.cmd - 20040916 jcoats - based a thread in
the ADSM-L list
REM requires command line e-mail client BLAT to send reprots

set PATH=%PATH%;c:\Progra~1\tivoli\tsm\baclient
set PDSM="C:\Program Files\Tivoli\tsm\baclient\"
set DSMC=dsmadmc.exe -ID=MYTSMADMIN -PASS=XX -OUTFILE=C:\SBIB\TEMP2.TXT
cd \sbib
del /q KillRec.txt
del /q temp.txt
del /q temp2.txt
del /q temp3.txt
del /q temp4.txt

Echo TSM Kill Reclaimation > temp.txt
date /t >>temp.txt
time /t >>temp.txt

cd %PDSM%
%DSMC% UPDATE STG TAPEDATA REC=100
%DSMC% UPDATE STG COPYPOOL REC=100
%DSMC% select * from processes where PROCESS like '%%Reclamation%%'
cd \sbib

REM save a copy of the reclaimations that are running
echo *** Reclaimations Running *** >temp4.txt
type temp2.txt >> temp4.txt

cd %PDSM%
%DSMC% select PROCESS_NUM from processes where PROCESS like
'%%Reclamation%%'
cd \sbib
copy TEMP2.TXT TEMP3.TXT
for /F "eol=A tokens=1* skip=8 " %%i in (TEMP3.TXT) do (
%DSMC% KILL PROC %%i
)

copy temp.txt+temp4.txt KillRec.txt
date /t >>KillRec.txt
time /t >>KillRec.txt
for /F "tokens=2-4 delims=/, " %%i in ('Date /t') do (
 copy KillRec.txt Logs\KillRec%%k%%i%%j.txt
)
blat KillRec.txt -Subject TSM-KillReclaimation -to [EMAIL PROTECTED]


del /q KillRec.txt
del /q temp.txt
del /q temp2.txt
del /q temp3.txt
del /q temp4.txt

Re: new server migrations

[Robin Sharpe]

I agree with Nathan... option 1 is not possible.  I tried it going from AIX
to HP.

Option 2 depends on how much data you have.  We had about 60TB on our AIX
TSM Server in a ATL P3000 (DLT7000 drives).  I roughly calculated it would
take over six months of  tape to tape copies, running 24x7 with optimal
throughput, to migrate the environment to the HP.  BTW, you must do
export/import, because there is no other way to get the database info from
AIX to "other" platform.  Even if you could get all the database info
migrated, you probably would not be able to read the tapes from the AIX
environment on the Sun hardware.  It is not a purely hardware issue
(obviously you can transfer tar images between platforms), but has
something to do with the way TSM records data on the different platforms.
That's what Tivoli support told me.  My solution to this messy problem was
to keep the legacy AIX environment up until all of the data residing there
expires (one year, which will be coming up in about a month!).   I simply
started backing up all clients to the new TSM server, and we handle any
restore requests for older data from the AIX server.  Obviously you have to
have new server and library, but it looks like you have all the pieces
as long as you did not have any plans for the legacy hardware.

Good Luck!
Robin Sharpe
Berlex Labs



Nathan King
<[EMAIL PROTECTED]
R.COM>To:[EMAIL PROTECTED]
Sent by:  cc:
"ADSM: Dist   Subject:
Stor Manager"    Re: new server migrations
<[EMAIL PROTECTED]
RIST.EDU>


09/16/02
05:11 PM
Please
respond to
"ADSM: Dist
Stor Manager"





Actually No.1 just flat out won't work. You can't backup the TSM DB on
one platform and restore to a different platform.

No.2 is your only option, in conjunction with import/export <-- that's
what the tools are for. Don't use server-server.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Nicola Albrecht
Sent: Monday, September 16, 2002 4:49 PM
To: [EMAIL PROTECTED]
Subject: Re: new server migrations


"Reiss David IT751 (ext-CDI)" wrote:

> I have several TSM servers that are going to be replaced with
> new-beefer TSM servers.  Right now the TSM servers are running on old
> RS/6000 boxes running AIX 4.3.3 with Breece Hill Q47 libraries with
> DLT8000 tapes drives in them. The new TSM Servers are going to be Sun
> boxes running Solaris 2.8 with ADIC Scalar 1000 libraries with LTO
> drives.
>
> The issue... I want to keep my current TSM data, as much as possible
> anyway. There seems to be two ways too do this.
>
> 1. On the old RS/6000 backup the TSM database to tape.  Connect the
> old Q47 library to the new Sun box, and restore the TSM database.
> Then, migrate the data via the directly attached SCSI drives from the
> old library to the new library.  Remove old library and beat it to
> death with nearest sledgehammer.
>
> 2. Bring up the new Sun box as a brand new TSM server, define
everything
> from scratch.   Then...and here lies the heart of my question, use
> Server-to-Server stuff to get old data from old Rs/6000 server to new
> one. I know I can push the data doing this... but could I push it in a

> logical manner so that it gets associated properly with what will be
> the node definitions on the new server?
>
> I don't like the #1 option because of all the hardware moving things
> around and such.  I would have to visit the places the server will be
> in.  We don't have people at these sites who would be comfortable just

> switching cables around and stuff.  So, sending them a whole new
> server... have them put it together, and once it is together I can
> just move on from there and do the data moving myself.
>
> Thanks,
>
> David N. Reiss
> TSM Support Engineer
> [EMAIL PROTECTED]
> 407-736-3912

David, of the 2 options, number one is the only one that is going to
accomplish the association of stored data to node definitions on the new
server.  The second option (Server-to-Server) stores the data as archive
files on the new server and associates these archive file with a node of
the type server (old server).  Not what it sounds like you want.

Another option could be exporting the data, then importing to the new
server.

Nici

Nici Albrecht
MDR Consulting & Education
1-210-860-4641

Re: new server migrations

[Kelly J. Lipp]

As mentioned before, restoring a db across platforms does not work.  You can
export and import information in the database, but not restore the database.

Kelly J. Lipp
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
[EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com or www.storserver.com
(719)531-5926
Fax: (240)539-7175


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Nicola Albrecht
Sent: Monday, September 16, 2002 2:49 PM
To: [EMAIL PROTECTED]
Subject: Re: new server migrations


"Reiss David IT751 (ext-CDI)" wrote:

> I have several TSM servers that are going to be replaced with new-beefer
TSM
> servers.  Right now the TSM servers are running on old RS/6000 boxes
running
> AIX 4.3.3 with Breece Hill Q47 libraries with DLT8000 tapes drives in
them.
> The new TSM Servers are going to be Sun boxes running Solaris 2.8 with
ADIC
> Scalar 1000 libraries with LTO drives.
>
> The issue... I want to keep my current TSM data, as much as possible
anyway.
> There seems to be two ways too do this.
>
> 1. On the old RS/6000 backup the TSM database to tape.  Connect the old
Q47
> library to the new Sun box, and restore the TSM database.  Then, migrate
the
> data via the directly attached SCSI drives from the old library to the new
> library.  Remove old library and beat it to death with nearest
sledgehammer.
>
> 2. Bring up the new Sun box as a brand new TSM server, define everything
> from scratch.   Then...and here lies the heart of my question, use
> Server-to-Server stuff to get old data from old Rs/6000 server to new one.
> I know I can push the data doing this... but could I push it in a logical
> manner so that it gets associated properly with what will be the node
> definitions on the new server?
>
> I don't like the #1 option because of all the hardware moving things
around
> and such.  I would have to visit the places the server will be in.  We
don't
> have people at these sites who would be comfortable just switching cables
> around and stuff.  So, sending them a whole new server... have them put it
> together, and once it is together I can just move on from there and do the
> data moving myself.
>
> Thanks,
>
> David N. Reiss
> TSM Support Engineer
> [EMAIL PROTECTED]
> 407-736-3912

David, of the 2 options, number one is the only one that is going to
accomplish
the association of stored data to node definitions on the new server.  The
second option (Server-to-Server) stores the data as archive files on the new
server and associates these archive file with a node of the type server (old
server).  Not what it sounds like you want.

Another option could be exporting the data, then importing to the new
server.

Nici

Nici Albrecht
MDR Consulting & Education
1-210-860-4641

Copy Stgpool and Migrations

[Dearman, Richard]

I backup my systems to a disk stgpool then backup that stgpool to an offsite
copy stgpool library at 8am then at 11am I migrate the disk stgpool to an
onsite tape library.  Currently I schedule the jobs in tsm by just issuing
the proper commands at 8am and 11am.  The problem is my 8am backup to my
copy stgpool sometimes runs into the migrattion at 11am.  Does anyone have a
more efficient way of doing this instead of me just changing the migration
to a later time.

Thanks
Richard

stgpool migrations between TSM instances

[coopermarsh]

Background:

Have 2 instances,

1. LTO3 stgpools (current)
2. LTO1 stgpools (older)


Issue
I need to migrate the data from the LTO1 stgpools to the LTO3 stgpools for a 
complete DR instance.

Both instances are running, but each instance does not know of the stgpools in 
the other instance, if you get me.

Is this possible?

If not I may have to set up the drives/devc/stgpools on the LTO3 instance and 
then set the NEXTPOOL= on the LTO1 stgpools.

Any help much appreciated.

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--

stgpool migrations between TSM instances

[TSTLTDTD]

Try exporting and importing

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--

Controlling nodes - storage pool migrations

[Roy P Costa]

We have storage groups set up for various parts of our business, primary
pools being to dasd and migrating to tape in an automated Tape Library
(ATL).  Most of the nodes in the different storage groups are file servers,
some holding many gigabytes of data.  As I understand from the TSM/ADSM
documentation and experience, when a dasd storage group meets the migration
criteria (High Mig), TSM looks for the node that has the MOST data in the
storage pool and then proceeds to migrate ALL of that node's filespaces
from dasd to tape before it checks to see if the migration low threshold
has been met.  We currently have the situation that the node with the most
data has over 200G of data on dasd, causing us to run out of tapes in the
ATL (and bringing down the dasd usage to well below the low threshold).
I've tried to make the Migration Delay = 30 days, which I believe will
check to see if ALL the files for a particular node have not been touched
in 30 days before migrating ALL of the node's files.  If this is true, then
these fileservers will never have all of their files 30 days old, since
files are updated regularly and I would need to have Migration Continue =
yes to avoid the dasd storage pools from filling totally.
If my assumptions are correct, throwing more dasd at the dasd storage pools
will only make these migrations even larger.
Is there a way to tell TSM to not migrate the node with the MOST data or
some workaround that gives us better control of these migrations?  I'm
willing to explore and test any suggestions that you may have.


Roy Costa
IBM International Technical Support Organization

Export Node and OS Migrations

[Richard Mochnaczewski]

Hi *,

We are currently in the middle of migrating our Novell file servers to Windows 
2003. We will be doing a copy of all our Novell file server data to our Windows 
2003 machines and then eventually deleting the Novell machine in the future. In 
the meantime, we will be running low on slots in our library because we will 
for a short time have the duplicate copies before we cut off our Novell 
servers.. If I do an export of our Novell data to get the data out of TSM and 
the library, it will free up our onsite slot issue, but what will happen to the 
reclamation for that server for my offsite tapes ?

Rich

Re: Copy Stgpool and Migrations

[Rushforth, Tim]

You could use a TSM script like:

ba stgpool stgpool1 offsite wait=y
update stgpool stgpool1 highmig=1 lowmig=1

and setup a schedule to run the script

-Original Message-
From: Dearman, Richard [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 25, 2002 10:38 AM
To: [EMAIL PROTECTED]
Subject: Copy Stgpool and Migrations


I backup my systems to a disk stgpool then backup that stgpool to an offsite
copy stgpool library at 8am then at 11am I migrate the disk stgpool to an
onsite tape library.  Currently I schedule the jobs in tsm by just issuing
the proper commands at 8am and 11am.  The problem is my 8am backup to my
copy stgpool sometimes runs into the migrattion at 11am.  Does anyone have a
more efficient way of doing this instead of me just changing the migration
to a later time.

Thanks
Richard

Re: Copy Stgpool and Migrations

[John Naylor]

Richard,
Simplest way is just to trigger earlier backups of your storage pool. Say you
triggered at 2/3 hour intervals during the night by the time your current backup
kicked in at 08:00 most of your pool has already been copied, so will finish
earlier, almost certainly before your migration.
cheers,
John




"Dearman, Richard" <[EMAIL PROTECTED]> on 03/25/2002 04:38:21 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Copy Stgpool and Migrations



I backup my systems to a disk stgpool then backup that stgpool to an offsite
copy stgpool library at 8am then at 11am I migrate the disk stgpool to an
onsite tape library.  Currently I schedule the jobs in tsm by just issuing
the proper commands at 8am and 11am.  The problem is my 8am backup to my
copy stgpool sometimes runs into the migrattion at 11am.  Does anyone have a
more efficient way of doing this instead of me just changing the migration
to a later time.

Thanks
Richard








**
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**

Re: Copy Stgpool and Migrations

[Francisco Molero]

Hi,
you can run all commands in a script, then you can run
the commands one per one. In addicion, you should see
the options movebatchsize ( 1000) and movesizethresh
(500), this options improve the performance in process
like migration , backup stg, reclamations,etc..

--- "Dearman, Richard" <[EMAIL PROTECTED]> escribis: > I
backup my systems to a disk stgpool then backup
> that stgpool to an offsite
> copy stgpool library at 8am then at 11am I migrate
> the disk stgpool to an
> onsite tape library.  Currently I schedule the jobs
> in tsm by just issuing
> the proper commands at 8am and 11am.  The problem is
> my 8am backup to my
> copy stgpool sometimes runs into the migrattion at
> 11am.  Does anyone have a
> more efficient way of doing this instead of me just
> changing the migration
> to a later time.
>
> Thanks
> Richard

___
Do You Yahoo!?
Yahoo! Messenger
Comunicacisn instantanea gratis con tu gente.
http://messenger.yahoo.es

Re: Copy Stgpool and Migrations

[John Underdown]

Here's how i wait on a  process to finish. Basically i query the process and if it's 
still running i re-spawn the schedule for ten minutes later. If you have any questions 
please let me know.

john
[EMAIL PROTECTED]
--
/*DAILY*/
/*backup db*/
delete schedule chkproc type=admin
q process
if(rc_notfound) goto cont
def schedule chkproc cmd="run daily" active=yes startd=today startt=now+00:10 exp=today
exit
cont:
backup db dev=bakdrive type=full wait=yes
def schedule chkproc cmd="run Script1" active=yes startd=today startt=now+00:10 
exp=today
exit
/* End of DAILY*/

/*SCRIPT1*/
/*Expire data bkup stg backup\archive pools*/
delete schedule chkproc type=admin
q process
if(rc_notfound) goto cont
def schedule chkproc cmd="run script1" active=yes startd=today startt=now+00:10 
exp=today
exit
cont:
def schedule chkproc cmd="run backupstg" active=yes startd=today startt=now+00:10 
exp=today
expire inventory
exit
/*End of SCRIPT1*/

/*Backupstg*/
delete schedule chkproc type=admin
q process
if(rc_notfound) goto cont
def schedule chkproc cmd="run backupstg" active=yes startd=today startt=now+00:10 
exp=today
exit
cont:
backup stg backuppool copypool
/*End of Backupstg*/

-Original Message-

Date:Mon, 1 Apr 2002 12:37:41 +0200
From:=?iso-8859-1?q?Francisco=20Molero?= <[EMAIL PROTECTED]>
Subject: Re: Copy Stgpool and Migrations

Hi,
you can run all commands in a script, then you can run
the commands one per one. In addicion, you should see
the options movebatchsize ( 1000) and movesizethresh
(500), this options improve the performance in process
like migration , backup stg, reclamations,etc..

--- "Dearman, Richard" <[EMAIL PROTECTED]> escribis: > I
backup my systems to a disk stgpool then backup
> that stgpool to an offsite
> copy stgpool library at 8am then at 11am I migrate
> the disk stgpool to an
> onsite tape library.  Currently I schedule the jobs
> in tsm by just issuing
> the proper commands at 8am and 11am.  The problem is
> my 8am backup to my
> copy stgpool sometimes runs into the migrattion at
> 11am.  Does anyone have a
> more efficient way of doing this instead of me just
> changing the migration
> to a later time.
>
> Thanks
> Richard

Re: stgpool migrations between TSM instances

[Stapleton, Mark]

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
TSTLTDTD
> Try exporting and importing

Yes. In fact that's the only way you'll be able to do that. Be prepared
to tie up at least one tape drive for each pool for long periods of
time. I would suggest that you use the "filedata=allactive" flag to
minimize the amount of data sought and moved.

--
Mark Stapleton
CDW Berbee
System engineer

Re: Controlling nodes - storage pool migrations

[Zlatko Krastev]

There is no method to convince the TSM server to skip the biggest node
(AFAIK). But the workaround is quite straightforward - define separate
stgpool for that node and use the existing stgpool for the rest. Also the
node with 200 GB might be very good candidate for direct-to-tape
backups/restores. Putting it into separate stgpool will ensure "manual"
collocation and good restore times.

--> I believe will check to see if ALL the files for a particular node have
not been touched in 30 days before migrating ALL of the node's files.

Incorrect. The files which are backed up more than 30 days ago will be
migrated, while the recently backed up files will stay in the stgpool. If
you look at the description of "def stg" command, you will see that
MIGContinue parameter is honoured when storage pool is filled with files
newer than MIGDelay period!

As not all your assimptions are correct and there are too many ways to
skin the same cat you can avoid adding dasd endlessly.

Zlatko Krastev
IT Consultant






Roy P Costa <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
07.10.2003 17:10
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
    Subject:Controlling nodes - storage pool migrations


We have storage groups set up for various parts of our business, primary
pools being to dasd and migrating to tape in an automated Tape Library
(ATL).  Most of the nodes in the different storage groups are file
servers,
some holding many gigabytes of data.  As I understand from the TSM/ADSM
documentation and experience, when a dasd storage group meets the
migration
criteria (High Mig), TSM looks for the node that has the MOST data in the
storage pool and then proceeds to migrate ALL of that node's filespaces
from dasd to tape before it checks to see if the migration low threshold
has been met.  We currently have the situation that the node with the most
data has over 200G of data on dasd, causing us to run out of tapes in the
ATL (and bringing down the dasd usage to well below the low threshold).
I've tried to make the Migration Delay = 30 days, which I believe will
check to see if ALL the files for a particular node have not been touched
in 30 days before migrating ALL of the node's files.  If this is true,
then
these fileservers will never have all of their files 30 days old, since
files are updated regularly and I would need to have Migration Continue =
yes to avoid the dasd storage pools from filling totally.
If my assumptions are correct, throwing more dasd at the dasd storage
pools
will only make these migrations even larger.
Is there a way to tell TSM to not migrate the node with the MOST data or
some workaround that gives us better control of these migrations?  I'm
willing to explore and test any suggestions that you may have.


Roy Costa
IBM International Technical Support Organization

Re: Export Node and OS Migrations

[Prather, Wanda]

An EXPORT is just a copy.
You have your data on an export tape, but nothing else happens.
 
To get the data "out of TSM", you need to 1) EXPORT the data 2) DELETE the 
filespaces for the nodes you have exported.
 
When you delete the filespace, it deletes the data from the primary tape AND 
the offsite tape.  Reclamation proceeds as normal.
 
If your data is collocated, or your NOVELL data is in a separate storage pool, 
look at the MOVE MEDIA command.  It's a way to eject the tapes (solving your 
slot problem), and tell TSM you are storing them outside the library.  You 
could just leave them that way until you are ready to completely destroy the 
NOVELL data.
 
 



From: ADSM: Dist Stor Manager on behalf of Richard Mochnaczewski
Sent: Tue 6/19/2007 3:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Export Node and OS Migrations



Hi *,

We are currently in the middle of migrating our Novell file servers to Windows 
2003. We will be doing a copy of all our Novell file server data to our Windows 
2003 machines and then eventually deleting the Novell machine in the future. In 
the meantime, we will be running low on slots in our library because we will 
for a short time have the duplicate copies before we cut off our Novell 
servers.. If I do an export of our Novell data to get the data out of TSM and 
the library, it will free up our onsite slot issue, but what will happen to the 
reclamation for that server for my offsite tapes ?

Rich

HELP!!!! Migrations taking too long and pools filling up!

[Joni Moyer]

Hello Everyone!

Due to our tape drive shortage I have added a tremendous amount of disk to
hold the data for 24 hours.  It appears as if now it is taking a very long
time for the disk pools to migrate to tape and processes are still backing
up and causing contention with backups of the client data sometimes of up
to 10 hours.  How can I resolve this issue so that the clients receive a
quick backup and do not have I/O contention?  I thought that adding more
disk would help because the landing spot for the data is now a larger disk
pool that can house all of the data, but it seems like it's hitting it's
70% full mark and when I came in this morning the disk pool was up to 95%
full, there are many clients that are waiting to write their backups and
everything is locked up.  Any suggestions would be appreciated!  I don't
know what to do for this environment any longer and I am not allowed to buy
tape drives.  Thank you in advance!


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]

Expire inventory (or audit license) hangs migrations and backups

[Tomáš Hrouda]

Hi there,

Env: TSM server for MVS v4.2.0.0 with about 200 client nodes

At last time I had noted TSM server hangs when expire inventory or audit
license processes are running.
Some client backup sessions and all processes (migrations including audit or
expire itself) are freezed, otherwise administration is possible. After
recycling TSM server all gone OK.
My question: Is there some restrictions to simultaneous running of expire
inventory (or audit license) and migrations (or client backups)? Is it
posible that these two precesses can definitely hangs all other server work?
The system that I mentioned is relatively high-loaded and there is hard to
avoid collisions with backups.

Any help will be appreciated.
Sorry for my english :-)

Tom

Re: HELP!!!! Migrations taking too long and pools filling up!

[John Naylor]

Joni,
Looks like you were unlucky and got hit by some extra large backups, which
filled up your disk pool faster than it could be emptied
I assume this is what caused a lot of backups to be delayed, by  media
wair.
In truth it does sound as if you need  more or faster tape drives.
That aside what I do in a tape constrained environment is to run overnight
with a diskpool high migration set at 40% and a lo of 20%
You may want to experiment with these values.
I also run concurrent to that hourly triggered backups of the disk storage
pool to a tape copy pool
In effect I use 3 drives overnight .
It does mean that I am doing tape to tape pool copies during the day but I
have more drives available then.
This in not perfect but it works for me
John



Joni Moyer <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
17/08/2005 12:40
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@vm.marist.edu
cc

Subject
HELP  Migrations taking too long and pools filling up!






Hello Everyone!

Due to our tape drive shortage I have added a tremendous amount of disk to
hold the data for 24 hours.  It appears as if now it is taking a very long
time for the disk pools to migrate to tape and processes are still backing
up and causing contention with backups of the client data sometimes of up
to 10 hours.  How can I resolve this issue so that the clients receive a
quick backup and do not have I/O contention?  I thought that adding more
disk would help because the landing spot for the data is now a larger disk
pool that can house all of the data, but it seems like it's hitting it's
70% full mark and when I came in this morning the disk pool was up to 95%
full, there are many clients that are waiting to write their backups and
everything is locked up.  Any suggestions would be appreciated!  I don't
know what to do for this environment any longer and I am not allowed to
buy
tape drives.  Thank you in advance!


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




**

The information in this e-mail is confidential and may be legally privileged. 
It may not represent the views of Scottish and Southern Energy Group.

It is intended solely for the addressees. Access to this e-mail by anyone else 
is unauthorised. If you are not the intended recipient, any disclosure, 
copying, distribution or any action taken or omitted to be taken in reliance on 
it, is prohibited and may be unlawful. Any unauthorised recipient should advise 
the sender immediately of the error in transmission. Unless specifically stated 
otherwise, this email (or any attachments to it) is not an offer capable of 
acceptance or acceptance of an offer and it does not form part of a binding 
contractual agreement.

Scottish Hydro-Electric, Southern Electric, SWALEC, Atlantic Electric and Gas, 
S+S and SSE Power Distribution are trading names of the Scottish and Southern 
Energy Group.

**

Re: HELP!!!! Migrations taking too long and pools filling up!

[Iain Barnetson]

I kinda had the same issues, only 6 tape drives & 250Gb of diskpool
space and a lot of servers to backup.
What I did, which works for us, is all the Exchange & SQL jobs go direct
to tape, they're the biggest in terms of Gb, the rest are staggered to
diskpool.
The Big Exch & SQL jobs are allowed 2 mount points, never more than 1 of
those jobs running at a time. 
The Exch & SQL jobs have a higher priority than diskpool migration just
in case there's ever contention for tape drives.
The diskpool is set to migrate at 70% and allowed 4 mount points, lower
limit set to 25%
Before the DB get backed up in the morning the diskpool gets flushed to
tape.

Our setup is such that data is on disk for as short a time as possible,
this suits us as our TSM backups aare predominantly for DR. Recovering
data users have "disappeared" is done via Snapshots.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
John Naylor
Sent: 17 August 2005 13:20
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] HELP Migrations taking too long and pools
filling up!

Joni,
Looks like you were unlucky and got hit by some extra large backups,
which filled up your disk pool faster than it could be emptied I assume
this is what caused a lot of backups to be delayed, by  media wair.
In truth it does sound as if you need  more or faster tape drives.
That aside what I do in a tape constrained environment is to run
overnight with a diskpool high migration set at 40% and a lo of 20% You
may want to experiment with these values.
I also run concurrent to that hourly triggered backups of the disk
storage pool to a tape copy pool In effect I use 3 drives overnight .
It does mean that I am doing tape to tape pool copies during the day but
I have more drives available then.
This in not perfect but it works for me
John



Joni Moyer <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
17/08/2005 12:40
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@vm.marist.edu
cc

Subject
HELP  Migrations taking too long and pools filling up!






Hello Everyone!

Due to our tape drive shortage I have added a tremendous amount of disk
to hold the data for 24 hours.  It appears as if now it is taking a very
long time for the disk pools to migrate to tape and processes are still
backing up and causing contention with backups of the client data
sometimes of up to 10 hours.  How can I resolve this issue so that the
clients receive a quick backup and do not have I/O contention?  I
thought that adding more disk would help because the landing spot for
the data is now a larger disk pool that can house all of the data, but
it seems like it's hitting it's 70% full mark and when I came in this
morning the disk pool was up to 95% full, there are many clients that
are waiting to write their backups and everything is locked up.  Any
suggestions would be appreciated!  I don't know what to do for this
environment any longer and I am not allowed to buy tape drives.  Thank
you in advance!


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




**

The information in this e-mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy Group.

It is intended solely for the addressees. Access to this e-mail by
anyone else is unauthorised. If you are not the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be
taken in reliance on it, is prohibited and may be unlawful. Any
unauthorised recipient should advise the sender immediately of the error
in transmission. Unless specifically stated otherwise, this email (or
any attachments to it) is not an offer capable of acceptance or
acceptance of an offer and it does not form part of a binding
contractual agreement.

Scottish Hydro-Electric, Southern Electric, SWALEC, Atlantic Electric
and Gas, S+S and SSE Power Distribution are trading names of the
Scottish and Southern Energy Group.

**
--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

Re: HELP!!!! Migrations taking too long and pools filling up!

[Pétur Eyþórsson]

Joni

what size do you have on your tsm attrigates? the smaller you have them 
the slower the migration process is going to take, alsow do you have 
collocation on the storage pools you are migratig to if you do it is going 
to take logner to migrate. Have you found out where the bollteneck is on 
your system?.

What is the hardware you are running on?
 
 



Kær kveðja / Best regards,
Pétur Eyþórsson  · Tæknilegur ráðgjafi eServer & Storage · Tivoli Advanced 
Storage Solutons Techical Expert
 · MCSE · SNIA Professional  ·  SNIA FC-SAN Practitioner  ·  IBM C AIX S · 
TSM CP · TSRM CP · TASS DP · IBM SAN P
Sími/tel: +354 569-7700 · GSM: +354 863-0560 
www.nyherji.is





Joni Moyer <[EMAIL PROTECTED]> 
Sent by: "ADSM: Dist Stor Manager" 
17.08.2005 11:40
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
[ADSM-L] HELP  Migrations taking too long and pools filling up!






Hello Everyone!

Due to our tape drive shortage I have added a tremendous amount of disk to
hold the data for 24 hours.  It appears as if now it is taking a very long
time for the disk pools to migrate to tape and processes are still backing
up and causing contention with backups of the client data sometimes of up
to 10 hours.  How can I resolve this issue so that the clients receive a
quick backup and do not have I/O contention?  I thought that adding more
disk would help because the landing spot for the data is now a larger disk
pool that can house all of the data, but it seems like it's hitting it's
70% full mark and when I came in this morning the disk pool was up to 95%
full, there are many clients that are waiting to write their backups and
everything is locked up.  Any suggestions would be appreciated!  I don't
know what to do for this environment any longer and I am not allowed to 
buy
tape drives.  Thank you in advance!


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]

Commands to kill migrations and sessions from connecting in the dsmserv.opt

[Nancy L Backhaus]

MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <[EMAIL PROTECTED]>
From: Nancy L Backhaus <[EMAIL PROTECTED]>
Date: Wed, 29 Mar 2006 13:36:25 -0500
X-MIMETrack: Serialize by Router on NSB01/HealthNow(Release 6.5.4FP2|September 
12, 2005) at
 03/29/2006 01:36:29 PM,
Serialize complete at 03/29/2006 01:36:29 PM
Content-Type: multipart/alternative; boundary="=_alternative 0066363185257140_="

This is a multipart message in MIME format.
--=_alternative 0066363185257140_=
Content-Type: text/plain; charset="us-ascii"

What is the command to kill all migrations and  sessions in the
dsmserv,opt file.

NoMig Something??



Nancy Backhaus
Enterprise Systems
HealthNow, NY
716-887-7979
--=_alternative 0066363185257140_=
Content-Type: text/html; charset="us-ascii"


What is the command to kill all migrations 
and  sessions in the dsmserv,opt file.

NoMig Something??



Nancy Backhaus
Enterprise Systems
HealthNow, NY
716-887-7979
--=_alternative 0066363185257140_=--


CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole 
use of the intended recipient(s) and may contain proprietary, confidential, 
trade secret or privileged information.  Any unauthorized review, use, 
disclosure or distribution is prohibited and may be a violation of law.  If you 
are not the intended recipient or a person responsible for delivering this 
message to an intended recipient, please contact the sender by reply email and 
destroy all copies of the original
message.

Re: Expire inventory (or audit license) hangs migrations and back ups

[Loon, E.J. van - SPLXM]

Hi Tom!
I have seen this too a few days ago on my AIX server, running TSM 4.2.2.0.
It looks like some kind of deadlock on a logpage. You will see that the
expire inventory is just hanging and that one of your backup sessions is
hanging too.
You don't have to recycle the server though. As soon as you cancel the
hanging client session, the expire inventory process continues.
I haven't seen an APAR or fix for it, but since Tivoli implemented a the
command SHOW LOGPINNED in 4.2.2.1 I think it's a known problem.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-Original Message-
From: Tomáš Hrouda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 16, 2002 12:14
To: [EMAIL PROTECTED]
Subject: Expire inventory (or audit license) hangs migrations and
backups


Hi there,

Env: TSM server for MVS v4.2.0.0 with about 200 client nodes

At last time I had noted TSM server hangs when expire inventory or audit
license processes are running.
Some client backup sessions and all processes (migrations including audit or
expire itself) are freezed, otherwise administration is possible. After
recycling TSM server all gone OK.
My question: Is there some restrictions to simultaneous running of expire
inventory (or audit license) and migrations (or client backups)? Is it
posible that these two precesses can definitely hangs all other server work?
The system that I mentioned is relatively high-loaded and there is hard to
avoid collisions with backups.

Any help will be appreciated.
Sorry for my english :-)

Tom


**
For information, services and offers, please visit our web site: http://www.klm.com. 
This e-mail and any attachment may contain confidential and privileged material 
intended for the addressee only. If you are not the addressee, you are notified that 
no part of the e-mail or any attachment may be disclosed, copied or distributed, and 
that any other action related to this e-mail or attachment is strictly prohibited, and 
may be unlawful. If you have received this e-mail by error, please notify the sender 
immediately by return e-mail, and delete this message. Koninklijke Luchtvaart 
Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for 
the incorrect or incomplete transmission of this e-mail or any attachments, nor 
responsible for any delay in receipt.
**

Re: Expire inventory (or audit license) hangs migrations and back ups

[Jolliff, Dale]

Another variation on the theme:

On a 4.1.4.1 server here we see the 'log pinned' situation a LOT - very
heavily abused server.
One of the oddities is that once we clear the sessions, and do an
incremental db backup,
the log utilization doesn't drop until we issue an expire inventory command.

Running an expire inventory drives log utilization up at an extremely high
rate on this server, consequently expiration has not completed on this
server in a very long time.

I'm shutting down all other activity on the server over a 24 hour period
this weekend to see if we can force a full expiration and hopefully that
will alleviate the symptoms a bit.





-Original Message-
From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 16, 2002 6:43 AM
To: [EMAIL PROTECTED]
Subject: Re: Expire inventory (or audit license) hangs migrations and
back ups


Hi Tom!
I have seen this too a few days ago on my AIX server, running TSM 4.2.2.0.
It looks like some kind of deadlock on a logpage. You will see that the
expire inventory is just hanging and that one of your backup sessions is
hanging too.
You don't have to recycle the server though. As soon as you cancel the
hanging client session, the expire inventory process continues.
I haven't seen an APAR or fix for it, but since Tivoli implemented a the
command SHOW LOGPINNED in 4.2.2.1 I think it's a known problem.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-Original Message-
From: Tomáš Hrouda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 16, 2002 12:14
To: [EMAIL PROTECTED]
Subject: Expire inventory (or audit license) hangs migrations and
backups


Hi there,

Env: TSM server for MVS v4.2.0.0 with about 200 client nodes

At last time I had noted TSM server hangs when expire inventory or audit
license processes are running.
Some client backup sessions and all processes (migrations including audit or
expire itself) are freezed, otherwise administration is possible. After
recycling TSM server all gone OK.
My question: Is there some restrictions to simultaneous running of expire
inventory (or audit license) and migrations (or client backups)? Is it
posible that these two precesses can definitely hangs all other server work?
The system that I mentioned is relatively high-loaded and there is hard to
avoid collisions with backups.

Any help will be appreciated.
Sorry for my english :-)

Tom


**
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential
and privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may
be disclosed, copied or distributed, and that any other action related to
this e-mail or attachment is strictly prohibited, and may be unlawful. If
you have received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message. Koninklijke Luchtvaart
Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be
liable for the incorrect or incomplete transmission of this e-mail or any
attachments, nor responsible for any delay in receipt.
**

Re: Expire inventory (or audit license) hangs migrations and back ups

[Jane Bamberger]

I had that problem with expiration - my mail server kept pinning the
process - When it finally ran to completion it took 4-5 days, and expired
16M files.

Good luck!

Jane

%%
Jane Bamberger
IS Department
Bassett Healthcare
607-547-4750
- Original Message -
From: "Jolliff, Dale" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 16, 2002 8:11 AM
Subject: Re: Expire inventory (or audit license) hangs migrations and back
ups


Another variation on the theme:

On a 4.1.4.1 server here we see the 'log pinned' situation a LOT - very
heavily abused server.
One of the oddities is that once we clear the sessions, and do an
incremental db backup,
the log utilization doesn't drop until we issue an expire inventory command.

Running an expire inventory drives log utilization up at an extremely high
rate on this server, consequently expiration has not completed on this
server in a very long time.

I'm shutting down all other activity on the server over a 24 hour period
this weekend to see if we can force a full expiration and hopefully that
will alleviate the symptoms a bit.





-Original Message-
From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 16, 2002 6:43 AM
To: [EMAIL PROTECTED]
Subject: Re: Expire inventory (or audit license) hangs migrations and
back ups


Hi Tom!
I have seen this too a few days ago on my AIX server, running TSM 4.2.2.0.
It looks like some kind of deadlock on a logpage. You will see that the
expire inventory is just hanging and that one of your backup sessions is
hanging too.
You don't have to recycle the server though. As soon as you cancel the
hanging client session, the expire inventory process continues.
I haven't seen an APAR or fix for it, but since Tivoli implemented a the
command SHOW LOGPINNED in 4.2.2.1 I think it's a known problem.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-Original Message-
From: Tomáš Hrouda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 16, 2002 12:14
To: [EMAIL PROTECTED]
Subject: Expire inventory (or audit license) hangs migrations and
backups


Hi there,

Env: TSM server for MVS v4.2.0.0 with about 200 client nodes

At last time I had noted TSM server hangs when expire inventory or audit
license processes are running.
Some client backup sessions and all processes (migrations including audit or
expire itself) are freezed, otherwise administration is possible. After
recycling TSM server all gone OK.
My question: Is there some restrictions to simultaneous running of expire
inventory (or audit license) and migrations (or client backups)? Is it
posible that these two precesses can definitely hangs all other server work?
The system that I mentioned is relatively high-loaded and there is hard to
avoid collisions with backups.

Any help will be appreciated.
Sorry for my english :-)

Tom


**
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential
and privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may
be disclosed, copied or distributed, and that any other action related to
this e-mail or attachment is strictly prohibited, and may be unlawful. If
you have received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message. Koninklijke Luchtvaart
Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be
liable for the incorrect or incomplete transmission of this e-mail or any
attachments, nor responsible for any delay in receipt.
**

Re: Expire inventory (or audit license) hangs migrations and back ups

[Tomáš Hrouda]

OK, now is question, how can I recognize hanging client session? (There is
about 150 sessions at the time)

I did "q sess" to file last time it happens, but all session were at "Run"
state. In addition ... when I recognize it and cancel it, will the client
reestablish session with server to end up backup?

I see no good solution for this situation in automated manner (this is what
I need), except of prevent it - this means write script to test if no client
sessions are started at the time, disable clients, start expiration, and
past it stops, enable clients.
Any other idea?

Tom

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Loon, E.J. van - SPLXM
Sent: Thursday, May 16, 2002 1:43 PM
To: [EMAIL PROTECTED]
Subject: Re: Expire inventory (or audit license) hangs migrations and
back ups


Hi Tom!
I have seen this too a few days ago on my AIX server, running TSM 4.2.2.0.
It looks like some kind of deadlock on a logpage. You will see that the
expire inventory is just hanging and that one of your backup sessions is
hanging too.
You don't have to recycle the server though. As soon as you cancel the
hanging client session, the expire inventory process continues.
I haven't seen an APAR or fix for it, but since Tivoli implemented a the
command SHOW LOGPINNED in 4.2.2.1 I think it's a known problem.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-Original Message-
From: Toma9 Hrouda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 16, 2002 12:14
To: [EMAIL PROTECTED]
Subject: Expire inventory (or audit license) hangs migrations and
backups


Hi there,

Env: TSM server for MVS v4.2.0.0 with about 200 client nodes

At last time I had noted TSM server hangs when expire inventory or audit
license processes are running.
Some client backup sessions and all processes (migrations including audit or
expire itself) are freezed, otherwise administration is possible. After
recycling TSM server all gone OK.
My question: Is there some restrictions to simultaneous running of expire
inventory (or audit license) and migrations (or client backups)? Is it
posible that these two precesses can definitely hangs all other server work?
The system that I mentioned is relatively high-loaded and there is hard to
avoid collisions with backups.

Any help will be appreciated.
Sorry for my english :-)

Tom


**
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential
and privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may
be disclosed, copied or distributed, and that any other action related to
this e-mail or attachment is strictly prohibited, and may be unlawful. If
you have received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message. Koninklijke Luchtvaart
Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be
liable for the incorrect or incomplete transmission of this e-mail or any
attachments, nor responsible for any delay in receipt.
**

Re: Expire inventory (or audit license) hangs migrations and back ups

[Mark Stapleton]

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On
Behalf Of Jane Bamberger
> I had that problem with expiration - my mail server kept pinning the
> process - When it finally ran to completion it took 4-5 days, and expired
> 16M files.

Which goes to show that you simply *must* run a complete expiration on a
regular basis. If your current schedule doesn't allow it, you need to shove
the start time for events until you *do* have a window. In my experience, a
fair percentage of heavily-used/heavily-abused TSM servers that fail to run
properly often do so because of incomplete expirations.

--
Mark Stapleton ([EMAIL PROTECTED])

Re: Commands to kill migrations and sessions from connecting in the dsmserv.opt

[Andrew Carlson]

nomigrrecl will stop migrations and reclamations, but as far as I know,
if you want to remove it, you have to stop and restart the server after
it is removed from the options file.

--- Nancy L Backhaus <[EMAIL PROTECTED]> wrote:

> MIME-Version: 1.0
> X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
> Message-ID:
>
<[EMAIL PROTECTED]>
> From: Nancy L Backhaus <[EMAIL PROTECTED]>
> Date: Wed, 29 Mar 2006 13:36:25 -0500
> X-MIMETrack: Serialize by Router on NSB01/HealthNow(Release
> 6.5.4FP2|September 12, 2005) at
>  03/29/2006 01:36:29 PM,
>   Serialize complete at 03/29/2006 01:36:29 PM
> Content-Type: multipart/alternative; boundary="=_alternative
> 0066363185257140_="
> 
> This is a multipart message in MIME format.
> --=_alternative 0066363185257140_=
> Content-Type: text/plain; charset="us-ascii"
> 
> What is the command to kill all migrations and  sessions in the
> dsmserv,opt file.
> 
> NoMig Something??
> 
> 
> 
> Nancy Backhaus
> Enterprise Systems
> HealthNow, NY
> 716-887-7979
> --=_alternative 0066363185257140_=
> Content-Type: text/html; charset="us-ascii"
> 
> 
> What is the command to kill all
> migrations and  sessions in the dsmserv,opt file.
> 
> NoMig Something??
> 
> 
> 
> Nancy Backhaus
> Enterprise Systems
> HealthNow, NY
> 716-887-7979
> --=_alternative 0066363185257140_=--
> 
> 
> CONFIDENTIALITY NOTICE: This email message and any attachments are
> for the sole use of the intended recipient(s) and may contain
> proprietary, confidential, trade secret or privileged information. 
> Any unauthorized review, use, disclosure or distribution is
> prohibited and may be a violation of law.  If you are not the
> intended recipient or a person responsible for delivering this
> message to an intended recipient, please contact the sender by reply
> email and destroy all copies of the original
> message.
> 


Andy Carlson 
---
Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month,
The feeling of seeing the red box with the item you want in it:Priceless.