Highlighted
8 Krypton

Restore doesn't work because backups just ignore the files...?

Of course your restore won't work if backup is not.  However, in my case backup does not fail - it just won't backup specific files.  Here is the situation: we use Honeywell Uniformance PHDServer which has its own structure and one of the most important folders is called - Archive.  So, imagine structure like this:

E:\Uniformance\PHDServer\Archive and some idx and dat files inside.  Now, one usually does scheduled backup and get's all green and forgets about it.  So did I.  Then restore request came today since disk failed and everything was restored except content of this Archive folder. 

I checked mminfo and size of E drive was rather small so I was quite sure I never backed up this.  Then I checked another host with same setup and found that data is there, but not backed up under E save set.  So, I thought, it must be some VSS SYSTEM saveset and did nsrinfo search - but it is not there at all. Great, so we have everything except perhaps most important data on the box. Let's do manual backup... guess what:

E:\Uniformance\PHDServer\Archive>save -s SERVER -b POOL SCAN00001.dat

save: E:\Uniformance\PHDServer\Archive\SCAN00001.dat  0 KB 00:00:32      0 files

7167:save: save completion time: 15-2-2013 16:37:09

Above file is 4GB - but bloody thing will always finish soon with 0KB saved.  Why!?  So, I did -D9 - but I do not see anything inside to ring the bell.  There is no directive assigned to this host, client side or server side, nothing.  It's funny, when you go to GUI and you select file it starts to run, asks for pool and then says - 0KB saved. Before you ask, this is local disk data - no DFS or any other mumbo jumbo.

I did however another test which is also sort of interesting:

  • created E:\H folder and copied SCAN00001.dat file there
  • backup process against E:\H\SCAN00001.dat works fine
  • created folder Archive and moved SCAN00001.dat to that folder
  • backup process against E:\H\Archive\SCAN00001.dat works fine
  • created folder PHDServer and moved Archive to that folder
  • backup process against E:\H\PHDServer\Archive\SCAN00001.dat works fine
  • created folder Unifomance and moved PHDServer to that folder
  • backup process against E:\H\Uniformance\PHDServer\Archive\SCAN00001.dat works fine

So, from here I see 3 possible outcomes:

  • there is some wierd registry setting which instructs these files not to be backed up ever - not sure if such thing exists in first place and I certainly do not see it from debug CLI log
  • there is exotic and exclusive lock on files breaking VSS/save the way it does - not sure only why Explorer is able to copy the file without any issues
  • there is a bug with software - namely NetWorker

It might be something else, but this little thing took my afternoon and most likely will take away rest of the weekend.  Did anyone had experience with events like this before or has some starting point to check against?  The affected system is win2k8 R2 running 7.6.3.6 client.

Tags (4)
9 Replies
8 Krypton

Re: Restore doesn't work because backups just ignores files...?

The registry setting you may want to search is:  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\BackupRestore\FilesNotToBackup

However, it could also be a local directive (nsr.dir) file on this drive. Although you state there is none, i would again search the whole drive's directory structure.

I do not expect a NW problem as your tests also show that it can backup the file from another path.

8 Krypton

Re: Restore doesn't work because backups just ignores files...?

Hi,

I did dir /s nsr.dir for whole system - nothing.

As for registry, I just checked and it is not there (I mean, this location is not mentioned). A real puzzle as it seems

8 Krypton

Re: Restore doesn't work because backups just ignores files...?

Next i would touch a file in the same directory and try NW's bigasm to create a backup stream.

8 Krypton

Re: Restore doesn't work because backups just ignores files...?

I don't think that is the problem.  I do see in debug that this thing has its own writer. 

VSS .. returning writer ASR Writer component 0  .. component name ASR  .. caption ASR  .. logicalpath ASR VSS .. returning writer ASR Writer component 1  .. component name Volume{eebcc5e5-8c4a-11e0-a194-806e6f6e6963}  .. caption Select this volume (C:) if it is a critical volume.

Critical volumes are those which ASR must restore.  .. logicalpath Volumes VSS .. returning writer ASR Writer component 2  .. component name Volume{13674e79-1635-11e1-9f00-001cc4591ec8}  .. caption Select this volume (D:) if it is a critical volume.

