cancel
Showing results for 
Search instead for 
Did you mean: 

Duplication failing with status 85 then 150.

Kevin_O_Connor
Level 4

Hi,

 

I'm manually running duplication jobs within Netbackup, NDMP & multiplex images hence the manual process.

Most of the jobs complete successfully but from time to time the job fails.

When you look at the job details it states the following.

 

12/12/2010 16:34:22 - Error bptm(pid=5164) cannot read image from media id VT0219, drive index 9, err = 170
12/12/2010 16:36:02 - Error bpduplicate(pid=9216) host app141s backup id fop010s _1288479670 read failed, media read error (85).  
12/12/2010 16:36:03 - Error bpduplicate(pid=9216) host app141s backupid fop010s _1288479670 write failed, termination requested by administrator (150).  
12/12/2010 16:36:03 - Error bpduplicate(pid=9216) Duplicate of backupid fop010s _1288479670 failed, termination requested by administrator (150).   
12/12/2010 16:36:03 - Error bpduplicate(pid=9216) Status = no images were successfully processed.      
12/12/2010 16:36:04 - end Duplicate; elapsed time: 23:35:58
no images were successfully processed(191)

So we get a status 85, then 150 and finally 191.

 

Every time this happens it happens at the same time of the day, shortly after 16.30.

I can see nothing wrong in the server event logs for this time and while one might fail three others will continue on the same media server.

How do I hunt down the problem on this and what logs should I be looking at ?

 

Thanks

Kevin

1 ACCEPTED SOLUTION

Accepted Solutions

Andy_Welburn
Level 6

there is the following T/N which indicates an "outside influence" - could this be why it happens at the same time each day? A scheduled windows job perhaps? Maybe there is more in your bptm log that could shed light on the issue?

http://www.symantec.com/business/support/index?page=content&id=TECH44859

Does the failed duplication always fail or do you get it to work at a different time?

View solution in original post

7 REPLIES 7

Andy_Welburn
Level 6

OS's, NB versions etc.

There is the following issue in NB7 (supposedly fixed in NB7.0.1 + fix available):

BUG REPORT: During backups performed with the collection of True Image Restore (TIR) information - including NDMP backups - if the TIR file grows to exceed 2GB in size, future attempts to read the image for restore, duplication or import may result in failure and status code 85 (media read error) reported.
http://www.symantec.com/business/support/index?page=content&id=TECH135813

Altho' this does not explain why it should happen at the same time of day.....

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

More info about your duplication job, please:

NBU version?

Was backup done to NDMP or Media Manager STU?

Where are you duplication from - source and destination STU?

Where do app141s and fop010s fit into the picture?

Do you have bptm logs on your source media server?

Kevin_O_Connor
Level 4

Sorry, I was meant to attach this but got caught up in work.

The master server is running 6.5.5 as is the media server.

The original backup was a FlashBackup of a virtual server using VCB to a VTL.

We're now trying to duplicate the image to ATL.

I'm using the bpduplicate command directing the duplication to use a storage unit on a media server which has direct access to the VTL and the ATL.

app141s is the media server which has direct access to the VTL and ATL.

fop010s is the virtual server and whose image I'm trying to duplicate.

 

I've had a look at the bptm logs for the time it failed but I'm not sure what to be looking for.

It does however have the folowing.

16:34:22.662 [5164.3584] <16> read_data: cannot read image from media id VT0219, drive index 9, err = 170

16:34:22.662 [5164.3584] <2> send_MDS_msg: DEVICE_STATUS 1 177407 app141s VT0219 4007079 VTL104 2001230 READ_ERROR 0 0

Andy_Welburn
Level 6

there is the following T/N which indicates an "outside influence" - could this be why it happens at the same time each day? A scheduled windows job perhaps? Maybe there is more in your bptm log that could shed light on the issue?

http://www.symantec.com/business/support/index?page=content&id=TECH44859

Does the failed duplication always fail or do you get it to work at a different time?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I agree with Andy - see what's in bptm above the error.

Also check Event Viewer System and Application log for clues (assuming that we're dealing with a Windows media server...)

Kevin_O_Connor
Level 4

Other duplication jobs run fine and complete on the same media server while another may have failed.

The problem is this image is 1.5TB in size so even if I start it at 17:00 it isn't complete by 16:30 the following day and then may or may not fail.

I've had to run these jobs after 17:00 unless I know they'll finish before 16:30.

 

Andy it looks like the T/N could be right on the button, I'll have to check the SMS route.

 

Thanks

Kevin

Kevin_O_Connor
Level 4

Hi,

 

I've disabled the SMS agent service on the media server and kicked off the duplication job again but it failed again, this time with the following.

 

11:25:43.893 [5856.2588] <2> read_data: ReadFile returned FALSE, The media in the drive may have changed. (1110);bytes = 262144
11:25:43.893 [5856.2588] <2> is_possible_recoverable_error: not attempting error recovery, errno = 1110
11:25:43.893 [5856.2588] <2> set_job_details: Sending Tfile jobid (689800)
11:25:43.893 [5856.2588] <2> set_job_details: LOG 1292325943 16 bptm 5856 cannot read image from media id VT0235, drive index 8, err = 1110

 

There's still nothing in the logs of the media server.

 

Regards

Kevin