Optimised duplication to a remote site - job quits with unknown error

[dgunner]

Hi,

My set up:

Windows 2008 SP2 x64

Backup Exec 2010 R2 with all patches

I'm looking at the deduplication option and have it working to a local media server for a VMware based server.

I have tried to extend the process to include an optimised deduplication to the remote site (which is where the CASO is based).

The remote server is linked via a 10Mbps Ethernet link over 2Km - no noticable latency. Previously I was running CPS over the link which has worked flawlessly for the last few years.

The job starts fine but after about 10 minutes it fails:

Job ended: 17 September 2010 at 09:57:07
Completed status: Failed
Final error: 0xe00084f4 - An unknown error has occurred.
Final error category: System Errors
 

There is also this bizarre error:

Duplicate- VMVCB::\\server.domain.com\VCGuestVm\server\vm\ProductionServers\servername
Source backup set had completed with following error/exceptions.

V-79-57344-33329 - Library - cleaning media was mounted.
 

What has library cleaning media on a deduplication folder got to do with it? There obviously isn't any! It seems to be assuming that a duplicate job is to tape rather than to disc??

In the logs I get this:

[7120] 09/17/10 09:45:17 [server]             - Status for: 'Duplicate Backup Sets 00006' updated
[2432] 09/17/10 09:56:30 [tpfmt]              - ProcessMoverError default case!  mvrRet = 0x0000001f.  Returning 0xe00084f4.
[2432] 09/17/10 09:56:30 [tpfmt]              - Execute( ADAMM_MOVER_EXECUTE_CONTROL_OST_IMAGE - OST_IMAGE_COMMAND_COPY_TEMP_IMAGE ) failed!  mvrRet = 0000001F

As you can seee it seems fine for about 10 minutes and then this odd error message that I can't work out.

Any ideas?

[Mahesh_Roja]

CAn you see any system or application errors or warning,

Get the Event id of those which occured

[Mahesh_Roja]

Refer this symantec guide

http://seer.entsupport.symantec.com/docs/329254.htm

[dgunner]

Any particilar section?

I don't think there are any special considerations for me because I am just backing up to local Windows storage.

[dgunner]

Here are the event logs:

Log Name:      Application
Source:        Backup Exec
Date:          17/09/2010 09:56:28
Event ID:      33152
Task Category: (1)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.com
Description:
Adamm Mover Error: DeviceIo: ostutil:Copy extent failed because of error 2060013

%2
%3
%4
%5
%6
%7
%8
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Backup Exec" />
    <EventID Qualifiers="8192">33152</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-09-17T08:56:28.000Z" />
    <EventRecordID>120545</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.domain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Adamm Mover Error: DeviceIo: ostutil:Copy extent failed because of error 2060013
</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Backup Exec
Date:          17/09/2010 09:56:30
Event ID:      57600
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.com
Description:
An unknown error occurred on device "Remote site:2".

 For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Backup Exec" />
    <EventID Qualifiers="8192">57600</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-09-17T08:56:30.000Z" />
    <EventRecordID>120546</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.domain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>remote site:2</Data>
    <Binary>F48400E0</Binary>
  </EventData>
</Event>

Log Name:      Application
Source:        Backup Exec
Date:          17/09/2010 09:57:08
Event ID:      34113
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.com
Description:
Backup Exec Alert: Job Failed
(Server: "server") (Job: "Duplicate Backup Sets 00006") Duplicate Backup Sets 00006 -- The job failed with the following error: An unknown error has occurred.
 

 For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Backup Exec" />
    <EventID Qualifiers="8192">34113</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-09-17T08:57:08.000Z" />
    <EventRecordID>120547</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.domain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Backup Exec Alert: Job Failed
(Server: "server") (Job: "Duplicate Backup Sets 00006") Duplicate Backup Sets 00006 -- The job failed with the following error: An unknown error has occurred.
</Data>
  </EventData>
</Event>

[Mifi01]

Hi all I have the same problem.

Is there any solution for this problem. My job stops and only robooting the services can help.

Thanks, Michi

[MatsHolm]

Hi!

Did you find any solution to your problem?

I have the same issue (not cleaning media issue)

Mine ends up the same with Unknown Error and then:
V-79-8192-4881 - The count of Files and Directories processed is not available for this operation. T...
 

And in event viewer application log:
5804] 12/30/10 01:37:48 Adamm Mover Error: DeviceIo: ostutil:Copy extent failed because of error 2060013

We see this on all our duplicate of Linux servers. We first thought it was when changing OST file since it started to fail on jobs bigger then 50 GB but now we see it on all Linux jobs.

We have a Exchange job that is 100% OK with backup and optimized deduplication....

We're creating a case to support today and see what they can do.

/M