cancel
Showing results for 
Search instead for 
Did you mean: 

Error restoring data from Quantum Disk

HEMANPR
Level 6

Hello People:

I'm doing backups from my master server to a Quantum DXI Disk. Backup's jobs running perfect.

Today I try to restore a file from one of that backup, But I get This Error:

10/7/2010 2:49:12 PM - begin Restore
10/7/2010 2:49:14 PM - restoring image SERVER_1286463088
10/7/2010 2:49:14 PM - requesting resource @aaaau
10/7/2010 2:49:15 PM - granted resource MediaID=@aaaau;DiskVolume=Open_Systems;DiskPool=QUANTUM_Disk;Path=Open_Systems;StorageServer=Open-St...
10/7/2010 2:49:32 PM - connecting
10/7/2010 2:49:35 PM - connected; connect time: 00:00:03
10/7/2010 2:49:35 PM - started process bptm (8100)
10/7/2010 2:49:38 PM - started process bptm (6544)
10/7/2010 2:50:01 PM - Critical bptm(pid=8100) sts_get_server_prop_byname failed: error 2060023 server is shut down    
10/7/2010 2:50:02 PM - Critical bptm(pid=8100) failure to open sts for storage server Open-Storage_10.0.0.1: plug-in reports error 2060023 server is shut down
10/7/2010 2:50:13 PM - Error bptm(pid=6544) The following files/folders were not restored:      
10/7/2010 2:50:13 PM - Error bptm(pid=6544) UTF - /C/RESTORE/File.html         
10/7/2010 2:50:15 PM - restored image SERVER_1286463088 - (media open error(83)); restore time 00:01:01
10/7/2010 2:50:18 PM - Warning bprd(pid=7880) Restore must be resumed prior to first image expiration on 11/7/2010 10:51:28 AM
10/7/2010 2:50:18 PM - end Restore; elapsed time: 00:01:06
the restore failed to recover the requested files(5)
10/7/2010 2:50:20 PM - Error bpbrm(pid=6564) client restore EXIT STATUS 83: media open error

Any HELP?

1 ACCEPTED SOLUTION

Accepted Solutions

HEMANPR
Level 6

People The real issue was a problems with the NIC on 1 of my media servers.

Backups are running perfects because it's still going trowh my Master Server but on restore, the job are tryng to use another media server. This media server have problems with the NIC. Change the NIC and try the jobs again.... WORKING PERFECT

Thanks very much for try to help me and Thanks to Sudhakar Bajpai - Technical Support Engineer NetBackup Team

View solution in original post

10 REPLIES 10

HEMANPR
Level 6

Before this error, The Job appear like INCOMPLETE and appear a error 5 on status, O check this but dont fix the error.

The NetBackup client service "Log on as" account is required to be a domain account with permissions to write to the UNC path.

On restore target, set the NetBackup client service "Log on as" account to match the current domain account logged into the NetBackup client.
 

HEMANPR
Level 6

Any help on this?

Thanks

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Do you only have a single master/media server in your environment?

Seems NBU thinks that the Storage Unit server is shutdown:

Critical bptm(pid=8100) sts_get_server_prop_byname failed: error 2060023 server is shut down.

How exactly is STU connected? Please post output of:

bpstulist -L

HEMANPR
Level 6

Hello Marianne

Here the bpstulist -L command result. Please look the Label:                NEW_MEDIA_SERVER-hcart its different on the Host Connection:      _STU_NO_DEV_HOST_

 

HERE START

Label:                MASTER_SERVER-hcart-ro
Storage Unit Type:    Media Manager
Host Connection:      MASTER_SERVER
Number of Drives:     10
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 0
Max Fragment Size:    10240
Max MPX/drive:        4

