Re: 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 -Message d'origine- De : ADSM: Dist Stor 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 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 Expiration Reclamation Start all over again Thanks!
Re: Migration question
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- reclaim copy pool - Original Message - From: CAYE PIERRE [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU 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 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 [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 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 Expiration Reclamation Start all over again Thanks!
Re: Migration question
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 (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- reclaim copy pool - Original Message - From: CAYE PIERRE [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU 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 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 [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 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 Expiration Reclamation Start all over again Thanks!
Re: 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 (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- reclaim copy pool - Original Message - From: CAYE PIERRE [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU 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 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 [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 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 Expiration Reclamation Start all over again Thanks!
Re: Migration question
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=SG245416file=21-02.htm Thanks, Ron Ron Welsh Systems Administrator Systems Technology Open Solutions Inc. 2091 Springdale Road Cherry Hill, NJ 08003 phone: 856-874-4121 email: [EMAIL PROTECTED] website: http://www.opensolutions.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Tuesday, October 02, 2007 11: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 (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- reclaim copy pool - Original Message - From: CAYE PIERRE [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU 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 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 [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 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 Expiration Reclamation Start all over again Thanks!
Re: Migration question
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 pools. The whole issue of migration dissappears, and you simply back up then do your VTL data to copypools. For those sites that have VTLs and high speed tape, they might be granular. Directing their large database backups, exports, mksysbs, (large files) to high speed tape directly and directing the remaining backups to the VTL. Both then copied to copypools. So, yes, every solution is situation dependent. What hardware you have to meet your needs and impress others with...:-). But it sounded from your initial post that you were in a primary storage pool on disk situation. - Original Message - From: Timothy Hughes [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU 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 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 (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- reclaim copy pool - Original Message - From: CAYE PIERRE [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU 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 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 [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 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 Expiration Reclamation Start all over again Thanks!
Re: Migration question
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 primary storage pools. Copypools are copies of data in primary storage pools. Their purpose is to provide for the loss of data in the primary pools and are populated using backup stg to the copypool. Fio example, a tape volume goes bad in your primary storage pool, you can recover it from the copypool. 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: ADSM-L@VM.MARIST.EDU Sent: Monday, October 01, 2007 12:35 PM Subject: [ADSM-L] 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 given is: Backup clients Migration Backup primary to copy Backup db Expiration Reclamation Start all over again Thanks!
Re: Migration question
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, 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 given is: Backup clients Migration Backup primary to copy Backup db Expiration Reclamation Start all over again Thanks! Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately. Please be advised that someone other than the intended recipients, including a third-party in the Seligman organization and government agencies, may review all electronic communications to and from this address.
Re: Migration question
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 volumes from primary storage pool volumes ( that have been migrated from disk to tape.). - Original Message - From: Dollens, Bruce [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 01, 2007 12:35 PM Subject: [ADSM-L] 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 given is: Backup clients Migration Backup primary to copy Backup db Expiration Reclamation Start all over again Thanks!
Re: Migration question
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 backup of a primary storage pool, you will have 2 copies of data on TSM server, and you can send the 2nd copy to an off-site location (vault). see: help migrate stg help backup stg hope it helps. regards Gabriel Peter On 1 Oct 2007, 18:35, 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)? 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 Expiration Reclamation Start all over again Thanks!
Re: Migration question
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 and the recommended order of steps I was given is: Backup clients Migration Backup primary to copy Backup db Expiration Reclamation Start all over again I'd change that order slightly to: Backup clients Backup disk pool(s) Migration Backup tape pool(s) Backup db Expiration Reclamation Repeat ad nauseum. Better to backup the storage pool data while it's still on disk, rather than to flush it out to tape and then back it up - saves on the amount of data read from tape. Some data may well still flush down to tape before the first backup stgpool runs, which is why you want to backup the tape pool as well after migration is complete.
Re: migration question
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 threshold yet. So if that node has enough data on disk, it could easily account for this behavior. -Bill Bill Kelly Auburn University OIT 334-844-9917 On Thu, 9 Sep 2004, Levi, Ralph wrote: 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 90% mark. It typically does not. Instead, it will continue to until it gets to the mid 70% level. My maxsize threshold is 20gb but with only 1 migprocess running that wouldn't account for such a big migration. Does anyone have any ideas ? Thanks, Ralph
Re: Migration question
No, each storage group has a setting that controls the number of migration processes used during migration. Do a Q STG stgpool F=D to show the setting, and UPD STG stgpool MIGPR=# to change it. For example, to use 3 drives during the migration of a stgpool named DISKPOOL, enter UPD STG DISKPOOL MIGPR=3. Steve Schaub Systems Engineer Haworth, Inc [EMAIL PROTECTED] 616-393-1457 Desk 616-836-6962 Cell Siempre Hay Esperanza [EMAIL PROTECTED] 09/13 3:43 AM 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 Chichester based offices have amalgamated and relocated to a new address John Wiley Sons Ltd The Atrium Southern Gate Chichester West Sussex PO19 8SQ Main phone and fax numbers remain the same: Phone +44 (0)1243 779777 Fax +44 (0)1243 775878 Direct dial numbers are unchanged Address, phone and fax nos. for all other Wiley UK locations are unchanged **
Re: Migration question
Thanks for that I see now that we have only ever been using one drive! I'll use two from now on. Thanks again Farren Steve Schaub [EMAIL PROTECTED]@VM.MARIST.EDU on 13/09/2002 11:56:28 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] 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 stgpool F=D to show the setting, and UPD STG stgpool MIGPR=# to change it. For example, to use 3 drives during the migration of a stgpool named DISKPOOL, enter UPD STG DISKPOOL MIGPR=3. Steve Schaub Systems Engineer Haworth, Inc [EMAIL PROTECTED] 616-393-1457 Desk 616-836-6962 Cell Siempre Hay Esperanza [EMAIL PROTECTED] 09/13 3:43 AM 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 Chichester based offices have amalgamated and relocated to a new address John Wiley Sons Ltd The Atrium Southern Gate Chichester West Sussex PO19 8SQ Main phone and fax numbers remain the same: Phone +44 (0)1243 779777 Fax +44 (0)1243 775878 Direct dial numbers are unchanged Address, phone and fax nos. for all other Wiley UK locations are unchanged ** Our Chichester based offices have amalgamated and relocated to a new address John Wiley Sons Ltd The Atrium Southern Gate Chichester West Sussex PO19 8SQ Main phone and fax numbers remain the same: Phone +44 (0)1243 779777 Fax +44 (0)1243 775878 Direct dial numbers are unchanged Address, phone and fax nos. for all other Wiley UK locations are unchanged **
Re: Migration question
Nope ! Migration uses drives based on the smallest number of : A) max number of migration processes set for stgpool to be migrated B) number of tape drives in the devclass of the stgpool being migrated to C) unique node's data in the stgpool to be migrated OK, so if you have 6 drives, migration processes set to 4, but only one node's data in a storage pool, you will only see a single migration process. I really hate this when a single node dumps 800 GB to disk :-( Dwight -Original Message- From: Farren Minns [mailto:[EMAIL PROTECTED]] Sent: 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 Chichester based offices have amalgamated and relocated to a new address John Wiley Sons Ltd The Atrium Southern Gate Chichester West Sussex PO19 8SQ Main phone and fax numbers remain the same: Phone +44 (0)1243 779777 Fax +44 (0)1243 775878 Direct dial numbers are unchanged Address, phone and fax nos. for all other Wiley UK locations are unchanged **
Re: Migration Question
I would say NO, that would cause you problems. When you restart the server
it will expect the files to still be in the disc pool if you skip item #2.
In this case you would have to do a restore stgpool to make the server
happy. You will not be saving any time by skipping item #2 and most likely,
it will take you longer.
Do it this way. If you migrate and backup the disc pool to the same tape
pool, skip item #1 you've described below. If you backup the disc pool to a
different pool than you migrate to, do both items 1 and 2 below.
Take care,
Al
Alan Davenport
Senior 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 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 saying that option 2 is un-necessary, as this data
should already reside on tape anyway (as it would have been backup up
sometime when a backup stgpool was taken)?.
Kind Regards,
Roy Lake
RS/6000 TSM Systems Administration Team
Tibbett Britten European I.T.
Judd House
Ripple Road
Barking
Essex IG11 0TU
0208 526 8853
[EMAIL PROTECTED]
This e-mail message has been scanned using Sophos Sweep
http://www.sophos.com
**
--- IMPORTANT INFORMATION -
This message is intended only for the use of the Person(s) ('the
intended recipient') to whom it was addressed. It may contain
information which is privileged confidential within the meaning
of applicable law. Accordingly any dissemination, distribution,
copying, or other use of this message, or any of its contents,
by any person other than the intended recipient may constitute
a breach of civil or criminal law and is strictly prohibited.
If you are NOT the intended recipient please contact the sender
and dispose of this email as soon as possible. If in doubt please
contact European IT on 0870 607 6777 (+44 20 85 26 88 88).
This message has been sent via the Public Internet.
**
Re: Migration Question
Hi,
I think IBM wants you to have at least 2 copies of backups on tape media.
So, I would also recommend that.
Regards,
Burak
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
07.05.2002 16:13
Please respond to ADSM-L
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 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 saying that option 2 is un-necessary, as this data
should already reside on tape anyway (as it would have been backup up
sometime when a backup stgpool was taken)?.
Kind Regards,
Roy Lake
RS/6000 TSM Systems Administration Team
Tibbett Britten European I.T.
Judd House
Ripple Road
Barking
Essex IG11 0TU
0208 526 8853
[EMAIL PROTECTED]
This e-mail message has been scanned using Sophos Sweep http://www.sophos.com
**
--- IMPORTANT INFORMATION -
This message is intended only for the use of the Person(s) ('the
intended recipient') to whom it was addressed. It may contain
information which is privileged confidential within the meaning
of applicable law. Accordingly any dissemination, distribution,
copying, or other use of this message, or any of its contents,
by any person other than the intended recipient may constitute
a breach of civil or criminal law and is strictly prohibited.
If you are NOT the intended recipient please contact the sender
and dispose of this email as soon as possible. If in doubt please
contact European IT on 0870 607 6777 (+44 20 85 26 88 88).
This message has been sent via the Public Internet.
**
Re: Migration Question
Roy,
You don't have to do the backup of the diskpool first, but why wouldn't you?
That is what you should do every day anyway. If all the data in diskpool
has already been backed up to your copypool in your daily processing, it
will only take a few seconds and you'll have piece of mind when you hit
return on the del volume command.
Before migrating the data to tapepool, however, do an
update stg diskpool cache=no
That will purge all the cached files in the diskpool during migration so you
shouldn't have to add the discarddata=yes when you delete the diskpool
volumes.
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 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 saying that option 2 is un-necessary, as this data
should already reside on tape anyway (as it would have been backup up
sometime when a backup stgpool was taken)?.
Kind Regards,
Roy Lake
RS/6000 TSM Systems Administration Team
Tibbett Britten European I.T.
Judd House
Ripple Road
Barking
Essex IG11 0TU
0208 526 8853
[EMAIL PROTECTED]
This e-mail message has been scanned using Sophos Sweep
http://www.sophos.com
**
--- IMPORTANT INFORMATION -
This message is intended only for the use of the Person(s) ('the
intended recipient') to whom it was addressed. It may contain
information which is privileged confidential within the meaning
of applicable law. Accordingly any dissemination, distribution,
copying, or other use of this message, or any of its contents,
by any person other than the intended recipient may constitute
a breach of civil or criminal law and is strictly prohibited.
If you are NOT the intended recipient please contact the sender
and dispose of this email as soon as possible. If in doubt please
contact European IT on 0870 607 6777 (+44 20 85 26 88 88).
This message has been sent via the Public Internet.
**
Re: Migration question
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 behaving a little more sanely now. (: Al + + I'd change it to: + + backup stg disk copy + backup stg tape copy (for anything that might have been migrated + during the + night. Do it this way since the copy pool tapes are already mounted and + ready to go) + migrate disk tape + + + + 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 very much for responding to my question. Looks + like I've be able to shave 2 hours off of my morning processing. + (That tape + to tape copy AFTER migration was a killer. Especially with 3490 tapes!) + + + + + We do what you describe every night - saves a lot of tape mounts, + + especially + + since our onsitetape is collocated: + + + + backup stgpool diskpool offsitecopypool + + migrate to onsitetape + + backup stgpool onsitetape offsitecopypool + + + + + + BACKUP STGPOOL is always INCREMENTAL - TSM checks the DB and only copies + + files that aren't in the destination copy pool already. + + + + + + + + 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. + + + + What I would like to do is this: + + + + Backup disk pool to vault tape (offsite) copy. + + Migrate disk to tape (primary onsite) copy. + + Backup primary tape pool to offsite pool to catch any migration + etc. that + + may have occurred during the last 24 hours. + + + + 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 from + + onsite tape pool to offsite tape pool.) That is, is *SM smart + + enough to know + + that the data that was backed up to the vault (offsite) pool prior to + + migration has already been backed up and will not back it up + + again from the + + onsite tape pool to the offsite pool when the BACKUP STG + + TAPEPOOL COPYPOOL + + command is executed? + + + + My environment is TSM 4.1.0.0 on OS390 with 24 3490 tape drives. + + + + Thanks for listening! + + + + Alan Davenport + + Selective Insurance + + [EMAIL PROTECTED] + + +
Re: Migration question
I'd change it to: backup stg disk copy backup stg tape copy (for anything that might have been migrated during the night. Do it this way since the copy pool tapes are already mounted and ready to go) migrate disk tape Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (240) 539-7175 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Alan Davenport Sent: Friday, August 17, 2001 12:26 PM To: [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 very much for responding to my question. Looks like I've be able to shave 2 hours off of my morning processing. (That tape to tape copy AFTER migration was a killer. Especially with 3490 tapes!) + -Original Message- + From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] + Sent: Friday, August 17, 2001 1:31 PM + To: [EMAIL PROTECTED]; [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 + since our onsitetape is collocated: + + backup stgpool diskpool offsitecopypool + migrate to onsitetape + backup stgpool onsitetape offsitecopypool + + + BACKUP STGPOOL is always INCREMENTAL - TSM checks 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 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. + + What I would like to do is this: + + Backup disk pool to vault tape (offsite) copy. + Migrate disk to tape (primary onsite) copy. + Backup primary tape pool to offsite pool to catch any migration etc. that + may have occurred during the last 24 hours. + + 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 from + onsite tape pool to offsite tape pool.) That is, is *SM smart + enough to know + that the data that was backed up to the vault (offsite) pool prior to + migration has already been backed up and will not back it up + again from the + onsite tape pool to the offsite pool when the BACKUP STG + TAPEPOOL COPYPOOL + command is executed? + + My environment is TSM 4.1.0.0 on OS390 with 24 3490 tape drives. + + Thanks for listening! + + Alan Davenport + Selective Insurance + [EMAIL PROTECTED] +
Re: Migration question
'Course TSM is smart! We do what you describe every night - saves a lot of tape mounts, especially since our onsitetape is collocated: backup stgpool diskpool offsitecopypool migrate to onsitetape backup stgpool onsitetape offsitecopypool BACKUP STGPOOL is always INCREMENTAL - TSM checks 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 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. What I would like to do is this: Backup disk pool to vault tape (offsite) copy. Migrate disk to tape (primary onsite) copy. Backup primary tape pool to offsite pool to catch any migration etc. that may have occurred during the last 24 hours. 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 from onsite tape pool to offsite tape pool.) That is, is *SM smart enough to know that the data that was backed up to the vault (offsite) pool prior to migration has already been backed up and will not back it up again from the onsite tape pool to the offsite pool when the BACKUP STG TAPEPOOL COPYPOOL command is executed? My environment is TSM 4.1.0.0 on OS390 with 24 3490 tape drives. Thanks for listening! Alan Davenport Selective Insurance [EMAIL PROTECTED]
Re: Migration question
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 from onsite tape pool to offsite tape pool.) That is, is *SM smart enough to know that the data that was backed up to the vault (offsite) pool prior to migration has already been backed up and will not back it up again from the onsite tape pool to the offsite pool when the BACKUP STG TAPEPOOL COPYPOOL command is executed? My environment is TSM 4.1.0.0 on OS390 with 24 3490 tape drives. Thanks for listening! Alan Davenport Selective Insurance [EMAIL PROTECTED] MMS health-first.org made the following annotations on 08/17/01 13:24:22 -- 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: 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 very much for responding to my question. Looks like I've be able to shave 2 hours off of my morning processing. (That tape to tape copy AFTER migration was a killer. Especially with 3490 tapes!) + -Original Message- + From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] + Sent: Friday, August 17, 2001 1:31 PM + To: [EMAIL PROTECTED]; [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 + since our onsitetape is collocated: + + backup stgpool diskpool offsitecopypool + migrate to onsitetape + backup stgpool onsitetape offsitecopypool + + + BACKUP STGPOOL is always INCREMENTAL - TSM checks 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 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. + + What I would like to do is this: + + Backup disk pool to vault tape (offsite) copy. + Migrate disk to tape (primary onsite) copy. + Backup primary tape pool to offsite pool to catch any migration etc. that + may have occurred during the last 24 hours. + + 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 from + onsite tape pool to offsite tape pool.) That is, is *SM smart + enough to know + that the data that was backed up to the vault (offsite) pool prior to + migration has already been backed up and will not back it up + again from the + onsite tape pool to the offsite pool when the BACKUP STG + TAPEPOOL COPYPOOL + command is executed? + + My environment is TSM 4.1.0.0 on OS390 with 24 3490 tape drives. + + Thanks for listening! + + Alan Davenport + Selective Insurance + [EMAIL PROTECTED] +
