cancel
Showing results for 
Search instead for 
Did you mean: 

Can't backup existing folders, but new folders are OK

CCBNZ
Level 4

Hi backup experts,

I have a strange problem here: I am able to use Netbackup server to backup any newly created folders which wahtever contents in them. But I can't back up the existing folders and their sub folders. The NTFS permisson on the new and old folders are the same.  I got a error message "media manager received no data for backup image  (90)".

I have done some research, some ppl said to use the Exclude and Include List from client side, then choose ALL_LOCAL_DRIVES from policy from server side, I tried that but it seems the backup is stuck on "begin writing" state forever, I think it might be the server side doesn't recognize the Exclude and Include List from client side at all, therefore it is doing a full backup on the client instead?

So basically two questions here:

1. What is the reason the existing folders can't be backup while the new folders can? How to resolve it?

2. If the Exclude and Include List from client side is the cause, how to make the server side to recognize them?

 

Thanks in advanced. 

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
As per my previous post, DFSR folders cannot be backed up as regular files/folders. It can only be backed up as part of Shadow Copy Components.

Please see this TN:
https://www.veritas.com/support/en_US/article.100038589


View solution in original post

16 REPLIES 16

CCBNZ
Level 4

Below is the Job log:

05/01/2018 16:48:45 - Info bpbkar32 (pid=5812) archive bit processing:<enabled>
05/01/2018 16:48:45 - Info bptm (pid=7836) start
05/01/2018 16:48:45 - Info bptm (pid=7836) using 65536 data buffer size
05/01/2018 16:48:45 - Info bptm (pid=7836) setting receive network buffer to 263168 bytes
05/01/2018 16:48:45 - Info bptm (pid=7836) using 30 data buffers
05/01/2018 16:48:45 - Info bptm (pid=7836) start backup
05/01/2018 16:48:45 - Info bptm (pid=7836) backup child process is pid 7020.3876
05/01/2018 16:48:45 - Info bptm (pid=7836) Waiting for mount of media id 6330L6 (copy 1) on server SERVER_SIDE.
05/01/2018 16:48:45 - Info bptm (pid=7020) start
05/01/2018 16:48:45 - mounting 6330L6
05/01/2018 16:48:49 - Info bpbkar32 (pid=5812) not using change journal data for <C:\>: not enabled
05/01/2018 16:48:50 - Info bpbkar32 (pid=5812) not using change journal data for <F:\>: not enabled
05/01/2018 16:49:45 - Info bptm (pid=7836) media id 6330L6 mounted on drive index 0, drivepath {3,0,0,0}, drivename HP.ULTRIUM6-SCSI.000, copy 1
05/01/2018 16:49:45 - mounted 6330L6; mount time: 0:01:00
05/01/2018 16:49:53 - positioning 6330L6 to file 7
05/01/2018 16:50:51 - positioned 6330L6; position time: 0:00:58
05/01/2018 16:50:51 - begin writing
05/01/2018 17:34:12 - Info bptm (pid=7836) waited for full buffer 1 times, delayed 166676 times
05/01/2018 17:34:18 - Info bptm (pid=7836) EXITING with status 90 <----------
05/01/2018 17:34:21 - Info bpbkar32 (pid=5812) done. status: 90: media manager received no data for backup image
05/01/2018 17:34:21 - end writing; write time: 0:43:30
05/01/2018 17:34:25 - Info bpbrm (pid=7004) Starting delete snapshot processing
05/01/2018 17:34:31 - Info bpfis (pid=5656) Backup started
05/01/2018 17:34:31 - Warning bpbrm (pid=7004) from client CLIENT_SIDE: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.CLIENT_SIDE_1525150108.1.0
05/01/2018 17:34:31 - Info bpfis (pid=5656) done. status: 4207
05/01/2018 17:34:31 - Info bpfis (pid=5656) done. status: 4207: Could not fetch snapshot metadata or state files
media manager received no data for backup image (90)

When processing fails on the client, look at the client logs, in this case bpbkar and bpfis.

The last error in your snippet is not the root cause. Bpfis gets called in pairs for VSS snapshots, one process to create the snapshot, the other to delete it. The 'bpfis delete' process reads the state file created by the 'bpfis create' process to get oriented. The fact that the second bpfis couldn't find the state file means that the first one didn't get far enough to create it.

On a Windows file system backup, bpbkar32 drives the backup. It calls bpfis when conditions require it. Examples of such conditions are when doing WOFB and there are files in use, or when backing up system state.

Two things to look for in the logs: Why does bpbkar32 not find any files to back up? You may find log entries saying why it skips one file or another. Second, why does 'bpfis create' not create a state file? If it fails to create a snapshot, why?

Thanks a lot for you reply, I took a look under the NetBackup/logs folder, I can't see any folder call bpbkar and bpfis...

The strange thing is I can backup the newly created folder and files, but not old ones. I thought it should be something to do with Windows permission, but the permisson between the new folders and old folders are all the same. Could it because I installed the client software using my domain admin account, but not local admin account?

Regards  

 

 

 

Systems_Team
Moderator
Moderator
   VIP   

Hi CCBNZ,

From your screenshot, it looks like you are looking at logs on your Master.  You need to be looking at logs on the client, as instructed by Lowell.

