-L] TSM Migration Question
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
ices Offerings
From: "Plair, Ricky"
To: ADSM-L@VM.MARIST.EDU
Date: 09/21/2016 08:57 AM
Subject:Re: [ADSM-L] TSM Migration Question
Sent by:"ADSM: Dist Stor Manager"
Nothing out of the normal, the below is kind of odd but I'm not sure it
has a
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
ptember 21, 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 th
:
> Auto-copy Mode: Client
> Contains Data Deduplicated by Client?: No
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> Skylar Thompson
> Sent: Wednesday, September 21, 2016 11:19 AM
> To:
nesday, September 21, 2016 11:19 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Migration Question
Can you post the output of "Q STG F=D" for each of those pools?
On Wed, Sep 21, 2016 at 02:33:42PM +, Plair, Ricky wrote:
> Within TSM I am migrating an old storage pool on a DD42
Can you post the output of "Q STG F=D" for each of those pools?
On Wed, Sep 21, 2016 at 02:33:42PM +, Plair, Ricky wrote:
> 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 an
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 it is migrat
uot;ADSM: Dist Stor Manager"
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
011 10:17
À : ADSM-L@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 implementation
av: "ADSM: Dist Stor Manager"
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 is the architecture of database files.
You ha
T.EDU
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
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 5.
erg Pohlmann
-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 the
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 U
changing these clients, especially the HA client?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Richard Rhodes
Sent: Thursday, October 16, 2008 11:31 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Library Manager and Migration question
some more
some more comments . . .
> > 228GB. We have finally received approval to move this to a new server,
> > upgrade to 5.5 and split the clients up to reduce the DB size.
We created new instances, then started assigning all new clients to the new
instances. Then, we went back and cherry picked the
-Nothing you do with TSM, I mean NOTHING, will result in data loss, if done
correctly.
-The whole POINT of TSM library sharing is so that you don't have to
partition the library; if you partition the library you can't share the
drives dynamically between the TSM instances.
-Splitting the clients
We origionally had 2 (at different datacenters) big TSM instances (+150gb
db each), each with their own library. In preparation for adding new
instances we converted to standalone library manager instances (one at each
site), then brought on new instances. It all worked very well. There are
a co
and Migration question
Thanks, hadn't thought about the restartable restores, good idea.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Howard Coles
Sent: Wednesday, October 15, 2008 1:07 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Li
M-L@VM.MARIST.EDU
> Subject: [ADSM-L] Library Manager and Migration question
>
> Hi All,
>
> We currently have 1 TSM server ver 5.3.3 on AIX 5.3, with a large
> database, 228GB. We have finally received approval to move this to a
> new server, upgrade to 5.5 and split the clients u
h, Debbie (IT)
Sent: Wednesday, October 15, 2008 10:52 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Library Manager and Migration question
Hi All,
We currently have 1 TSM server ver 5.3.3 on AIX 5.3, with a large database,
228GB. We have finally received approval to move this to a new server,
u
.EDU
> Subject: [ADSM-L] Library Manager and Migration question
>
> Hi All,
>
> We currently have 1 TSM server ver 5.3.3 on AIX 5.3, with a large
> database, 228GB. We have finally received approval to move this to a
> new server, upgrade to 5.5 and split the clients up to red
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
> Due to the size and complexity of our environment, we contracted with
a
> vendor to do the setup and start the process. Now that the contract
> has been signed and we have started our planning sessions, the vendor
> is having a pr
Hi All,
We currently have 1 TSM server ver 5.3.3 on AIX 5.3, with a large database,
228GB. We have finally received approval to move this to a new server, upgrade
to 5.5 and split the clients up to reduce the DB size. We would like to have 4
LPAR's created on the new server, 1 for a Library m
Sent: Thursday, June 05, 2008 9:35 AM
To: ADSM-L@VM.MARIST.EDU
Subject: LTO1 to LTO4 migration question
I'm trying to find the best way to migrate a 3584 library from LTO1 to LTO4
media. For a period of time, both drive types will be installed. I know
the library can be partitioned, but c
It should not put tapes in wrong drive. LTO4 drive can read/write
LTO3 tape and can read LTO2 but not LTO1.
David Longo
>>> TSM User <[EMAIL PROTECTED]> 6/5/2008 11:01 AM >>>
Thanks for the info--this is what I was hoping to read. We will be
retaining enough LTO1 drives in the environment for l
Thanks for the info--this is what I was hoping to read. We will be
retaining enough LTO1 drives in the environment for long enough to migrate,
and we do expect to actively migrate data as well as force all new data to
the new media. Mostly, I wanted to be certain that the various components
would
@VM.MARIST.EDU
Subject: Re: [ADSM-L] LTO1 to LTO4 migration question
You do not have to partition the library, mixed LTO devices can exist in
same logical library now.
Install and configure the LTO4 drives. Then label/checkin LTO4 tapes
and create new Tape Stg Pools. Then take an existing Mgmnt Class
You do not have to partition the library, mixed LTO devices
can exist in same logical library now.
Install and configure the LTO4 drives. Then label/checkin LTO4
tapes and create new Tape Stg Pools. Then take an existing Mgmnt
Class and point it to new tape pool. Data will then go there and gra
I'm trying to find the best way to migrate a 3584 library from LTO1 to LTO4
media. For a period of time, both drive types will be installed. I know
the library can be partitioned, but capacity is already pretty tight, and it
would almost certainly require continuous "redrawing the borders" as the
.
- Original Message -
From: "Timothy Hughes" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, October 02, 2007 11:34 AM
Subject: Re: [ADSM-L] Migration question
Is there really recomended sequence every TSM Environment should follow?
Or does it depend on your Individual env
1:35 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Migration question
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
02, 2007 3:25 AM
Subject: Re: [ADSM-L] Migration question
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
-M
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- b
- reclaim copy pool
- Original Message -
From: "CAYE PIERRE" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, October 02, 2007 3:25 AM
Subject: Re: [ADSM-L] Migration question
May I suggest a sequence ?
1- backups nodes
2- backup primary disk pools to tape
3- backup primary tap
tor Manager [mailto:[EMAIL PROTECTED] De
> la part de Dollens, Bruce
> Envoyé : lundi 1 octobre 2007 18:36
> À : ADSM-L@VM.MARIST.EDU
> Objet : [ADSM-L] Migration question
>
> I have a question that I feel a little stupid in asking.
>
> What is the difference between migrat
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
copypool volumes from primary storage pool volumes ( that have been
migrated from disk to tape.).
- Original Message -
From: "Dollens, Bruce" <[EMAIL PROTECTED]>
To:
Sent: Monday, October 01, 2007 12:35 PM
Subject: [ADSM-L] Migration question
I have a question that I feel a
, October 01, 2007 12:36 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Migration question
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)?
I am working on changing my scheduling up and the recommended order of steps
I was
.
Copypools are also used at some sites for vaulting. The copies of the
primary data that is created on the copypools is sent offsite.
- Original Message -
From: "Dollens, Bruce" <[EMAIL PROTECTED]>
To:
Sent: Monday, October 01, 2007 12:35 PM
Subject: [ADSM-L] Migration que
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)?
I am working on changing my scheduling up and the recommended order of
steps I was given is:
Backup clients
Migration
Backup primary to copy
Backup db
Expi
Gerry,
We migrated from 5.1.7.0 to 5.3.0.0, and then to 5.3.3.3 on z/OS.
If you have any questions, feel free to contact me directly.
Kevin Kinder
admin(at)wvadmin.gov
>>> [EMAIL PROTECTED] 8/22/06 1:57 PM >>>
Good Day To All.
Currently, we are running 5.2.3.3 on a Z/os platform
Good Day To All.
Currently, we are running 5.2.3.3 on a Z/os platform and we
are preparing to migrate to 5.3
Couple of questions:
1) Has anyone in the Z/os world gone to 5.3.3 yet?
2) From 5.2.3.3 can we migrate directly to 5.3.3? Or do we
migrate from 5.2.3.
I know I can set the migration delay to more than 0 days to delay
migration.
I would like to keep all of my active versions of backup on disk and
migrate inactive versions only to tape.
Is there a way to specify only inactive versions of files are eligible for
migration?
The information transmi
Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D.
Rodriguez
Sent: Thursday, August 11, 2005 12:08 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Server to Server migration question
Robert,
The only other thing I can think of right now is to have you start a migration
and let it run until it
.
Rodriguez
Sent: Wednesday, August 10, 2005 10:32 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Server to Server migration question
Robert,
You have a naming problem. Your storage pool name is I2000_server1, but your
copy destination is sending it to a storage pool called I2000_postback!
Update your
, August 10, 2005 10:32 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Server to Server migration question
Robert,
You have a naming problem. Your storage pool name is I2000_server1, but your
copy destination is sending it to a storage pool called I2000_postback!
Update your copydestination in the
Mark D.
Rodriguez
Sent: Wednesday, August 10, 2005 9:58 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Server to Server migration question
Robert,
You are right it looks like the destination is correct. I am assuming the
error message you got was on the target server, correct? What is the out
:
Low-level Address:
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D.
Rodriguez
Sent: Wednesday, August 10, 2005 9:58 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Server to Server migration question
Robert,
You are right it looks
??
Regards Robert
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D.
Rodriguez
Sent: Wednesday, August 10, 2005 9:19 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Server to Server migration question
Robert
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Of Mark D. Rodriguez
Sent: Wednesday, August 10, 2005 8:54 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Server to Server migration question
Robert,
When you are doing virtual volumes like you are doing the virtual volume on the
ta
Server migration question
Robert,
Could you please post the output of the following commands:
q mg standard active
q co standard active t=a f=d
Then I can see a little more clearly what might be going on.
--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc
EMAIL PROTECTED] On Behalf Of Mark D.
Rodriguez
Sent: Wednesday, August 10, 2005 8:54 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Server to Server migration question
Robert,
When you are doing virtual volumes like you are doing the virtual volume on the
target server is actually managed as an ar
t: Re: Server to Server migration question
Robert,
When you are doing virtual volumes like you are doing the virtual volume on the
target server is actually managed as an archive object.
Therefore, I would bet that the archive copygroup for that management class is
pointing at the diskpool. Also, it
Check to see if DISKPOOL is defined. It may be the default for DIRMC,
assuming this is for WinNT.
At 09:19 PM 8/10/2005 +0300, you wrote:
Hi to all
I tried to make a server to server migration here the steps I made:
On source Server named SERVER1
1. I define a server SERVER2 (target
Robert,
When you are doing virtual volumes like you are doing the virtual volume
on the target server is actually managed as an archive object.
Therefore, I would bet that the archive copygroup for that management
class is pointing at the diskpool. Also, it is a good practice to put
server nodes
Hi to all
I tried to make a server to server migration here the steps I made:
On source Server named SERVER1
1. I define a server SERVER2 (target server)
2. I define a devclass SERVERCLASS with device type SERVER and servername
SERVER2
3. I create a stg SERVER1_POOL with devcl
Ralph,
The migration process will pick the node that is currently occupying the
greatest amount of space in the disk pool, and will migrate all of that
node's data (not just the largest individual files belonging to that node)
to tape before it checks again to see if we're below the low migration
I am running TSM 5.1.9 on AIX 4.3.3 . My primary disk pool is 490GB
with the himig=95, lowmig=90 and migprocess=1 . Occasionally, I hit the
95% mark before the normal scheduled migration takes place. When that
happens the automigration starts and I would expect it to stop once it
gets below the
intressting send me a privet email.
/Christian Svensson
-Ursprungligt meddelande-
Från: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Krishnan,
Vyju
Skickat: den 15 augusti 2003 15:46
Till: [EMAIL PROTECTED]
Ämne: Migration Question
Hello folks,
Any one here who had done migration to TSM
Hello folks,
Any one here who had done migration to TSM from other backup software
products like StorageTek REEL Librarian, Legato NetWorker, CA BrightStor,
etc. I am currently using STK REEL Products and looking for a best
compatible replacement for this. Any help in this regard would be highly
Subject: Re: Tape reclaim & stgpool migration question/
Reclamation % is set to 50 on tapepool.Reclamation Threshold: 50
Migration set as High Mig Pct: 80 on SQUEnTIal ACCESS Stgpool disk with
devclass cfile.
Low Mig Pct: 0
Migration takes place but after certain retri
PROTECTED]
Subject: Re: Tape reclaim & stgpool migration question/
You may have a little confusion about Reclamation and Migration.
Do 'q stg xxxpool f=d' and find 'Reclamation Threshold' which governs how
reclamation will be done.
Highmig=xx and lowmig=xx are parame
You may have a little confusion about Reclamation and Migration.
Do 'q stg xxxpool f=d' and find 'Reclamation Threshold' which governs how reclamation
will be done.
Highmig=xx and lowmig=xx are parameters that works only for Migration of data from one
pool to another. When a stg reaches highmig
All-
I recently created reclaim stgpool with upper mig to 80% and lower mig to
0%.
But the CFILE devclass stgpool that is disk when gets to 80 % migrate level
, tapes do not stop to reclaim but it continues .What might have been
missing
Thanks in advance
Balanand Pinni
nt: Friday, September 13, 2002 2:44 AM
To: [EMAIL PROTECTED]
Subject: Migration question
Good morning to all of you.
I have a quick question. Does migration automatically use all available
tape drives?
Thanks in advance
Farren Minns - TSM and Solaris System Admin - John Wiley and Sons Ltd
Our Chiche
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To:[EMAIL PROTECTED]
cc:
Subject:Re: Migration question
No, each storage group has a setting that controls the number of migration
processes used during migration. Do a Q STG F=D to show the
setting, and UPD STG
No, each storage group has a setting that controls the number of migration processes
used during migration. Do a Q STG F=D to show the setting, and UPD STG
MIGPR=<#> to change it. For example, to use 3 drives during the migration
of a stgpool named DISKPOOL, enter UPD STG DISKPOOL MIGPR=3.
olumes.
Bill SmoldtSSSI
STORServer, Inc.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Roy Lake
Sent: Tuesday, May 07, 2002 6:07 AM
To: [EMAIL PROTECTED]
Subject: Migration Question
Hi Guys,
I have a quick question for you
I am about to delet
Hi Guys,
I have a quick question for you
I am about to delete all of the promary disk storage pools for a
resizing and re-placement exercise.
IBM have given me their recommendations as:-
1. Backup stgpool.
2. Update lo mig and Hi mig to 0 to migrate everything to tape.
Now, am I right in sayi
To: [EMAIL PROTECTED]
cc:
Subject: Migration Question
Hi Guys,
I have a quick question for you
I am about to delete all of the promary disk storage pools for a
resizing and re-placement
enior Storage Administrator
Selective Insurance
[EMAIL PROTECTED]
(973) 948-1306
-Original Message-
From: Roy Lake [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 07, 2002 8:07 AM
To: [EMAIL PROTECTED]
Subject: Migration Question
Hi Guys,
I have a quick question for you
I am about to delet
Thanks but that willl not work here. I have mount retention set at 1 minute.
When I inherited the system, mount retention was set at 1 HOUR and with
collocation and lots of nodes *SM had almost all 24 tape drives tied up
preventing other batch processes and HSM from getting any drives! It's
behavi
EMAIL PROTECTED]
Subject: Re: Migration question
Thank you, and all the others who have responded. I inherited *SM and those
who set it up before me were under the impression that it WOULD back the
data up twice. I believed otherwise but I gave them the benefit of the doubt
and asked. Again, thank you
ECTED]; [EMAIL PROTECTED]
+ Subject: Re: Migration question
+
+
+ From: [EMAIL PROTECTED]
+ To: [EMAIL PROTECTED]
+ Date: Fri, 17 Aug 2001 13:31:08 -0400
+ Subject: Re: Migration question
+
+ 'Course TSM is smart!
+
+ We do what you describe every night - saves a lot of tape mounts,
+ especially
+
Yes, it is smart enough that it won't backup the data twice. It keeps
track of all that stuff.
David Longo
>>> [EMAIL PROTECTED] 08/17/01 12:58PM >>>
My concern is this. I do not want to back up the data TWICE from the disk
pool to the offsite pool. (Once from disk to offsite pool and again fro
s the DB and only copies
files that aren't in the destination copy pool already.
-Original Message-
From: Alan Davenport [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 17, 2001 12:58 PM
To: [EMAIL PROTECTED]
Subject: Migration question
Hello fellow *SMers! I'm thinking of
Hello fellow *SMers! I'm thinking of redoing how our backup pool
migration/tape copies process is done to increase efficiency. We are
currently processing this way:
Backuppool (disk) migration to primary onsite tape pool (3490).
Tapepool (onsite) copy backed up to vault (offsite) tape copy pool.
80 matches
Mail list logo
