Re: RFE - DEACTIVATE FS

[Stefan Folkerts]

Ha, that's clever!
Never thought of that, thank's for sharing.


On Mon, Jan 25, 2016 at 2:02 PM, Martin Janosik 
wrote:

> Hi Yann,
>
> it seems the proposed functionality can be already achieved via command
> DECOMMISSION VM while specifying FSID. Here is a real-word test:
>
> Server Version 7, Release 1, Level 3.0 @AIX
>
> tsm: TSM_2>q fi SERVERA
>
> Node Name   Filespace   FSID Platform Filespace Is
> Filesp-Capacity   Pct
> Name  Type  ace
> Unico-  Util
>
> de?
> --- ---   -
> -- --- -
> SERVERA /  1 Linux86  EXT2
> No4,925 MB  52.7
> SERVERA /home  2 Linux86  EXT2
> No   32,127 MB   8.5
>
> tsm: TSM_2>decommission vm SERVERA 2 nametype=fsid
> ANR3392W DECOMMISSION VM: This command will decommission the specified
> virtual machine. The active files that belong to the virtual machine will
> be inactivated, and the file space of the
> virtual machine will be automatically deleted after its all the files are
> expired.
>
> Do you wish to proceed? (Yes (Y)/No (N)) y
> ANR3394I Process 3634 was started to decommission virtual machine 2 on node
> SERVERA.
> ANS8003I Process number 3634 started.
>
> tsm: TSM_2>q act s=3634
> 01/25/2016 07:50:43 ANR0984I Process 3634 for DECOMMISSION VM started
> in the BACKGROUND at 07:50:43. (SESSION: 2898529, PROCESS: 3634)
> 01/25/2016 07:50:43 ANR3394I Process 3634 was started to decommission
> virtual machine 2 on node SERVERA. (SESSION: 2898529, PROCESS: 3634)
> 01/25/2016 07:51:25 ANR0987I Process 3634 for DECOMMISSION VM running
> in the BACKGROUND processed 69,547 items with a completion state of SUCCESS
> at 07:51:25. (SESSION: 2898529, PROCESS: 3634)
>
> tsm: TSM_2>select state, count(*) from backups where node_name='SERVERA'
> and FILESPACE_ID=2 group by state
>
> STATE   Unnamed[2]
> - 
> INACTIVE_VERSION 69547
>
> Bye
>
> M. Janosik
>
> "ADSM: Dist Stor Manager"  wrote on 01/25/2016
> 01:33:03 PM:
>
> > From: "Meunier, Yann" 
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 01/25/2016 01:34 PM
> > Subject: [ADSM-L] RFE - DEACTIVATE FS
> > Sent by: "ADSM: Dist Stor Manager" 
> >
> > Hi,
> >
> > I’ve just post a new RFE : https://www.ibm.com/developerworks/rfe/
> > execute?use_case=viewRfe_ID=82944
> > What do you think about ?
> >
> > Best Regards,
> > Yann MEUNIER
> >
> >
> >
> >
> > Ce message et toutes les pièces jointes (ci-après le « message »)
> > sont confidentiels et établis à l’intention exclusive de ses
> > destinataires. Toute utilisation de ce message non conforme à sa
> > destination, toute diffusion ou toute publication, totale ou
> > partielle, est interdite, sauf autorisation expresse. Si vous
> > recevez ce message par erreur, merci de le détruire sans en
> > conserver de copie et d’en avertir immédiatement l’expéditeur.
> > Internet ne permettant pas de garantir l’intégrité de ce message, la
> > Caisse des Dépôts et Consignations décline toute responsabilité au
> > titre de ce message s’il a été modifié, altéré, déformé ou falsifié.
> > Par ailleurs et malgré toutes les précautions prises pour éviter la
> > présence de virus dans nos envois, nous vous recommandons de
> > prendre, de votre côté, les mesures permettant d'assurer la non-
> > introduction de virus dans votre système informatique.
> >
> > This email message and any attachments (“the email”) are
> > confidential and intended only for the recipient(s) indicated. If
> > you are not an intended recipient, please be advised that any use,
> > dissemination, forwarding or copying of this email whatsoever is
> > prohibited without prior written consent of Caisse des Depots et
> > Consignations. If you have received this email in error, please
> > delete it without saving a copy and notify the sender immediately.
> > Internet emails are not necessarily secure, and Caisse des Depots et
> > Consignations declines responsibility for any changes that may have
> > been made to this email after it was sent. While we take all
> > reasonable precautions to ensure that viruses are not transmitted
> > via emails, we recommend that you take your own measures to prevent
> > viruses from entering your computer system.
> >
>

