Tsm replication 7.1
Hi to all Long time ago I test the replication feature for DRM purpose. Now I wanted to implant it between two TSM servers version 7.1 and O.S Windows 2008 R2 64B. I have some questions: · The command replicate node if no domain exist in the TARGET server as in SOURCE server , put the node under the domain STANDARD. My question is after it can I update the node to a different domain (created on the TARGET server but in the SOURCE server is not exist) , and in the next replicate node it will go to this domain and not to STANDARD ? · In SOURCE server in the command "update fi" it is an option replstate=purgedata" I don't quite understand the purpose ? · When replicate node with type ARCH have in ARREPLRULEDEFAULT the options : ALL_DATA , ALL_DATA_HIGH_PRIORITY , DEFAULT , NONE . I am using ALL_DATA If I have a node in the SOURCE server with archive copygroups rentention of 360 days and in the TARGET server in the archive coypgroups retention of the domain STANDARD is 90. My question what happen in the replicate node to the TARGET server when no same archive copygroups retention ? Did all data will be replicate and only after running an expire inventory in the TARGET server only the data for 90 days will remain ? or already during the replicate node only the data for 90 days with will replicate ? T.I.A Best Regards Robert
memory usage TSM for exchange
Hi all, our exchange team has been investigating a problem regarding available memory on their servers for quite some time. They've now correlated the alert "A significant portion of the database buffer cache has been written out to the system paging file" to the end of the TSM exchange backup. We're running TSM 6.4 with TSM for Mail 6.4 on win 2k8R2 and exchange 2010, on a system with 24 GB ram (and 4 cpu's). Anyone got a hint as to what might be causing TSM or the system to use so much memory at the end of the backup? And, what can we do to avoid the system paging? -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: Upgrading to v6 storage agent and TDPO
>Be aware that filesets are different in v5 and v6, and they install in >different path. Yes, that is part of my confusion. Once for a TSM Server v5->v6 upgrade I forgot to uninstall the v5 server and has both installed. It worked fine, but was confusing to figure out the uninstall for the old v5. So this happens with the storage agent also. So I should probably uninstall the v5 storage agent, then install the v6.2. Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Erwann Simon Sent: Wednesday, April 30, 2014 2:08 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Upgrading to v6 storage agent and TDPO Hello Richard, I'm just answering to the storage agent question on AIX. Be aware that filesets are different in v5 and v6, and they install in different path (under /usr and /opt in v6) so both may be installed simultaneously. When upgrading, you have to move the configuration files from an install path to the other and adapt the path in startup script or inittab entry. On 29 avril 2014 21:17:59 CEST, "Rhodes, Richard L." wrote: >We just finished our TSM v5 to TSM v6 server upgrades. I'll have to >say it generally went very well. Lots of work but no real problems. > >Now I have to upgrade a bunch of V5 Storage Agents and TDPO setups. I >looked at the upgrade guide and Storage Agent guide, but didn't find >much on how to upgrade them. All the storage agents are at v551, the >highest v5. Let me ask some questions . . . > >- Do you have to uninstall v5 before running install.bin to >upgrade/install to v6? > >- Since it's not installing DB2, is it possible to just run a smitty >install of the AIX binaries, instead of using the Java install.bin pgm? > >- Any other thoughts/suggestions for upgrading a Storage Agent? > >(Haven't looked at TDPO yet . . .) > >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. -- Erwann SIMON Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.
Re: Upgrading to v6 storage agent and TDPO
> 1) stop TSM services; > 2) upgrade TSM Client by "smitty update_all"; Yes, this is how I upgrade in TSM v5. My confusing is that TSMv6 comes as one big package: CZG6SML_TSM_AIX_server_v6.2.1.bin (v6.2.1 base) 6.2.5.000-TIV-TSMALL-AIX.bin. (v6.2.5 upgrade) The AIX install packages are buried down in the dir structure when this is exploded. How did you run "smitty update_all"? Did you cd to the filesets in this structure? I really don't want to run the install.bin java gui to do this storage agent upgrade. Thanks! Rick asasdasdf -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Grigori Solonovitch Sent: Tuesday, April 29, 2014 11:45 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Upgrading to v6 storage agent and TDPO We have done this a year ago (5.5 --> 6.3.3.100). For Windows TSM Clients: 1) stop all TSM services; 2) run TSM Installer from new agent; 3) start TSM services; Notes: 1. Stopping TSM services is critical - reboot is required is any of the services is not stopped!! 2) There are some limitations for Windows 2003 (we are using: TSM Client 7.1 for Windows 2008/2012 and TSM Client 6.4.1 for Windows 2003, which officially is not certified, but required for TBMR 7.1). For AIX : 1) stop TSM services; 2) upgrade TSM Client by "smitty update_all"; 3) start TSM services. Notes: 1) Maximum allowed version for AIX 5.3 is 6.2 (6.2.4.4 in my case); 2) There is no limit for AIX 7.1 (7.1 in my case??); For TDP: 1) for Oracle under AIX just "smitty update_all" for selected version (7.1 in AIX 7.1); 2) for MS SQL it is much more complicated and you need to pay specific attention for each used version and selected target version; 3) for Exchange see MS SQL. I hope this information will help you at least a little bit:):) Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rhodes, Richard L. Sent: 29 04 2014 10:18 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Upgrading to v6 storage agent and TDPO We just finished our TSM v5 to TSM v6 server upgrades. I'll have to say it generally went very well. Lots of work but no real problems. Now I have to upgrade a bunch of V5 Storage Agents and TDPO setups. I looked at the upgrade guide and Storage Agent guide, but didn't find much on how to upgrade them. All the storage agents are at v551, the highest v5. Let me ask some questions . . . - Do you have to uninstall v5 before running install.bin to upgrade/install to v6? - Since it's not installing DB2, is it possible to just run a smitty install of the AIX binaries, instead of using the Java install.bin pgm? - Any other thoughts/suggestions for upgrading a Storage Agent? (Haven't looked at TDPO yet . . .) 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. Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Re: Upgrading to v6 storage agent and TDPO
Just rename *.bin to *.tar and un-tar it. Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rhodes, Richard L. Sent: 30 04 2014 3:37 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Upgrading to v6 storage agent and TDPO > 1) stop TSM services; > 2) upgrade TSM Client by "smitty update_all"; Yes, this is how I upgrade in TSM v5. My confusing is that TSMv6 comes as one big package: CZG6SML_TSM_AIX_server_v6.2.1.bin (v6.2.1 base) 6.2.5.000-TIV-TSMALL-AIX.bin. (v6.2.5 upgrade) The AIX install packages are buried down in the dir structure when this is exploded. How did you run "smitty update_all"? Did you cd to the filesets in this structure? I really don't want to run the install.bin java gui to do this storage agent upgrade. Thanks! Rick asasdasdf -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Grigori Solonovitch Sent: Tuesday, April 29, 2014 11:45 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Upgrading to v6 storage agent and TDPO We have done this a year ago (5.5 --> 6.3.3.100). For Windows TSM Clients: 1) stop all TSM services; 2) run TSM Installer from new agent; 3) start TSM services; Notes: 1. Stopping TSM services is critical - reboot is required is any of the services is not stopped!! 2) There are some limitations for Windows 2003 (we are using: TSM Client 7.1 for Windows 2008/2012 and TSM Client 6.4.1 for Windows 2003, which officially is not certified, but required for TBMR 7.1). For AIX : 1) stop TSM services; 2) upgrade TSM Client by "smitty update_all"; 3) start TSM services. Notes: 1) Maximum allowed version for AIX 5.3 is 6.2 (6.2.4.4 in my case); 2) There is no limit for AIX 7.1 (7.1 in my case??); For TDP: 1) for Oracle under AIX just "smitty update_all" for selected version (7.1 in AIX 7.1); 2) for MS SQL it is much more complicated and you need to pay specific attention for each used version and selected target version; 3) for Exchange see MS SQL. I hope this information will help you at least a little bit:):) Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rhodes, Richard L. Sent: 29 04 2014 10:18 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Upgrading to v6 storage agent and TDPO We just finished our TSM v5 to TSM v6 server upgrades. I'll have to say it generally went very well. Lots of work but no real problems. Now I have to upgrade a bunch of V5 Storage Agents and TDPO setups. I looked at the upgrade guide and Storage Agent guide, but didn't find much on how to upgrade them. All the storage agents are at v551, the highest v5. Let me ask some questions . . . - Do you have to uninstall v5 before running install.bin to upgrade/install to v6? - Since it's not installing DB2, is it possible to just run a smitty install of the AIX binaries, instead of using the Java install.bin pgm? - Any other thoughts/suggestions for upgrading a Storage Agent? (Haven't looked at TDPO yet . . .) 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. Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are
AW: Tsm replication 7.1
Hallo Robert, interesting questions: As I'm currently documenting and testing as well the node replication feature (see http://www.mm-it.at/de/TSM_Node_Replication_CMDs_Options_at_a_glance.html) I try to share my current knowledge: Domain Change on Target Replication Server: If you move a node to a different domain on the target, replication will move it back Means, that if I change a domain for the node on the target replication server AFTER a successful replication and then try another replication to the same node , the domain for the node on the target server changed back (without a message!!!) to the original one. replstate=purgedata E.g. if you do: de fi node-name * replstate=purgedata datatype=backup, then: è Backup rule data is then set to state "Purge Data":à see q fi node * f=d è During next replication the objects will be deleted on the target server (see message during replication) and è The replstate for the filespace will be set to disabled You can see the status of the deleted objects later on with q replicaton node-name f=d What remains to be clarified for me: also with "update node" you have the "undocumented" option of purgedata for the replstate, but I can not see any "purge data" status è My be TSM development can clarify - thanks Expiration: The Source server instructs target to delete objects during replication rgds Michael michael.mal...@tsmpoweradmin.com -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von Robert Ouzen Gesendet: Mittwoch, 30. April 2014 11:53 An: ADSM-L@VM.MARIST.EDU Betreff: Tsm replication 7.1 Hi to all Long time ago I test the replication feature for DRM purpose. Now I wanted to implant it between two TSM servers version 7.1 and O.S Windows 2008 R2 64B. I have some questions: · The command replicate node if no domain exist in the TARGET server as in SOURCE server , put the node under the domain STANDARD. My question is after it can I update the node to a different domain (created on the TARGET server but in the SOURCE server is not exist) , and in the next replicate node it will go to this domain and not to STANDARD ? · In SOURCE server in the command "update fi" it is an option replstate=purgedata" I don't quite understand the purpose ? · When replicate node with type ARCH have in ARREPLRULEDEFAULT the options : ALL_DATA , ALL_DATA_HIGH_PRIORITY , DEFAULT , NONE . I am using ALL_DATA If I have a node in the SOURCE server with archive copygroups rentention of 360 days and in the TARGET server in the archive coypgroups retention of the domain STANDARD is 90. My question what happen in the replicate node to the TARGET server when no same archive copygroups retention ? Did all data will be replicate and only after running an expire inventory in the TARGET server only the data for 90 days will remain ? or already during the replicate node only the data for 90 days with will replicate ? T.I.A Best Regards Robert
Re: memory usage TSM for exchange
Hi Remco, Judging from these similar posts... http://social.technet.microsoft.com/Forums/exchange/en-US/3736df82-e5cb-4665-a97c-eb4a70868271/information-store-database-buffer-paged-during-backup?forum=exchangesvravailabilityandisasterrecoverylegacy http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27697281.html ... it looks like it could be related to activity that the Exchange Server does during a backup. It also looks like it's a general backup issue since the same problem appears with Windows Server Backup as well. The second link above showed that increasing the page file size helped. Thank you, Del "ADSM: Dist Stor Manager" wrote on 04/30/2014 07:57:25 AM: > From: Remco Post > To: ADSM-L@vm.marist.edu, > Date: 04/30/2014 07:58 AM > Subject: memory usage TSM for exchange > Sent by: "ADSM: Dist Stor Manager" > > Hi all, > > our exchange team has been investigating a problem regarding > available memory on their servers for quite some time. They've now > correlated the alert "A significant portion of the database buffer > cache has been written out to the system paging file" to the end of > the TSM exchange backup. We're running TSM 6.4 with TSM for Mail 6.4 > on win 2k8R2 and exchange 2010, on a system with 24 GB ram (and 4 cpu's). > > Anyone got a hint as to what might be causing TSM or the system to > use so much memory at the end of the backup? And, what can we do to > avoid the system paging? > > -- > > Met vriendelijke groeten/Kind Regards, > > Remco Post > r.p...@plcs.nl > +31 6 248 21 622 >
TSM User group meeting May 12, Columbia SC.
For agenda and sign-up information go to the http://tivoli-ug.org/ site or click this link: http://bit.ly/QBq3NM -- Ken Bury kenb...@us.ibm.com
Re: AW: Tsm replication 7.1
Hi Michael Thank you very much for the information . make more sense now. Your link is very helpful too .. I have just need another clarification about the policy retention , if they are not the same in SOURCE and TARGET servers . I mean that I want to keep in TARGET server less versions (type backup) or last days (type archive). To make simple in source F.S (default) - Node (default) - server (ALL_DATA) So if I have for a node a policy (archive) of keeping 365 days and on the TARGET server I just want to keep 60 days. During the first replicate node which policy works ? All data for 365 days will be replicate or just the data for 60 days ? T.I.A Best Regards Robert Ouzen Haifa University Israel -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Michael malitz Sent: Wednesday, April 30, 2014 3:49 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] AW: Tsm replication 7.1 Hallo Robert, interesting questions: As I'm currently documenting and testing as well the node replication feature (see http://www.mm-it.at/de/TSM_Node_Replication_CMDs_Options_at_a_glance.html) I try to share my current knowledge: Domain Change on Target Replication Server: If you move a node to a different domain on the target, replication will move it back Means, that if I change a domain for the node on the target replication server AFTER a successful replication and then try another replication to the same node , the domain for the node on the target server changed back (without a message!!!) to the original one. replstate=purgedata E.g. if you do: de fi node-name * replstate=purgedata datatype=backup, then: è Backup rule data is then set to state "Purge Data":à see q fi node * f=d è During next replication the objects will be deleted on the target server (see message during replication) and è The replstate for the filespace will be set to disabled You can see the status of the deleted objects later on with q replicaton node-name f=d What remains to be clarified for me: also with "update node" you have the "undocumented" option of purgedata for the replstate, but I can not see any "purge data" status è My be TSM development can clarify - thanks Expiration: The Source server instructs target to delete objects during replication rgds Michael michael.mal...@tsmpoweradmin.com -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von Robert Ouzen Gesendet: Mittwoch, 30. April 2014 11:53 An: ADSM-L@VM.MARIST.EDU Betreff: Tsm replication 7.1 Hi to all Long time ago I test the replication feature for DRM purpose. Now I wanted to implant it between two TSM servers version 7.1 and O.S Windows 2008 R2 64B. I have some questions: · The command replicate node if no domain exist in the TARGET server as in SOURCE server , put the node under the domain STANDARD. My question is after it can I update the node to a different domain (created on the TARGET server but in the SOURCE server is not exist) , and in the next replicate node it will go to this domain and not to STANDARD ? · In SOURCE server in the command "update fi" it is an option replstate=purgedata" I don't quite understand the purpose ? · When replicate node with type ARCH have in ARREPLRULEDEFAULT the options : ALL_DATA , ALL_DATA_HIGH_PRIORITY , DEFAULT , NONE . I am using ALL_DATA If I have a node in the SOURCE server with archive copygroups rentention of 360 days and in the TARGET server in the archive coypgroups retention of the domain STANDARD is 90. My question what happen in the replicate node to the TARGET server when no same archive copygroups retention ? Did all data will be replicate and only after running an expire inventory in the TARGET server only the data for 90 days will remain ? or already during the replicate node only the data for 90 days with will replicate ? T.I.A Best Regards Robert
