|
Re: [ADSM-L] Version 7.1.3
2015-10-19 10:29:55
Stefan,
If you do not have the need to move
non-container data into a container, then I would recommend performing
the upgrade to SP v7.1.3.2. We found a small bug in the 7.1.3.0 and have
patched the code. It only affected the movement of non-container stgpool
data into a container stgpool.
The decommission function works and
is much easier to perform via the Op Center than doing it manually.
Best Regards, _________________________________________________________
 
email: ron.delaware AT us.ibm DOT com
From:
Stefan Folkerts <stefan.folkerts AT GMAIL DOT COM>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
10/19/15 06:45
Subject:
Re: [ADSM-L]
Version 7.1.3
Sent by:
"ADSM:
Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
The relatively new TSM admin at the site I am currently
implementing
Spectrum Protect is keen on getting the decommission function (in the OC)
because they decommission at least 5 development VM's every week and don't
like deleting filespaces from the commandline on multiple servers.
I haven't heard of any major issues in 7.1.3.0, the download is still
up...can any of you think of a reason to hold back on the production
upgrade to 7.1.3.0?
Regards,
Stefan
On Wed, Sep 30, 2015 at 7:05 PM, J. Pohlmann <jpohlmann AT shaw DOT ca>
wrote:
> Karel, your reference is to 6.1 - note the fix in 6.1.3 - it was supported
> but in many cases you did not get a great dedup percentage. My test
was for
> a 7.1.3 environment with directory container storage pools.
>
> Virtual volumes are still very useful for TSM database backups and
storing
> Recovery Plan Files at another TSM server. For client data protection,
I
> will always prefer node replication.
>
> Regards,
> Joerg Pohlmann
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]
On Behalf Of
> Karel Bos
> Sent: September 30, 2015 00:27
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Version 7.1.3
>
> Hi,
>
> Storing virtual volumes in a dedup pool is not supported. It was not
> restricted but ....
>
> http://www-01.ibm.com/support/docview.wss?uid=swg1IC64970
>
> Kind regards,
>
> Karel
>
> 2015-09-23 20:44 GMT+02:00 J. Pohlmann <jpohlmann AT shaw DOT ca>:
>
> > So far only in a lab environment. Found that, when using directory
> > container storage pools, only node type=client data works. For
my node
> > type=server, the attempt to store data in the directory container
pool
> > failed. Sounds like a restrictions that you can't store virtual
volume
> > data (the archive
> > objects) at the target server in a directory container pool.
Storing
> > the archive objects for virtual volumes in a deduped file device
class
> > storage pool works as before.
> >
> > Regards,
> > Joerg Pohlmann
> >
> > 09/22/2015 13:05:39 ANR0406I Session 111
started for node VVVISTA
> > (Windows)
> >
(Tcp/Ip W2K8-TSM63(49256)). (SESSION: 111)
> > 09/22/2015 13:05:50 ANR2776W Transaction
failed for session 111 for
> > node
> >
VVVISTA (Windows) - A storage pool for the
> target
> >
destination is associated with a container
> > or cloud
> >
storage pool. (SESSION: 111)
> > 09/22/2015 13:06:36 ANR0403I Session 111
ended for node VVVISTA
> > (Windows).
> >
(SESSION: 111)
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]
On Behalf
> > Of Robert Ouzen
> > Sent: September 23, 2015 03:59
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: [ADSM-L] Version 7.1.3
> >
> > Hello All
> >
> > I wonder if people , already upgrade to version 7.1.3 and
have
> > comments , appreciation .. I understand that it's a new big concept
as
> > STG container for inline dedup.
> >
> > Anyone use it ? and can share remarks !
> >
> > T.I.A Robert
> >
>
|
|
|
