Advice On Scheduling Stop/Start of RPC

[Kayraam]

Can someone give me some tips on how to schedule the Backup Agent RPC service to stop/start before my backup job runs.

I basically am having problems when backing up Exchange on Win 2000/arcserve 9 getting the E8604 error, The backup works one day then not the next when the service fails.


Thanks in advance.

 

[GSC]

Hi Kayraam
Write a batch file with Net stop and Net start the service that you want to stop / start during your backup.
When you edit the backup job go into Options.
On the tab Pre/Post type in the path to your batch file under:
"Run command before backup job"
and
"Run command after job"

Hope that this helps.

Regards,
GSC

 

[mohamdr]

Sure there is cause for this problem an need to troubleshoote it better than just scheduling to stop & start RPC services.

Have you checked if you have a licensing problem.

 

[Kayraam]

No , there is no licensing problem, there is a known problem with this service being unstable, and CA unofficially advise the course of action of restarting the service before brick lvl backups.

Unfortunately scheduling this is turning out to be more tricky then expected as this service doenst use the standard net stop/start commands.

 

[Stat1c]

Kayraam you sure..
netsvc dbasvr.exe \\Server name /stop
netsvc dbasvr.exe \\Server name /start

 

[mohamdr]

Does anybody the cause of RPC giving problem while doing brick level backup since restarting the service is not a solution it is only workaround?

 

[velley]

yes. that should be workaround but not solution. but there's also no magic solution for E8604 which might have different error codes EC=???.

another possiblility might be due to the Exchange database consistency. ie. isinteg.exe, edbutil.exe for Exch 5.5

actually, brick-level b/k is not a great idea for large org. what I would recommend is upgrade to R11 with Exchange Agent Premium Add-On which supports Exch SIS. Check below URL for more info regarding SIS

http://support.ca.com/techbases/basb11win/basb11win-faq.html#exchange

 

[bloxster]

The cause for the Brick level problem is poor programming. In fact I think it's the RPC mapper that's at fault, but I can't prove it. We have to regularly restart the BEB RPC Service just so that backups can continue. We use Task Scheduler to run a batch file. Task sceduler has to run as the Brightstor service account though ...