Highlighted
Trusted Contributor.
Trusted Contributor.
971 views

DP 9.09 (117) Sessions missing

Hi All,

So my problem today is... 🙂

I was required to perform a restore from LTO tape of some files from our NetApp filers. We have 4 jobs that run monthly with a 52 week retention period. Despite the jobs always completing successfully, for some reason, I only see the last 3 month's sessions for 2 of the 4 jobs. Their media pools do have 12 sets worth of media though.

Any suggestions as to how I find/get these sessions back??

TIA

0 Likes
11 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Hi TIA,

What about changing the interval accordingly? It does default to 3 month and does not display anything beyond that.

Regards,
Sebastian Koehler
---
Please use the Like button below, if you find this post useful.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Hello TIA,

Let me try to offer some suggestions.

Any suggestions as to how I find/get these sessions back??

Can you login to the CM server and run this CLI "omnidb -sess -last 365". We query for the sessions for the last 365 days as you have 52 weeks retention.

I only see the last 3 month's sessions for 2 of the 4 jobs.

Can you identify the backup specification for these backups and then generate a listing.

omnidb -sess -detail 

Their media pools do have 12 sets worth of media though.

Can you identify these media - what is the media ID/label ?

You try to isolate things using the backup specification so you can check how many backup info are still in the IDB.

 

Hope this helps

Rgds,

Sherman

 

 

0 Likes
Highlighted
Trusted Contributor.
Trusted Contributor.

Good morning Sherman,

Thank you for the help!

omnidb -sess -last 365 and omnidb -sess -detail show all 12 sessions.

If I select 'Internal Database' from the GUI drop down menu and select 2 of the 4 jobs I mentioned, for some reason it only shows 3 sessions when there should actually be 12. I've attached screen shots, both of these should show a similar list.

Regards,

Mark

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Hello Mark,

For this one:

omnidb -sess -last 365

and

omnidb -sess -detail

show all 12 sessions.

Can you share to me so I can check these 12 sessions.

 

I've checked the files you've uploaded and here is what I see

allsess.jpg
pclsto00201l_NDMP_CL1_Monthly

Misses.jpg
pclsto00202l_NDMP_CL2_Monthly

Basically, you specify a filter parameter and it is the backup specification.

You have 4 backup jobs - can you identify the backup specification of each of this job, and then you can generate also this output:

omnidb -session -datalist "Backup Specification Name" -detail

 Dump to 1 text file so we can check things.

Hope this helps

Rgds,

Sherman

DP Support

0 Likes
Highlighted
Trusted Contributor.
Trusted Contributor.

Hi Sherman,

Here is the output for each of the 4 jobs.

 

Best Regards,

Mark

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Thanks

pclsto00201l_NDMP_CL1_Monthly.txt:SessionID : 2017/07/07-2794
pclsto00201l_NDMP_CL1_Monthly.txt:SessionID : 2017/08/07-2427
pclsto00201l_NDMP_CL1_Monthly.txt:SessionID : 2017/09/01-2937
pclsto00201l_NDMP_CL1_Monthly.txt:SessionID : 2017/10/06-3040
pclsto00201l_NDMP_CL1_Monthly.txt:SessionID : 2017/11/03-2584
pclsto00201l_NDMP_CL1_Monthly.txt:SessionID : 2017/12/01-3322
pclsto00201l_NDMP_CL1_Monthly.txt:SessionID : 2018/01/05-3291
pclsto00201l_NDMP_CL1_Monthly.txt:SessionID : 2018/02/02-3299
pclsto00201l_NDMP_CL1_Monthly.txt:SessionID : 2018/03/02-3325
pclsto00201l_NDMP_CL1_Monthly.txt:SessionID : 2018/04/06-3336
pclsto00201l_NDMP_CL1_Monthly.txt:SessionID : 2018/05/15-2008
pclsto00201l_NDMP_CL1_Monthly.txt:SessionID : 2018/06/04-2201

pclsto00202l_NDMP_CL2_Monthly.txt:SessionID : 2018/05/21-1419
pclsto00202l_NDMP_CL2_Monthly.txt:SessionID : 2018/06/01-3401


pjwsto00201l_NDMP_JW1_Monthly.txt:SessionID : 2018/05/15-2011
pjwsto00201l_NDMP_JW1_Monthly.txt:SessionID : 2018/06/01-3404


pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2017/06/02-2808
pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2017/06/06-1628
pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2017/07/07-2795
pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2017/08/04-3003
pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2017/09/01-2938
pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2017/10/06-3043
pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2017/11/03-2586
pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2017/12/01-3324
pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2018/01/05-3294
pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2018/02/02-3302
pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2018/03/02-3326
pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2018/04/06-3339
pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2018/05/21-1420
pjwsto00202l_NDMP_JW2_Monthly.txt:SessionID : 2018/06/01-3403

 

