Contact us - Horizon DataSys
Go Back   Horizon DataSys Community Forums > Horizon DataSys > Disaster Recovery Programs > RollBack Rx
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Rollback RX taking a lot of cpu

This is a discussion on Rollback RX taking a lot of cpu within the RollBack Rx forums, part of the Disaster Recovery Programs category; Lately, I've seen one of the cores of my 2-core processor getting 100% occupied during something like 10-20 minutes at ...

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 03-02-2010, 11:24 AM
Junior Member
 
Join Date: Mar 2010
Posts: 5
Default Rollback RX taking a lot of cpu

Lately, I've seen one of the cores of my 2-core processor getting 100% occupied during something like 10-20 minutes at a time, for no apparent reason. Using Process Explorer, I found that the processes occupying the cpu are either System or SHDSERV.exe. When it is System, Process Explorer tells me that it is the Shield.sys thread that is occupying the cpu. At these times, if I try to open the GUI of Rollback RX, it takes very long (1 minute or more) to open.

When this happens, Rollback RX isn't supposed to be doing anything special, like taking a snapshot or defragging.

Can someone help me to solve this issue? Has anyone seen any similar behavior? I've only seem a similar, but apparently more limited version of this problem in post

http://horizondatasys-forum.com/roll...k-process.html

and that post doesn't mention any solution.

Thanks in advance for any help.
Reply With Quote
  #2 (permalink)  
Old 03-02-2010, 12:45 PM
Administrator
 
Join Date: Feb 2010
Posts: 394
Default Greetings

Hello and welcome kabluiii! Thanks for stopping by the forum. Let's see if we can get some input on this.
Reply With Quote
  #3 (permalink)  
Old 03-03-2010, 03:04 AM
Junior Member
 
Join Date: Mar 2010
Posts: 5
Default

Some more information.

My operating system: Windows Vista Business SP2 32 bit.

When it is System that is taking the cpu, Process Explorer says that the thread is Shield.sys+0x6dbc. I guess that 0x6dbc is the address of the routine that is being executed within Shield.sys. This may help to understand what is going on.

My version of Rollback Rx is 9.0, build 2694141964.

Last edited by kabluiii; 03-03-2010 at 05:52 AM. Reason: Adding some further information
Reply With Quote
  #4 (permalink)  
Old 03-04-2010, 12:37 PM
Support Person
 
Join Date: Sep 2009
Posts: 11
Default

Quote:
Originally Posted by kabluiii View Post
I've only seem a similar, but apparently more limited version of this problem in post

http://horizondatasys-forum.com/roll...k-process.html
and that post doesn't mention any solution.
.
Good morning Mr. Bluiii (or, may I call you Ka?):

Yes, the lack of a resolution is true of almost of all threads. People get a complex problem and discuss it in the Forum. They are eventually sent to the Service Ticket system. If their problem gets solved, hardly anyone reports back to the Forum to let the rest of us know. Which is exactly the same situation we would see if the problem didn't get solved.

Now, I would continue on and on in this vein, but I live in a glass house and throwing stones is not a good idea.
__________________
Cheers,
DMC
Reply With Quote
  #5 (permalink)  
Old 03-05-2010, 10:00 AM
Nick10's Avatar
Horizon Staff
 
Join Date: Feb 2009
Location: Burnaby
Posts: 242
Default

Quote:
Originally Posted by kabluiii View Post
Lately, I've seen one of the cores of my 2-core processor getting 100% occupied during something like 10-20 minutes at a time, for no apparent reason. Using Process Explorer, I found that the processes occupying the cpu are either System or SHDSERV.exe. When it is System, Process Explorer tells me that it is the Shield.sys thread that is occupying the cpu. At these times, if I try to open the GUI of Rollback RX, it takes very long (1 minute or more) to open...
This is not normal activity. The SHDSERV.exe will usually do a background snapshot defrag when the PC is idle. However, if you try to open the GUI of RollBack Rx or any other application this process should stop. The Shield.sys driver does lock the drive during the defragging so that nothing corrupts the process; however, again if you open any application etc these should stop and your PC should be fully available resource wise.

