media manager received no data for backup image (Status code 90) DFSR Backup

[John_Snodgrass]

I've ready several tech notes and forum posts, but most of them talked about a backup selection being filtered by VSS and a backup of a direct path (E:\MyFiles for example) is protected by the Shadow Copy. becuase they are DFSR.  I'm getting the error when I try and backup the Shadow Copy path.  I've reqyested the bpbkap log from the client, I can post that when I have it.  In the mean time, here is what I have to start with.

Master RHEL 6 NBU 7.5.0.7

Client Windows 2008, NBU 7.5.0.6

Policy Backup Selction:

Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders                   (failes the full backup only)
D:\                                                                                                                                                                  (works with no issues)

File List:

SET SNAP_ID=ammfs02_1450054801
Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders

Details:

12/13/2015 20:00:33 - Info nbjm (pid=4303) starting backup job (jobid=9031) for client ammfs02, policy Amalgamated-AIR-TKLM_ALISLM01-IUS-02-001-NBMA_MAN_2K8_VFIL_0_1, schedule Monthly_Full
12/13/2015 20:00:33 - Info bpbrm (pid=28633) ammfs02 is the host to backup data from
12/13/2015 20:00:33 - Info bpbrm (pid=28633) reading file list from client
12/13/2015 20:00:33 - estimated 0 kbytes needed
12/13/2015 20:00:33 - Info nbjm (pid=4303) started backup (backupid=ammfs02_1450054833) job for client ammfs02, policy Amalgamated-AIR-TKLM_ALISLM01-IUS-02-001-NBMA_MAN_2K8_VFIL_0_1, schedule Monthly_Full on storage unit alislm01-ius-02-001-nbma_MSDP01
12/13/2015 20:00:33 - started process bpbrm (pid=28633)
12/13/2015 20:00:33 - connecting
12/13/2015 20:00:34 - Info bpbrm (pid=28633) starting bpbkar on client
12/13/2015 20:00:34 - connected; connect time: 0:00:00
12/13/2015 20:00:38 - Info bpbkar (pid=7804) Backup started
12/13/2015 20:00:38 - Info bpbrm (pid=28633) bptm pid: 28652
12/13/2015 20:00:38 - Info bptm (pid=28652) start
12/13/2015 20:00:38 - Info bptm (pid=28652) using 262144 data buffer size
12/13/2015 20:00:38 - Info bptm (pid=28652) setting receive network buffer to 524288 bytes
12/13/2015 20:00:38 - Info bptm (pid=28652) using 16 data buffers
12/13/2015 20:00:39 - Info bptm (pid=28652) start backup
12/13/2015 20:00:44 - Info bptm (pid=28652) backup child process is pid 28716
12/13/2015 20:00:44 - begin writing
12/13/2015 20:01:09 - Info bptm (pid=28652) waited for full buffer 1 times, delayed 1654 times
12/13/2015 20:01:09 - Info bptm (pid=28652) EXITING with status 90 <----------
12/13/2015 20:01:09 - Info alislm01-ius-02-001-nbma (pid=28652) StorageServer=PureDisk:alislm01-ius-02-001-nbma; Report=PDDO Stats for (alislm01-ius-02-001-nbma): scanned: 3 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%
12/13/2015 20:01:10 - Info bpbkar (pid=7804) done. status: 90: media manager received no data for backup image
12/13/2015 20:01:10 - end writing; write time: 0:00:26
media manager received no data for backup image  (90)

The Incremental backups don't fail, I suspect thats becuse there is nothing to backup and it does not care.  If I just do the default Shadow Copy Components, that works fine as well.  I've asked that the customer confirm that path is correct and valid and they indicate that it is.

[Marianne]

Something else to confirm on the client is to ensure the NBU services are running under a domain account with sufficient access to SCC. Something else you try while waiting for bpbkar log is to change backup selection to Shadow Copy Components:\ only.

[John_Snodgrass]

Hi Marianne,

Alway nice to hear from you.  I did the Shadow Copy Componets:\ as a test before and it worked.if I recall, but it did not seem to pick up the DFSR data.  Is it supposed to?  I was under the impression that you had to specifically select that data.  I am wrong about that?  I will also have them check the account as that seems to be a very likely as well.

[Marianne · Accepted solution]

SCC should pick up everything underneath it. Unless there is permission isue or Exclude List. Level 3 bpbkar log should tell what the problem is.

[John_Snodgrass]

We just used the SCC and left it at that.  I could never get an clear consise answer back from the customer that the DFSR path was really there or not.