Error 83 : Open Media Error

Hi Everybody,

I reiterate my issue concerning the title.
Last time, I did not sent any log because I expected that our partner would have solved the issue. Well it is not.

Before I introduce the configuration of the NB :

Master Server = Win 2008 R2 NB 7.0.1

Media Server (where the issue is) = Win 2003 R2

I attached a file wich contains 3 sheet (3 client with the 83 status error code)

We escalated it to the support but it proves to be that they had to escalate to the maker.

The maker feeback's is that all the client return the following error = "image open failed: error 2060017:system call failed"

Thus, they recommend to create a touch file on the Media Server named SIZE_DATA_BUFFERS_DISK and to set up the value to 327680

We did it BUT, the problem is still here....

Anybody knows how to resolve this problem permanently ?

Thank you for your help !

Lala.

Windows Server (2003-2008)

Mark_Solutions
11 years ago
Memory tuning as i outlined above .. tcpip tuning as per the link Marianne gave you .. as you are using Win 2003 then add these keys at the same time you add the memory keys above - after which reboot the server for them to take effect:

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\

DWORD - KeepAliveTime – Decimal value of 510000

DWORD – KeepAliveInterval – Decimal Value of 3

Also worth creating the proxy file on your master / media servers:

Create this file with the value of 800 inside:
\program files\veritas\netbackup\db\config\DPS_PROXYDEFAULTRECVTMO

This needs a service re-start so do all of it then reboot the server

Michael_G_Ander
Level 6
11 years ago
If you are running backup to a dedup pool, the problem can be the number of streams going in and out of the pool at the same time. I have solved status 83 on dedup pools by limiting the IO streams

As your media server is Windows 2003 you also need to look at the memory to see if there is anything getting exhausted e.g. pool, non-pool, heap
RamNagalla
Moderator
11 years ago
I am seeing the backup destination as F:\Backup for 2 clients and E:\Backup for one client.

is there any other clients going to this same destinations...? if yes are they getting successfulll or failures?
lanira_1509
Level 4
11 years ago
Hi Michael,

Thank you very much for your prompt reply.

You know I am a beginner in this environment and I apoligize in advance.

Concretely, when you say limiting the IO streams, what should I do ?

As your media server is Windows 2003 you also need to look at the memory to see if there is anything getting exhausted e.g. pool, non-pool, heap

==> concretely, what do you mean ?

Thank you very much in advance !
lanira_1509
Level 4
11 years ago
To Nagalla,

Yes there are other clients and the result is successfull.
RamNagalla
Moderator
11 years ago
try to run the backup for only these 3 clients to this storage unit.. and make sure no other jobs are running on this srorage unit , for testing purpose.

only 3 clients jobs active for testing.. it will make sure if this is due to the load on the disk or not...

and what type of storage unit it is.. does it basic disk or advanced disk , msdp?
lanira_1509
Level 4
11 years ago
@Nagalla,

OK, I will do it tomorrow.

The type of storage unit is basic disk.
lanira_1509
Level 4
11 years ago
@Nagalla,

Hello,

Today, (very weird) there was no failed jobs...
I will keep this discussion and see on Monday.

I will keep you informed.

Regards,

Lala
lanira_1509
Level 4
11 years ago
@Nagalla,

Today, I tried to rerun the job, all 3, which are on the same storage disk, failed with the same status 83.

I do not know what to do...
lanira_1509
Level 4
11 years ago
Please find a example (same for the 2) of the log.
RamNagalla
Moderator
11 years ago
does this basic disk is from the NFS mount? if yes please have a look into below T/N

http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=S:TECH54767

to make sure this this is not specific to storage unit issue... pleaset try to take the backup of these 3 clients to another storage unit DIsk or tape and see how its working..

if the clients are getting successfull in another storage unit..

provide the output of failed storage unit

1) bpstulist -label <storageunit> -U

2) also enable the bptm log in media server

--> make sure bptm directory is created in /usr/openv/netbackup/logs/bptm (unix media server)

installpath/veritas/netbackup/logs/bptm (windows media server)

and keep the verbose to 5 and test the backups again.

collect the bptm log and attach it to this post...