I think that our development team would need some log files to see what disk activity is occuring on your PC. For this you would need to submit a support ticket (as advised by DMC Campbell):

Please attach the following 3 files and include them in your support ticket. You can submit your support request at http://support.horizondatasys.com

setup.log (c:\program files\shield)
subconsole.log (c:\program files\shield)
128.dat (c:\program files\shield)


Thanks.
Reply With Quote
  #6 (permalink)  
Old 03-07-2010, 09:55 AM
Junior Member
 
Join Date: Mar 2010
Posts: 5
Default

Quote:
Originally Posted by HDS-DMCampbell View Post
Good morning Mr. Bluiii (or, may I call you Ka?):

Yes, the lack of a resolution is true of almost of all threads. People get a complex problem and discuss it in the Forum. They are eventually sent to the Service Ticket system. If their problem gets solved, hardly anyone reports back to the Forum to let the rest of us know. Which is exactly the same situation we would see if the problem didn't get solved.

Now, I would continue on and on in this vein, but I live in a glass house and throwing stones is not a good idea.
Hello,

My real name is Luis (Portuguese), but it's ok if you call me Bluii or Ka

I understand what you say, and I was not complaining about not finding a resolution. I just mentioned the fact to explain why I was posting about this problem despite having found a similar problem posted in another thread.

Last edited by kabluiii; 03-07-2010 at 10:06 AM. Reason: Correct spelling error
Reply With Quote
  #7 (permalink)  
Old 03-07-2010, 10:06 AM
Junior Member
 
Join Date: Mar 2010
Posts: 5
Default

Quote:
Originally Posted by Nick10 View Post
This is not normal activity. The SHDSERV.exe will usually do a background snapshot defrag when the PC is idle. However, if you try to open the GUI of RollBack Rx or any other application this process should stop. The Shield.sys driver does lock the drive during the defragging so that nothing corrupts the process; however, again if you open any application etc these should stop and your PC should be fully available resource wise.

I think that our development team would need some log files to see what disk activity is occuring on your PC. For this you would need to submit a support ticket (as advised by DMC Campbell):

Please attach the following 3 files and include them in your support ticket. You can submit your support request at http://support.horizondatasys.com

setup.log (c:\program files\shield)
subconsole.log (c:\program files\shield)
128.dat (c:\program files\shield)


Thanks.
Thank you for your help. A few days ago I decided to make a manual defrag of my snapshots and, since then, I haven't observed the problem again. If I do, I'll collect the logs and submit them as you indicated.

Incidentally, during this manually started defrag, what I observed was very similar to the "spontaneous" activity that I had observed before: Periods of activity of System (thread Shield.sys+0x6dbc) interspersed with shorter periods of activity of SHDSERV.exe. A possibility would be that Rollback RX was autonomously performing defrags, and not stopping them when I started to use the computer. I have the program configured to not perform any automatic defrags.
Reply With Quote
  #8 (permalink)  
Old 03-08-2010, 11:18 AM
Junior Member
 
Join Date: Mar 2010
Posts: 5
Default

Quote:
Originally Posted by Nick10 View Post
I think that our development team would need some log files to see what disk activity is occuring on your PC. For this you would need to submit a support ticket (as advised by DMC Campbell):

Please attach the following 3 files and include them in your support ticket. You can submit your support request at http://support.horizondatasys.com

setup.log (c:\program files\shield)
subconsole.log (c:\program files\shield)
128.dat (c:\program files\shield)
Hi. The problem returned after a few more snapshots were taken. I've submitted a ticket and uploaded the files that you suggested. I'll try not to forget to post here when the problem gets solved.

Regards,
Luis
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -8. The time now is 05:31 AM.


Powered by vBulletin® Version 3.8.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Site content Copyright (C) 2009 by Horizon DataSys