dsRestore process?

Last post 10-22-2019, 4:23 PM by Wwong. 6 replies.
Sort Posts: Previous Next
  • dsRestore process?
    Posted: 10-21-2019, 10:14 AM

    Hello,

    We have a synthetic full that reaches 22% but then appears to get stuck there for an extended period of time.  When checking the MA, (Linux Hyperscale node) I see a dsRestore process consuming over 100% CPU.  What is this process and what specifically is it doing?  Thanks.

  • Re: dsRestore process?
    Posted: 10-22-2019, 4:16 AM

    Hi BillyK

    Synthetic Full is an operation that considerates the previous Full and Incrementals to create the new Synthetic Full. dsRestore is a a read operation so it can process and update the reference for the subsequent full. 

    How many Synthetic Fulls are you running concurrently?

    Regards

    Winston 

  • Re: dsRestore process?
    Posted: 10-22-2019, 8:54 AM

    We need to be troubleshoot it. dsRestore process should not take 100% CPU. 

  • Re: dsRestore process?
    Posted: 10-22-2019, 8:56 AM

    I checked this morning and it's still consuming 105% CPU and has accumulated over 26 hours of CPU time.  The job is still stuck at 22% with no errors or events being reported.  This can't be normal.  Thanks.

  • Re: dsRestore process?
    Posted: 10-22-2019, 10:42 AM

    Bill,

           This is the first time we are hearning something like this. Can you please escalate the issue.

    Regards,

    Prasad.

  • Re: dsRestore process?
    Posted: 10-22-2019, 4:09 PM

    Hi BillyK

    Seeing the process continuously spiking at 100+% is definitely not normal. 

    Would recommend to engage support so they can review and potential grab Process DUMPs to confirm what could be consuming all the CPU 

    Regards

    Winston

  • Re: dsRestore process?
    Posted: 10-22-2019, 4:23 PM

    Hi BillyK

    Seeing the process continuously spiking at 100+% is definitely not normal. 

    Would recommend to engage support so they can review and potential grab Process DUMPs to confirm what could be consuming all the CPU 

    Regards

    Winston

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy