• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

tsm report on failed replications

#1
Hello all,
I would like to get a report on failed replication using the OC.(ver 7.1.7)...so that I can get emails with the failures..I found the following select statement but it doesn't tell which node failed :0( ..any suggestions?..or maybe someone knows the ANR that tsm gives out with the failed replication node name?
SELECT date_time,severity,message from actlog WHERE message LIKE"ANR1893E'' -
and date_time>current_timestamp-24 hours

thank you in advance for your help :0)
 

marclant

ADSM.ORG Moderator
#2
Try this instead:
Code:
SELECT START_TIME,END_TIME,NODE_NAME,STATE,PHASE,COMP_STATE,COMP_REASON,COMP_CODE FROM REPLICATIONVIEW WHERE COMP_CODE!=0 AND START_TIME>current_timestamp-24 hours
You may need to look at SELECT * FROM REPLICATIONVIEW to see all the fields and possible values in case you need additional filtering. On my test box, they were all successful, so hard to test.
 
#3
Marclant thank you!! it took me a while to tweak the select statement but I think I got it..however, I'm trying to double check in the actlogs but not seeing it..here is my select; SELECT START_TIME,END_TIME,NODE_NAME,STATE,PHASE,COMP_STATE,COMP_REASON,COMP_CODE FROM REPLICATIONVIEW WHERE COMP_STATE='COMPLETE' AND START_TIME>current_timestamp-24 hours
I got;

START_TIME END_TIME NODE_NAME STATE PHASE COMP_STATE COMP_REASON COMP_CODE
2017-10-11 13:00:01.000000 1900-01-01 00:00:00.000000 TNGKPAP01 ENDED NONE COMPLETE NONE 0
2017-10-11 13:00:01.000000 1900-01-01 00:00:00.000000 TNGKPAP01 FAILED REPLICATING COMPLETE NONE 0
2017-10-11 13:00:01.000000 1900-01-01 00:00:00.000000 TNGKPAP01 FAILED REPLICATING COMPLETE NONE
0
I ALSO TRIED;
tsm: >SELECT START_TIME,END_TIME,NODE_NAME,STATE,PHASE,COMP_STATE,COMP_REASON,COMP_CODE FROM REPLICATIONVIEW WHERE STATE='FAILED' AND START_TIME>current_timestamp-24 hours

START_TIME END_TIME NODE_NAME STATE PHASE COMP_STATE COMP_REASON COMP_CODE
--------------------------- --------------------------- ------------------------------------------------------------------ -------- ------------ ----------- ------------ ------------
2017-10-11 13:00:01.000000 1900-01-01 00:00:00.000000 TNGKPAP01 FAILED REPLICATING COMPLETE NONE 0
2017-10-11 13:00:01.000000 1900-01-01 00:00:00.000000 TNGKPAP01 FAILED REPLICATING COMPLETE NONE 0
2017-10-11 13:00:01.000000 1900-01-01 00:00:00.000000 BFSKPAP01 FAILED REPLICATING COMPLETE NONE 0

BUT when I search in actlogs to get more info..nothing related to the replication failure :0( ..where else should I look for this..any idea?
 

rowl

ADSM.ORG Senior Member
#4
Did this issue get resolved? I have a similar question. I have a node replication job that works for 399 out of 400 nodes. I isolated the problem to the D: drive on one Windows client from the replicationview table. The activity log on the source/destination servers only shows "Status of FAILED". When I look at the q noder nodename
Node Name Type Filespace Name FSID Files on Replication Files on
Server Server (1) Server (1)
--------------- ---- --------------- ---- ---------- --------------- ----------
nodename Bkup \\nodename\c$ 2 119,116 TARGETSERVER 120,559
nodename Bkup \\nodename\d$ 1 5,730,399 TARGETSERVER 5,730,398

I tried to replicate these individually by FSID and FSID 2 returns SUCCESSFUL but 1 is FAILED.

Is there any way to query why this is reporting failed?

This is from Spectrum Protect 8.1.0 on both source and target.

Thanks,
-Rowl
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 9 16.4%
  • Keep using TSM for Spectrum Protect.

    Votes: 32 58.2%
  • Let's be formal and just say Spectrum Protect

    Votes: 9 16.4%
  • Other (please comement)

    Votes: 5 9.1%

Forum statistics

Threads
31,150
Messages
132,626
Members
21,324
Latest member
h3llb0y
Top