This content has been marked as final. Show 4 replies
I have splitted your post to a new topic.
Regarding you question a recovery of the epo server (master repository) can be done the following way:
1) Reinstall OS
2) Reinstall ePO 4 with the exact same patch level and exact same port configuration
3) Checkin all packages and extensions you had before
4) Restore you security keys (be sure to EXPORT your security keys from your existing server regularly)
5) Delete new initial database and restore backup database
Regarding policies, thr clients will only get them from your ePO Server, so if it is down there is no way to apply new policies.
I am now starting to get concerned that this is the only option for disastery recovery and this now links back to my initial post about the ePO design where you have suggested using only one ePO server and one distributed repository. I am aware that the solution we are outlining is limited due to limited chassis and indeed not taking advantage of clustering.
Sorry to be a pain but could you please outline why you have suggested using only one ePO server and not both our severs being master ePO servers? Is it due to being technically difficult\impossible or another reason altogther?
In my defence...I have had only a few days to get to grips with the product :)
Asking is no problem :-)
The only option to get a real failover solution is to install a epo server cluster.
Installing two seperate epo servers will not be a failover because (currently) the agent can only access one epo server. For feature releases it is planned to configure more epo servers for one agent.
It now becomes clearer, I think I'm getting there and should have realised that as I read it yesterday
When the FRAMEPKG.EXE is created it contains the IP address of the server.....etc.