cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Veritas.com
Support

Recommended Settings for Linux Master/Media Servers

Go to solution
backup-botw
Level 6

‎06-02-2015 09:25 AM

Is there is a list of recommended config settings for the RedHat Linux OS when running as a master or media server? Kind of a vague question I know but I am curious about settings like these ones below...

cat /proc/sys/net/ipv4/tcp_keepalive_time
7200
cat /proc/sys/net/ipv4/tcp_keepalive_intvl
75
cat /proc/sys/net/ipv4/tcp_keepalive_probes
9

Currently they are just default settings as this is a new site, but I would like to go ahead and best practice it to avoid any issues.

Thank you!

0 Kudos
1 ACCEPTED SOLUTION

Accepted Solutions

Go to solution
watsons
Level 6

‎06-02-2015 11:24 PM

See also: 

http://www.symantec.com/docs/TECH167095

The TCP keepalive settings are usually tuned only when there is a problem, such as error 24 or socket connection terminated by firewall.

View solution in original post

0 Kudos
5 REPLIES 5

Go to solution
backup-botw
Level 6

‎06-02-2015 09:27 AM

I should note that I already have the semaphore values configured based on this link...

https://support.symantec.com/en_US/article.TECH203066.html

0 Kudos

Go to solution
RamNagalla
Moderator
Moderator
Partner    VIP    Certified

‎06-02-2015 10:37 AM

 

the best value that i can say for tcp_keepalive_time is 900

please refer NetBackup Backup Planning and Performance Tuning Guide Release 7.5 and Release 7.6 page number 196

https://support.symantec.com/en_US/article.DOC7449.html

0 Kudos

Go to solution
watsons
Level 6

‎06-02-2015 11:24 PM

See also: 

http://www.symantec.com/docs/TECH167095

The TCP keepalive settings are usually tuned only when there is a problem, such as error 24 or socket connection terminated by firewall.

0 Kudos

Go to solution
backup-botw
Level 6

‎06-03-2015 05:51 AM

Thats actually whats driving the question...had an issue doing a restore at a new site.

1: (2820) NBU VMware policy restore error
06/02/2015 09:57:02 - begin Restore
06/02/2015 09:57:03 - restoring from image 43test051vm_1430854933
06/02/2015 09:57:03 - Info bprd (pid=19313) Restoring from copy 1 of image created Tue May  5 12:42:13 2015 from policy Denver_VMware_Test
06/02/2015 09:57:03 - requesting resource @aaaab
06/02/2015 09:57:03 - granted resource  MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=XP43TAPE008;Path=PureDiskVolume;StorageServer=xp43tape008;MediaServer=xp43tape010
06/02/2015 09:57:04 - Info bprd.sfr (pid=19313) Restoring to vCenter server 43apps002vm, ESX host v43host004.bankofthewest.com, Datacenter /Denver, Folder /Denver/vm/VM's/, Display Name 43test051vm_restore, Resource Pool/vApp /Denver/host/Trusted-Denver - 00 - Prod - UCS/Resources, Datastore/Datastore Cluster Regular VM's - Less Then 1TB
06/02/2015 09:57:05 - Info bpdm (pid=18218) started
06/02/2015 09:57:05 - started process bpdm (pid=18218)
06/02/2015 09:57:05 - Info bpdm (pid=18218) reading backup image
06/02/2015 09:57:05 - Info bpdm (pid=18218) requesting nbjm for media
06/02/2015 09:57:06 - Info bpdm (pid=18218) using 30 data buffers
06/02/2015 09:57:06 - Info bpdm (pid=18218) spawning a child process
06/02/2015 09:57:06 - Info bpbrm (pid=18218) child pid: 18227
06/02/2015 09:57:14 - begin reading
06/02/2015 09:57:17 - end reading; read time: 0:00:03
06/02/2015 09:57:17 - Info bpdm (pid=18218) completed reading backup image
06/02/2015 09:57:17 - Info bpdm (pid=18218) EXITING with status 0
06/02/2015 09:57:17 - Info xp43tape010 (pid=18218) StorageServer=PureDisk:xp43tape008; Report=PDDO Stats for (xp43tape008): read: 11199 KB, CR received: 26308 KB, CR received over FC: 0 KB, dedup: 0.0%
06/02/2015 09:57:41 - requesting resource @aaaab
06/02/2015 09:57:42 - granted resource  MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=XP43TAPE008;Path=PureDiskVolume;StorageServer=xp43tape008;MediaServer=xp43tape010
06/02/2015 09:57:43 - Info bpbrm (pid=18242) 43tape001 is the host to restore to
06/02/2015 09:57:43 - Info bpbrm (pid=18242) reading file list for client
06/02/2015 09:57:43 - connecting
06/02/2015 09:57:43 - Info bpbrm (pid=18242) starting bptm
06/02/2015 09:57:50 - Info tar (pid=6112) Restore started
06/02/2015 09:57:50 - connected; connect time: 0:00:00
06/02/2015 09:57:50 - Info bpbrm (pid=18242) bptm pid: 18243
06/02/2015 09:57:50 - Info bptm (pid=18243) start
06/02/2015 09:57:50 - started process bptm (pid=18243)
06/02/2015 09:57:50 - Info bptm (pid=18243) reading backup image
06/02/2015 09:57:50 - Info bptm (pid=18243) using 30 data buffers
06/02/2015 09:57:50 - Info bptm (pid=18243) spawning a child process
06/02/2015 09:57:50 - Info bptm (pid=18243) child pid: 18244
06/02/2015 09:57:53 - begin reading
06/02/2015 09:57:58 - Info tar (pid=6112) INF - Transport Type = san
06/02/2015 09:57:58 - Error bptm (pid=18244) cannot write data to socket, Broken pipe
06/02/2015 09:57:58 - Info bptm (pid=18243) EXITING with status 24 <----------
06/02/2015 09:57:58 - Info xp43tape010 (pid=18243) StorageServer=PureDisk:xp43tape008; Report=PDDO Stats for (xp43tape008): read: 13503 KB, CR received: 26318 KB, CR received over FC: 0 KB, dedup: 0.0%
06/02/2015 09:57:58 - Info tar (pid=6112) done. status: 24: socket write failed
06/02/2015 09:57:58 - Error bpbrm (pid=18242) client restore EXIT STATUS 24: socket write failed
06/02/2015 09:59:11 - restored from image 43test051vm_1430854933; restore time: 0:02:08
06/02/2015 09:59:11 - end Restore; elapsed time 0:02:09
NBU VMware policy restore error  (2820)

 

0 Kudos