• 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.

Consecutive Failures Command

kvkbabu

Active Newcomer
Joined
Jan 21, 2009
Messages
7
Reaction score
0
Points
0
i am looking for a Consecutive Failures command for file level backups and VM backups, can some share me pls
 

marclant

ADSM.ORG Moderator
Joined
Jun 16, 2006
Messages
3,698
Reaction score
610
Points
0
Location
Canada
Website
www.ibm.com
Not sure exactly what you mean by consecutive failure. If you mean that the backup failed more than X days in a row, the best method is to use the Operation Center.

First, set the At-Risk value globally to what you want. You can then update individual nodes to have a different At-Risk or bypass if you don't care that they miss/fail.

Second, open the Clients panel and sort by At-Risk. All those with a red X in the At-Risk column have not had a backup in your At-Risk criteria.

Alternatively, you can email yourself the General Operations Report. Open the attached .html version the report which will include all the nodes at-risk.


You could also do something similar with a SQL query.
SQL:
select node_name,filespace_name,last_backup_complete from filespaces where date(last_backup_complete)<timestamp(current_date)-(3)days order by node_name,filespace_name
In that example, I used 3 days because that's what we were interested in, the list of filespaces that have not backed up in more than 3 days. So that would have meant that the backup was either missed of failed.
 

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: 19 18.3%
  • Keep using TSM for Spectrum Protect.

    Votes: 63 60.6%
  • Let's be formal and just say Spectrum Protect

    Votes: 13 12.5%
  • Other (please comement)

    Votes: 9 8.7%

Forum statistics

Threads
31,824
Messages
135,716
Members
21,788
Latest member
ajay24983
Top