RFE - DEACTIVATE FS

[Meunier, Yann]

Hi,

I’ve just post a new RFE : 
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=82944
What do you think about ?

Best Regards,
Yann MEUNIER




Ce message et toutes les pièces jointes (ci-après le « message ») sont 
confidentiels et établis à l’intention exclusive de ses destinataires. Toute 
utilisation de ce message non conforme à sa destination, toute diffusion ou 
toute publication, totale ou partielle, est interdite, sauf autorisation 
expresse. Si vous recevez ce message par erreur, merci de le détruire sans en 
conserver de copie et d’en avertir immédiatement l’expéditeur. Internet ne 
permettant pas de garantir l’intégrité de ce message, la Caisse des Dépôts et 
Consignations décline toute responsabilité au titre de ce message s’il a été 
modifié, altéré, déformé ou falsifié. Par ailleurs et malgré toutes les 
précautions prises pour éviter la présence de virus dans nos envois, nous vous 
recommandons de prendre, de votre côté, les mesures permettant d'assurer la 
non-introduction de virus dans votre système informatique.

This email message and any attachments (“the email”) are confidential and 
intended only for the recipient(s) indicated. If you are not an intended 
recipient, please be advised that any use, dissemination, forwarding or copying 
of this email whatsoever is prohibited without prior written consent of Caisse 
des Depots et Consignations. If you have received this email in error, please 
delete it without saving a copy and notify the sender immediately. Internet 
emails are not necessarily secure, and Caisse des Depots et Consignations 
declines responsibility for any changes that may have been made to this email 
after it was sent. While we take all reasonable precautions to ensure that 
viruses are not transmitted via emails, we recommend that you take your own 
measures to prevent viruses from entering your computer system.

Re: RFE - DEACTIVATE FS

[Martin Janosik]

Hi Yann,

it seems the proposed functionality can be already achieved via command
DECOMMISSION VM while specifying FSID. Here is a real-word test:

Server Version 7, Release 1, Level 3.0 @AIX

tsm: TSM_2>q fi SERVERA

Node Name   Filespace   FSID Platform Filespace Is
Filesp-Capacity   Pct
Name  Type  ace
Unico-  Util

de?
--- ---   -
-- --- -
SERVERA /  1 Linux86  EXT2
No4,925 MB  52.7
SERVERA /home  2 Linux86  EXT2
No   32,127 MB   8.5

tsm: TSM_2>decommission vm SERVERA 2 nametype=fsid
ANR3392W DECOMMISSION VM: This command will decommission the specified
virtual machine. The active files that belong to the virtual machine will
be inactivated, and the file space of the
virtual machine will be automatically deleted after its all the files are
expired.

Do you wish to proceed? (Yes (Y)/No (N)) y
ANR3394I Process 3634 was started to decommission virtual machine 2 on node
SERVERA.
ANS8003I Process number 3634 started.

tsm: TSM_2>q act s=3634
01/25/2016 07:50:43 ANR0984I Process 3634 for DECOMMISSION VM started
in the BACKGROUND at 07:50:43. (SESSION: 2898529, PROCESS: 3634)
01/25/2016 07:50:43 ANR3394I Process 3634 was started to decommission
virtual machine 2 on node SERVERA. (SESSION: 2898529, PROCESS: 3634)
01/25/2016 07:51:25 ANR0987I Process 3634 for DECOMMISSION VM running
in the BACKGROUND processed 69,547 items with a completion state of SUCCESS
at 07:51:25. (SESSION: 2898529, PROCESS: 3634)