Critical volumes are those which ASR must restore.  .. logicalpath Volumes VSS .. returning writer ASR Writer component 3  .. component name Volume{13674e80-1635-11e1-9f00-001cc4591ec8}  .. caption Select this volume (E:) if it is a critical volume.

Critical volumes are those which ASR must restore.  .. logicalpath Volumes VSS .. returning writer ASR Writer component 4  .. component name harddisk1  .. caption Select to include disk #1 (of signature 0xd6980119) for ASR restore.  .. logicalpath Disks VSS .. returning writer ASR Writer component 5  .. component name harddisk0  .. caption Select to include disk #0 (of signature 0xe79e99e) for ASR restore.  .. logicalpath Disks VSS .. returning writer ASR Writer component 6  .. component name BCD  .. caption This is the path to the boot BCD store and the boot managers.

All the files in this directory need to be backed up.  .. logicalpath BCD sow_setup_directives: Setting up directives for writer=PHD VSS Writer

VSS .. returning writer PHD VSS Writer component 0  .. component name SCAN  .. caption PHD SCAN Archive VSS .. returning writer PHD VSS Writer component 1  .. component name MANV  .. caption PHD MANV Archive VSS .. returning writer PHD VSS Writer component 2  .. component name CHAR  .. caption PHD CHAR Archive sow_setup_directives: Setting up directives for writer=WMI Writer

VSS .. returning writer WMI Writer component 0  .. component name WMI  .. caption Windows Managment Instrumentation sow_setup_directives: Setting up directives for writer=Shadow Copy Optimization Writer

sow_setup_directives: No components found for writer=Shadow Copy Optimization Writer

sow_setup_directives: Setting up directives for writer=COM+ REGDB Writer

VSS .. returning writer COM+ REGDB Writer component 0  .. component name COM+ REGDB  .. caption COM+ REGDB win32_pre_save(): Called

[skip]

fullcanon(name=Archive\)

   exit fullcanon(fullname=\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy21\Uniformance\PHDServer\Archive)

fullcanon(name=\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy21\Uniformance\PHDServer\Archive)

   exit fullcanon(fullname=\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy21\Uniformance\PHDServer\Archive)

NTFS Change Journal will not be used for this save. Change Journal only supported at volume level.

Walking for \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy21\Uniformance\PHDServer\Archive\SCAN00001.dat

saphddi2934.eur.corp.vattenfall.com:E:\Uniformance\PHDServer\Archive\SCAN00001.dat size 0 KB, 0 file(s), took   0 min   4 sec

save: E:\Uniformance\PHDServer\Archive\SCAN00001.dat  0 KB 00:00:10      0 files

7167:save: save completion time: 15-2-2013 13:28:50

Bare in mind this is debug=9 so loads of unnecessary messages, but I see PHD VSS Writer mentioned which is probably in use.  I also see that file which is backed up from shadow copy seems to be 0KB.  In other words, if I can reproduce this outside NW, I have a winner.  But, right now I'm not sure how to:

a) create snapshot in a same way as NW would do using Windows commands

b) mount/browse that snapshot to see size of the file on it

0 Kudos
8 Krypton

Re: Restore doesn't work because backups just ignores files...?

I did some work on this during the weekend while I could get some time free... one thing I found strange was that verbose save would create bigger log and than debug one.  Anyway, highlight of the verbose run shows following:

chdir(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy38\Uniformance\PHDServer\Archive\)

Name=`\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy38\Uniformance\PHDServer\Archive\SCAN00001.dat', name=`\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy38\Uniformance\PHDServer\Archive\SCAN00001.dat', fname=`SCAN00001.dat'

32240:save: found protofile spec for /:

  mntasm : C:

32240:save: found protofile spec for \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy38\:

  skip : Pagefile.sys

32240:save: found protofile spec for \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy38\Uniformance\PHDServer\Archive\:

  skip : .idx

walk(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy38\Uniformance\PHDServer\Archive\SCAN00001.dat, SCAN00001.dat)

32246:save: matched internal `skip' on `SCAN00001.dat' for `\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy38\Uniformance\PHDServer\Archive\SCAN00001.dat'

save: E:\Uniformance\PHDServer\Archive\SCAN00001.dat  0 KB 00:00:01      0 files

7167:save: save completion time: 16-2-2013 16:03:37

This is non sense as I do not have any client nor server side directive so I have no idea from where this internal skip comes from. Anyway, I went to check if I will find anything on server side log when running full backup of the machine and I found following:

