cancel
Showing results for 
Search instead for 
Did you mean: 

Error 84 from time to time

leszekjed
Level 3

I attache message during failed backup. It's seems that this error occure during most rush time (after midnight when  jobs do day backup). Storage is local disk matrix and a lot of free space on it.

2011-03-24 01:29:13 - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=backup001;Path=PureDiskVolume;StorageServer=llimbackup001;MediaServer=llimbackup001
2011-03-24 01:29:13 - granted resource Dedup001
2011-03-24 01:29:14 - estimated 0 Kbytes needed
2011-03-24 01:29:15 - started process bpbrm (32407)
2011-03-24 01:29:16 - connecting
2011-03-24 01:29:24 - connected; connect time: 00:00:08
2011-03-24 01:29:50 - Critical bptm(pid=32570) image open failed: error 2060012: call should be repeated    
2011-03-24 01:30:25 - end writing
media write error(84)

I tried to analyse case against official explanations of this error but no decsciption match to my situation close enought. Any idea will be welcome ;)

L.J.

7 REPLIES 7

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Have a look at this TN: http://www.symantec.com/docs/TECH75230

Details:
NetBackup PureDisk Deduplication Option (PDDO) backups fail with satus 84 'media write error' after 3 hours. Others may fail to start at all, failing with status 196 after falling outside the NetBackup backup schedule window.
 