We will concentrate on these two backup specification 


Backup Specification: pclsto00202l_NDMP_CL2_Monthly
Backup Specification: pjwsto00201l_NDMP_JW1_Monthly

Can you collect these CLI output

omnidb -sess 2018/05/21-1419 -detail
omnidb -sess 2018/06/01-3401 -detail

omnidb -sess 2018/05/15-2011 -detail
omnidb -sess 2018/06/01-3404 -detail

I would like to check details of the backup session for this two specification.

Do you know the session ID or backup tape (media ID or label) of the missing session? If yes, do let me know and then do also collect/send me a copy of the "media.log" - let me check them entries.

Let me know when you have them so I can check.

Rgds,

Sherman

DP Support

 

 

0 Likes
Highlighted
Trusted Contributor.
Trusted Contributor.

Hi Sherman,

We will concentrate on these two backup specification 


Backup Specification: pclsto00202l_NDMP_CL2_Monthly 
Backup Specification: pjwsto00201l_NDMP_JW1_Monthly

Can you collect these CLI output

omnidb -sess 2018/05/21-1419 -detail 
omnidb -sess 2018/06/01-3401 -detail

omnidb -sess 2018/05/15-2011 -detail 
omnidb -sess 2018/06/01-3404 -detail

I would like to check details of the backup session for this two specification.

Sessions captured and attached, media log is too large to attach.

 

Do you know the session ID or backup tape (media ID or label) of the missing session? If yes, do let me know and then do also collect/send me a copy of the "media.log" - let me check them entries.

There are 10 missing sessions for each Backup Specification. Do you need media IDs for all media related to these sessions?

 

Best Regards,

Mark

 

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Thanks

I will hold on and keep these session details, for reference.

2018/05/21-1419
2018/06/01-3401

2018/05/15-2011
2018/06/01-3404

media.log - you can compress it to make it smaller since this is just a text file.


Missing Sessions

If you have the session ID, much better. Else, if you have media IDs for all media related to these missing sessions, we can take a look inside and check.

If you have the backup tape info (media ID or label), then I will query the catalog info.

omnimm -catalog [mediumID or label]


Depending on the output, this might be huge.

 

We can continue to work on this one - step by step but at this point, I would now probably recommend that you log a SW DP case and the next available DP support can work this one with you.

I can handle this logged case but I need to know your working hours to sync things up - I work during APJ hours 8am - 5pm Singapore timezone.

Hope this helps

 

Rgds,

Sherman

DP Support

0 Likes
Highlighted
Trusted Contributor.
Trusted Contributor.

Hi Sherman,

I've just checked to see what sessions I can see if I were to attempt a restore and they do actually appear in the restore list strangely!

 

sess.jpg

 

 

 

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Hi @TA-SS,

Please refer to Internal Database => Objects. Most likely the Object in question was backed up using a differnet backup spec. The filter in Internal Database => Sessions looks exactly the name of the backup spec. If this has changed in the meantime it won't be displayed.

Besides of the Restore context the Internal Database => Objects will show all information on backup sessions per object still in the IDB.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
Highlighted
Micro Focus Expert
Micro Focus Expert

Thanks for sharing.

You can run this CLI

 omnidb -filesystem

This will give you a lists of the backed-up objects and then we can query for specific objects.

Here are examples (this is from WINDOWS)

omnidb -winfs

Object Name Object type
===============================================================================
apollo.prod.hpe.com:/C 'C: [PC COE]' WinFS
apollo.prod.hpe.com:/CONFIGURATION 'CONFIGURATION:' WinFS


omnidb -winfs apollo.prod.hpe.com:/C "C: [PC COE]"

SessionID Started Duration Object Status Size [KB] NumberOfErr
=============================================================================================
2013/11/14-3 13:13:58 00:00:08 Completed 132 0
2013/11/08-2 14:05:47 00:28:41 Completed 23779002 0
2013/11/08-1 13:54:23 00:00:08 Completed 4350 0


omnidb -winfs apollo.prod.hpe.com:/C "C: [PC COE]" -ses 2013/11/14-3 -catalog
Protection Owner Group Size [kB] Time Path
=======================================================================================
----r----- -2 -2 134976 27.04.2010 10:58:38 /Users/charlesshultz/Desktop/Documents/Technical Documentation/! Web Sites/dp/home/calvin.png

This is IDB query.

I have checked your screenshot and as in anything GUI, it is best to verify via CLI output.

 

RGds,

Sherman

DP Support

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.