VSS OTHER: VSS Writer: PHD VSS Writer is not supported, ignoring it.

I doubt data I miss should go under VSS OTHER:, but I'm puzzled as tp why is this not supported.  vssadmin list writer is clear:

E:\Uniformance\PHDServer\Archive>vssadmin list writers

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

(C) Copyright 2001-2005 Microsoft Corp.

 

Writer name: 'Task Scheduler Writer'

   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}

   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}

   State: [1] Stable

   Last error: No error

 

Writer name: 'VSS Metadata Store Writer'

   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}

   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

   State: [1] Stable

   Last error: No error

 

Writer name: 'Performance Counters Writer'

   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}

   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

   State: [1] Stable

   Last error: No error

 

Writer name: 'System Writer'

   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

   Writer Instance Id: {883a0b8c-48a4-43f0-bdb8-87b2134a4fb0}

   State: [1] Stable

   Last error: No error

 

Writer name: 'ASR Writer'

   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

   Writer Instance Id: {ff692d31-df87-4370-ba28-61391e5a96b0}

   State: [1] Stable

   Last error: No error

 

Writer name: 'Registry Writer'

   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

   Writer Instance Id: {760f497f-9fc7-4131-877c-02b3f7afca1f}

   State: [1] Stable

   Last error: No error

 

Writer name: 'Shadow Copy Optimization Writer'

   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

   Writer Instance Id: {0c454e30-02b2-4fdd-951a-ef154b746334}

   State: [1] Stable

   Last error: No error

 

Writer name: 'COM+ REGDB Writer'

   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

   Writer Instance Id: {42277d3f-8c4f-4b9d-80e2-a4f84f1642b5}

   State: [1] Stable

   Last error: No error

Writer name: 'PHD VSS Writer'

   Writer Id: {db0bb827-b4bc-4b79-8f1a-810a03bde092}

   Writer Instance Id: {6987a118-7f28-484a-936d-f5ed88290abd}

   State: [1] Stable

   Last error: No error

 

Writer name: 'WMI Writer'

   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

   Writer Instance Id: {e9dab57c-adb2-4601-ab95-815982dbe37d}

   State: [1] Stable

   Last error: No error

At this point, I'm thinking writer is sort of strange to whatever NW expects and it builds skip directive on the fly for all data which is covered otherwise by this writer.  On second thought, that would be terrible and I can't believe that.  So I proceed with vssadmin test of snapshot as indicated in previous message:

E:\Uniformance\PHDServer\Archive>vssadmin create shadow /For=E:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

(C) Copyright 2001-2005 Microsoft Corp.

Successfully created shadow copy for 'E:\'

    Shadow Copy ID: {accf49f7-1d83-48dd-94d7-dbde178582d1}

    Shadow Copy Volume Name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy40

E:\Uniformance\PHDServer\Archive>vssadmin list shadows

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

(C) Copyright 2001-2005 Microsoft Corp.

Contents of shadow copy set ID: {2571a7a7-b2a8-4ebb-8553-a71e5a95d070}

   Contained 1 shadow copies at creation time: 16-2-2013 22:32:37

      Shadow Copy ID: {accf49f7-1d83-48dd-94d7-dbde178582d1}

         Original Volume: (E:)\\?\Volume{13674e80-1635-11e1-9f00-001cc4591ec8}\

         Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy40

         Originating Machine: FOO

         Service Machine: FOO

         Provider: 'Microsoft Software Shadow Copy provider 1.0'

         Type: ClientAccessible

         Attributes: Persistent, Client-accessible, No auto release, No writers,

Differential

  

D:\H>mklink /d d:\H\VSS2 \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy40\

symbolic link created for d:\H\VSS2 <<===>> \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy40\

D:\H>dir

Volume in drive D is Apps

Volume Serial Number is EEAA-D559

 

Directory of D:\H

 

16-02-2013  22:41    <DIR>          .

16-02-2013  22:41    <DIR>          ..

16-02-2013  22:39    <SYMLINKD>     VSS [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy40]

16-02-2013  22:41    <SYMLINKD>     VSS2 [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy40\]

               0 File(s)              0 bytes

               4 Dir(s)  35.245.912.064 bytes free

D:\H>cd VSS2

D:\H\VSS2>dir

Volume in drive D is Apps

Volume Serial Number is EEAA-D559

  Directory of D:\H\VSS2

