* Needed command -> # echo “” > /etc/xinetd.d/omni Server_args = inet -log /var/opt/omni/log/inet.log – rw permission for owner is enough for the file, Note that even you had xinetd daemon not installed on RHEL 6, DP client installation script doesn’t warn you about that and not install the needed daemon either.ġ) First I created sub-service named “omni” by adding a file also named “omni” under /etc/xinetd.d/ path – Agent’s configuration path (folders and files), – Agent service (daemon) which runs as xinetd daemon’s sub-service, After a little survey I found that several parts of DP agent are missing at RHEL 6 server. As expected, Cell Manager server couldn’t establish communication with the RHEL 6 client. I installed client application including core, disk agent (da) components from DP 6.0 DVD successfully, just with an “Import host failed” warning message. Recently we needed to install Data Protector 6.0 client on one of our new Linux servers on which has Red Hat 6.2 64 Bit. PS : T oday (25 Dec 13), I’ve noticed that there was a related Symantec Technote here. I wish this saves a few hours of you SEP experts/admins. Now feel free to run a LiveUpdate session on SEPM console. * Set the “Restricted File Growth” value to let me say 40.000 MB (till next year 😉 )
* Select Files page and click on “… button” stated after the value located in “sem5_content” row and “Autogrowth” column * Right click sem5 database select Properties Until Symantec come up with, I have a manual solution. Symantec have to find a solution to this issue urgently.
Consequently the older design of SEP database doesn’t meet today’s requirements. And these definitions’ sizes getting larger day by day. size limit of a database file of sem5 (SEP’s db) database.Īs you may know, definition revisions mainly stored in SEP Database. If you have encountered SEP virus-definition update problem on SEPM recently (late 2013) and if this is a large enterprise’s production system which keeps about 30 definition revisions, the reason is most probably the max.
0 kommentar(er)
