I should have been more complete in my procedure. My apologies.
After stopping the service there might be hung processes running (a good
indication something is broken). You would have to kill those processes also
(it's usually just one process).
Services could be identified by names starting with Sym*. I am looking at one
server that lists two services: "Symantec System Recovery" and
"SymTrackService" and the corresponding processes are "VProSvc.exe" and
"SymTrackServicex64.exe"
Stop the service and check if any .exe for Symantec is still running, if so
kill it. Then start the services.
Tip on associating running process to an application: Task manager default view
shows a description column, but those descriptions can be too generic to
associate task to an application. In task manager, click on "View" in menu bar
and pick "Select Columns..." you will get a list of other available columns to
display. Toward the bottom there is a pick for "Command Line", check mark it
and click "OK". Now your task manager will show you full path of the
application that is running and any arguments passed to it. Sort by this column
and now you have an easy way to find the associated application by looking at
the folder structure.
I would also recommend to clean out any unused backups in the schedule, and the
backup destinations. For example, during an update you might attach a drive,
back up to it, update the station, everything is normal, you disconnect the
drive and are done. If you never delete the backup job and never remove the
drive from the list of backup destinations the software will try to connect to
it every time you open it. This slows down software GUI.
Hope this info is enough to restart your backup software without rebooting.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Stankiewicz, Anthony P.
Sent: Tuesday, February 02, 2016 10:20 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Symantec System Recovery 2013 error
I tried this yesterday on a PDC with the same issue. Did not work. Had to
reboot.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Duc M Do
Sent: Monday, February 01, 2016 10:06 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Symantec System Recovery 2013 error
Denis,
Thanks for that tip. I thought I also tried that tack, but I cannot be 100%
sure -- I've slept since then.
The next time SSR 2013 fails, I'll try this to see if it fixes our problem also.
Duc
On Mon, Feb 1, 2016 at 4:22 PM, Markan, Denis <Denis.Markan@xxxxxxxxxxxx>
wrote:
We are able to resolve this issue by restarting the services for
SSR2013 without having to reboot the server.
Denis Markan
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Duc M Do
Sent: Thursday, January 28, 2016 9:40 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Symantec System Recovery 2013 error
Just a heads-up if you have Symantec System Recovery 2013 running on
Windows 2008 Server (H90).
We have about 20 of these H90 servers running SSR 2013 and have been
having random failures where SSR just fails with a "Cannot create
recovery points for job" error. And the only way to recover from that
is by rebooting the server. ("It's a Windows machine, rebooting is expected,"
some of you will
snort.)
Googling the error leads to Veritas and a knowledge base article:
https://www.veritas.com/support/en_US/article.TECH195857
http://www.veritas.com/docs/000086207
As specified in that article, you'll have to call technical support to
have a case opened for your installation, and they'll supply a link to
download a patch. The article refers to Service Pack 1, but Service
Pack 2 is available now and it's what furnished in the link, which is:
https://www.veritas.com/support/en_US/article.TECH214768
Click on "Attachments" on the right side of the page and choose the
appropriate package (32- or 64-bit) to download.
Disclaimer: As Alex Johnson is fond of saying, this advice is worth
exactly what you pay for it.
Duc
