cancel
Showing results for 
Search instead for 
Did you mean: 

media write error 84

garima721
Level 3

Whenever I try to take backup using Netbackup 7.5 on my fuse filesystem, backup command exits giving error

EXIT STATUS 84: media write error

Do we need to do any addional setting for the same?

1 ACCEPTED SOLUTION

Accepted Solutions

Nicolai
Moderator
Moderator
Partner    VIP   

Take a look at http://www.symantec.com/docs/TECH76648

Page 61 - File System Compatibility

Unfortunately the FUSE file system is not supported.

That does not mean you can bring it to work - but you should consider if you want to be in a unsupported state. Sorry for the bad new - but I am only the messenger :)

 

View solution in original post

10 REPLIES 10

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

you would need to provide the more details

before that please follow the guide in below like and let us know the results...

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

Nicolai
Moderator
Moderator
Partner    VIP   

Take a look at http://www.symantec.com/docs/TECH76648

Page 61 - File System Compatibility

Unfortunately the FUSE file system is not supported.

That does not mean you can bring it to work - but you should consider if you want to be in a unsupported state. Sorry for the bad new - but I am only the messenger :)

 

garima721
Level 3

Isn't there any work-around to do the same?

I mean when we can take backup on NFS mounted fuse filesystem, then why is it not possible to take backup on simple fuse filesystem?

 

Marianne
Level 6
Partner    VIP    Accredited Certified

As per Nagalla's post - you need to find out what exactly is causing the status 84.

Look at information in Details tab in Activity Monitor, bptm log on the media server as well as /var/log/messages file on Linux media server.

Extract from Status 84 doc: 

As an application, NetBackup has no direct access to a device, instead relying on the operating system (OS) to handle any communication with the device. This means that during a write operation NetBackup asks the OS to write to the device and report back the success or failure of that operation. If there is a failure, NetBackup will merely report that a failure occurred, and any troubleshooting should start at the OS level. If the OS is unable to perform the write, there are three likely causes; OS configuration, a problem on the SCSI path, or a problem with the device.

 

Nicolai
Moderator
Moderator
Partner    VIP   

FUSE is not a real file system but  a rely on phycial EXT3/NFS file systems. I believe my earlyer post may be wrong.

http://en.wikipedia.org/wiki/Filesystem_in_Userspace

devesh_gupta
Level 3

Hello Marianne,

 

Below is the snippet from bptm logs:

------------

12:59:28.865 [3394] <2> bp_sts_open_image: STH set to STS_SA_IMAGE
12:59:28.865 [3394] <2> bp_sts_open_image: STSBasicDisk:hydra117
/home/gmishra/OST_19_7/hydraOST/plugin/unittest/pluginDllTest/simple_fuse/tmp2
hydra117_1375847967_C1_HDR 1 1 1 sth 0 2 8 LSU 0x7 0x1 0x2 saveas 0x4,
stream_type 0x4 fscp 0
12:59:28.865 [3394] <2> 429:bptm:3394:hydra117: entering
stspi_create_image(4)
12:59:29.003 [3394] <2> bp_sts_close_image: 0x1badff0 0
<hydra117_1375847967_C1_HDR 2 1> 1 4 1 1 1 0 complete flag
(64)(M_BACKUP_COMPLETE ), close type (1)(STS_CLOSEF_IH_COMPLETE ) 11
12:59:29.055 [3394] <16> 429:bptm:3394:hydra117: STSImageManager: Caught
exception in STSIMGImageInfo::SetImageSize, FILE=STSIMGImageInfo.cpp,
FUNCTION=, LINE=699, ERROR=STS_ESYS
12:59:29.089 [3394] <16> 429:bptm:3394:hydra117: STSImageManager: Caught
exception in STSIMGImageManager::CloseImage, FILE=STSIMGImage.cpp,
FUNCTION=, LINE=687, ERROR=STS_EPERM
12:59:29.089 [3394] <2> set_job_details: Tfile (429): LOG 1375847969 32
bptm 3394 sts_close_handle failed: 2060037 access not allowed

12:59:29.089 [3394] <2> send_job_file: job ID 429, ftype = 3 msg len =
80, msg = LOG 1375847969 32 bptm 3394 sts_close_handle failed: 2060037
access not allowed

12:59:29.090 [3394] <32> bp_sts_close_image: sts_close_handle failed:
2060037
12:59:29.090 [3394] <2> set_job_details: Tfile (429): LOG 1375847969 32
bptm 3394 image close failed: error 2060037: access not allowed

12:59:29.090 [3394] <2> send_job_file: job ID 429, ftype = 3 msg len =
82, msg = LOG 1375847969 32 bptm 3394 image close failed: error 2060037:
access not allowed

------------

Verbose level is set to 5.

Kindly let us know if any other logs are required.

 

Marianne
Level 6
Partner    VIP    Accredited Certified

Error in bptm log:

sts_close_handle failed: 2060037 access not allowed

Please tell us more about your Storage Unit - is this the 'fuse filesystem' that you mentioned in your opening post?

Seems it is not mounted with correct write permissions.

devesh_gupta
Level 3

>Please tell us more about your Storage Unit - is this the 'fuse filesystem' that you mentioned in your opening post?

Yes, it is a fuse file system,  as stated in the opening post.

I will check regarding the permissions but as per us the permission doesnt seems to be the issue because netbackup is successfully able to open and write files in the fuse filesystem.

ex: *C1_HDR*.img and C1_HDR*.info were created during the backup operation.

 

Marianne
Level 6
Partner    VIP    Accredited Certified

I have had a look at the link that Nicolai provided. 

I am sure you will have better luck with a local filesystem or else with a 'standard' NFS filesystem. 
I cannot see that this type of filesystem will be supported as disk STU.

See requirements for NFS STU's (different error, but requirements remain):

http://www.symantec.com/docs/TECH54767

garima721
Level 3

We were able to solve the problem.

It seems there was some problem in my filesystem.

Thank you all for your help.