NetWorker 7.6 SP2 / W2k8 system drives C:\ and D:\ aren't used as DISASTER_RECOVERY:\ save set

Hi vucko- moving this over to the support forum for additional help.

Thx.

Allan

Many thanks for your reply Hrvoje,

Unfortunately the current size of saved data on drive F:\ is around 1 TB, but if it is required, I will run a full backup of drive F:
Sorry, but how can I check what is inside of recovery save set with nsradmin?

Thanks & Rgds..

Sorry, did a typo... not nsradmin, but nsrinfo.

I am still facing with same problem, unfortunately no help from nsrinfo…

but it is very interesting to get a few different save sets entries all assigned to one SSID….

me@my_bkp_srv>mminfo -q ssid=1547175309 -r name,sumsize,level,ssflags,nsavetime

name                             size  lvl ssflags save time
OSSR_F                          244 GB full vrF    1312294197
OSSR_F                          119 GB full vrF    1312294197
OSSR_F                           55 GB full vrF    1312294197
OSSR_F                           76 GB full vrF    1312294197
OSSR_F                           41 GB full vrF    1312294197
OSSR_F                           43 GB full vrF    1312294197
OSSR_F                          143 GB full vrF    1312294197
OSSR_F                          117 GB full vrF    1312294197
OSSR_F                           47 GB full vrF    1312294197
OSSR_F                           56 GB full vrF    1312294197
OSSR_F                          161 GB full vrF    1312294197
OSSR_F                          177 GB full vrF    1312294197
OSSR_F                           59 GB full vrF    1312294197
OSSR_F                           89 GB full vrF    1312294197

me@my_bkp_srv>nsrinfo -t 1312294197 my_fsr_01
scanning client `my_fsr_01' for savetime 1312294197(Tue 02 Aug 2011 03:09:57 PM BST) from the backup namespace
0 objects found
me@my_bkp_srv>
me@my_bkp_srv>

Is there any other way to check what is saved under save set# 1547175309?

Our backup of windows system files and drive C:\ is actually scheduled to run over day, and normally it took only a few minute per server,  but due this issue OSSR_F the backup of this server runs almost 24 hours…

Vucko,

The saveset flags show these are recoverable savesets therefore the data regarding the individual file detail is no longer with the Client File Index.

Using mminfo -q ssid= -r name,sumsize,level,ssflags,nsavetime,volume,sumflags

I think this will show you that you have a saveset which spans volumes and the sumflags will tell you which has header, middle and tails sections of the data of the saveset.

If you need the detail of the file data the only way to achieve this is to scan in the saveset starting with the header - and then NetWorker should prompt you for the tapes in order. This must be done in one operation (no breaks and in the right order to be successful). There is also some work on the saveset for the browse time which will be required to ensure the index entries remain and are not deleted by NetWorker housekeeping. Search Powerlink for recovering savesets passed browse and you should get a solution which details what you have to do.

Regards,

Bill Mason

Hi Vucko,

I would say that you should change the saveset configuration.

Please note that DISASTER_RECOVERY:\ saveset is intended for BMR.

Could you please try to run only the saveset DISASTER_RECOVERY:\ and let us know the results?

Thank you.

Carlos.

Ok, here is what I’ve done to make ssid#1547175309 browsable, but only this save set cannot be changed to browsable…?!?

1. get based info's about save set  1547175309

mminfo -q ssid=1547175309 -r name,sumsize,volume,level,nsavetime,ssbrowse,ssretent,volume,sumflags,ssflags
name                             size volume          lvl  save time browse   retent  volume         fl ssflags
OSSR_F                          244 GB 011391         full 1312294197 08/30/11 12/12/22 011391        mr vrF
OSSR_F                          119 GB 012389         full 1312294197 08/30/11 12/12/22 012389        mr vrF
OSSR_F                           55 GB 012483         full 1312294197 08/30/11 12/12/22 012483        mr vrF
OSSR_F                           76 GB 012797         full 1312294197 08/30/11 12/12/22 012797        mr vrF
OSSR_F                           41 GB 013166         full 1312294197 08/30/11 12/12/22 013166        mr vrF
OSSR_F                           43 GB 013184         full 1312294197 08/30/11 12/12/22 013184        hr vrF
OSSR_F                          143 GB 013186         full 1312294197 08/30/11 12/12/22 013186        mr vrF
OSSR_F                          117 GB 013244         full 1312294197 08/30/11 12/12/22 013244        mr vrF
OSSR_F                           47 GB 013334         full 1312294197 08/30/11 12/12/22 013334        mr vrF
OSSR_F                           56 GB 013338         full 1312294197 08/30/11 12/12/22 013338        mr vrF
OSSR_F                          161 GB 013359         full 1312294197 08/30/11 12/12/22 013359        mr vrF
OSSR_F                          177 GB 013631         full 1312294197 08/30/11 12/12/22 013631        mr vrF
OSSR_F                           59 GB 013656         full 1312294197 08/30/11 12/12/22 013656        tr vrF
OSSR_F                           89 GB 013774         full 1312294197 08/30/11 12/12/22 013774        mr vrF

2.  Retention policy for this server is set on decade and the retent time was actually properly set to 08/02/2021
and save set was marked as recovable, but since the first run of nsrck -L7 for this client,
was successful but without any changes for this ssid, I did...:

nsrmm -S 1547175309/1312294285 -e 12/12/22

nsrmm -S 1547175309/1312294285 -o notrecyclable
Mark save set copy 1547175309/1312294285 as not recyclable? yes
Save set `1547175309' cloneid `1312294285' is already not eligible

