Replications between source and target means that that data is being sent
from source is being received by target. If the target doesn't confirm
receive of data  the replication process failes.

After replication process had completed one can use the q repln command to
check the replication state of any node configured to do replication. It
shows how many objects and amount data of the nodes are on source and on
the target.

Op 22 jul. 2016 17:39 schreef "Jeanne Bruno" <JBruno AT cenhud DOT com>:

> Hello.  for this:  but, I need to verify that on the TSM TARGET server  as
> well. Management wants to be able to verity that what the TSM SOURCE server
> states was replicated is the same as what the TSM TARGET server states.
>
>
>
> We don't have replicated info on our Target server either.  I'm thinking
> only the source would store it and the Target server sees it as just data
> and not 'replicated' data once stored in the pools.
>
>
>
> Can you verify doing 'FI' queries on both target and source. (the capacity
> & percent utilization should be the same on both servers, no?)
>
> Also maybe open a TSM gui or command line on one of the replicated servers
> and see what's there to restore.
>
>
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Rick Adamson
> Sent: Friday, July 22, 2016 8:54 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] TSM Replication
>
>
>
>
>
> ** THIS IS AN EXTERNAL EMAIL ** Use caution before opening links /
> attachments. Never supply UserID/PASSWORD information.
>
>
>
>
>
> Ricky,
>
> I know that on the source server there is a field (BKBYTES_REPLICATED) in
> the REPLCIATIONVIEW table. I have used it to query the amount of replicated
> data.
>
> Perhaps someone can chime in from IBM but I did not find this information
> maintained on the target server; if fact I receive an error when attempting
> to query the REPLCIATIONVIEW or REPLTASK tables on it.
>
>
>
> On another note I'm not sure it is necessary; when the "replicate" task
> starts the source server initiates sessions with the target server and
> begins sending data. I would think that there is some type of integrity
> check and acknowledgement performed by the target server and sent back to
> the source server, if there's any issues the task would complete with a
> failure state.
>
> But again that's more of a logical assumption, I have to defer to gurus at
> IBM for clarification....
>
>
>
> -Rick Adamson
>
>
>
>
>
> -----Original Message-----
>
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]<mailto:
> [mailto:ADSM-L AT VM.MARIST DOT EDU]> On Behalf Of Plair, Ricky
>
> Sent: Friday, July 22, 2016 7:57 AM
>
> To: ADSM-L AT VM.MARIST DOT EDU<mailto:ADSM-L AT VM.MARIST DOT EDU>
>
> Subject: [ADSM-L] TSM Replication
>
>
>
> Happy Friday to everyone!
>
>
>
> Can some tell me if there is a command, script or another way to find out
> the summary of how much data was replicated during the replication process
> on the TARGET server?
>
>
>
> Once replication has completed, I can go into the logs on the TSM SOURCE
> server and find out how many files were deleted, and how much data was
> replicated, etc..... but, I need to verify that on the TSM TARGET server
> as well. Management wants to be able to verity that what the TSM SOURCE
> server states was replicated is the same as what the TSM TARGET server
> states.
>
>
>
> Anyway of doing this?
>
>
>
>
>
> I appreciate any help.
>
>
>
>
>
>
>
>
>
> Ricky M. Plair
>
> Storage Engineer
>
> HealthPlan Services
>
> Office: 813 289 1000 Ext 2273
>
> Mobile: 813 357 9673
>
>
>
>
>
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ CONFIDENTIALITY NOTICE: This email message, including any attachments, is
> for the sole use of the intended recipient(s) and may contain confidential
> and privileged information and/or Protected Health Information (PHI)
> subject to protection under the law, including the Health Insurance
> Portability and Accountability Act of 1996, as amended (HIPAA). If you are
> not the intended recipient or the person responsible for delivering the
> email to the intended recipient, be advised that you have received this
> email in error and that any use, disclosure, distribution, forwarding,
> printing, or copying of this email is strictly prohibited. If you have
> received this email in error, please notify the sender immediately and
> destroy all copies of the original message.
>