ADSM-L

Re: Migration proccess issue

2004-01-07 09:40:43
Subject: Re: Migration proccess issue
From: Bill Boyer <bill.boyer AT VERIZON DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 7 Jan 2004 09:40:19 -0500
The image backup is a single OBJECT to TSM. That's why you only see 1
migration task even if you have MIGPRO set to a higher value. I believe that
a migration task will handle ALL the objects for a node. You won't get
multiple migration tasks if there's only data for 1 node in the storage
pool.

Try sending the image direct to tape...

Bill Boyer
DSS, Inc.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Anderson F. Nobre
Sent: Wednesday, January 07, 2004 9:29 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Migration proccess issue


  So see the parameter migration process (migprocess) in the stgpool. If the
value is equal to one try update to 4.

  Regards,

  Anderson

  ----- Original Message -----
  From: "Abdulaziz Almuammar" <amuammar AT KFSHRC.EDU DOT SA>
  To: <ADSM-L AT VM.MARIST DOT EDU>
  Sent: Wednesday, January 07, 2004 6:12 AM
  Subject: Re: Migration proccess issue


  > There are alot of file spaces on that node.
  > Actually I am doing an image backup of raw logical volumes on AIX
server.
  > each raw logical volume is backedup as a file space.
  > when the migration is triggered only one proccess works.
  >
  >
  > Regards,
  > Abdulaziz
  >
  >
  >
  >
  >
  > ----- Original Message -----
  > From: "Anderson F. Nobre" <afnobre AT UOL.COM DOT BR>
  > To: <ADSM-L AT VM.MARIST DOT EDU>
  > Sent: Wednesday, January 07, 2004 8:57 AM
  > Subject: Re: Migration proccess issue
  >
  >
  > >   Abdulaziz,
  > >
  > >   How many filespaces are there per node? The migration process
migrates
  > the
  > > data of one node per filespace.
  > >
  > >   Regards,
  > >
  > >   Anderson
  > >
  > >   ----- Original Message -----
  > >   From: "Abdulaziz Almuammar" <amuammar AT KFSHRC.EDU DOT SA>
  > >   To: <ADSM-L AT VM.MARIST DOT EDU>
  > >   Sent: Wednesday, January 07, 2004 3:38 AM
  > >   Subject: Re: Migration proccess issue
  > >
  > >
  > >   > Hi Zosi,
  > >   > I checked the collocation option and it was set to NO.
  > >   >
  > >   >
  > >   > Regards,
  > >   > Abdulaziz
  > >   > ----- Original Message -----
  > >   > From: "Zosimo Noriega" <znoriega AT ADNOC DOT COM>
  > >   > To: <ADSM-L AT VM.MARIST DOT EDU>
  > >   > Sent: Wednesday, January 07, 2004 6:26 AM
  > >   > Subject: Re: Migration proccess issue
  > >   >
  > >   >
  > >   > > Verify the collocation option in the storage pool, set it to no.
  > >   > > (Collocate?  NO)
  > >   > >
  > >   > > regards,
  > >   > > Zosi
  > >   > >
  > >   > > -----Original Message-----
  > >   > > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] 
On
  > Behalf
  > > Of
  > >   > > Abdulaziz Almuammar
  > >   > > Sent: Tuesday, January 06, 2004 8:05 PM
  > >   > > To: ADSM-L AT VM.MARIST DOT EDU
  > >   > > Subject: Migration proccess issue
  > >   > >
  > >   > > Hi Guys,
  > >   > >
  > >   > >
  > >   > > I have TSM 5.1.5 and 4 tape drives on 3494 tape library
  > >   > > I configured the migration proccess to start with 4 migration
  > > proccesses
  > >   > and
  > >   > > it is working fine.
  > >   > > the problem is i noteced that there is only one migration
proccess
  > > when
  > >   > the
  > >   > > disk pool has data of one node.
  > >   > > is there any way that i can make the migration proccess to start
  > with
  > > 4
  > >   > > proccesses when it is triggered although the disk pool has only
data
  > > of
  > >   > one
  > >   > > node?
  > >   > > ( the disk pool has alot of file spaces of one node ).
  > >   > >
  > >   > >
  > >   > >
  > >   > > Best Regards,
  > >   > > Abdulaziz
  > >   > >

<Prev in Thread] Current Thread [Next in Thread>