Data Protection Software

 View Only
  • 1.  What does q event status "Severed" means?

    Posted Thu November 26, 2020 12:20 AM

    Hi,
    I have configured one spectrum Protect 8.1.4 client schedule on windows 2016 and it has executed but the status is showing "Severed", all others backup showing completed.
    I have check help to find out the meaning and got to know the general meaning is 'Specifies that the communications with the client is severed before the event can complete'.
    Now, i am concerning that does my backup completed or not?
    Looking for your expert opinion.

    SP Server and client version is 8.1.4


    Kind regards,



    ------------------------------
    Md Mokarrom Hossain
    ------------------------------


  • 2.  RE: What does q event status "Severed" means?

    IBM Champion
    Posted Thu November 26, 2020 01:25 AM
    check dsmerror.log on the client side.

    ------------------------------
    NEZIH BOYACIOGLU
    ------------------------------



  • 3.  RE: What does q event status "Severed" means?

    Posted Fri November 27, 2020 05:14 AM
    Edited by Md Mokarrom Hossain Fri November 27, 2020 05:14 AM
    Thank for your reply message.
    After looking at schedule log, found that schedule backup task had canceled. Also checked system uptime as well as event log, they're clear message regarding automatic restart happened due to os patch update. 
    Now schedule running as expected without user action.


    Thanks


    ------------------------------
    Md Mokarrom Hossain
    ------------------------------



  • 4.  RE: What does q event status "Severed" means?

    Posted Mon August 28, 2023 04:05 PM

    The "Severed" status in IBM Spectrum Protect (formerly known as Tivoli Storage Manager) indicates that the communication between the client and the server was interrupted before the backup event could complete. This interruption could be due to various factors, such as network issues, connectivity problems, or even a configuration mismatch.

    Here are some steps to help you troubleshoot and determine whether your backup actually completed or not:

    Check Logs:
    Look at both the client-side and server-side logs to gather more information about why the communication was severed. Logs can provide insights into any errors or issues that might have occurred during the backup process.

    Network and Connectivity:
    Ensure that there are no network issues between the client and the server. Check for any connectivity problems, firewalls, or security settings that might be affecting the communication.

    Client Configuration:
    Verify that the client configuration is correct, including the communication settings, authentication credentials, and backup paths. Any misconfiguration can lead to communication issues.

    Server Configuration:
    Similarly, double-check the server configuration to ensure that it's properly configured to accept connections from the client. Ensure that the client's certificate (if SSL is being used) is valid and accepted by the server.

    Firewalls and Security Software:
    If there are firewalls or security software in place, make sure they are not blocking the communication between the client and the server.

    Network Latency:
    High network latency can sometimes lead to communication timeouts. If the backup is particularly large or the network is slow, consider adjusting the communication timeout settings in the client's options file.

    Update Client and Server:
    Ensure that both the client and the server are running the latest version and any available patches. Sometimes, issues related to communication can be resolved by updating the software.

    Client Scheduling:
    Check the scheduling settings for the backup event. Ensure that there is enough time allocated for the backup to complete before the scheduled event ends.

    Run Manual Backup:
    To determine whether the backup actually completed, consider running a manual backup of a small dataset and monitoring it closely. This will help you understand if the "Severed" status is persistent or if it was an isolated incident.

    IBM Support:
    If you've gone through these steps and the issue persists, consider reaching out to IBM support for more targeted assistance. They can provide insights into your specific configuration and environment.

    Remember that determining whether the backup completed or not is crucial for data protection. If you're uncertain about the integrity of your backups, it's important to address the "Severed" status and work towards resolving it to ensure the safety of your data.



    ------------------------------
    big redd
    ------------------------------