16-02-2013  17:10           161.560 file-d9.log

16-02-2013  16:03           618.912 file-v.log

15-02-2013  13:28           161.666 file.d9.txt

15-02-2013  13:56    <DIR>          H

15-02-2013  10:51    <DIR>          Ldata

01-12-2006  23:37           904.704 msdia80.dll

15-02-2013  13:15             5.022 test.d1.log

15-02-2013  13:14           174.860 test.log

09-01-2012  17:14    <DIR>          Uniformance

               6 File(s)      2.026.724 bytes

               3 Dir(s)  100.354.756.608 bytes free

D:\H\VSS2>cd Uniformance

D:\H\VSS2\Uniformance>cd PHDServer

D:\H\VSS2\Uniformance\PHDServer>cd Archive

 

D:\H\VSS2\Uniformance\PHDServer\Archive>dir

Volume in drive D is Apps

Volume Serial Number is EEAA-D559

 

Directory of D:\H\VSS2\Uniformance\PHDServer\Archive

 

15-02-2013  14:13    <DIR>          .

15-02-2013  14:13    <DIR>          ..

14-02-2013  11:44             2.049 CHAR00001.dat

14-02-2013  11:44             3.072 CHAR00001.idx

14-02-2013  11:44             2.049 MANV00001.dat

14-02-2013  11:44             3.072 MANV00001.idx

15-02-2013  14:13     4.050.571.797 SCAN00001.dat

15-02-2013  14:13        73.094.144 SCAN00001.idx

16-02-2013  15:59        47.708.916 SCAN00002.dat

15-02-2013  17:45           194.560 SCAN00002.idx

               8 File(s)  4.171.579.659 bytes

               2 Dir(s)  100.354.756.608 bytes free

D:\H\VSS2\Uniformance\PHDServer\Archive>save -s BAR -bPOOL SCAN00001.dat

D:\H\VSS2\Uniformance\PHDServer\Archive\SCAN00001.dat

D:\H\VSS2\Uniformance\PHDServer\Archive\

D:\H\VSS2\Uniformance\PHDServer\

D:\H\VSS2\Uniformance\

D:\H\VSS2\

D:\H\

D:\

/

 

save: D:\H\VSS2\Uniformance\PHDServer\Archive\SCAN00001.dat  3956 MB 00:28:57  8 files

7167:save: save completion time: 16-2-2013 23:12:26