Label:                MASTER_SERVER-hcart-ro
Storage Unit Type:    NDMP
Host Connection:      MASTER_SERVER
Number of Drives:     2
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 1
Max Fragment Size:    1048576
Max MPX/drive:        1
NDMP attach host:     QUANTUM_DXI_DISK
Label:                MASTER_SERVER-hcart3-r
Storage Unit Type:    Media Manager
Host Connection:      MASTER_SERVER
Number of Drives:     1
On Demand Only:       no
Density:              hcart3 (20)
Robot Type/Number:    TLD (8) / 4
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MASTER_SERVER-hcart-ro
Storage Unit Type:    Media Manager
Host Connection:      MASTER_SERVER
Number of Drives:     2
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 2
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MASTER_SERVER-hcart-ro
Storage Unit Type:    Media Manager
Host Connection:      MASTER_SERVER
Number of Drives:     2
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 1
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MEDIA_SERVER1-hcart-robot
Storage Unit Type:    Media Manager
Host Connection:      MEDIA_SERVER1
Number of Drives:     6
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 0
Max Fragment Size:    10240
Max MPX/drive:        1
Label:                MEDIA_SERVER2-hcart-robot
Storage Unit Type:    Media Manager
Host Connection:      MEDIA_SERVER2
Number of Drives:     6
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 0
Max Fragment Size:    10240
Max MPX/drive:        1
Label:                MEDIA_SERVER3-hcart
Storage Unit Type:    Media Manager
Host Connection:      MEDIA_SERVER3
Number of Drives:     6
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 0
Max Fragment Size:    10240
Max MPX/drive:        1
Label:                MEDIA_SERVER1-hcart-robot
Storage Unit Type:    Media Manager
Host Connection:      MEDIA_SERVER1
Number of Drives:     2
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 1
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MASTER_SERVER-hcart-ro
Storage Unit Type:    Media Manager
Host Connection:      MASTER_SERVER
Number of Drives:     8
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 0
Max Fragment Size:    10240
Max MPX/drive:        4
Label:                MASTER_SERVER-hcart
Storage Unit Type:    Media Manager
Host Connection:      MASTER_SERVER
Number of Drives:     1
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 0
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MASTER_SERVER-hcart3-r
Storage Unit Type:    Media Manager
Host Connection:      MASTER_SERVER
Number of Drives:     1
On Demand Only:       no
Density:              hcart3 (20)
Robot Type/Number:    TLD (8) / 3
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MEDIA_SERVER1-hcart
Storage Unit Type:    Media Manager
Host Connection:      MEDIA_SERVER1
Number of Drives:     1
On Demand Only:       no
Density:              hcart (6)
Robot Type:           (not robotic)
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MEDIA_SERVER2-hcart
Storage Unit Type:    Media Manager
Host Connection:      MEDIA_SERVER2
Number of Drives:     1
On Demand Only:       no
Density:              hcart (6)
Robot Type:           (not robotic)
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MEDIA_SERVER3-hcart
Storage Unit Type:    Media Manager
Host Connection:      MEDIA_SERVER3
Number of Drives:     1
On Demand Only:       no
Density:              hcart (6)
Robot Type:           (not robotic)
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MASTER_SERVER-hcart2-r
Storage Unit Type:    Media Manager
Host Connection:      MASTER_SERVER
Number of Drives:     1
On Demand Only:       no
Density:              hcart2 (14)
Robot Type/Number:    TLD (8) / 0
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MEDIA_SERVER2-hcart-robot
Storage Unit Type:    Media Manager
Host Connection:      MEDIA_SERVER2
Number of Drives:     1
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 1
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MEDIA_SERVER1-hcart2-robo
Storage Unit Type:    Media Manager
Host Connection:      MEDIA_SERVER1
Number of Drives:     1
On Demand Only:       no
Density:              hcart2 (14)
Robot Type/Number:    TLD (8) / 0
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MEDIA_SERVER2-hcart2-robo
Storage Unit Type:    Media Manager
Host Connection:      MEDIA_SERVER2
Number of Drives:     1
On Demand Only:       no
Density:              hcart2 (14)
Robot Type/Number:    TLD (8) / 0
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MEDIA_SERVER3-hcart
Storage Unit Type:    Media Manager
Host Connection:      MEDIA_SERVER3
Number of Drives:     1
On Demand Only:       no
Density:              hcart2 (14)
Robot Type/Number:    TLD (8) / 0
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MEDIA_SERVER3-hcart
Storage Unit Type:    Media Manager
Host Connection:      MEDIA_SERVER3
Number of Drives:     2
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 1
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                NEW_MEDIA_SERVER-hcart
Storage Unit Type:    Media Manager
Host Connection:      _STU_NO_DEV_HOST_
Number of Drives:     1
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 0
Max Fragment Size:    1048576
Max MPX/drive:        1
Label:                MASTER_SERVER-QUANTUMDXI
Storage Unit Type:    Disk
Media Subtype:        DiskPool (6)
Host Connection:      MASTER_SERVER
Concurrent Jobs:      100
On Demand Only:       yes
Robot Type:           (not robotic)
Max Fragment Size:    2000
Max MPX:              1
Block Sharing:        no
File System Export:   no
Ok On Root:           no
Disk Pool:            QUANTUM_DXI_DISK_Disk
Label:                MEDIA_SERVER1-QUANTUMDXI
Storage Unit Type:    Disk
Media Subtype:        DiskPool (6)
Host Connection:      MEDIA_SERVER1
Concurrent Jobs:      100
On Demand Only:       yes
Robot Type:           (not robotic)
Max Fragment Size:    2000
Max MPX:              1
Block Sharing:        no
File System Export:   no
Ok On Root:           no
Disk Pool:            QUANTUM_DXI_DISK_Disk
Label:                MEDIA_SERVER2-QUANTUMDXI
Storage Unit Type:    Disk
Media Subtype:        DiskPool (6)
Host Connection:      MEDIA_SERVER2
Concurrent Jobs:      100
On Demand Only:       yes
Robot Type:           (not robotic)
Max Fragment Size:    2000
Max MPX:              1
Block Sharing:        no
File System Export:   no
Ok On Root:           no
Disk Pool:            QUANTUM_DXI_DISK_Disk
Label:                MEDIA_SERVER3-QUANTUMDXI
Storage Unit Type:    Disk
Media Subtype:        DiskPool (6)
Host Connection:      MEDIA_SERVER3
Concurrent Jobs:      100
On Demand Only:       yes
Robot Type:           (not robotic)
Max Fragment Size:    2000
Max MPX:              1
Block Sharing:        no
File System Export:   no
Ok On Root:           no
Disk Pool:            QUANTUM_DXI_DISK_Disk