tsm: TSM_2>select state, count(*) from backups where node_name='SERVERA'
and FILESPACE_ID=2 group by state

STATE   Unnamed[2]
- 
INACTIVE_VERSION 69547

Bye

M. Janosik

"ADSM: Dist Stor Manager"  wrote on 01/25/2016
01:33:03 PM:

> From: "Meunier, Yann" 
> To: ADSM-L@VM.MARIST.EDU
> Date: 01/25/2016 01:34 PM
> Subject: [ADSM-L] RFE - DEACTIVATE FS
> Sent by: "ADSM: Dist Stor Manager" 
>
> Hi,
>
> I’ve just post a new RFE : https://www.ibm.com/developerworks/rfe/
> execute?use_case=viewRfe_ID=82944
> What do you think about ?
>
> Best Regards,
> Yann MEUNIER
>
>
>
>
> Ce message et toutes les pièces jointes (ci-après le « message »)
> sont confidentiels et établis à l’intention exclusive de ses
> destinataires. Toute utilisation de ce message non conforme à sa
> destination, toute diffusion ou toute publication, totale ou
> partielle, est interdite, sauf autorisation expresse. Si vous
> recevez ce message par erreur, merci de le détruire sans en
> conserver de copie et d’en avertir immédiatement l’expéditeur.
> Internet ne permettant pas de garantir l’intégrité de ce message, la
> Caisse des Dépôts et Consignations décline toute responsabilité au
> titre de ce message s’il a été modifié, altéré, déformé ou falsifié.
> Par ailleurs et malgré toutes les précautions prises pour éviter la
> présence de virus dans nos envois, nous vous recommandons de
> prendre, de votre côté, les mesures permettant d'assurer la non-
> introduction de virus dans votre système informatique.
>
> This email message and any attachments (“the email”) are
> confidential and intended only for the recipient(s) indicated. If
> you are not an intended recipient, please be advised that any use,
> dissemination, forwarding or copying of this email whatsoever is
> prohibited without prior written consent of Caisse des Depots et
> Consignations. If you have received this email in error, please
> delete it without saving a copy and notify the sender immediately.
> Internet emails are not necessarily secure, and Caisse des Depots et
> Consignations declines responsibility for any changes that may have
> been made to this email after it was sent. While we take all
> reasonable precautions to ensure that viruses are not transmitted
> via emails, we recommend that you take your own measures to prevent
> viruses from entering your computer system.
>

Upgrade server from 6.3 to 7.1

[molin gregory]

Hello everyone

I plan to upgrade my server from version 6.3 to version 7.1.
Have you had problems with this procedure?

Thank you beforehand
Grégory
"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système.

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: Upgrade server from 6.3 to 7.1

[Andrew Carlson]

This bit me too in our test environment, though the DB upgrade worked, but
it later tanked and could not be restarted.

On Mon, Jan 25, 2016 at 10:15 AM, Rainer Tammer 
wrote:

> Hello,
> Is this mentioned in the docs?
>
> That would be a bit difficult in our setup:
>
> Filesystem GB blocks   Free   %Used  Iused %Iused Mounted on
> /dev/lvtsmactlog   130.00  1.98   99%262   1%
> /tsminst1/tsmactlog  <- active log
> /dev/lvtsmarchlog  197.00  193.37 2% 251%
> /tsminst1/tsmarchlog <- archive log
>
>
> Bye
>   Rainer
>
> On 25.01.2016 16:51, Lee, Gary wrote:
> > Yes.
> >
> > Make sure that you have at least double the size of your active and
> archive logs as available free space in the respective log directories.
> > i.e. . if your active log size is 32 gB, insure that your log directory
> has more than 64 gB free.  Otherwise the database upgrade will fail on
> install.
> >
> > Other than that, it went well, going from 6.3.4 to 7.1.3.
> >
> >
> >
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
> Of molin gregory
> > Sent: Monday, January 25, 2016 10:30 AM
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: [ADSM-L] Upgrade server from 6.3 to 7.1
> >
> > Hello everyone
> >
> > I plan to upgrade my server from version 6.3 to version 7.1.
> > Have you had problems with this procedure?
> >
> > Thank you beforehand
> > Grégory
> > "ATTENTION.
> >
> > Ce message et les pièces jointes sont confidentiels et établis à
> l'attention exclusive de leur destinataire (aux adresses spécifiques
> auxquelles il a été adressé). Si vous n'êtes pas le destinataire de ce
> message, vous devez immédiatement en avertir l'expéditeur et supprimer ce
> message et les pièces jointes de votre système.
> >
> > This message and any attachments are confidential and intended to be
> received only by the addressee. If you are not the intended recipient,
> please notify immediately the sender by reply and delete the message and
> any attachments from your system. "
> >
> >
>



