Just got 5.9 in... anything to worry about?

[Rakerr]

Just for 5.9 in and will be using it to run 3 libraries (L180,L40,SL500) and have any issues with these libraries using 5.9?

 

[Rakerr]

BTW I am installing my Commserve on a Win2k3 server
and will have 32bit and 64bit Media agents.
Backing up 5.1TB (God I hope this works lol)

 

[JG5]

Make sure you install SP1 and any applicable patches that CV Support deems necessary. You shouldn't have any problems with the 32 & 64 bit media agents - I have both with no issues. What's your take on the SL500 so far? We're thinking about getting one as soon as they start shipping with LTO3.

 

[Rakerr]

Just had it installed ... went flawless
The app they give you to view the library is useless
The only thing it is good for is getting the WWN of the fiber drives.

I like it so far... if for nothing else it is the expandability of it.
Seems to run good... better than my old STK L180

I would recommend it

 

[birky]

Patches are available for those experiencing problems with auxiliary copy after upgrading to 5.9.

I hear that SP2 is on it's way shortly

 

[JG5]

I would imagine so considering the number of patches post SP1.

 

[PTALLY]

CV5.9 is not what its craked up to be thats for sure! Too many problems arise even with all the critical updates that seem to come out everyday. I hope you don't have remote media agents if you do good luck!

PTALLY

 

[JG5]

I've got 38 remote Media Agents and have no problems with them at all. What specifically are you referring to?

 

[PTALLY]

WOW 38 is a pretty good number there i have 8 remote agents around the world and they all have problems. I know its not out network we have tested this and connectivity is fine. I have all the latest updates and still have issues with all thr MA's having a constant connection to our CS. Are there any suggestions u have to mke this work better? is there a way to setup CV so that all of the MA's are not depandent of the CS?

Thanks,

PTALLY

 

[JG5]

All of my media agents are in the US. I'm sure you've heard this, but Galaxy is heavily dependent upon a solid DNS infrastructure. The MA's have to communicate with the CS, no way around that. You might want to try to set up a data interface pair between the CS and the MA's using the IP addresses instead of the DNS names.

 

[socrys]

I am having the same issue and when i go to set up my DIP's it doesn't give me the CS as an option. So all of my jobs are failing due to name resolution errors. I need to set the DIP's by IP but it won't let me choose the CS to the MA.