HEMANPR
Level 6

By the way, This NEW_MEDIA_SERVER was a deleted Media Server. I don't know Why it's still there.

Maibe this is the issue

Label:                NEW_MEDIA_SERVER-hcart
Storage Unit Type:    Media Manager
Host Connection:      _STU_NO_DEV_HOST_
Number of Drives:     1
On Demand Only:       no
Density:              hcart (6)
Robot Type/Number:    TLD (8) / 0
Max Fragment Size:    1048576
Max MPX/drive:        1 

HEMANPR
Level 6

Hello Any Idea? I have all the backups but problems for restore... NOT A GOOD DEAL RIGHT... ;)

Mahesh_Roja
Level 6

 

Unable to restore backup written to a Disk Storage Unit using a different Media server (media host override).

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

StefanosM
Level 6
Partner    VIP    Accredited Certified

have you restart the master/media server?

If not try it

HEMANPR
Level 6

I try the documentation provide by Maheshroja, I set the Restore server from all my media servers to the master server. Dont Work...

I dont retstart the server yet, Duplicates Jobs are running But I gonna do what the documentation said:

Workaround:
Restore data using media server that initiated the backup job.  If that is not possible please contact Symantec technical support and refer to Etrack 1162799.

Really I try lot of resources and Continue the error.
I will be post the Sym. Support solution

HEMANPR
Level 6

People The real issue was a problems with the NIC on 1 of my media servers.

Backups are running perfects because it's still going trowh my Master Server but on restore, the job are tryng to use another media server. This media server have problems with the NIC. Change the NIC and try the jobs again.... WORKING PERFECT

Thanks very much for try to help me and Thanks to Sudhakar Bajpai - Technical Support Engineer NetBackup Team