-- 
Andy Carlson
---
Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month,
The feeling of seeing the red box with the item you want in it:Priceless.

Re: Upgrade server from 6.3 to 7.1

[Lee, Gary]

Yes.

Make sure that you have at least double the size of your active and archive 
logs as available free space in the respective log directories.
i.e. . if your active log size is 32 gB, insure that your log directory has 
more than 64 gB free.  Otherwise the database upgrade will fail on install.

Other than that, it went well, going from 6.3.4 to 7.1.3.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of molin 
gregory
Sent: Monday, January 25, 2016 10:30 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Upgrade server from 6.3 to 7.1

Hello everyone

I plan to upgrade my server from version 6.3 to version 7.1.
Have you had problems with this procedure?

Thank you beforehand
Grégory
"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système.

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: Copy Mode: Absolute misunderstanding

[Andrew Raibeck]

Hi Erwann,

This option was added to the product, starting with version 6.4.1, through
APAR IC91871:

http://www.ibm.com/support/docview.wss?uid=swg1IC91871

Best regards,

- Andy



Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com

IBM Tivoli Storage Manager links:
Product support:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome
Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager

"ADSM: Dist Stor Manager"  wrote on 2016-01-24
05:40:40:

> From: Erwann SIMON 
> To: ADSM-L@VM.MARIST.EDU
> Date: 2016-01-24 05:41
> Subject: Re: Copy Mode: Absolute misunderstanding
> Sent by: "ADSM: Dist Stor Manager" 
>
> Hi Robert,
>
> I thought that it's a new option in the 7.x branch, not already
> available in 6.x. Anyway, this absolute option does not appear in 6.
> 4 client documentation.
>
> --
> Best regards / Cordialement / مع تحياتي
> Erwann SIMON
>
> - Mail original -
> De: "Robert Ouzen" 
> À: ADSM-L@VM.MARIST.EDU
> Envoyé: Dimanche 24 Janvier 2016 07:12:58
> Objet: Re: [ADSM-L] Copy Mode: Absolute misunderstanding
>
> Hi Erwann
>
> IN client 6.x.x..x I have to the option of copy mode ABSOLUTE .
> so why I nned client vrsion 7+ ?
> It will not work ?
>
> Best Regards Robert
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
> Behalf Of Erwann SIMON
> Sent: Saturday, January 23, 2016 8:08 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Copy Mode: Absolute misunderstanding
>
> Hello Robert,
>
> If you only have client whose version is 7.1 or later, you can also
> use the absolute option :
>
> Use the absolute option with the incremental command to force a
> backup of all files and directories that match the file
> specification or domain, even if the objects were not changed since
> the last incremental backup.
>
> This option overrides the management class copy group mode parameter
> for backup copy groups; it does not affect the frequency parameter
> or any other backup copy group parameters.
>
>
> --
> Best regards / Cordialement / مع تحياتي
> Erwann SIMON
>
> - Mail original -
> De: "Robert Ouzen" 
> À: ADSM-L@VM.MARIST.EDU
> Envoyé: Samedi 23 Janvier 2016 16:12:07
> Objet: Re: [ADSM-L] Copy Mode: Absolute misunderstanding
>
> Hi Keith
>
> I am curious of the result .
>
> I need too, to back up to a new storage pool of type directory
> container (new feature inV7.1.4).  Cannot do a nextstg or move nodedata.
>
> So want to try your suggestion COPY MODE ABSOLUTE for now I did in
> another way.
>
> Rename the node to node_OLD   (all FI are with extension _OLD after
> it) , recreate the node and change the destination to the new
> storage directory.
>
> After a wild delete the OLD FI and OLD node.
>
> My copypool looks like this:
>
> Policy Domain Policy Set Name  Mgmt Class Name   Versions
> Data ExistsVersions Data Deleted Retain Extra
> Versions  Retain Only VersionCopy Mode Copy Destination
>
> CC   ACTIVE  MGCC12
> 4  1
> No Limit60
> Modified  NET_TSM
>
> So  need to change to
>
> Policy Domain Policy Set Name  Mgmt Class Name   Versions
> Data ExistsVersions Data Deleted Retain Extra
> Versions  Retain Only VersionCopy Mode  Copy Destination
>
> CC   ACTIVE  MGCC12
> 4  1
> 10  10
> Absolute V7000_D1
>
> So after 10-11 days all my 3 inactive versions will vanish  from STG
> NET_TSM ... correct >
>
> Best Regards
>
> Robert
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
> Behalf Of Arbogast, Warren K
> Sent: Friday, January 22, 2016 8:22 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Copy Mode: Absolute misunderstanding
>
> Hi Thomas,
> Thank you for your insight. RETONLY was 60 days during the absolute
> backups. We just reduced it to 30 days this morning when we saw
> unexpected files on the VTL. Perhaps tomorrow the VTL will look better.
>
> Best wishes,
> Keith Arbogast
> Indiana University
>
>
>
>
>
>
> On 1/22/16, 13:11, "ADSM: Dist Stor Manager on behalf of Thomas
> Denier" 
wrote:
>
> >Is RETONLY also set to 30 days? If RETONLY is longer than 30 days,
> backup copies some files deleted before the absolute backups would
> be retained for more than 30 days after the absolute backups.
> >
> >Thomas Denier
> 