nsrmm -S 1547175309 -w 12/12/12
Cannot exceed the browse time of a recoverable save set 1547175309

Ok, now the new try with nsrck -L7

3.
mminfo -avot -N index:my_fsr_01

012831         my_bkp_srv 08/07/11 11:22:55 AM 7097 MB 373188479 cr full index:my_fsr_01

nsrck -L7 -t "08/07/11 11:22:55"  my_fsr_01
nsrck: checking index for 'my_fsr_01'
9343:nsrck: The file index for client 'my_fsr_01' will be recovered.Requesting 1 recover session(s) from server.
Recover completion time: Thu 29 Sep 2011 02:38:57 PM BST

nsrck: /var/nsr/index/my_fsr_01 contains 100787509 records occupying 15 GB
nsrck: Completed checking 1 client(s)

4.
Still no changes for save set 1547175309

mminfo -q ssid=1547175309 -r name,sumsize,volume,level,nsavetime,ssbrowse,ssretent,volume,sumflags,ssflags
name                             size volume          lvl  save time browse   retent  volume         fl ssflags
OSSR_F                          244 GB 011391         full 1312294197 08/30/11 12/12/22 011391        mr vrF
OSSR_F                          119 GB 012389         full 1312294197 08/30/11 12/12/22 012389        mr vrF
OSSR_F                           55 GB 012483         full 1312294197 08/30/11 12/12/22 012483        mr vrF
OSSR_F                           76 GB 012797         full 1312294197 08/30/11 12/12/22 012797        mr vrF
OSSR_F                           41 GB 013166         full 1312294197 08/30/11 12/12/22 013166        mr vrF
OSSR_F                           43 GB 013184         full 1312294197 08/30/11 12/12/22 013184        hr vrF
OSSR_F                          143 GB 013186         full 1312294197 08/30/11 12/12/22 013186        mr vrF
OSSR_F                          117 GB 013244         full 1312294197 08/30/11 12/12/22 013244        mr vrF
OSSR_F                           47 GB 013334         full 1312294197 08/30/11 12/12/22 013334        mr vrF
OSSR_F                           56 GB 013338         full 1312294197 08/30/11 12/12/22 013338        mr vrF
OSSR_F                          161 GB 013359         full 1312294197 08/30/11 12/12/22 013359        mr vrF
OSSR_F                          177 GB 013631         full 1312294197 08/30/11 12/12/22 013631        mr vrF
OSSR_F                           59 GB 013656         full 1312294197 08/30/11 12/12/22 013656        tr vrF
OSSR_F                           89 GB 013774         full 1312294197 08/30/11 12/12/22 013774        mr vrF

5.
All other save sets, that were saved during the same full backup of my_fsr_01 are now browsaable.
For example here are the save sets from tape 013184

