I think it depends on the size/load on the server.
For smaller environments we even use the midrange read intensive SSD's in
raid 1 (2 of them) or sometimes even raid 5 with a spare and they run for
years, this works just fine for S en M blueprints.
For very intensive environments we tent to use th
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 temporar
A similar script could use MOVE DATA instead of RECLAIM, which has the
advantage of checking as each MOVE ends to see if there are drive resources,
and intelligently picking a volume, before starting a new MOVE. It also can
check an external file for a "pause" or "halt" command, or parse the ac
We've had this problem as well. Our fix has been to define a maintenance
script MANUAL_RECLAIM that reclaims each storage pool in parallel, but with
a duration of 3 hours:
PARALLEL
RECL STG DESPOT-OFFSITE-LTO TH=60 DU=180 W=Y
...
SERIAL
An admin schedule will run the script every four hours, exce
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 wanting library resources. The TSM instances are blind to each
others needs. This _IS_ difficult to control.
The _current_ solution
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
To: ADSM-L@VM
On Wednesday 17 April 2013 19:09:31 you wrote:
> Hi,
>
> the output is very interlaced and so not that easily readable. Which
> command did you use to migrate the data from one pool to the other one?
Either an update stgp with low and high parameter or migrate stgp triggers the
same result.
The st
Hi, Stef. There is only a loose correlation between the devclass
directory and the volume directories. Would you please post the output of:
q vol /home/app/tsm/diskpool/diskpool13/diskpool/297D.BFS
On 4/17/2013 2:42 AM, Stef Coene wrote:
Hi,
We have a strange storage pool problem.
POOL4
Hi,
the output is very interlaced and so not that easily readable. Which
command did you use to migrate the data from one pool to the other one?
Regards,
Michael
On Wed, Apr 17, 2013 at 11:42 AM, Stef Coene wrote:
> Hi,
>
> We have a strange storage pool problem.
> POOL48 is next storage pool
Nope. Went directly to the "console" and typed the command. Activity log
shows the command just as I entered it.
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU
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 f=l
And check the lines regarding migration
~Rick Adamson
Jacksonville, FL.
-Original Message-
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."
To: ADSM-L@VM.MARIST.EDU
Date: 04/11/2012 11:45 AM
Subject:Re: [ADSM-L] Migration duration default?
Sent by:"ADSM: Dis
"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
IST.EDU
Från: amit jain
Sänt av: "ADSM: Dist Stor Manager"
Datum: 03/15/2012 17:46
Ärende: Re: migration threads for random access pool and backups issue
Thanks to all for these valuable inputs. Appreciate it a lot.
Well this is first time this data is getting backed up.
For now her
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 unde
Since your disk pool is much smaller than what you are backing up, plus you
have plenty of tape drives, it doesn't make much sense to send those 3 large
filespaces to the diskpool.
Create a new management class, send each of those 3 filespaces directly to the
tape drives, bypassing the disk p
The last time I changed servers, I had our network group change the name of the
current server, then create a dns alias using our usual dns name to point to
the old server.
On the day of the switch, we simply pointed that alias to the new tsm server
and all went smoothly. I insist that all my t
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 proces
Were you running ExtendedFabric on the old switch? If so, is it setup on
the new switch ports for the ISL's over the dwdm?
Check for port errors on the vtl connection and isl links.
Rick
woodbm
To
Sent by
That's a relief!
--
Bruce T. Harvey
UNIX System Administrator, SAIC | DHS/ICE OCIO
1120 Vermont Ave, Suite 300, Washington, DC 20005
202.261.9589 (office) - 202.465.9537 (cell) | harv...@saic-dc.com
| -Original Message-
| From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On B
We've also had this morning pick all 4 output volumes in the same pool.
Gretchen got it in 1 - it's doing reclamation.
I also found in the SUMMARY table that the volumes showed up as having been
RECLAIMED, not migrated.
We set reclaim to 100 on the source pool, killed and restarted, and Bob's
You
Have you tried to lower the number of processes to 3 or increase it to 5
to see how they end up picking volumes? If it goes away in 3 and you
get two CDLPOOL output volumes, that could mean a silly limitation
somebody left in. However, if it's always 1, whether 2, 3, or 9,
there's still something
es.
>
> If everything was done correctly and verified properly you should be able to
> start up your TSM database.
>
> Then you will have to redefine your library and drives.
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On
Yeah, as I dig into this it becomes more complicated.
We have a number of pools:
Disk Pools:
diskpool
Sequential Access Storage Pools:
ltopool
8mmpool1 (which needs to die)
archivepool
ltoarchive
reclaimpool
Copy Storage po
ssage-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt
Buff
Sent: Monday, October 12, 2009 3:37 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migration for Windows-based installation
Disk for the current TSM server is IDE/PATA in a RAID5 array internal
to the machine - thoug
Disk for the current TSM server is IDE/PATA in a RAID5 array internal
to the machine - though the OS is on a (eep!) single IDE/PATA drive
connected to the motherboard.
Kurt
On Mon, Oct 12, 2009 at 13:19, David McClelland wrote:
> Okay, another fun question for you Kurt, investigating some altern
When we migrated to a new server and LTO4 from LTO1, we installed all of the
new stuff and tested the hardware with the TSM version we were running.
When that was working well, we drained all of the disk pools, backed up the
database from the existing server, shut it down, attached the old tape
dri
Okay, another fun question for you Kurt, investigating some alternative lines
of simply migrating your current TSM server instance to new hardware: is the
disk upon which your current TSM database/recovery log/storage pool live
internal to your old server, or is it instead hosted upon external d
So, what happens to all the tapes I have offsite at Iron Mountain, and
the archives I have stored in my basement vault, etc.
I'll be perusing the archives as you suggest, but this isn't exactly
crystalline to me just yet.
A complicating factor that I hadn't realized until I did a bit of
digging j
Start from scratch. Install TSM at the level you would like, move and
configure the library. Point the clients at the new server and go. That first
backup will necessarily be a full. Will take longer than usual, but easy.
This method allows you go "clean up" your database.
Keep the old serve
I'd prefer to be able to migrate server data as much as possible,
including the diskpool, but if it it would be an incredibly difficult
maneuver (or take inordinate amounts of time, say on the order of more
than a 4-day weekend) and/or the downside of losing the diskpool is
relatively minor, I coul
Are you looking purely at a lift and shift hardware change here, or at a clean
installation of TSM Server (at 5.5.3 for example) and migrating clients into
the new instance?
Cheers,
/David Mc
London, UK
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On B
Hi TSM-ers!
Just to let you all know, I found the cause of the storagepool migration
issue: a show cont reveiled that all files in the diskpool belonged to
just one (very large) client. That's why TSM only starts one migration.
There doesn't seem to be a way to force TSM to do multiple migrations
f
o:ads...@vm.marist.edu] On Behalf Of
Huebschman, George J.
Sent: maandag 5 oktober 2009 12:02
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migration problem
It sounds a lot like TSM is allocating space in your disk pool for a lot
of data from many clients and finding itself maxed out. It is not
always how
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Huebschman, George J.
Sent: maandag 5 oktober 2009 12:02
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migration problem
It sounds a lot like T
nager [mailto:ads...@vm.marist.edu] On Behalf Of
Remco Post
Sent: vrijdag 2 oktober 2009 17:10
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migration problem
Have you ever considered increasing the high threshold? IIRC TSM won't
start new automig processes when migration is already running, and
will onl
Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Remco Post
Sent: vrijdag 2 oktober 2009 17:10
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migration problem
Have you ever considered increasing the high threshold? IIRC TSM won't
star
o:ads...@vm.marist.edu] On Behalf Of
Remco Post
Sent: vrijdag 2 oktober 2009 17:10
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migration problem
Have you ever considered increasing the high threshold? IIRC TSM won't
start new automig processes when migration is already running, and
will only start as many
deviceclass has mountlimit=drives which is 30 drives.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Remco Post
Sent: vrijdag 2 oktober 2009 17:10
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migration
Have you ever considered increasing the high threshold? IIRC TSM won't
start new automig processes when migration is already running, and
will only start as many processes as there are different clients
having data in your pool. Also, check out your mountlimit on the tape
devclass.
Furthermor
Behalf Of
Huebschman, George J.
Sent: vrijdag 2 oktober 2009 16:03
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migration problem
The diskpool was full, but high migration is 5%.
A low highmig threshold could easily start off migrations that run just
one file then quit, especially if there are large files
Reclamation Type:
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Eric Vaughn
Sent: vrijdag 2 oktober 2009 15:01
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migration problem
Do you have a high and low
oktober 2009 15:01
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migration problem
Do you have a high and low migration threshold set?
Eric Vaughn
Technical Administrator
Stevenson University
Office (443)334-2301
evau...@stevenson.edu
>>> "Loon, EJ van - SPLXM" 10/2/2009 8:33 AM &g
Do you have a high and low migration threshold set?
Eric Vaughn
Technical Administrator
Stevenson University
Office (443)334-2301
evau...@stevenson.edu
>>> "Loon, EJ van - SPLXM" 10/2/2009 8:33 AM >>>
Hi TSM-ers!
Today I came in the office and customers complained about failing
backups. I che
That last migration process is probably working on the data for a
single nodename, where there can be no more than one migration process
for one nodename.
It may be that there is still a lot of new data entering that disk
pool such that migration is still going on; or, the tape/drive has
issues w
Dear Bj0rn,
I agree wiht Curtis, we did the same thing also when migrating Netbackup or
Brighstor to TSM.
BR,
Martin
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of W.
Curtis Preston
Sent: 12 Mei 2009 1:57
To: ADSM-L@VM.MARIST.EDU
Subject: R
Are you saying you're going to stop using TSM and start using some other
backup software, but that you have a bunch of tapes that you still want to
restore from?
This is generally impossible with any backup software. (There are some
exceptions like Backup Exec -> NetBackup, but they're from the s
On May 11, 2009, at 9:09 AM, Shawn Drew wrote:
- The Management Class on the receiving server (I.E. Import server)
determines where the data will end up
- Storage pools can be named whatever you want them to be. As long
as the
management class matches the name
- Nothing "needs" to be the same o
Drew
Sent by: "ADSM: Dist Stor Manager"
05/08/09 09:29 AM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: Migration from Windows to Linux
First step is to be more descriptive on what type of hardware you have.
You mentioned the librar
d any attachments without reading, forwarding or
saving them. Thank you.
Shawn Drew
Sent by: "ADSM: Dist Stor Manager"
05/08/09 09:29 AM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: Migration from Windows to Linux
First step
First step is to be more descriptive on what type of hardware you have.
You mentioned the library, but not the Drives. Are they on a SAN? Do
they have dual connections, etc?
If you can share them, you should setup the new TSM server as the library
manager and make the old one a Library client
Hi,
On 7 mei 2009, at 21:42, Desalegne Guangul wrote:
Hi Everyone,
I need all your help on this. There are a lot of topics on the archive
about migration but none of them address my questions. I'm
migrating TSM
v 5.3.3.1 on Windows 2000 server to TSM v 5.5.0 on SuSE Linux (SELS
10 sp
2).
Might I ask how you have determined it is going to itself rather than the
"next" storage pool? (by the volume assignment of the destination volume?)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Hart, Charles A
Sent: Monday, August 25, 2008 3:59 P
On Aug 21, 2008, at 1:12 PM, Lepre, James wrote:
Hello Everyone
I have a question regarding Migration
We are running Tivoli 5.4.1.1. on a windows platform, using a Quantum
DXI 5500 VTL. My question is during a migration which tapes are used
first, tapes that are not full or scratch tapes.
Check out the entry for "Filling" on here:
http://people.bu.edu/rbs/ADSM.QuickFacts
Regards,
Shawn
Shawn Drew
Internet
[EMAIL PROTECTED]
Sent by: ADSM-L@VM.MARIST.EDU
08/21/2008 01:12 PM
Please respond to
ADSM-L@VM.MARIST.EDU
To
ADSM-L
cc
S
Hello Everyone
I have a question regarding Migration
We are running Tivoli 5.4.1.1. on a windows platform, using a Quantum
DXI 5500 VTL. My question is during a migration which tapes are used
first, tapes that are not full or scratch tapes. Meaning will TSM fill
up a tape to 100% then use scr
Hi Rick
Can you sent the script to the forum , like to see .
Regards
Robert
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard
Mochnaczewski
Sent: Tuesday, February 26, 2008 6:06 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] migration vs
Hi Rick,
I'm just about to write such a script ( moving data from a 3494 library to a
SL8500 ). Can you send me a copy of it ?
Rich
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Richard Rhodes
Sent: Tuesday, February 26, 2008 10:51 AM
To: ADSM-L@
When I moved our primary pools from 3494/3590's to 3584/3592's, I used
movedata.
I found the movedat was much easier to control the process. I coded a
script that would vary
the number of movedata's running concurrently depending upon the number of
free/available tape drives. During the day It w
I believe this is the general recommended sequence in most contexts where
the initial incrementals are directed to disk to be later migrated to tape.
That covers most sites.
For those sites with VTLs the situation changes. You are not migrating from
primary storage pools, disk based, to copy p
TSM has their "wheel of life" with the recommended operational procedure:
http://www.redbooks.ibm.com/redbooks/SG245416/wwhelp/wwhimpl/common/html/wwhelp.htm?context=SG245416&file=21-02.htm
Thanks,
Ron
Ron Welsh
Systems Administrator
Systems & Technology
Open Solutions In
Is there really recomended sequence every TSM Environment should follow?
Or does it depend on your Individual environmental needs?
Tim
Larry Clark wrote:
1- backups nodes
2- backup primary disk pools to tape (copypool)
3- migrate primary disk pool to tape
4- backup primary tape pool to tape
Well done !
> -Message d'origine-
> De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De
> la part de Larry Clark
> Envoyé : mardi 2 octobre 2007 13:03
> À : ADSM-L@VM.MARIST.EDU
> Objet : Re: [ADSM-L] Migration question
>
> 1- backups nodes
> 2- backup primary disk pools to tape (
1- backups nodes
2- backup primary disk pools to tape (copypool)
3- migrate primary disk pool to tape
4- backup primary tape pool to tape (copypool) ( this allows picking up
files to copypool not completed in 2 before 3 was triggered)
5- db backup
6- expiration
7- reclaim primary tape pool
8- re
May I suggest a sequence ?
1- backups nodes
2- backup primary disk pools to tape
3- backup primary tape pool to tape
4- migrate primary disk pool
5- db backup
6- expiration
7- reclaim primary tape pool
8- reclaim copy pool
Pierre
> -Message d'origine-
> De : ADSM: Dist Stor Manager [mai
On 02/10/2007, at 2:35 AM, Dollens, Bruce wrote:
I have a question that I feel a little stupid in asking.
What is the difference between migration and backup primary (disk) to
copy (tape)?
Other people have already answered, so I won't bother. :)
I am working on changing my scheduling up an
hi Bruce,
migration *MOVES* your clients' data from a PRIMARY storage pool
to a NEXT PRIMARY storage pool, e.g. from DISK to a primary TAPE pool.
backup stgpool *COPIES* clients' data stored on a PRIMARY pool
to a COPY pool (that has to be SEQUENTIAL, i.e. a tape pool).
after the successful back
And about your sequence list.
- Expiration will trigger the reclamations
- You might want to schedule your backup primary to copy prior to your
migration. Assuming you are backing up to disk, then migrating to tape.
That way, you avoid the overhead of mounts of tapes when you are creating
copypool
Migration moves the data from one primary pool to another. A storage pool
backup is copying the data from a primary storage pool to a copy storage
pool.
Mark Remeta
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Dollens, Bruce
Sent: Monday, Octob
Migration involves moving between primary storage pools.
The conventional situation was ( before VTLs) a site would have a hierarchy
of storage. The clients would back up to disks to permits a large number of
concurrent backups, then those backups to disk would be migrated to tape.
Both are primar
Here is some information that might prove helpful. I recently received
this from Tivoli support;
One consideration when upgrading the TSM Server is that 5.4 is 64bit
code, so, if your current 5.2 (or even 5.3) server is 32bit, you'll need
to do one of the following in order to upgrade to 5.4:
1.
On Jul 28, 2007, at 2:02 PM, Mario Wilson Castro Torres wrote:
Morning,
Where find documents about migration of TSM 5.2 to TSM 5.3.4
Your best bet is go to to the TSM Support Page,
http://www-306.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManager.html
and search on 5.3 u
>> On Wed, 11 Jul 2007 08:40:48 -0400, Richard Rhodes <[EMAIL PROTECTED]> said:
> While not what you are trying to do, next year I'm going to have a
> similar copy pool issue. Next year we plan to replace our old 3494
> libs (3590 drives) by expanding our new 3584 libs (3592 drives).
> The 3494
On Wed, Jul 11, 2007 at 04:00:57PM +0200, CAYE PIERRE wrote:
> Hi
>
>
>
> Try move nodedata which can move data's even from copystg to another copystg
I wish it did this! In my current 5.3 server, I would love to be able to
move copy storage pool volumes to another copy storage pool. There is no
"ADSM: Dist Stor Manager" wrote on 07/11/2007
10:34:18 AM:
> Do you keep all of your Copy Pool tapes in the library?
Yes, the copy pool is offsite from the primary, but connected via
DWDM. All tapes are within the libs - no manual tape movement.
So we have a onsite 3584/3592 and a offsite 3494/3
Do you keep all of your Copy Pool tapes in the library? If so, why not
move data? Email me off line about how our STORServer Manager product
can help out here.
Or why not simply start a new copy pool and leave the old one to expire
(perhaps not completely, but enough to make the load on the prim
|
| cc:
|
| Subject: Re: Migration of a Copy storag
|
| cc:
|
| Subject: Re: Migration of a Copy s
"ADSM: Dist Stor Manager" wrote on 07/11/2007
02:39:52 AM:
> version 5.4.0.3 it is not possible to have a NEXTSTORAGEPOOL on a copy
pool
> to migrate data from stage 1 DISK to stage 2 on TAPE, it is also not
> possible to make a script to use move data command to move data from
stage
> 1 to stage
|
| To: ADSM-L@VM.MARIST.EDU
|
| cc:
Hi,
What is the size of the copy stg to migrate ?
Pierre
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Anders
St¦hlbom
Envoyé : mercredi 11 juillet 2007 08:40
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Migration of a Copy storage pool impossibl
And, ofcourse, You must migrate data from tape from aix to windows.
2007/6/13, Richard Sims <[EMAIL PROTECTED]>:
On Jun 13, 2007, at 11:07 AM, TSM User wrote:
> To migrate a server TSM from a platform to another (AIX to Windows)
>
> Recommended strategy to migrate DB?
>
> DSMSERV DUMPDB ???
>
On Jun 13, 2007, at 11:07 AM, TSM User wrote:
To migrate a server TSM from a platform to another (AIX to Windows)
Recommended strategy to migrate DB?
DSMSERV DUMPDB ???
Export ???
Use Export, as described in the Admin Guide. Technote 1137678
emphasizes using Export.
And, my sympathies in
-Mark Stapleton wrote: -
>Has anyone out there done this sort of migration by restoring the TSM
>database from the old server to the new server?
>
>I've never worked with zLinux before, but my understanding is that
>zLinux partitions use the same type of filespaces (EXT2, EXT3,
>ReiserFS,
Richard Sims wrote:
>
> On Apr 10, 2007, at 7:57 PM, David Bronder wrote:
>
> > ... However, the
> > automated migrations seem to not be very sensitive to the LOWMIG value
> > (I've been moving it closer to HIGHMIG but the migrations still keep
> > on running). ...
>
> David -
>
> See "Migration" i
Well David,
TSM will always choose the node with the most data to migrate first, and
won't check again till that is done. If you have one node with much
more data than any other, that could explain why the lowmig value
appears to have little effect.
Regards
Steve
Steven Harris
AIX and TSM adm
On Apr 10, 2007, at 7:57 PM, David Bronder wrote:
... However, the
automated migrations seem to not be very sensitive to the LOWMIG value
(I've been moving it closer to HIGHMIG but the migrations still keep
on running). ...
David -
See "Migration" in the TSM Concepts redbook, and "LOwmig"
in
Allen S. Rout wrote:
>
> This used to be the only way to accomplish this effect, and it's still
> what I do now. But When I Get Around To It, I'm going to change to the
> somewhat new
>
> migrate stgpool [yadda] lowmig=0 duration=[minutes]
>
> which has the advantage that you don't have to actually
We run at 80/60. Do you empty the pools during the day? We run
migration each day until our disk pools are empty.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Gregory Lynch
Sent: Tuesday, April 10, 2007 2:50 PM
To: ADSM-L@VM.MARIST
Allen,
Bingo!
Kelly
Kelly J. Lipp
VP Manufacturing & CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
[EMAIL PROTECTED]
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Allen S. Rout
Sent: Tuesday, April 10, 2007 4:
>> On Tue, 10 Apr 2007 14:06:46 -0600, Kelly Lipp <[EMAIL PROTECTED]> said:
> An even better way is to lower to 0 0, then immediately update again to
> 90 0 (migration will continue since it started) and then sometime later
> set low back to 70.
This used to be the only way to accomplish this e
Gregory Lynch wrote:
> No, caching is not enabled
>
How are you running the migrate? If you just give a storage pool name,
then it will still use the thresholds in the storage pool configuration.
That would keep it from getting below 70% if that's it's set for. You
can override that by setting th
Typically, a site will completely drain their cachepool before nightly
backups run. To do this, create an admin schedule that lowers the
thresholds to highmig=0 lowmig=0. This will fire migration processes
and continue to run them until all of the data has been migrated. If
caching is enabled on
No, caching is not enabled
***
Gregory Lynch
Lead Programmer Analyst
IT Infrastructure/Systems Administration
Stony Brook University Medical Center
HSC Level 3, Room 121 ZIP 8037
Phone: 631-444-9783
[EMAIL PROTECTED]
This e- mail mess
Gregory Lynch wrote:
> Hello All,
>
> I have noticed that migration has been kicking off during the backup
> window and is slowing down the nightly backups. We have migration running
> during the day via an admin schedule for a hour, but the diskpool never
> seems to get below 70%. I checked the p
We upgrade from 5.1 to 5.3 earlier this year. It went very well. The
upgrade does take some
time to convert the TSM db. There is a procedure for cleaning up the Win
system objects
you will need to run. See the v5.3 readme file and the installation guide.
As with any upgrade, I would strongly
Ive done it,
Lay down 5.2 first, or you are in for a world of hurt.
Jeremy Cloward
"In this golden age of communication , means everyone talks at the
same time"
Justin Sullivan
TSM User <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manage
Aha. Thanks, I'll go get 5.3.3...
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
PAC Brion Arnaud
Sent: Thursday, May 18, 2006 11:36 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migration not in Summary table
Hi,
Search for APAR IC47709 on IB
Mine is even stranger - TSM server 5.3.2 on Win2K3 -
about 2 weeks ago I stopped getting migration activity for one disk pool
in the summary table, but migration for the OTHER disk pool still shows
up. (And yes, I've confirmed migration does run successfully for both
pools.)
Haven't reported it
Hi,
Search for APAR IC47709 on IBM web site : not exactly what you're
experiencing, but a variant of it. Another bug (serious one to my eyes,
as there is no other convenient way monitoring migration processes) to
thank IBM for ...
Cheers.
Arnaud
**
1 - 100 of 290 matches
Mail list logo