Re: Upgrade server from 6.3 to 7.1

[Michaud, Luc [Analyste principal - soutien techni (TI)]]

Greetings TSM fellows,

(My first post on ADSM-L here)

Funny enough we had an ACTIVE LOG setup similar to Rainer (e.g. 99+%)...  

Last week we noticed spurious "Filesystem full" errors for the active log 
filesystem in the DB2 logs.

We had just recently turned on the active log compression.

TSM support (Magdy) recommended that we go with 25% free space on the active 
log filesystem; that's much less than 66%, but still a whallop above our 
previous config.  

So... I guess that static allocation of the active log structure is not always 
so static after all...

Regards,

Luc



-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Rainer 
Tammer
Envoyé : 25 janvier 2016 11:16
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] Upgrade server from 6.3 to 7.1

Hello,
Is this mentioned in the docs?

That would be a bit difficult in our setup:

Filesystem GB blocks   Free   %Used  Iused %Iused Mounted on
/dev/lvtsmactlog   130.00  1.98   99%262   1%
/tsminst1/tsmactlog  <- active log
/dev/lvtsmarchlog  197.00  193.37 2% 251%
/tsminst1/tsmarchlog <- archive log


Bye
  Rainer

On 25.01.2016 16:51, Lee, Gary wrote:
> Yes.
>
> Make sure that you have at least double the size of your active and archive 
> logs as available free space in the respective log directories.
> i.e. . if your active log size is 32 gB, insure that your log directory has 
> more than 64 gB free.  Otherwise the database upgrade will fail on install.
>
> Other than that, it went well, going from 6.3.4 to 7.1.3.
>
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> molin gregory
> Sent: Monday, January 25, 2016 10:30 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] Upgrade server from 6.3 to 7.1
>
> Hello everyone
>
> I plan to upgrade my server from version 6.3 to version 7.1.
> Have you had problems with this procedure?
>
> Thank you beforehand
> Grégory
> "ATTENTION.
>
> Ce message et les pièces jointes sont confidentiels et établis à l'attention 
> exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
> adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
> immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
> jointes de votre système.
>
> This message and any attachments are confidential and intended to be received 
> only by the addressee. If you are not the intended recipient, please notify 
> immediately the sender by reply and delete the message and any attachments 
> from your system. "
>
>