mminfo  -q volume=013184 -r ssid,client,name,nsavetime,ssbrowse,ssretent,ssflags,sumflags | grep  my_fsr_01

3543635474 my_fsr_01 K:\xxxxxxxxx                            1312265746 10/28/11 09/30/21 vF    tb
3442972187 my_fsr_01 K:\xxxxxxxxxxx s                      1312265755 10/28/11 09/30/21 vF    mb
3342308910 my_fsr_01 N:\xxxxx\xxxxxxxxxx                 1312265774 10/28/11 09/30/21 vF    mb
1647838513 my_fsr_01 VSS OTHER:\                            1312294193 10/05/11 09/07/21 vF    cb
1614284081 my_fsr_01 VSS USER DATA:\                     1312294195 10/05/11 09/07/21 vF    cb
1664615729 my_fsr_01 VSS SYSTEM SERVICES:\        1312294192 10/05/11 09/07/21 vF    cb
1631061297 my_fsr_01 VSS SYSTEM BOOT:\                1312294194 10/05/11 09/07/21 vF    cb
1597506866 my_fsr_01 VSS SYSTEM FILESET:\            1312294196 10/27/11 09/29/21 vF    cb
1580729706 my_fsr_01 C:\                                             1312294249 10/05/11 09/07/21 vF    cb
1563952502 my_fsr_01 D:\                                             1312294260 10/05/11 09/07/21 vF    cb
1547175309 my_fsr_01 OSSR_F                                    1312294197 08/30/11 12/12/22 vrF   hr

Hello Carlos,

here is aborted output of running backup for DISASTER_RECOVERY:\ only...
I've aborted it as I saw that the backup of OSSR_F  was started, (1.4 TB of data)

* my_fsr_01 :DISASTER_RECOVERY:\ savegrp: suppressed 89 lines of output.

* my_fsr_01 :DISASTER_RECOVERY:\ << "C:\ProgramData\Microsoft\Network\Downloader\\" >>

* my_fsr_01 :DISASTER_RECOVERY:\ +skip: *

* my_fsr_01 :DISASTER_RECOVERY:\ << "C:\Windows\SoftwareDistribution\Download\a0929fb7c5c83baabfaeabba559a9f32\" >>

* my_fsr_01 :DISASTER_RECOVERY:\ skip: BIT5AE.tmp

* my_fsr_01 :DISASTER_RECOVERY:\ << "C:\Windows\SoftwareDistribution\Download\a799f3878beb133cda8bcd101db25f06\" >>

* my_fsr_01 :DISASTER_RECOVERY:\ skip: BIT6B8.tmp

* my_fsr_01 :DISASTER_RECOVERY:\ << "C:\Windows\SoftwareDistribution\Download\8135a0dba986235be8d2d4844d05f456\" >>

* my_fsr_01 :DISASTER_RECOVERY:\ skip: BIT4A33.tmp

* my_fsr_01 :DISASTER_RECOVERY:\ 77775:save: Processing completed for disaster recover backup.

* my_fsr_01 :DISASTER_RECOVERY:\ 74209:save: Quit signal received.

* my_fsr_01 :DISASTER_RECOVERY:\ 83452:save: Handling an abort while processing Windows disaster recovery backup.

* my_fsr_01 :DISASTER_RECOVERY:\ aborted

#######################################

Completion report of last full backup of system files, C and D drives of my_fsr_01

* my_fsr_01 :Probe savefs my_fsr_01 : succeeded.

  my_fsr_01 : VSS SYSTEM FILESET:\ level=full, 9869 MB 00:23:35 104641 files

  my_fsr_01 : C:\           level=full,   3158 MB 00:07:46  10835 files

  my_fsr_01 : D:\           level=full,   2531 MB 00:05:36    373 files

* my_fsr_01 :DISASTER_RECOVERY:\ savegrp: suppressed 91 lines of output.

* my_fsr_01 :DISASTER_RECOVERY:\ << "C:\Windows\SoftwareDistribution\Download\a0929fb7c5c83baabfaeabba559a9f32\" >>

* my_fsr_01 :DISASTER_RECOVERY:\ skip: BIT5AE.tmp