Logging:
NetBackup administration console Activity Monitor - Detailed Status window for the failed PDDO backup job will contain:
Critifcal bptm(pid=<pid#>) image open failed: error 2060012 call should be repeated

media write error(84)

 

.......

Background:
PureDisk prevents certain jobs/workflows from running concurrently, such as 'PDDO Data Removal' and 'PDDO Backup' jobs. This cannot and should not be changed for to do so would risk data loss.
 
Resolution:
Ensure that the 'PDDO Data Removal' policy is not scheduled too frequently such as daily, hourly or during heavy backup periods like weekend full backup windows.
 

leszekjed
Level 3

Thanks Marianne for sugestion.

Unfortunely my Netbackup set has no GUI for Pure Disk solution. Is it possible to instal GUI ora manage Pure Disc from CLI? I try fo find any files belong to Pure Disk in my RedHat serwer but no luck. It is very probably that my Pure Disc instance is scheduled 2 times during day (about midnight and after noon) and I notice that error 84 has time coincidence.

Leszek

leszekjed
Level 3

Again, 84 and 83 error today after night backup session. 49 errors with 84 code and 9 with 83 code. All errors occured almost at the same time about midnight when most od daily backup starts. Jobs with 83 code has 4 failed attempts every half an hour. The another common thing is that all 83 and 84 errors comming from db backup (MSSQL/Windows and Oracle/Linux servers).

Typical messages for error 83:

2011-03-24 23:59:35 - requesting resource Dedup001
2011-03-24 23:59:35 - requesting resource llimbackup001.NBU_CLIENT.MAXJOBS.LLIMDB011
2011-03-24 23:59:35 - requesting resource llimbackup001.NBU_POLICY.MAXJOBS.file_OS_Linux_Oracle
2011-03-24 23:59:37 - awaiting resource Dedup001 Reason: Maximum I/O stream count has been reached for disk volume, Media Server: llimbackup001,
     Robot Number: NONE, Robot Type: NONE, Media ID: N/A, Drive Name: N/A,
     Volume Pool: NetBackup, Storage Unit: Dedup001, Drive Scan Host: N/A
    
2011-03-25 00:11:36 - granted resource llimbackup001.NBU_CLIENT.MAXJOBS.LLIMDB011
2011-03-25 00:11:36 - granted resource llimbackup001.NBU_POLICY.MAXJOBS.file_OS_Linux_Oracle
2011-03-25 00:11:36 - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=backup001;Path=PureDiskVolume;StorageServer=llimbackup001;MediaServer=llimbackup001
2011-03-25 00:11:36 - granted resource Dedup001
2011-03-25 00:11:36 - estimated 44 Kbytes needed
2011-03-25 00:11:36 - started process bpbrm (12766)
2011-03-25 00:14:47 - Error bpbrm(pid=12766) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 0, status = 1  
2011-03-25 00:14:47 - Error bpbrm(pid=12766) sts_get_server_prop_byname failed: error 2060057 - retrying       
2011-03-25 00:14:51 - connecting
2011-03-25 00:14:52 - Info llimbackup001(pid=13237) Using OpenStorage client direct to backup from client LLIMDB011 to llimbackup001  
2011-03-25 00:14:52 - connected; connect time: 00:00:01
2011-03-25 00:18:04 - Critical bptm(pid=13237) sts_open_target_server failed: error 2060018 file not found      
2011-03-25 00:18:04 - Critical bptm(pid=13237) failure to open proxy target server llimbackup001: plug-in reports error 2060018 file not found
2011-03-25 00:18:04 - end writing
media open error(83)

and typical message for the error 84 is:

2011-03-24 23:59:41 - requesting resource Dedup001
2011-03-24 23:59:41 - requesting resource llimbackup001.NBU_CLIENT.MAXJOBS.MLIMDB006
2011-03-24 23:59:41 - requesting resource llimbackup001.NBU_POLICY.MAXJOBS.db_MSSQL_Logs
2011-03-24 23:59:45 - awaiting resource Dedup001 Reason: Maximum I/O stream count has been reached for disk volume, Media Server: llimbackup001,
     Robot Number: NONE, Robot Type: NONE, Media ID: N/A, Drive Name: N/A,
     Volume Pool: NetBackup, Storage Unit: Dedup001, Drive Scan Host: N/A
    
2011-03-25 01:37:42 - granted resource llimbackup001.NBU_CLIENT.MAXJOBS.MLIMDB006
2011-03-25 01:37:42 - granted resource llimbackup001.NBU_POLICY.MAXJOBS.db_MSSQL_Logs
2011-03-25 01:37:42 - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=backup001;Path=PureDiskVolume;StorageServer=llimbackup001;MediaServer=llimbackup001
2011-03-25 01:37:42 - granted resource Dedup001
2011-03-25 01:37:43 - estimated 0 Kbytes needed
2011-03-25 01:37:44 - started process bpbrm (29059)
2011-03-25 01:37:45 - connecting
2011-03-25 01:37:52 - connected; connect time: 00:00:07
2011-03-25 01:38:21 - Critical bptm(pid=29127) image open failed: error 2060012: call should be repeated    
2011-03-25 01:38:38 - end writing
media write error(84)

My backup and storage server is the same linux (RedHat 5) with raid matrix:

  9.9T  3.6T  5.9T  38% /srv/stor0 (abt 10TB with abt 6T free)

I try to investigate something next day but has no idea how to catch problem.

Leszek

Stumpr2
Level 6

This looks similiar to another posting. Please look at this one.

https://www-secure.symantec.com/connect/forums/client-side-deduplication-nbu-701

 

leszekjed
Level 3

I have stiil 84 error problem. Error occure every day after midnight when system starts to do daily backup for all jobs. Normally jobs should be queued until job window is open but in my case error window is open from 00 to 6 but all errors (abt 60 pcs) appereas almost the same time. Almost all belong to the MSSQL backup (Windows). I notice such behaviour since 10 days when, by mistake, backup server was down and, probably, some backups was in run. From the other hand, when I try to repeat the same backup manually everything is going on perfect. My last move was to remove history from Catalog for some job which produce more 84 errors. Maybe it is problem of PureDisk function and garbage collection time? I read that garbage collections running every week. Have anybody experience about simillar situation?

L.J.

 

2011-03-28 01:46:46 - requesting resource Dedup001
2011-03-28 01:46:46 - requesting resource llimbackup001.NBU_CLIENT.MAXJOBS.MLIMDB006
2011-03-28 01:46:46 - requesting resource llimbackup001.NBU_POLICY.MAXJOBS.db_MSSQL_Logs
2011-03-28 01:46:47 - granted resource llimbackup001.NBU_CLIENT.MAXJOBS.MLIMDB006
2011-03-28 01:46:47 - granted resource llimbackup001.NBU_POLICY.MAXJOBS.db_MSSQL_Logs
2011-03-28 01:46:47 - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=backup001;Path=PureDiskVolume;StorageServer=llimbackup001;MediaServer=llimbackup001
2011-03-28 01:46:47 - granted resource Dedup001
2011-03-28 01:46:47 - estimated 0 Kbytes needed
2011-03-28 01:46:48 - started process bpbrm (20365)
2011-03-28 01:46:49 - connecting
2011-03-28 01:46:58 - connected; connect time: 00:00:09
2011-03-28 01:47:03 - Critical bptm(pid=20406) image open failed: error 2060012: call should be repeated    
2011-03-28 01:47:04 - end writing
media write error(84)

rajeshthink
Level 4

I have applied EEB (Rock Solid) . and even after that the backup keep failing with error 84.

for some reason the Services on Puredisk stops, and time and again i have to restart.

/etc/init.d # ./puredisk restart
Checking for CRON daemon                                             running
Stopping CRON daemon: cron                                           done
Checking for PureDisk JAVA GUI                                       running
Stopping PureDisk JAVA GUI: java                                     done
Checking for PureDisk MetabaseEngine                                 running
Stopping PureDisk MetabaseEngine: java .                             done
Checking for PureDisk Workflow Engine                                running
Stopping PureDisk Workflow Engine: pdwfe ..                          done
Checking for PureDisk ContentRouter                                  running
Stopping PureDisk ContentRouter: spoold                              done
Checking for PureDisk Server Agent                                   running
Stopping PureDisk Server Agent: pdagent ....                         done
Checking for PureDisk Controller Monitor                             running
Stopping PureDisk Controller Monitor: pdctrlmon .                    done
Checking for PureDisk Controller                                     running
Stopping PureDisk Controller: pdctrl                                 done
Checking for PureDisk WebServer                                      running
Stopping PureDisk WebServer: apache2 .                               done
Checking for PureDisk Database Server                                running
Stopping PureDisk Database Server: postmaster                        done
Checking for PureDisk Memory Cache Daemon                            running
Stopping PureDisk Memory Cache Daemon: memcached                     done
Checking for VxATd daemon                                            running
Stopping VxATd daemon: vxatd                                         done
Checking for LDAP-server                                             running
Stopping LDAP-server: ldap                                           done
Checking for LDAP-server                                             unused
Starting LDAP-server: ldap                                           done
Checking for VxATd daemon                                            unused
Starting VxATd daemon: vxatd                                         done
Checking for PureDisk Memory Cache Daemon                            unused
Starting PureDisk Memory Cache Daemon: memcached                     done
Checking for PureDisk Database Server                                unused
Starting PureDisk Database Server: postmaster                        done
Checking for PureDisk WebServer                                      unused
Starting PureDisk WebServer: apache2 .                               done
Checking for PureDisk Controller                                     unused
Starting PureDisk Controller: pdctrl                                 done
Checking for PureDisk Controller Monitor                             unused
Starting PureDisk Controller Monitor: pdctrlmon                      done
Checking for PureDisk Server Agent                                   unused
Starting PureDisk Server Agent: pdagent                              done
Checking for PureDisk ContentRouter                                  unused
Starting PureDisk ContentRouter: spoold                              done
Checking for PureDisk Workflow Engine                                unused
Starting PureDisk Workflow Engine: pdwfe                             done
Checking for PureDisk MetabaseEngine                                 unused
Starting PureDisk MetabaseEngine: java .                             done
Checking for PureDisk JAVA GUI                                       unused
Starting PureDisk JAVA GUI: java ......                              done
Checking for CRON daemon                                             unused
Starting CRON daemon: cron                                           done
Restarting PureDisk Services                                         done
 

 

But still i am getting error 84... will symantec come up with a resolution on this..

 

07/24/2011 16:14:00 - started process bpbrm (pid=3034)
07/24/2011 16:14:02 - connecting
07/24/2011 16:14:04 - connected; connect time: 0:00:00
07/24/2011 19:14:33 - Critical bptm (pid=3035) image open failed: error 2060012: call should be repeated
07/24/2011 19:14:36 - end writing
media write error (84)

Malak
Level 4
Partner

Hello,

 

I see no reference to version in this post, and I cant access to "http://www.symantec.com/docs/TECH75230"...
 

Does this problem occur in NBU 7.1?

I'm having a very similar problem... but I have no Ideia how to check PDDO data removal policy.

How can I do this:

"Resolution:

Ensure that the 'PDDO Data Removal' policy is not scheduled too frequently such as daily, hourly or during heavy backup periods like weekend full backup windows."
 
 
Thank you,
Malak