Re: Upgrade server from 6.3 to 7.1

[Rainer Tammer]

Hello,
Is this mentioned in the docs?

That would be a bit difficult in our setup:

Filesystem GB blocks   Free   %Used  Iused %Iused Mounted on
/dev/lvtsmactlog   130.00  1.98   99%262   1%
/tsminst1/tsmactlog  <- active log
/dev/lvtsmarchlog  197.00  193.37 2% 251%
/tsminst1/tsmarchlog <- archive log


Bye
  Rainer

On 25.01.2016 16:51, Lee, Gary wrote:
> Yes.
>
> Make sure that you have at least double the size of your active and archive 
> logs as available free space in the respective log directories.
> i.e. . if your active log size is 32 gB, insure that your log directory has 
> more than 64 gB free.  Otherwise the database upgrade will fail on install.
>
> Other than that, it went well, going from 6.3.4 to 7.1.3.
>
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> molin gregory
> Sent: Monday, January 25, 2016 10:30 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] Upgrade server from 6.3 to 7.1
>
> Hello everyone
>
> I plan to upgrade my server from version 6.3 to version 7.1.
> Have you had problems with this procedure?
>
> Thank you beforehand
> Grégory
> "ATTENTION.
>
> Ce message et les pièces jointes sont confidentiels et établis à l'attention 
> exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
> adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
> immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
> jointes de votre système.
>
> This message and any attachments are confidential and intended to be received 
> only by the addressee. If you are not the intended recipient, please notify 
> immediately the sender by reply and delete the message and any attachments 
> from your system. "
>
>

Re: Upgrade server from 6.3 to 7.1

[Lee, Gary]

I never saw it in the docs.

What I had to do was disable the server, do a full backup on the db, then once 
I had verified the logs were empty, reduced log size to less than half file 
system space.
Then do the upgrade, and enlarge logs as necessary after upgrade is verified 
working.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rainer 
Tammer
Sent: Monday, January 25, 2016 11:16 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Upgrade server from 6.3 to 7.1

Hello,
Is this mentioned in the docs?

That would be a bit difficult in our setup:

Filesystem GB blocks   Free   %Used  Iused %Iused Mounted on
/dev/lvtsmactlog   130.00  1.98   99%262   1%
/tsminst1/tsmactlog  <- active log
/dev/lvtsmarchlog  197.00  193.37 2% 251%
/tsminst1/tsmarchlog <- archive log


Bye
  Rainer

On 25.01.2016 16:51, Lee, Gary wrote:
> Yes.
>
> Make sure that you have at least double the size of your active and archive 
> logs as available free space in the respective log directories.
> i.e. . if your active log size is 32 gB, insure that your log directory has 
> more than 64 gB free.  Otherwise the database upgrade will fail on install.
>
> Other than that, it went well, going from 6.3.4 to 7.1.3.
>
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> molin gregory
> Sent: Monday, January 25, 2016 10:30 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] Upgrade server from 6.3 to 7.1
>
> Hello everyone
>
> I plan to upgrade my server from version 6.3 to version 7.1.
> Have you had problems with this procedure?
>
> Thank you beforehand
> Grégory
> "ATTENTION.
>
> Ce message et les pièces jointes sont confidentiels et établis à l'attention 
> exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
> adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
> immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
> jointes de votre système.
>
> This message and any attachments are confidential and intended to be received 
> only by the addressee. If you are not the intended recipient, please notify 
> immediately the sender by reply and delete the message and any attachments 
> from your system. "
>
>

Re: Copy Mode: Absolute misunderstanding

[Arbogast, Warren K]

