cancel
Showing results for 
Search instead for 
Did you mean: 

FT backups failing 83 on few Linux mediaservers and not on other media servers....

Sym_2010
Level 3

Hi,

we have a situation where we see sanclient backups fail with 83 error after recycling/reboot of few of linux mediaservers on some sites..but this is not the situation in other sites...backups running good even after recycling/reboot of mediaservers here.

we need to recycle san client ft services every time to get backups running....

master ----7.5.0.6 linux

media -----7.5.0.6 linux

client ------7.1.0.3 linux especially.....

somebody please help me to resolve this issue.....

 

5 REPLIES 5

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

Hi,

 

Anything special about the sites that fail? Do they have less bandwidth to the main site where the master server is? Do you give adequate time after reboot before you try and backup?

RamNagalla
Moderator
Moderator
Partner    VIP    Certified
Does san client ft services are starting when the server got rebooted? show us the detail status of the failed job

Sym_2010
Level 3

thanks for reply...

yes .we give adequate time after reboot to start backup....

backups fail with pipe open failed...after media server recycle......

when we check on client..we see ft services running on them.....

 

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

After you do the restart of the services/reboot, check the FT server (media server) / client logs using vxlogview.

 

vxlogview -a -o 199 -t 00:10 <<from media server/appliance

vxlogview -a -o 200 -t 00:10 << from client

 

See if you find any clues in there.

Sym_2010
Level 3

Do you guys see any 83 failures on linx environments after recycle/reboot of FT media servers in your environments.....