They will be in the same location, but on your client.  You need bpbkar and bpfis.  If these folders don't exist then you can create them manually and then rerun your backup to create the log files.  I've checked on a default client install, and those two are not automatically created.

It won't matter wether you have installed the client using a domain admin or local admin account, so you can discount that as being your issue.

Hope this helps,

Steve

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
You need to manually create bpbkar and bpfis folders on the client.
Increase logging level to 3 in Host Properties.

Please tell us what exactly you have in Backup Selection in the policy and Exclude and Include list on the client?

Hi Marianne,

You need to manually create bpbkar and bpfis folders on the client.
Increase logging level to 3 in Host Properties. 
---------> WIll give a try, thank you.
 
Please tell us what exactly you have in Backup Selection in the policy and Exclude and Include list on the client?
--------->I didn't touch any settings on the client, so everything is default... What do I ? Can you tell me please?
 

Thanks, will give a try.

CCBNZ
Level 4

Update:

Just found out that other old folders also can be backup, only one of  the old folder can't - which is the largest one.

Regards

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I am confused. Your opening post clearly mentions Include and Exclude list on the client:

"2. If the Exclude and Include List from client side is the cause, how to make the server side to recognize them?"

Please help me to understand what exactly has been configured?

What is in Backup Selection in the Policy?



Hi Marianne,

Sorry about the confusion, I was doing a couple of testing and the last one I default all the setting on the "Netbackup Client Properties" of client side, meanwhile you was asking the question, so I answered "I didn't touch it", my bad.

So what I did on the "Netbackup Client Properties" of client side was: From Exclusion list, I put all the local drives in; From Include List, I put the specific folder under one of the drive letter; From Backup Policy, I put the policy name the same as the one in the Netbackup server side: From Backup Schedule, I put "FULLBACKUP" as the same schedule name in the Netbackup server side. Then I do a Manual Bakcup on the policy from server side, and from the job monitor, the backup is stuck on "begin writing" state.

I have created the bpbkar and bpfis folder, then grab some logs from it for both fail and success backup, please see attached. 

And just for quick update: I am now able to backup directly on the mapped shared drive which bypass the Netbackup client software on the client (have to mapped the local folder to itself by using UNC //127.0.0.1/XXXXX which is dumb...). The only problem is it looks like the shadow copy files with "~$" infront can't be backup? Please see the last attached screenshot.

Although I can backup by using this "bypass" method, I still want to use the proper way which is to use the client software to backup. Can you tell me how to fix it?

Regards

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I will have a look at logs when time permits.

Using Host Properties updates the registry on the client.

Why configure such a complex backup system?

Why not simply specify ALL_LOCAL_DRIVES or the drive letter /folder that you want to backup in Backup Selection in the Policy and remove everything in Exclude and Include List? 

Most customers stick to the defaults in Exclude List and only add database files that are backed up via an agent (e.g. SQL *.mdf and *.ldf).
I have personally never had a use for Include list (in 19 years with NBU).

Hi Marianne,

I have tried what you said many times but no luck, that is why I was thinking maybe the issue is with Exlusion and Inclusion list...

If you could, please have a look the logs... I have breifly went through it, it seems Netbackup didn't pick up the files at all.

Thank you

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

We still have no idea what exactly you have in Backup Selection or in Exclude and/or Include List.

The Client's logging level is at 0. So, very little helpful info:
10:40:17.747 [1472.6724] <4> ov_log::OVInit: GENERAL Log Level (Effective): 0

With logging level at about 3, we can normally see details of Include and/or Exclude list in bpbkar log. 
In these level 0 logs, there is no reference. I only see this line that gives no helpful info: 
10:40:30.414 [1472.6724] <4> tar_backup_tfi::UpdateExcludeListWithVHD: INF - UpdateExludeListWithVHD begin.

The OLD folder log shows successful backups of F:\CCBNZ\General Data\test1\ with 0 bytes!

10:41:01.162 [1472.6724] <2> tar_base::backup_finish: TAR - backup: file data: 0 bytes
10:41:01.162 [1472.6724] <2> tar_base::backup_finish: TAR - backup: image data: 0 bytes
10:41:01.162 [1472.6724] <2> tar_base::backup_finish: TAR - backup: elapsed time: 44 secs 0 bps
10:41:01.162 [1472.6724] <4> tar_backup::backup_done_state: INF - number of file directives not found: 0
10:41:01.162 [1472.6724] <4> tar_backup::backup_done_state: INF - number of file directives found: 1
10:41:01.162 [1472.6724] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 0: the requested operation was successfully completed

Without additional logging level, there is no indication of why the contents of this folder is not read.

Is F:\CCBNZ by any chance part of DFS replication?

If so, are you aware that DFSR folder are backed up as part of Shadow Copy Components and cannot be backed up as 'regular' files/folders? 

Hi Marianne,

Sorry about the late reply. I have attached the client server Exclude list as a screenshot. The include list contains nothing which is default, and all the files under the Backup tab are all "any" which are also default.

And yes, the F:\CCBNZ folder is a part of DFS replication.

I have attached the bpbkar and bpfis logs on the failed job - it should be level 3 this time.

Regards

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
As per my previous post, DFSR folders cannot be backed up as regular files/folders. It can only be backed up as part of Shadow Copy Components.

Please see this TN:
https://www.veritas.com/support/en_US/article.100038589


Thank you very much for answering, Marianne.