Robert Ouzen,
Using copy mode: absolute worked quite well, but not perfectly for our 
purposes. Since it does honor include/exclude statements it did not backup all 
files that were in storage. So there was some cleanup to do afterward (move 
node data fromstg=VTL tostg=b). The target of the mode node data could not be 
the DEDUP pool, but the count of orphan files was small so we moved them to 
tape. It did accomplish 99% of what we wanted it to do, which was to hurry up 
the migration to the DEDUP pool. Keep in mind that an absolute backup increases 
total storage temporarily, till retextra and retonly expire, since it creates a 
new active version for every file, and all the previous active versions are 
promoted to inactive status. For some Linux/Oracle nodes there was also the 
curious case of nodes which had one file per filesystem remaining in in the VTL 
after all the other inactive versions had expired. Five filesystems, five 
files. I can’t make up a story for that one. I used move nodedata again to move 
them off the VTL. 

Best wishes to all,
Keith Arbogast
Indiana University



On 1/25/16, 10:35, "ADSM: Dist Stor Manager on behalf of Andrew Raibeck" 
 wrote:

>Hi Erwann,
>
>This option was added to the product, starting with version 6.4.1, through
>APAR IC91871:
>
>http://www.ibm.com/support/docview.wss?uid=swg1IC91871
>
>Best regards,
>
>- Andy
>
>
>
>Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com
>
>IBM Tivoli Storage Manager links:
>Product support:
>http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager
>
>Online documentation:
>http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome
>Product Wiki:
>https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager
>
>"ADSM: Dist Stor Manager"  wrote on 2016-01-24
>05:40:40:
>
>> From: Erwann SIMON 
>> To: ADSM-L@VM.MARIST.EDU
>> Date: 2016-01-24 05:41
>> Subject: Re: Copy Mode: Absolute misunderstanding
>> Sent by: "ADSM: Dist Stor Manager" 
>>
>> Hi Robert,
>>
>> I thought that it's a new option in the 7.x branch, not already
>> available in 6.x. Anyway, this absolute option does not appear in 6.
>> 4 client documentation.
>>
>> --
>> Best regards / Cordialement / مع تحياتي
>> Erwann SIMON
>>
>> - Mail original -
>> De: "Robert Ouzen" 
>> À: ADSM-L@VM.MARIST.EDU
>> Envoyé: Dimanche 24 Janvier 2016 07:12:58
>> Objet: Re: [ADSM-L] Copy Mode: Absolute misunderstanding
>>
>> Hi Erwann
>>
>> IN client 6.x.x..x I have to the option of copy mode ABSOLUTE .
>> so why I nned client vrsion 7+ ?
>> It will not work ?
>>
>> Best Regards Robert
>>
>> -Original Message-
>> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
>> Behalf Of Erwann SIMON
>> Sent: Saturday, January 23, 2016 8:08 PM
>> To: ADSM-L@VM.MARIST.EDU
>> Subject: Re: [ADSM-L] Copy Mode: Absolute misunderstanding
>>
>> Hello Robert,
>>
>> If you only have client whose version is 7.1 or later, you can also
>> use the absolute option :
>>
>> Use the absolute option with the incremental command to force a
>> backup of all files and directories that match the file
>> specification or domain, even if the objects were not changed since
>> the last incremental backup.
>>
>> This option overrides the management class copy group mode parameter
>> for backup copy groups; it does not affect the frequency parameter
>> or any other backup copy group parameters.
>>
>>
>> --
>> Best regards / Cordialement / مع تحياتي
>> Erwann SIMON
>>
>> - Mail original -
>> De: "Robert Ouzen" 
>> À: ADSM-L@VM.MARIST.EDU
>> Envoyé: Samedi 23 Janvier 2016 16:12:07
>> Objet: Re: [ADSM-L] Copy Mode: Absolute misunderstanding
>>
>> Hi Keith
>>
>> I am curious of the result .
>>
>> I need too, to back up to a new storage pool of type directory
>> container (new feature inV7.1.4).  Cannot do a nextstg or move nodedata.
>>
>> So want to try your suggestion COPY MODE ABSOLUTE for now I did in
>> another way.
>>
>> Rename the node to node_OLD   (all FI are with extension _OLD after
>> it) , recreate the node and change the destination to the new
>> storage directory.
>>
>> After a wild delete the OLD FI and OLD node.
>>
>> My copypool looks like this:
>>
>> Policy Domain Policy Set Name  Mgmt Class Name   Versions
>> Data ExistsVersions Data Deleted Retain Extra
>> Versions  Retain Only VersionCopy Mode Copy Destination
>>
>> CC   ACTIVE  MGCC12
>> 4  1
>> No Limit60
>> Modified  NET_TSM
>>
>> So  need to change to
>>
>> Policy Domain Policy Set Name  Mgmt Class Name   Versions
>> Data Exists

