Video Screencast Help

Error while creating netbackup datadomain storage unit by cifs share

Created: 29 Aug 2013 • Updated: 18 Sep 2013 | 10 comments
This issue has been solved. See solution.

I have created new storage unit to take vmware backups.

But unable to see  the storage unit properties.

Backups are failing by 2074 Disk volume down error.

Operating Systems:

Comments 10 CommentsJump to latest comment

Nate.D's picture

Try running a

bperror -disk

And let us know what it returns for the storage unit you just created.  That may give some info on whats wrong with the SU.

If I was helpful in solving your issue please mark my post with a thumbs up or a solution!  Have a great day :)

Will Restore's picture

New setup?  Did it ever work?

The OpenStorage plugin developed by DataDomain requires access to UDP port 111 and TCP 2049 (default port) on target DataDomain array. If there is a firewall separating the media server and target storage server, these ports need to be opened. Else optimized duplications to the target storage server will fail with status 83.

Article URL

Will Restore -- where there is a Will there is a way

Nicolai's picture

See page 251 "Data Access for CIFS"

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

bobby62's picture

Its new setup to test vmware backup.

I created new storage unit for that and created new CIFS share path for that in datadomain and it shows path exists in datadomain box.But unable to see the properties of that disk which created in netbackup.

Getting error which was shown in Screenshot.

What need to be done.

Kevin Good's picture

Is there a reason you're setting this up to use a CIFS share, and not straight to OST?

Backing up the VM's in the manner you are attempting will mean that 100% of the VMDK images traverse the network from your Media Server to your Data Domain.  If you configure OST, and enable ddboost distributed segment processing will enable the media server to process the deduplication work, and improve the network utilization.

Backups are IT-101 (Do Backups) Doing Backups well is an art form. Nobody cares about getting their data backed up... They only care that you can restore it for them!

Will Restore's picture

couple older technotes

STATUS CODE 83: When attempting a backup which goes to a NAS server

STATUS CODE 83: A Status 83 "media open error" occurs on a recently configured disk storage unit

Will Restore -- where there is a Will there is a way

bobby62's picture

Now i am able to see the properties of the storage unit which i have created.

But when i run the backup by keeping the storage unit backups are failing and showing the error.

84 media write error.

09/04/2013 02:26:59 - Info bptm (pid=3580) start backup
09/04/2013 02:27:00 - Critical bptm (pid=3580) image open failed: error 2060017: system call failed
09/04/2013 02:27:00 - Info bptm (pid=3580) EXITING with status 84 <----------
09/04/2013 02:27:38 - Info nbjm (pid=19095) starting backup job (jobid=1379058) for client, policy VMWARE-ontario-vmbackup1-DD, schedule Quarterly
09/04/2013 02:27:38 - estimated 0 kbytes needed
09/04/2013 02:27:38 - Info nbjm (pid=19095) started backup job for client, policy VMWARE-ontario-vmbackup1-DD, schedule Quarterly on storage unit vmbackup1-dd565
09/04/2013 02:27:39 - started process bpbrm (pid=4348)
09/04/2013 02:27:39 - connecting
09/04/2013 02:27:39 - connected; connect time: 0:00:00
09/04/2013 02:30:04 - end writing
media write error  (84)

Marianne's picture

Have you had a look at the 2 TNs in Bill's post?

Important to change NBU services to domain logon account with write permissions on the CIFS share.

Extract from NBU Admin Guide I:

Configuring credentials for CIFS and disk storage units
ForCommonInternet File System (CIFS) storage with AdvancedDisk and BasicDisk
storage units, two NetBackup services on Windows computers require matching
The following NetBackup services on Windows media servers to which the CIFS
storage is attached must use the same credentials:
NetBackup Client Service
The NetBackup Client Service is either bpcd.exe or bpinetd.exe, depending
on NetBackup release level. Regardless of the binary file name, the service
requires the credentials.
NetBackup Remote Manager and Monitor Service
The NetBackup Remote Manager and Monitor Service binary file name is
The credentials must be valid Windows credentials that allow read and write
access to the storage. Configure the credentials on the media server or media
servers that have a file system mount on the CIFS storage.
If credentials are not configured, NetBackup marks all CIFS AdvancedDisk and
BasicDisk storage units that use the UNC naming convention as DOWN.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

bobby62's picture

Thanks for the support now i can see the properties of the path for the storage unit.

I configured the vmware backups with this new storage unit and backup is successfull.

Now i need to restore the vmware server backups through netbackup.

Plz suggest how we can restore the vmware server backup.

Marianne's picture

I believe the problem in your opening post is resolved, right? 

Please select a post that has answered your query and 'Mark as solution', else 'Request split solution' if more than one post has helped you.

VMware restore is a separate issue. If you have read through the NBU for VMware Admin Guide and still have questions, please start a new discussion.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links