I never played with VSS before so this was first time I ever did manually snapshot and browse the it (mount it).  A bit of advice, when doing mklink command remember:

  1. destination should be folder which does not exist - it will be created by mklink
  2. source should end with \ - otherwise you end up with unusable structure (this is why I had VSS and VSS2 folders - first one was without \ and I could not use it

Anyway, it works so I doubt VSS Writer is doing anything wrong at this point. Of course, my backup pointed out to monted VSS snapshot instead of original, but that's just matter of masking - and can't be related to the issue.

As last thing to test, I upgraded client from 7.6.3.6 to 7.6.5.0 - same issue.  Right now, I believe issue is "internal skip" thingy, but I still don't know from where is that coming from. However enough data collected for support to play around on Monday. I would still like to believe I'm missing the obvious, but somehow I doubt it...

0 Kudos
8 Krypton

Re: Restore doesn't work because backups just ignores files...?

In my previous update, I forgot to mention another finding which isolates this issue solely to VSS - if I do save command with VSS enabled, despite the fact that this is win2k8 R2, backup is running then just fine.  No VSS, no problems (except DR ones if you wish to have things by the book of course).

0 Kudos
8 Krypton

Re: Restore doesn't work because backups just ignores files...?

Hi Hrvoje,

NetWorker develops a list of directories that it needs to skip and your directory for some reason matches the criteria and is being skipped automatically.    You might get some explanation by using the diskshadow command to get more info about what the writers are listing:  See here for details.

-Bobby

0 Kudos
8 Krypton

Re: Restore doesn't work because backups just ignores files...?

Hi Bobby,

Thanks.  The files (and writer) of interest give me following (I'm not a VSS expert so certain things here do not make sense to me):

  * WRITER "PHD VSS Writer"

    - Writer ID   = {db0bb827-b4bc-4b79-8f1a-810a03bde092}

    - Writer instance ID = {6987a118-7f28-484a-936d-f5ed88290abd}

    - Supports restore events = TRUE

    - Writer restore conditions = VSS_WRE_ALWAYS

    - Restore method = VSS_RME_RESTORE_IF_NOT_THERE

    - Requires reboot after restore = FALSE

    - Excluded files:

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = MANV00001.dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = MANV00001.idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = CHAR00001.dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = CHAR00001.idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - Exclude: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

    + Component "PHD VSS Writer:\SCAN"

      - Name: SCAN

      - Logical path:

      - Full path: \SCAN

      - Caption: PHD SCAN Archive

      - Type: VSS_CT_FILEGROUP [2]

      - Is selectable: TRUE

      - Is top level: TRUE

      - Notify on backup complete: TRUE

      - Components:

      - File List: Path = E:\Uniformance\PHDServer\Archive, Filespec = SCAN00002.dat

      - File List: Path = E:\Uniformance\PHDServer\Archive, Filespec = SCAN00002.idx

      - File List: Path = E:\Uniformance\PHDServer\Archive, Filespec = SCAN00001.dat

      - File List: Path = E:\Uniformance\PHDServer\Archive, Filespec = SCAN00001.idx

      - Paths affected by this component:

        - E:\Uniformance\PHDServer\Archive

      - Volumes affected by this component:

        - \\?\Volume{13674e80-1635-11e1-9f00-001cc4591ec8}\

      - Component Dependencies:

    + Component "PHD VSS Writer:\MANV"

      - Name: MANV

      - Logical path:

      - Full path: \MANV

      - Caption: PHD MANV Archive

      - Type: VSS_CT_FILEGROUP [2]

      - Is selectable: TRUE

      - Is top level: TRUE

      - Notify on backup complete: TRUE

      - Components:

      - File List: Path = E:\Uniformance\PHDServer\Archive, Filespec = MANV00001.dat

      - File List: Path = E:\Uniformance\PHDServer\Archive, Filespec = MANV00001.idx

      - File List: Path = E:\Uniformance\PHDServer\Archive, Filespec = CHAR00001.dat

      - File List: Path = E:\Uniformance\PHDServer\Archive, Filespec = CHAR00001.idx

      - Paths affected by this component:

        - E:\Uniformance\PHDServer\Archive

      - Volumes affected by this component:

        - \\?\Volume{13674e80-1635-11e1-9f00-001cc4591ec8}\

      - Component Dependencies:

    + Component "PHD VSS Writer:\CHAR"

      - Name: CHAR

      - Logical path:

      - Full path: \CHAR

      - Caption: PHD CHAR Archive

      - Type: VSS_CT_FILEGROUP [2]

      - Is selectable: TRUE

      - Is top level: TRUE

      - Notify on backup complete: TRUE

      - Components:

      - File List: Path = E:\Uniformance\PHDServer\Archive, Filespec = CHAR00001.dat

      - File List: Path = E:\Uniformance\PHDServer\Archive, Filespec = CHAR00001.idx

      - File List: Path = E:\Uniformance\PHDServer\Archive, Filespec = .dat

      - File List: Path = E:\Uniformance\PHDServer\Archive, Filespec = .idx

      - Paths affected by this component:

        - E:\Uniformance\PHDServer\Archive

      - Volumes affected by this component:

        - \\?\Volume{13674e80-1635-11e1-9f00-001cc4591ec8}\

      - Component Dependencies:

What I see above is PHD VSS Writer and few components - each takking care of their own files.  What I find a bit strange, and perhaps part of this puzzle, is the teh fact that it has Exclude Path defined many many times for .idx and .dat which is pretty much everything in Archive directory (so it would apply to components too).  I do not understand why it is listed so many times, is this what is causing NW when using VSS to skip these files and finally how to change it.  Do you know if this is something that can be changed and if NW interpretation is good one? (given that my interpretation was correct in the first place)

0 Kudos
8 Krypton

Re: Restore doesn't work because backups just ignores files...?

Hi,

Looks to me like NetWorker is doing what its told.  From what I read here:

http://msdn.microsoft.com/en-us/library/windows/desktop/aa819132%28v=vs.85%29.aspx

it looks like this exclude was programmed directly into the writer when the writer was developed.  I don't know of any way you can modify that.  You could try disabling this writer to see if that causes these files to be backed up using the standard writers (since they are not actively excluding the files).

-Bobby