Completely normal, working as designed. We do this on purpose. Depending on how
you set the migration and reclamation thresholds, that first FILE storage pool
will be internally reclaimed before any migration starts. That reclamation
process will be labeled "Migration". (This has tri
PE).
The disk pool was filling faster than it could migrate.
We recently resurrected an old 200TB Dell Powervault attached to this
server (regular FILE DEVCLASS WITH DEDUPE and NEXTPOOL is tape) and as an
"emergency" measure, decided to change the disk stgpool NEXTPOOL to point
to the Power
Subject: [EXTERNAL] [ADSM-L] TSM 6.2.3 data migration
Good Morning,
Had an issue with TSM a few weeks ago and did a DB restore. I had to drop the
TSM DB before I could do the restore and now that the restore was done migrate
and reclamations do not run.
I have had several looking but we can
HI all,
many thanks for all who sent an answer. It was very helpful for me.
thanks
regards
Michael Stahlberg
On 4/17/19 3:42 PM, Mondore, E Andrew wrote:
> We are also planning to migrate from AIX to Linux. One thing to note is that
> if you are using physical tape drives like we are, you
e only 2 or 4 disks mirrored
> with a spare disk, or if it might be useful to use Raid5. Has anybody
> experiences with it, please. The documentation I found about this is in
> my eyes not up to date and so I'm asking this group now, for their
> experiences about this.
> It will be also fine,
to use Raid5. Has anybody
experiences with it, please. The documentation I found about this is in
my eyes not up to date and so I'm asking this group now, for their
experiences about this.
It will be also fine, if somebody did such a migration already. I read
about export and import the database from
The problem was corrected but, I have no idea how.
I stopped the migration and replication kicked off. I let the replication run
for an hour or so while I was at lunch. When I got back I stopped replication
and restarted the migration. I have no idea how but it used the correct volumes
Ricky,
could you please send the output of the following commands:
1. Q MOUNT
2. q act begint=-12 se=Migration
Also, the only way that the stgpool would migrate back to itself would be
if there was a loop, meaning your disk pool points to the tape pool as the
next stgpool, and your tape pool
Is it migrating or reclaiming at 70% as defined.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Plair,
Ricky
Sent: Wednesday, September 21, 2016 8:50 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM Migration Question
Nothing out of the normal
, 2016 11:35 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Migration Question
The only oddity I see is that DDSTGPOOL4500 has a NEXTSTGPOOL of TAPEPOOL.
Shouldn't cause any problems now since utilization is 0% but would get
triggered once you hit the HIGHMIG threshold.
Is there anything
The only oddity I see is that DDSTGPOOL4500 has a NEXTSTGPOOL of TAPEPOOL.
Shouldn't cause any problems now since utilization is 0% but would get
triggered once you hit the HIGHMIG threshold.
Is there anything in the activity log for the errant migration processes?
On Wed, Sep 21, 2016 at 03:28
9.4
Pct Util: 70.4
Pct Migr: 70.4
Pct Logical: 95.9
High Mig Pct: 100
Low Mig Pct: 95
Migration Delay: 0
Migration Continue:
> The nextpool is correct and migration is hi=0 lo=0 and using 25 migration
> process, but I had to stop it.
>
> Now when I restart it the migration process it is migrating to the old
> storage volumes instead of the new storage volumes. Basically it's just
> migrating from one
Within TSM I am migrating an old storage pool on a DD4200 to a new storage pool
on a DD4500.
First of all, it worked fine yesterday.
The nextpool is correct and migration is hi=0 lo=0 and using 25 migration
process, but I had to stop it.
Now when I restart it the migration process
p; Systems
>UW Information Technology
>
>> -Original Message-
>> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
>> Bill Mansfield
>> Sent: Friday, July 29, 2016 8:43 AM
>> To: ADSM-L@VM.MARIST.EDU
>> Subject: [ADSM-L] AIX to Linux m
sfield
> Sent: Friday, July 29, 2016 8:43 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] AIX to Linux migration performance
>
> Has anyone migrated a big TSM server from AIX to Linux using the
> Extract/Insert capability in 7.1.5? Have a 2.5TB DB to migrate, would
> like s
I thought that functionality was long gone in 5.x?
Thank you,
Systems Administrator
Systems & Network Services
NYU IT/Technology Operations Services
212-998-1110
646-539-8239
On Fri, Jul 29, 2016 at 11:43 AM, Bill Mansfield <
bill.mansfi...@us.logicalis.com> wrote:
> Has anyone migrated a
Has anyone migrated a big TSM server from AIX to Linux using the Extract/Insert
capability in 7.1.5? Have a 2.5TB DB to migrate, would like some idea of how
long it might take.
Bill Mansfield
Roger
Worth mentioning is that the issue is most likely compounded by the
migration/reclamation process running during a backup, the performance hit to
the TSM server can be severe.
You may find a significant reduction in task processing times if you do isolate
them.
In the past I have
L.
Sent: Thursday, February 18, 2016 9:34 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Migration should preempt reclamation
This is a tough one. On the one hand we want Reclamation to use as many tape
drives as possible, but not consume them all. We also have multiple TSM
instances wanti
der the impression that higher priority tasks could preempt
> lower priority tasks. That is, migration should be able to preempt
> reclamation. But it doesn't. A very careful reading of Administrator's
> Guide tells me that it does not.
>
> We're having a problem with a large client
Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Roger
Deschner
Sent: Wednesday, February 17, 2016 8:43 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Migration should preempt reclamation
I was under the impression that higher priority tasks could preempt
lower priority tasks
Could you reduce the "Reclamation Processes" count on the storagepool by one
leaving a tape drive free for migration?
David
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Roger
Deschner
Sent: Wednesday, February 17, 2016 8:43 PM
I was under the impression that higher priority tasks could preempt
lower priority tasks. That is, migration should be able to preempt
reclamation. But it doesn't. A very careful reading of Administrator's
Guide tells me that it does not.
We're having a problem with a large client backup
Followup,
We upgraded a customer from 6.3.5 to 7.1.1.100 today (Windows TSM server).
The disk pool where TSM/VE 7.1.1 data lands will now indeed do multiple
concurrent migration processes out to a sequential pool, even though all the
data is owned by one node. (It's migrating at the filespace
running the EKM software are being retired due
to OS level. Is there a migration path to get my EKM keystore in to SKLM?
The customer's last Passport renewal has them licensed for SKLM.
Any help or suggestions is very appreciated!
Bill Boyer
DSS, Inc.
(610) 927-4407
Enjoy life
I have a customer that is still using the original Java based EKM for server
up the LTO keys. The servers running the EKM software are being retired due
to OS level. Is there a migration path to get my EKM keystore in to SKLM?
The customer's last Passport renewal has them licensed for SKLM.
Any
Didn't I read that there were supposed to be changes in the 7.1 server to make
migration run at the filespace level? Which would make this a multi-thread
process - anybody with experience? I have a 6.3.5 customer with the same
issue, but don't have a 7.1 customer in production to verify
Does any one is using storage pool migration from de-dupe pool to non de-dupe
pool? Am looking for some migration performance statistic so that I can compare
the same with one of our customer environment, currently I am getting very poor
performance in migration approx. 25 GB in 5 hrs, even
I've been going over logs of tape mounts, looking for a tape performance
issue. I watched the tape library for a while during migration, and the
robot was being kept very busy, mounting and dismounting the same set of
tapes over and over. When each tape volume is mounted and dismounted as
many
- 15.699 G 87,2 87,2 100 99
POOL48
POOL
POOL48 FILE_POOL-9.878 G 29,5 29,5 90 70
48
However, when we start migration, the data is written from pool DISKPOOL to
DISKPOOL just like a reclamation!:
442
POOL
POOL48 FILE_POOL-9.878 G 29,5 29,5 90
70
48
However, when we start migration, the data is written from pool DISKPOOL to
DISKPOOL just like a reclamation!:
442 MigrationVolume
/home/app/tsm/diskpool
POOL
POOL48 FILE_POOL-9.878 G 29,5 29,5 90 70
48
However, when we start migration, the data is written from pool DISKPOOL to
DISKPOOL just like a reclamation!:
442 MigrationVolume
/home/app/tsm
.
The strange thing is that I just started the migration as test and now the
correct storage pool is used!
I have no idea why, but it's working :)
Stef
Hi All
I need to migrate an SAP enviroment from one country to another - and would
appreciate a sanity check of my thoughts so far...
Current environ is SAP on Oracle on AIX, TSM (5.5) is on Windows.
Target environ is SAP on Oracle on AIX, TSM (5.5) is on AIX.
My bit is the db migration
.
(I do not use a duration parameter)
First migration finishes after a few minutes, migrating 500mb. Lower
than i expected, i guess
Second migration finishes after 30 minutes, migrating 138gb.
Third migration finishes after 1.5 hours, migrating 819gb
But the pool now shows about 24% utilised, so
Do you have a migration delay setting on the disk pool by any chance?
Regards,
Shawn
Shawn Drew
-Original Message-
From: ADSM-L@VM.MARIST.EDU [mailto:ADSM-L@VM.MARIST.EDU]
Sent: Thursday, February 14, 2013 5:41 AM
To: ADSM-L@VM.MARIST.EDU
Subject
Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Shawn
DREW
Sent: Thursday, February 14, 2013 11:20 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Odd Migration Behaviour
Do you have a migration delay setting on the disk pool by any chance?
Regards,
Shawn
Hi. No, migdelay set to 0
Thanks
On 14 February 2013 16:19, Shawn DREW shawn.d...@us.bnpparibas.com wrote:
Do you have a migration delay setting on the disk pool by any chance?
Regards,
Shawn
Shawn Drew
-Original Message-
From: ADSM-L
: Re: [ADSM-L] Odd Migration Behaviour
Do you have a migration delay setting on the disk pool by any chance?
Regards,
Shawn
Shawn Drew
-Original Message-
From: ADSM-L@VM.MARIST.EDU [mailto:ADSM-L@VM.MARIST.EDU]
Sent: Thursday, February 14, 2013 5
: Odd Migration Behaviour
Hi
Thanks for the response. There was a backup in progress, but it had only
backed up 7gb. There was about 1.5tb in the pool. The other clients had
finished backing up several hours earlier. Migs ran as expected, but
completed, leaving 1.5tb in the pool
I will find out
Linux Server - 6.1.5.100
Is there a default value for manual Migration, that I am not aware of? I
never use the DUR value. Yesterday around 14:40, I started a manual
migration (mig stg backuppool lo=0). This morning at 7:26am I see the
message:
ANR4925W Migration process 1727 terminated
help mig stg on TSM 6.2 on AIX says DUration
Specifies the maximum number of minutes the migration will run before
being automatically cancelled. When the specified number of minutes
elapses, the server will automatically cancel all migration processes
for this storage pool. As soon
My point exactly. I DID NOT specify a DUR value - I never do. Help says
it should have run until lo=value, which I set to 0.
From: Ehresman,David E. deehr...@louisville.edu
To: ADSM-L@VM.MARIST.EDU
Date: 04/11/2012 11:45 AM
Subject:Re: [ADSM-L] Migration duration default?
Sent
Do you use a maintenance script?
When configured you have the option to specify the duration value,
perhaps this is where the message is coming from.
Query the script using: q script script-name f=l
And check the lines regarding migration
~Rick Adamson
Jacksonville, FL.
-Original
@VM.MARIST.EDU
Date: 04/11/2012 12:59 PM
Subject:Re: [ADSM-L] Migration duration default?
Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
Do you use a maintenance script?
When configured you have the option to specify the duration value,
perhaps this is where the message is coming
Svensson
Cell: +46-70-325 1577
E-mail: christian.svens...@cristie.se
CPU2TSM Support: http://www.cristie.se/cpu2tsm-supported-platforms
Från: Christian Svensson
Skickat: den 14 mars 2012 07:07
Till: ADSM: Dist Stor Manager
Ämne: SV: migration threads
Hi
A migration process will always only use 1 process per node, independent on the
storage media. So if you migrate disk tape, it's 1 process per node, and if
you do tape tape it's only 1 process per node.
As for the original poster, you claim that you need to backup 300TB of data.
I'm
Hello,
is there a description or experience, how to migrate a TSM server
from TSM 6.1 Windows 2008 32bit
to TSM 6.2 Windows 2008 R2 64bit ?
What are the steps?
Is it less risk to use separat servers?
Thanks in advance
Andreas.
Also, using a random access disk pool that is undersized will result in
migration potentially kicking off while the backup/archive process is still
running. It has been my experience, and I have often read, this situation has
an enormous negative impact to the TSM server performance.
~Rick
That's also correct. The hugely negative impact from running migration while
performing backups is due to the heavy load migration puts on the database
(aswell as stealing valuable I/O from your disks which should be used for
backups).
Regards
Daniel
Daniel Sparrman
Exist i Stockholm AB
Thanks to all for these valuable inputs. Appreciate it a lot.
Well this is first time this data is getting backed up.
For now here is what I was not aware and what I have done: 1. On Random
Access pools multiple migration sessions can be generated, only if we
backup on multiple nodes ? Is my
the data somewhere
else.
b) For ALL storage pools, there will be 1 migration process per node. It doesnt
matter if it's random, sequential or a CD. It's always gonna be 1 process per
node.
c) Migration processes is usually not the issue. The issue is somewhere else.
So dont get blind on the 1
Hi Wanda,
Glad to see you at Pulse, but I got a similar problem here in Sweden where the
migration only use one process during migration.
I was thinking of to open a PMR to understand why it only use one drive.
Best Regards
Christian Svensson
Cell: +46-70-325 1577
E-mail: christian.svens
I'm assuming the number of filling tapes isn't increasing, it's higher than
you want, but stable. yes?
As i'm sure you are aware, this is normal behavior. I've also been there
and tried to fight it. In that instance I ran a job after the migration
that did a move data on the smallest volumes
pool.
W
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of amit
jain
Sent: Sunday, March 11, 2012 12:09 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] migration threads for random access pool and backups issue
Hi,
I have to backup large data
I'm having a problem with FILLING tapes multiplying out of control,
which have very little data on them.
It appears that this happens at the end of migration, when that one last
collocation group is being migrated, and all others have finished. TSM
sees empty tape drives, and less than
Is there a way, short of combining collocation groups, to deal with this
problem?
some options
1 Reduce the number of migration processes
2 Increase the time between migrations eg rather than daily do weekly.
3 do reclamation after migration.
AFAIK the combination of migration processes
sessions the, server starts only one migration
process and one tape mount.
As per ADMIN GUIDE the Migration for Random Access is Performed by node.
Migration from random-access pools can use multiple processes.
My Question:
1. On Random Access pools multiple migration sessions can be generated,
only if we
evironment (you do
need to upgrade TSM) and it's not such a big-bang migration.
However you do this, it's going to take a some solid preparation and
planning.
Make sure you get somebody that has good TSM 5, TSM 6 and LTO tape skills.
On Sat, Dec 3, 2011 at 7:50 AM, venkatb tsm-fo
This has been the migration strategy we adopted, and are right now in
the middle of. New server machine, new TSM version, the client nodes
make fresh, new backups spread over a period of time. The old system
gradually expires away until you can get rid of it.
Run the new server on 6.2.3, instead
we cheeck out 100% full tapes from lib and
check in free tape and assign to stgpool, since last5years almost 1500 full
tapes are in boxes, when some restoration comes, TSM will ask for check in the
required volumes, and we check in, once finishes we removes, during the
migration check
in, once finishes we removes,
during the migration check-in check-out task will become difficult, How can i
shorten this procedure
6)usually LTO5 media box shows that 3TB (2:1) compression, whether TSM uses
this compression ratio ?
It sounds like you have a fairly lengthy list of items
@VM.MARIST.EDU
Objet : [ADSM-L] Ang: Re: Tsm v6 migration question
That's not really something new to TSM v6. For performance reasons, it has
always been recommended to separate database and log on different spindles.
As with v6, at least for larger implementations, the same rule of thumb
ADSM-L@VM.MARIST.EDU
Datum: 03/25/2011 14:47
Ärende: Re: Ang: Re: Tsm v6 migration question
Hello Daniel,
You say : ' That's not really something new to TSM v6'.
DB2 is now the DBMS for TSM, and if DB2 improve database, DB2 has system
requirement who was not the same in previous version
My
Objet : [ADSM-L] Tsm v6 migration question
We are preparing to migrate our tsm v5,5,4 system to 6.2.2.
Are there any rules of thumb for relating db size in v5.5.4 with what we will
need under v6?
I assume it will be somewhat larger being a truly relational structure.
Thanks for any help
...@afnor.org
Sänt av: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
Datum: 03/24/2011 11:06
Ärende: Re: Tsm v6 migration question
Hello Gary,
Effectively, the database grows between 10 and 20 %. (more if new features,
like dedup, are intalled)
But, the most important with the 6.x
We are preparing to migrate our tsm v5,5,4 system to 6.2.2.
Are there any rules of thumb for relating db size in v5.5.4 with what we will
need under v6?
I assume it will be somewhat larger being a truly relational structure.
Thanks for any help.
Gary Lee
Senior System Programmer
Ball State
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Lee, Gary D.
Sent: Wednesday, March 23, 2011 10:44
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Tsm v6 migration question
We are preparing to migrate our tsm v5,5,4 system to 6.2.2.
Are there any rules
My experience from the latest upgrades are that the database will
grow by 10% when upgrading from 5.5 to 6.2.2.2.
2 days ago upgraded a 5.5 server to 6.2.2.2 and this happened
with the database size:
**
*** --- Q DB F=Dfrom TSM
.
The problem is we have to maintain the current TSM server's IP address.
Which means that we'll need to use a temp address on the new server
until after the migration is complete, shut down the old server, change
IPs, and then bring up the new server.
My question is has anyone here done
Senior System Programmer
Ball State University
phone: 765-285-1310
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Howard
Coles
Sent: Wednesday, February 23, 2011 5:27 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Migration, IP address change
server's IP address.
Which means that we'll need to use a temp address on the new server
until after the migration is complete, shut down the old server, change
IPs, and then bring up the new server.
My question is has anyone here done this that would have suggestions on
steps related
Hello!
I have some users that are upgrading their 2003 (32-bit) 2 node cluster to 2008
(64-bit) in the very near future. They plan on using the same two machines in
what is called an in-place cluster migration. Does anyone have any experience
with this?
I understand that the local hosts
: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] On Behalf Of Rhuobhe
[tsm-fo...@backupcentral.com]
Sent: Friday, February 04, 2011 12:25 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Windows Cluster migration/update and TSM
Hello!
I have some users that are upgrading their 2003 (32-bit) 2 node
@VM.MARIST.EDU] On Behalf Of Rhuobhe
[tsm-fo...@backupcentral.com]
Sent: Friday, February 04, 2011 10:25 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Windows Cluster migration/update and TSM
Hello!
I have some users that are upgrading their 2003 (32-bit) 2 node cluster to 2008
(64-bit) in the very near
Good day everyone,
I've been kicking around a couple different methods to migrate. In one of my
sites I have the luxury of a new server and library to export to, which is
working well.
Has anyone tried to install a fresh 6.2 instance on a current system running
5.5 , then remove the library
06, 2010 6:10 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Storage Pool Migration
We have TSM 5.5. Shortly after this was originally setup at the start of this
year data from the DIRMC storage pool was migrated to tape due to the settings
for the DIRMC storage pool not being correct. Now 9 months
We have TSM 5.5. Shortly after this was originally setup at the start of this
year data from the DIRMC storage pool was migrated to tape due to the settings
for the DIRMC storage pool not being correct. Now 9 months later the DIRMC
storage pool is still only at 3% of capacity. The migrated data
: [ADSM-L] Storage Pool Migration
We have TSM 5.5. Shortly after this was originally setup at the start of this
year data from the DIRMC storage pool was migrated to tape due to the settings
for the DIRMC storage pool not being correct. Now 9 months later the DIRMC
storage pool is still only at 3
I have a TSM V5.5 server on AIX. I need to get all of the data to a
Windows or Linux TSM environment on x86.
Export node will work well for everything EXCEPT a NAS node (you have to
really love these little caveats and exceptions). A backup/restore or
unload/load will probably fail due to
On 12 aug 2010, at 19:54, Strand, Neil B. wrote:
I am thinking that I will have to do a full restore to a spare NAS
device and then back it all up again.
why not back it al up just from the source, you do a full backup once a week?
anyway
--
Met vriendelijke groeten/Kind Regards,
It is legacy data from legacy sources.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Remco Post
Sent: Thursday, August 12, 2010 2:38 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Server migration
On 12 aug 2010, at 19:54, Strand, Neil
...@vm.marist.edu] On Behalf Of
Remco Post
Sent: Thursday, August 12, 2010 2:38 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Server migration
On 12 aug 2010, at 19:54, Strand, Neil B. wrote:
I am thinking that I will have to do a full restore to a spare NAS
device and then back
@VM.MARIST.EDU
To
ADSM-L
cc
Subject
[ADSM-L] TSM Server migration
I have a TSM V5.5 server on AIX. I need to get all of the data to a
Windows or Linux TSM environment on x86.
Export node will work well for everything EXCEPT a NAS node (you have to
really love these little caveats and exceptions
Testing hsm client, when creating migration job. choose source files tab
and whether I choose New File or New Directory when I choose browse
and select drive it shows Drive C: on Server but the OK button doesnt
result in any response.
m Brown
Systems Specialist - Project Leader
Central Hudson
On May 31, 2010, at 4:02 AM, Mehdi Salehi wrote:
Hi experts,
A client is restoring a large object (say a filesystem image) from disk
storage pool. What happens If migration starts and above client is still
restoring the object that should be migrated?
TSM realizes when a session or process
Hi experts,
A client is restoring a large object (say a filesystem image) from disk
storage pool. What happens If migration starts and above client is still
restoring the object that should be migrated?
Thanks
Wanda,
I am seeing something roughly similar, but different enough that it may be
irrelevant to your question-- or well understood, but not by me.
My TSM server is on LInux and is at 5.5.4.1. A backup of a primary tape pool
to an offsite library is scripted to start 11 processes, assuming
I suspect that these thumb-twiddling processes are impeded by locks, but
pursuing lock issues is beyond the ken of the software customer.
Richard Sims
That was a misunderstanding, David.
Regards,
Mehdi
Hi,
- When a storage pool reaches the high threshold of migration, how TSM
selects filespaces to migrate?
- When a filespace is migrated, does it include all active and inactive
backups?
Thanks
...@vm.marist.edu] On Behalf Of
Mehdi Salehi
Sent: 17 May 2010 09:53
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] what filespaces are candidate for migration?
Hi,
- When a storage pool reaches the high threshold of migration, how TSM
selects filespaces to migrate?
- When a filespace is migrated, does
Thanks for the link.
P.S:
Nobody is born as expert.
: Re: [ADSM-L] what filespaces are candidate for migration?
Thanks for the link.
P.S:
Nobody is born as expert.
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.819 / Virus Database: 271.1.1/2870 - Release Date: 05/16/10
19:26:00
why does 5.4 need to be uninstalled?
if the add/remove programs is not allowing uninstall, what are other
avenues are there to uninstall
migration
why does 5.4 need to be uninstalled?
if the add/remove programs is not allowing uninstall, what are other
avenues are there to uninstall
Hello all,
I need some help. I recently moved to a new Brocade SAN switch running 4 GB.
My copy pools, which interface through a SAN switch and down the DWDN to get to
my copy pool library which interfaces the same way, are running very poorly.
They average around 7 MB/s. Prior to the move
To
Sent by: ADSM: ADSM-L@VM.MARIST.EDU
Dist Stor cc
Manager
ads...@vm.marist Subject
.EDU Migration
The apars fixed in this release doc for 6.1.2.1 and also 6.1.3 says there
is a fix for IC62884 (migration hang).
I'm at 6.1.2.1, and still see the symptoms documented in the APAR.
Can anybody tell me whether this really IS fixed in 6.1.3?
If yes I'll go there, but I'd rather not if there's no fix
1 - 100 of 884 matches
Mail list logo
