Have been given the task of trying to take over/fix some rotating backups from someone. 2x tape 2x disk standard type schedule is already in place.

My issue is that it seems to deal decently with Windows boxes and MSSQL backups but I have about a dozen linux machines(RHEL) that it really does not like to play with. The agent hangs, and the symantec kb suggested to just disable selinux (which annoyed me just in principle) and I can't imagine that's been a tenable solution for people and the backup machine media server doesn't want to connect/trust the connection to the agent.

Being that I know more of the *nix side of the world my initial inclination is to find a different solution but since this is a licensed/supported (read: they've already paid the $$$$$ so me telling them that a opensource type product would have served their needs doesn't make them super happy) I figured I would see if anyone knew anything.

 

-----signature-----

Glad to see the "we paid for it now use it and I don't care if there are other ways to create a solution exist that are better" is a common annoyance.

It's even better when later (year+) they tell you to use/do what you told them to do in the first place .

 

-----signature-----

Are you doing the remote agent install? I ended having to manually install the agent on all our boxes.

 

-----signature-----

I am trying to get the media server to authenticate talk with the agents. I did install (upgrade from older versions in some cases) them manually but the thing will not connect/"trust" with them. It shows them in the list of machines but complains about credentials and such, which I've added/removed/modified is where I'm stuck.

At this point what I suspect is that when someone was doing some rack reorganization(albeit months ago ) they crossed up network cables because I noticed all the network traffic was coming through just 1 nics (which it shouldn't be as it physically connects to 2 switches which enforce some network segmentation and correspond well with which backups are happening and which aren't...) but I will have to make a trip out to verify because I didn't want to risk breaking remote access by messing with the windows settings.. making me that the machine wasn't virtualized.

 

-----signature-----

/facepalm

Yup, time to activate sneakernet

 

-----signature-----

I never had any issues with our RHEL servers. Though like the other poster, I did end up manually installing the agents.

 

-----signature-----

I've for the most part got it going... although it's been irritating for a variety of reasons at each step of the way.

Like an idiot I had grabbed 2010 R3 off their site without looking closely enough and our server is running 2010 R2 So the agent packaged within the DVD is a different build and when I went back to and older agent it at least connects.. although I learned that the symantec thing was really bad about changing login credentials to remote machines when the account i was logged in from didn't create the profile...

On the linux side however I really dislike their suggestion of setenforce 0, and I honestly have no idea how things were previously running at all in some cases because there is no iptable rule and when i have the linux firewall up it complains and pukes so I'll have to open a port range or something. I've also noticed that the beremote process on the linux box has got a lot of complaints and it did hang on 1 system and seems to routinely crash on the one Domino/Notes server that it's attached to but that's not my problem (yet).

But on the upside I'm down to just getting through all of the rotating jobs and making sure that there's not some other squirrely difference between the different days or device backups.

 

-----signature-----