DB2 active and mirror logs

[Rhodes, Richard L.]

Hello,

I just noticed something weird about "q log f=d" on all of our TSM systems.

(TSM v6.3.5.0)

==> dsmserv.opt log entries

   ACTIVELOGSize25000
   MIRRORLOGDirectory/tsmdata/tsmsap2/db2activelog2
   ACTIVELOGDirectory/tsmdata/tsmsap2/db2activelog1
   ARCHLOGDirectory  /tsmdata/tsmsap2/db2archivelog
   archfailoverlogdir/DD/tsmsap2/db2failoverlog


==> Filesystem info for DB2 logs:

  df -g
  Filesystem GB blocks  Free %UsedIused %Iused Mounted on
  /dev/db2activelog1 31.25  6.74   79%   55 1% 
/tsmdata/tsmsap2/db2activelog1  (active log)
  /dev/db2activelog2 31.25  6.74   79%   55 1% 
/tsmdata/tsmsap2/db2activelog2  (mirror log)
  /dev/db2archivelog 93.75 90.983%   23 1% 
/tsmdata/tsmsap2/db2archivelog  (archive log)

  Note how both the active/mirror logs are exactly the same - as expected.



==> Now a "q log f=d" for what TSM/DB2 thinks:

  tsm=tsmsap2 cmd=q log f=d
Active Log Directory: /tsmdata/tsmsap2/db2activelog1
 Total Space(MB): 24,576
  Used Space(MB): 157
  Free Space(MB): 24,419

   Archive Log Directory: /tsmdata/tsmsap2/db2archivelog
  Total Size of File System (MB): 96,000.00
  Space Used on File System (MB): 2,834.08
  Free Space(MB): 93,165.92

Mirror Log Directory: /tsmdata/tsmsap2/db2activelog2
  Total Size of File System (MB): 32,000.00
  Space Used on File System (MB): 25,093.63
  Free Space(MB): 6,906.37

  Archive Failover Log Directory: /DD/tsmsap2/db2failoverlog
  Total Size of File System (MB): 401,935,639.50
  Space Used on File System (MB): 317,544,655.50
  Free Space(MB): 84,390,984.00


==> Question

Note how the MIRROR LOG shows filesystem totals for total/used/free space.
But the ACTIVE LOG is the space in the actual log files allocated with the 
used/free space.

Anyone have an idea why the difference in display between ACTIVE and MIRROR 
output?


Thanks

Rick



-
The information contained in this message is intended only for the personal and 
confidential use of the recipient(s) named above. If the reader of this message 
is not the intended recipient or an agent responsible for delivering it to the 
intended recipient, you are hereby notified that you have received this 
document in error and that any review, dissemination, distribution, or copying 
of this message is strictly prohibited. If you have received this communication 
in error, please notify us immediately, and delete the original message.

Re: VM dsm.opt configuration

[Tom Alverson]

Are you asking if the include/exclude can be wild carded?  I don't know. I
started by excluding the non "Disk 1" drives on our VM's until I read that
using the INCLUDE option implies excluding all of the other disks so now I
just have a separate INCLUDE statement for the DISK 1 drive for each VM (I
am likewise only using TSM for VE to back up the OS drive and use the
conventional TSM client to back up the data drives.

On Sat, Jan 23, 2016 at 6:46 AM, Robert Ouzen 
wrote:

> Hello all
>
> I want to figure how to back up in TSM for VE V7.1.4  all my VM’machine
> (300) in my Data Center .
>
> For all of them only “Hard Disk 1” and only for specific VM’s more disks
>
> What will be the correct syntax in my dsm.opt.
>
> T.I.A Regards
>
> Robert
>