RHEL ES 4 Acronis True Image Echo 8.018 Issues
So I inherited this server and come to find out it stopped backing up about 2 weeks ago. The logs in Acronis stop at the last completed job. It almost seems as though none of the jobs have ran since then but the Scheduler stills how them all.
Looking in the Scheduled Tasks three of the jobs have a status of Waiting.
This server cannot be rebooted until Sundays so I;d love to figure this out w/o bouncing it.
So Im trying to find where/if Acronis generates other logs (google thusfar has been unproductive)
And how can I stop those jobs as the Circle with a slash button does nothing.
Thanks
Looking in the Scheduled Tasks three of the jobs have a status of Waiting.
This server cannot be rebooted until Sundays so I;d love to figure this out w/o bouncing it.
So Im trying to find where/if Acronis generates other logs (google thusfar has been unproductive)
And how can I stop those jobs as the Circle with a slash button does nothing.
Thanks
awed1
It has been a while since I have done this, but the methodology was along this line, in Task Manager, kill the Acronis processes. We had to do so three consecutive times because they would restart. Then, we had to kill the Acronis services. Then we would double check the processes and kill if necessary. Then restart the services. After that, we could restart the BUs or alternately, we could write new policies etc. I hope this works and I hope this helps.
ASKER
Thanks awed1.. Checking all the currently running processes the only acronis one is the TrueImageNotify. So unless they're called something rather archaic there is nothing running.
I apologize Ben, I don't remember the names of the processes that Acronis used.
mms was one. Beyond that, it was too long ago to be any help. Sorry. B.
mms was one. Beyond that, it was too long ago to be any help. Sorry. B.
ASKER
I did find the cron jobs. I removed those then recreated a test job that's running now but in a Waiting state.
I created a test job, scheduled it for my local time today and I watched it start then hit Waiting and never run. So there's my problem I think.. for whatever reason the whatever binary is never started...
I created a test job, scheduled it for my local time today and I watched it start then hit Waiting and never run. So there's my problem I think.. for whatever reason the whatever binary is never started...
ASKER
OK its a gui issue it seems. Ive got a working job running right now from the cmdline
PTL! good work!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
During the course of posting I determined a viable workaround.