* my_fsr_01 :DISASTER_RECOVERY:\ << "C:\Windows\SoftwareDistribution\Download\a799f3878beb133cda8bcd101db25f06\" >>

* my_fsr_01 :DISASTER_RECOVERY:\ skip: BIT6B8.tmp

* my_fsr_01 :DISASTER_RECOVERY:\ << "C:\Windows\SoftwareDistribution\Download\8135a0dba986235be8d2d4844d05f456\" >>

* my_fsr_01 :DISASTER_RECOVERY:\ skip: BIT4A33.tmp

* my_fsr_01 :DISASTER_RECOVERY:\ 77775:save: Processing completed for disaster recover backup.

  my_fsr_01 : OSSR_F        level=full,   1434 GB 39:04:53 2226034 files

  my_fsr_01 : OSSR_C        level=full,     13 GB 39:26:36 102060 files

* my_fsr_01 :DISASTER_RECOVERY:\ 80889:save: Created disaster recover logical object.

  my_fsr_01 : DISASTER_RECOVERY:\ level=full, 41 KB 39:26:44      4 files

  my_fsr_01 : VSS OTHER:\   level=full,      1 KB 00:00:14      1 file

* my_fsr_01 :VSS SYSTEM BOOT:\ VSS SYSTEM BOOT: VSS Writer: ASR Writer is not supported, ignoring it.

  my_fsr_01 : VSS SYSTEM BOOT:\ level=full, 97 MB 00:00:56    145 files

  my_fsr_01 : VSS SYSTEM SERVICES:\ level=full, 61 MB 00:00:46     43 files

  my_fsr_01 : VSS USER DATA:\ level=full,    1 KB 00:00:16      1 file

V ne-bkp-lgto01.teg.teda: index:my_fsr_01  level=full, 6997 MB 01:05:38    854 files

vucko wrote: I am still facing with same problem, unfortunately no help from nsrinfo… but it is very interesting to get a few different save sets entries all assigned to one SSID….

Errr... do you use perhaps nsrauth on server?

Thanks Hrvoje for this great troubleshoot,

the xml files in nsr/tmp was the real good hint, since the information that I could catch from those files were much as enough for  us.

In the OSSR_Info.xml file all drives are listed with some “system own information”, but only drives C.\ and F.\ are specified as a “Critical Volume"

<Saveset Saveset_type="Critical Volume" Saveset_name="OSSR_F" 
 Saveset_ssid="bf48c5c2-00000006-cd86a5aa-4e86a5aa-06380014-4f671d21" 
 Volume_name="F:\" Volume_guid="\\?\Volume{1b6f1197-ac8e-11e0-9c37-806e6f6e6963}" Volume_label="BU_HD" 
 Disk_numbers="2" Volume_type="2" Disk_capacity="1799352128" Saveset_size="1414686359" Saveset_action="0" 
 Volume_was_backed_up="True" /> 
  <Saveset Saveset_type="Critical Volume" Saveset_name="OSSR_C" 
 Saveset_ssid="d238005d-00000006-9c888662-4e888662-11690014-4f671d21" 
 Volume_name="C:\" Volume_guid="\\?\Volume{470b9d70-acc6-11e0-981c-806e6f6e6963}" 
 Volume_label="" Disk_numbers="0" Volume_type="2" Disk_capacity="33554428" Saveset_size="14647187" 
 Saveset_action="0" Volume_was_backed_up="True" /> 

OSSR_BCDoc.xml” provides much more info’s, like:….

<WRITER_COMPONENTS instanceId="aa1f95bd-3382-46fc-8ad5-4901e9e93af2" 
 writerId="12ce4370-5bb7-4c58-a76a-e5d5097e3674" backupSchema="1280">
  <COMPONENT componentName="FSRM Global Configuration" componentType="filegroup" backupSucceeded="yes" /> 
 
  <COMPONENT componentName="FSRM Classification Module Configuration" componentType="filegroup" backupSucceeded="yes" /> 
 
  <COMPONENT componentName="FSRM Configuration on Volume F:/" componentType="filegroup" backupSucceeded="yes" /> 
 
  <COMPONENT componentName="FSRM Reports" componentType="filegroup" backupSucceeded="yes" /> 
  WRITER_COMPONENTS>