[prev in list] [next in list] [prev in thread] [next in thread] 

List:       adsm-l
Subject:    Re: finding remaining replication  workload
From:       PAC Brion Arnaud <Arnaud.Brion () PANALPINA ! COM>
Date:       2017-10-17 12:54:53
Message-ID: a2800143710247a699e57af552faca55 () ch22k640 ! corp ! panorg ! com
[Download RAW message or body]

Rick,

You saved my day ! 

Thanks a lot for your help : now that I know what table to look after, I'll improve \
your query a bit to fit my needs, and I'll be good ;-)

Cheers.

Arnaud 


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick Adamson
Sent: Tuesday, October 17, 2017 2:41 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: finding remaining replication workload

The information is in the REPLICATIONVIEW table.

Something like this:
select NODE_NAME, START_TIME, cast(TOTBYTES_TO_REPLICATE/1024/1024 as integer) from \
REPLICATIONVIEW where START_TIME>=(current_timestamp-24 hours) order by \
TOTBYTES_TO_REPLICATE desc

It will display date left to replicate largest to smallest amount in megabytes. 

-Rick Adamson

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of PAC Brion \
                Arnaud
Sent: Tuesday, October 17, 2017 8:13 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] finding remaining replication workload

Hi Rick,

Thanks a lot for the tip : I never paid attention to this, probably because my first \
experiences with the new O.C. were so disappointing ;-)

Note that I'm still taker for some SQL query that would allow me to build my \
homegrown reports ...

Cheers.

Arnaud

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick Adamson
Sent: Tuesday, October 17, 2017 1:55 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: finding remaining replication workload

Arnaud,
Did you try looking in the operations center?
Select "Clients" from the menu, there is a column "Replication Workload" that \
provides the amount of data per node that has not been replicated.

-Rick Adamson


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of PAC Brion \
                Arnaud
Sent: Tuesday, October 17, 2017 6:45 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] finding remaining replication workload

Hi Team,

We are working on a new TSM environment (still experimenting),  where we entirely \
rely on TSM replication features to ensure disaster resiliency. We therefore \
installed two Spectrum Protect servers (8.1.1.0), which are making exclusively use of \
directory based storage pools to store client data (one exception for NDMP based \
backups which are landing on file based stgpools). Both servers are configured to \
replicate each other.

Protect stgpool as well as replicate node operations are scheduled to be executed on \
a regular basis, but it appears that even after these have been executed,  the S.P. \
operation center still reports a certain workload of data to be replicated. \
Unfortunately, without any detail on which node might be the culprit.

I therefore would be interested to know if any of you succeeded in writing a query \
that would report the name of nodes, filespaces, and data amount still to be \
replicated !

Thanks for any hint !

Cheers.

Arnaud

******************************************************************************************************************************
 Backup and Recovery Systems Administrator Panalpina Management Ltd., Basle, \
                Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: arnaud.brion@panalpina.com<mailto:arnaud.brion@panalpina.com>
This electronic message transmission contains information from Panalpina and is \
confidential or privileged. This information is intended only for the person (s) \
named above. If you are not the intended recipient, any disclosure, copying, \
distribution or use or any other action based on the contents of this information is \
strictly prohibited.

If you receive this electronic transmission in error, please notify the sender by \
                e-mail, telephone or fax at the numbers listed above. Thank you.
******************************************************************************************************************************



[prev in list] [next in list] [prev in thread] [next in thread]