converting named pipes

[cnicoli]

hey guys i get this error on my backup server and i read on the ca website that it has to do with ports being different in the exchange configuration and in a txt file..but the ports match..and when backing up takes forever because of the converting...any ideas? brightstor 11.5 SP3 btw

 

[Cyklops]

If this concerns an SQL agent, right-click the agent in the source tab of the backup job and change the protocol to named pipes.

regards

 

[cnicoli]

its not doing SQL..it is when document level backup of mailboxes start

 

[davidmichel]

TCP/IP Remote Backup/Restore Configuration—These options apply only to Exchange database level backups.

 

[cnicoli]

im still getting this error, any ideas guys? this is becoming a real pain? our exchange backup runs for like 5 hours its rediculous..please help me out..like i said in my original posts..im running 11.5 w/ SP3 and the port config are correct both are using 6074..one thing i did notice was that when i try to use th command 'telnet servername 6074' i get the error Could not open connection to the host, on port 6074: Connect failed
there isnt any firewalls running on these servers..

do you guys have any ideas?
thanks

 

[davidmichel]

Again with Exchange backup the database level backup can use the IP but bricks level must go back to named pipes. Also Bricks level is just real slow.

Check out the Microsoft Exchange Premium Add-on it will let you do multiple backups at the same time.

 

[cnicoli]

but it was never this slow and my other servers that are doing brick level arent this slow but then again the backup drive & mailbox store are on the same server

 

[davidmichel]

it can also depend on the number and type of attachments. Another thing the Premium add-on does is backup only one copy of the same attachment. So if 20 people get the same attachment only one copy is saved.

Anyways thats my best guess. I'm more a hardware guy and limited as to my Exchange knowledge.