Eric, If you have nodes that are not replicating, or have not replicated yet, another approach might be to exclude nodes in RECEIVE or SYNCRECEIVE instead.
... where node_name in (select node_name from nodes where repl_mode not like '%RECEIVE') group by node_name - Thanks, Marc... Marc Lanteigne Spectrum Protect Specialist AVP / SRT IBM Systems, Spectrum Protect / Plus +1-506-460-9074 <- New phone number marclantei...@ca.ibm.com Office Hours: Monday to Friday, 7:00 to 15:30 Eastern IBM -----Original Message----- From: Loon, Eric van (ITOP NS) - KLM <eric-van.l...@klm.com> Sent: Wednesday, September 30, 2020 05:23 AM To: ADSM-L@VM.MARIST.EDU Subject: [EXTERNAL] Re: [ADSM-L] Amount of stored data with node replication Hi Lynn, That is indeed what we are going to do. However, we cannot use the schedule association because we do not use the SP scheduler. We use a third party scheduler which is used for all other non-backup related scheduling too. However, Marc Lanteigne came up with the perfect solution. Thanks Marc! Kind regards, Eric van Loon Air France/KLM Storage & Backup -----Original Message----- From: ADSM: Dist Stor Manager <ADSM-L@VM.MARIST.EDU> On Behalf Of Hall, Lynn Sent: dinsdag 29 september 2020 20:53 To: ADSM-L@VM.MARIST.EDU Subject: Re: Amount of stored data with node replication Do you mean to say that you are replicating nodes both directions on the same storage pool? Which from something I recently saw sounds like it might now be possible. Server1, Pool1, Node1 is backed up on Server1 and replicated to Server2. Server2, Pool1, Node2 is backed up on Server2 and replicated to Server1. If that is the case the simple way would be to define which nodes are associated with schedules on each server. And, sum their MB. Try these. The first is simply a report of each node and its Occupancy so you can check to see if it is collecting the nodes you want. The second sums the MB from the Auditocc table. select AO1.NODE_NAME, AO1.BACKUP_MB from Auditocc AO1 left join associations AS1 on AO1.node_name=AS1.node_name where AS1.Schedule_Name is NOT null select SUM(AO1.BACKUP_MB) from Auditocc AO1 left join associations AS1 on AO1.node_name=AS1.node_name where AS1.Schedule_Name is NOT null [image: OCIO-logo-Transparent.png] <https://ocio.iowa.gov/ > Lynn Hall Information Technology Specialist IV Platform Services Office of the Chief Information Officer 200 E Grand Ave | Des Moines, IA 50309 - Mailing mobile 515-669-4325 ocio.iowa.gov [image: social media icons_Twitter cir.png] <https://twitter.com/IowaOCIO >[image: social media icons_LinkedIn cir.png] <https://www.linkedin.com/company/state-of-iowa > On Tue, Sep 29, 2020 at 5:07 AM Loon, Eric van (ITOP NS) - KLM < eric-van.l...@klm.com> wrote: > Hi guys, > > In our company the creation of TSM nodes is automated via a portal. > The script first checks all TSM servers and uses the TSM server > database size to select one of the available servers; the one with the > lowest DB size is selected. > We are now implementing new SP servers and we are switching to node > replication. I like to use a different criterion to select which > server is used as backup target, the one with the lowest amount of > data stored should be used. However, the number of MB stored returned > by a "select > sum(REPORTING_MB) MB from occupancy" is the same on both servers > because of the node replication. How can I retrieve the amount of data > stored, without the replicated data? > Thanks for any help in advance! > > Kind regards, > Eric van Loon > Air France/KLM Storage & Backup > > ******************************************************** > For information, services and offers, please visit our web site: > http://www.klm.com > aQ&c=jf_iaSHvJObTbx-siA1ZOg&r=hMBqtRSV0jXgOdXEmlNk_-O9LHkPCGSh9PJBRSlL8Q4&m=zkN2dMXMHvTuewWHJLniZ3g0sStWY46MA-mMVaqxyeI&s=kE8kXfBnqsxW3ZEsbNZisqHehGnSoN97unLgTMusEa8&e= . This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. > If you are not the addressee, you are notified that no part of the > e-mail or any attachment may be disclosed, copied or distributed, and > that any other action related to this e-mail or attachment is strictly > prohibited, and may be unlawful. If you have received this e-mail by > error, please notify the sender immediately by return e-mail, and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or > its employees shall not be liable for the incorrect or incomplete > transmission of this e-mail or any attachments, nor responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal > Dutch > Airlines) is registered in Amstelveen, The Netherlands, with > registered number 33014286 > ******************************************************** > ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com . This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ********************************************************
