Veritas-bu

Re: [Veritas-bu] bpduplicate errors - read failed, socket write failed (24) and write failed, media read error (85)

2008-06-02 16:28:27
Subject: Re: [Veritas-bu] bpduplicate errors - read failed, socket write failed (24) and write failed, media read error (85)
From: "Aleksandr Nepomnyashchiy" <anepomn AT gmail DOT com>
To: "Chapa, David" <David.Chapa AT netapp DOT com>
Date: Mon, 2 Jun 2008 16:13:42 -0400
David,
Thanks a lot for suggestion, I am googling "disallow_server_file_writes".

The reason why I thought that errors were caused by heavy load is that
out the script with 18 "bpduplicate" commands (for different clients)
only 3 failed.

-Aleksandr


On Mon, Jun 2, 2008 at 3:41 PM, Chapa, David <David.Chapa AT netapp DOT com> 
wrote:
> Wow 3.4?  Let's see if I can pull this out of my memory banks...
>
> I don't necessarily think it is a problem with your TCP settings
>
> I think there is a bp.conf entry that you need to change...
>
> Disallow_server_file_writes
>
> Are you duplicating to/from the same media server?  This needs to go in
> the 'destination' media server's bp.conf file I believe.
>
> Its been a long time since I saw this, but I'm fairly certain this was
> the fix.  I was writing my own duplication scripts years ago and came
> across this one.
>
> David
>
> David A. Chapa
> Director, Backup and Recovery Solutions
> Solutions Marketing HQ
>
> NetApp
> 720-272-8452 Mobile
> chapa AT netapp DOT com
> www.netapp.com
>
>
>
> -----Original Message-----
> From: Aleksandr Nepomnyashchiy [mailto:anepomn AT gmail DOT com]
> Sent: Monday, June 02, 2008 1:01 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] bpduplicate errors - read failed,socket write
> failed (24) and write failed, media read error (85)
>
> Dear All,
> I am running NetBackup 3.4 on Solaris 8. Was trying to bpduplicate from
> disk to tape and got the error below. Google brought me this article
> about tuning TCP parameters on Solaris
> http://seer.support.veritas.com/docs/271200.htm
>
> All my TCP parameters are set to default (see below)... Are these errors
> just a sign that the system was overloaded (which I am already aware)?
> Or there is more?
>
> Thank you,
> Aleksandr
>
> root@bh-ap2 /b2d # ndd -get /dev/tcp tcp_ip_abort_interval 480000
> root@bh-ap2 /b2d # ndd -get /dev/tcp tcp_rexmit_interval_initial 3000
> root@bh-ap2 /b2d # ndd -get /dev/tcp tcp_rexmit_interval_min 400
> root@bh-ap2 /b2d # ndd -get /dev/tcp tcp_rexmit_interval_max 60000
> root@bh-ap2 /b2d #
>
>
> root@bh-ap2 ~ # /usr/openv/netbackup/bin/admincmd/bpduplicate
> -backupid sh-int2_1212294108 -dstunit mktdb1_L1000
>
> Duplicate started Mon Jun 02 01:55:00 2008 INF - Destination storage
> unit mktdb1_L1000 on host bh-ap2.
> INF - Duplicating class Unix-servers, schedule
> dailyDIFF_SunMonTueWedThuSat_2000_01week (sh-int2_1212294108) created
> 06/01/2008 00:21:48, path /b2d.
> INF - host bh-ap2 backup id sh-int2_1212294108 read failed, socket write
> failed (24).
>
> INF - host bh-ap2 backupid sh-int2_1212294108 write failed, media read
> error (85).
>
> INF - Duplicate of backup id sh-int2_1212294108 failed, media read error
> (85).
>
> INF - Status = no images were successfully processed.
>
> root@bh-ap2 ~ #
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

<Prev in Thread] Current Thread [Next in Thread>