Highlighted

Is there a way to tell Netbackup to ignore any empty drives

Hi - Is there a way to tell Netbackup to ignore any empty drives or directory during backup?

We do not want to add these drives to exclude list as they will be use in future. However, they are currently empty & netbackup is reporting "(90) media manager received no data for backup image" during backup which is causing tickets to be generated.

Please advise.

Thank you

Tags (2)
1 Solution

Accepted Solutions
Accepted Solution!

Re: Is there a way to tell Netbackup to ignore any empty drives

I had something similar where sometimes files would mount and sometimes not - I ended up putting a small text file named - DRIVE\something.should.mount.here.txt

Then I check the backup - 32K is not mounted, 2TB is mounted. LOL

You are kind of bypassing the error checking NB uses, in my case, I did not want to alert on error 71 file not found.

 

NetBackup 8.1.2 on Solaris 11, writing to DataDomain 9800
duplicating via SLP to LTO5 in SL8500 via ACSLS

View solution in original post

Tags (2)
4 Replies

Re: Is there a way to tell Netbackup to ignore any empty drives

@Dollypee

Can you give us an example of Backup Selection in a policy where you have this issue?
Is this drive letter a regular NTFS filesystem? Not under DFS replication control?
Can you confirm that nobody has added this drive letter to Exclude List for this client? 

My experience has been that the path for drive letter will be backed up - something like 32KB backup size.

For troubleshooting, please ensure that bpbkar log folder exists on the client. Level 1 logging should be sufficient at this stage. 

Re: Is there a way to tell Netbackup to ignore any empty drives

@Marianne 

=>backup selection are ALL_LOCAL_DRIVES. These drives are SQL database shared/cluster resource between multiple physical nodes. I checked the active node, and found the drives are successfully backing up. These errors are occurring for full backup but exiting with status 1 for differential backup on the passive nodes. Activity monitors details shows " device are not ready"

Could that be the reason it's exiting with status 90?

WRN - can't open directory: E: (WIN32 21: The device is not ready. )

 

Re: Is there a way to tell Netbackup to ignore any empty drives

I doubt that this is causing status 90 - that is a warning, not an error.

We really need more info - as a start NBU version and OS on the cluster node. You have selected NBU 7.7 and Windows 8. You will agree that MS Cluster is for some server version, right?

If the drive letters are not at all present on the inactive node, then they should not be enumerated for ALL_LOCAL_DRIVES.
The only time where we have see issues with inactive cluster nodes, was with Shadow Copy Component backups in older NBU versions - details here : https://www.veritas.com/support/en_US/article.000081391

Oh - I also found the following for older NBU versions:

https://vox.veritas.com/t5/NetBackup/error-code-90-on-windows-client-it-s-a-cluster-server/td-p/4346...

https://support.symantec.com/en_US/article.TECH173606.html
The Solution in above (old) Symantec should still be valid. 

Create one policy, with below configuration
Client tab: Physical name of the cluster node(s)
Backup Selection list: (non shared disks)
ex:
C:\
D:\
Shadow Copy Components:\

You need a separate policy to backup SQL data using the cluster virtual hostname. 
Preferably MS-SQL policy type. 

Accepted Solution!

Re: Is there a way to tell Netbackup to ignore any empty drives

I had something similar where sometimes files would mount and sometimes not - I ended up putting a small text file named - DRIVE\something.should.mount.here.txt

Then I check the backup - 32K is not mounted, 2TB is mounted. LOL

You are kind of bypassing the error checking NB uses, in my case, I did not want to alert on error 71 file not found.

 

NetBackup 8.1.2 on Solaris 11, writing to DataDomain 9800
duplicating via SLP to LTO5 in SL8500 via ACSLS

View solution in original post

Tags (2)