Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1737

June 3rd, 2014 08:00

Savegroup logs missing information for Windows 2008/2012 backups

Using client version 8.1.1.5 on Windows 2008/2012 servers, the savegroup log that gets generated does not include any drives that Microsoft considers to be Disaster Recovery drives.  As an example, on one client the C:, D:, and F: drives are deemed as Disaster Recovery drives and a savegroup log from the client does not show any information about these drives.  The information does appear in the NMC when looking at the savegroup details, so I at least know it's getting backed up. (note: using save set defined as All, and the admins want the DR save sets backed up)

According to EMC support, this is a Microsoft issue and the logs work as designed.  I find this answer totally unacceptable.  We're a shop that use the savegroup logs quite heavily (we've developed a website that keeps 45 days of logs available online).  We have many users (dba's, admins, app owners, etc.) that use the logs on a daily basis and not having complete information in the logs is an issue. 

Since the information is appearing in NMC, I don't understand why EMC can't get the same information to show in the savegroup log.

My Networker server is running 7.6.5   Yes, I know I'm behind and need to get to the upgrade :-)

I'm wondering if the same results are seen by people running version 8+ on their Networker servers?

Has anyone else seen this issue?  If so, what did you do about it?

Thanks,

Jim

14.3K Posts

June 3rd, 2014 09:00

I never heard of savegroup log on client - do you mean on server? I do not create reports based on savegroup log, but rather mminfo where I feed the data to separate portal. I'm not sure what exactly do you look for as I don't use that log, but data inside is feed by save command on client and its input depends on API used used on client.  As native Windows API is used, it sounds as if change is in direct connection to that process.

I checked one client which is win2k12 and in savegrp log I see:

* :All savefs : succeeded.

* :DISASTER_RECOVERY:\ Suppressed 14239871 bytes of output.

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\72f35a0c-fd31-44c6-a5fd-74c656230c66

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\7413b569-8bd6-4d45-ae89-d983968361dd

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\74c0e636-efd4-4f52-820e-1d318d1abe7d

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\7d857ec8-cb75-48f6-9963-7e68982b8465

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\8b34f644-f627-47e7-98e0-957ba1c5eb6d

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\9536335e-476b-42f7-8624-2308ca0f222b

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\997514a9-18e8-4c71-a9cd-1d360c83a600

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\bbdea12e-91e2-4cc5-bff0-a64897f04a96

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\c911a4f6-6cdc-4598-8251-f6ff82453881

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\d0999fca-49b0-4f9f-8fd6-3def808b3295

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\ebccdb21-f118-4dec-bb6f-7d91c6d06968

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\f00fd1e5-e940-487a-bade-23e9c5c4d9c7

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\f572dbad-ebd2-4f99-b4d2-0fa1e28fac40

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\f85a1245-0209-468b-a878-e83ed0e980a6

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\fbcc008d-ba20-477d-bd4f-1b6962e60989

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Scm\

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Sum\Current.mdb

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Sum\Svc.chk

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Sum\SystemIdentity.mdb

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Sum\{930BE254-9062-4F22-9AE4-DA82AD141A63}.mdb

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\Sum\

* :DISASTER_RECOVERY:\ C:\Windows\System32\LogFiles\

* :DISASTER_RECOVERY:\ C:\Windows\System32\

* :DISASTER_RECOVERY:\ C:\Windows\WindowsUpdate.log

* :DISASTER_RECOVERY:\ C:\Windows\

* :DISASTER_RECOVERY:\ C:\

* :DISASTER_RECOVERY:\ /

* :DISASTER_RECOVERY:\

  : C:\ level=incr, 1242 MB 00:03:37    777 files

* :DISASTER_RECOVERY:\ Completed savetime=1401296515

* :DISASTER_RECOVERY:\ 90015:save: The backup of VSS emit save set 'C:\' succeeded.

* :DISASTER_RECOVERY:\ OSSRInfo XML Version:2.0

* :DISASTER_RECOVERY:\ 90011:save: The backup of the disaster recovery save sets succeeded.

* :DISASTER_RECOVERY:\ 86704:save: Successfully established DDCL session for save-set ID '294000483' ( :DISASTER_RECOVERY:\).

* :DISASTER_RECOVERY:\ OSSRInfo XML Version:2.0

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

  : DISASTER_RECOVERY:\ level=incr, 17 KB 00:19:27      3 files

* :DISASTER_RECOVERY:\ completed savetime=1401295789

Is that what you are referring to?

24 Posts

June 3rd, 2014 09:00

I'm sorry.... I didn't intend to imply savegroup log on the client.  I was obviously referring to the savegroup log that gets stored on the Networker server.

The log you supplied in your reply was what I was referring to.  It appears that you do have the Disaster recovery information included in your log.  The problem I'm having must be because my Networker server is still running 7.6.5.  Thanks for your reply!  It is good to see that the problem will go away once I upgrade.  I just need to find the time to perform the upgrade (and all that it entails).

Just for completeness sake, here is what my savegroup log looks like (notice no mention of the C:, D:, or F: drives):

--- Successful Save Sets ---

* :All savefs : succeeded.

* :DISASTER_RECOVERY:\ savegrp: suppressed 20 lines of output.

* :DISASTER_RECOVERY:\ Performance Counters Writer - Starting save

* :DISASTER_RECOVERY:\ System Writer - Starting save

* :DISASTER_RECOVERY:\ IIS Config Writer - Starting save

* :DISASTER_RECOVERY:\ COM+ REGDB Writer - Starting save

* :DISASTER_RECOVERY:\ WMI Writer - Starting save

* :DISASTER_RECOVERY:\ Disk Quota Databases - Starting save

* :DISASTER_RECOVERY:\ ASR Writer - Starting save

  : WINDOWS ROLES AND FEATURES:\ level=full, 6138 KB 00:01:09     27 files

* :DISASTER_RECOVERY:\ Completed savetime=1401749346

* :DISASTER_RECOVERY:\ 90011:save: The backup of the disaster recovery save sets succeeded.

* :DISASTER_RECOVERY:\ OSSRInfo XML Version:3.0

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

  : DISASTER_RECOVERY:\ level=incr,    29 KB 00:06:05      4 files

* :I:\ libDDBoost version: major: 2, minor: 6, patch: 2, engineering: 0, build: 410681

  : I:\                level=incr,      2 KB 00:01:11      4 files

* :I:\ Completed savetime=1401749149

* :I:\ 94694:save: The backup of save set 'I:\' succeeded.

* :H:\ libDDBoost version: major: 2, minor: 6, patch: 2, engineering: 0, build: 410681

  : H:\                level=incr,      2 KB 00:01:09      4 files

* :H:\ Completed savetime=1401749166

* :H:\ 94694:save: The backup of save set 'H:\' succeeded.

* :G:\ libDDBoost version: major: 2, minor: 6, patch: 2, engineering: 0, build: 410681

  : G:\                level=incr,      2 KB 00:01:09      4 files

* :G:\ Completed savetime=1401749177

* :G:\ 94694:save: The backup of save set 'G:\' succeeded.

  : index:      level=9,      1218 KB 00:00:01     89 files

14.3K Posts

June 3rd, 2014 10:00

While I don't see it here, I wonder if it is possible that information you look for is suppressed - because if limit would come from client parsing output, I would expect information to be the same regardless of what version server is running?  There is one easy way to test it. Pick any Windows machine and install NetWorker server on it.  You can do it on your laptop.  Then pick any client you want which is NW8 and define it on this test installation.  I would use laptop and USB disk as disk device and start backup during lunch break (so yeah, pick some smaller client).  That way you can easily compare results between NW7 and NW8 server.

24 Posts

June 3rd, 2014 12:00

Good idea..... makes me wonder why I didn't think of that....  temporary brain freeze maybe? 

I did a quick install of 8.1 on a server and backed up the same client.... and the missing information magically appears again in the savegroup logs.  I should've known better.......

Thanks again for your help!

Now I have to call off my local EMC team from harassing support..... wonder why support never mentioned it was a version mismatch problem?

No Events found!

Top