Forum Discussion

ianhoskins's avatar
ianhoskins
Level 4
9 years ago

List Images On DiskPool Before Phase I Import

Is there a way to query a diskpool to get a list of images on it before I initiate a Phase I import? 
I am hesitant to run the Phase I import until I have time to finish the Phase II import as I have been burned in the past where NBU will expire the images off disk because the Phase I sets a 1 week retention on the images in the catalog.
The diskpool I want to query if from a legacy NBU environment that has been decommisioned.
 

I was hoping I could use bpstsinfo to grab the info, but it requires a mediaid which isn't created until Phase I

NBU 7.6.0.2 on RHL

7.6
Backup and Recovery
Linux
NetBackup
Tip-How to
  • Amol_Nair's avatar
    Amol_Nair
    9 years ago
    As far as I know the disk media id is generated as soon as you add disk volumes in netbackup.. It wouldn't really wait for you to run phase 1 import.. run the "nbdevquery -listdv" command and it should list the media id that you are looking for.

24 Replies

Sort By
Replies have been turned off for this discussion
  • mph999's avatar
    mph999
    Level 6
    9 years ago

    No, NBU knows nothing about the images, so the only way is to run phase 1 import.

    If the storage is basic or advanced disk, you could just run ls -al (Unix) or dir (win) directly on the 'disk' and look at the filenames.

  • ianhoskins's avatar
    ianhoskins
    Level 4
    9 years ago

    Thanks Martin, so after the Phase I import can I extend the retention using bpexpdate on the images so I can have more time to get the Phase II done?

  • sdo's avatar
    sdo
    Moderator
    9 years ago

    I've just done a test:

    - backup to basic disk STU on master "A" Windows 2008 R2 SP1 NetBackup Server v7.6.1.2 - backup of some files with 1 day retention

    - CIFS/SMB network copy of backup image files to basic disk STU on master "B" Windows 2012 R2 NetBackup Server v7.7

    - phase 1 import on master "B"

    - on master "B" - bpimagelist -d 01/01/1970 00:00:00 -option ONLY_PRE_IMPORT, to get the image ID, then a bpimagelist -backupid blah -L -option ONLY_PRE_IMPRT, which shows expiring tomorrow.

    - on master "B" - bpexpdate -backupid blah -d 31/12/2015 23:59:59

    - on master "B" - bpimagelist -backupid blah -L -option ONLY_PRE_IMPORT

    ...which shows new/correct future date.

    .

    I would think that catalog behaviour/functionality is irrespective of storage unit type and irrespective of OS upon which NetBackup Server is running, so I think you'll be ok be doing a phase 1 import and then setting a future date (...unless anyone on here knows different?).

  • ianhoskins's avatar
    ianhoskins
    Level 4
    9 years ago

    Interesting, because I thought Phase I import didn't read in retention, so where did your retention of 1 day come from?  I though after a Phase I there was a generic 1 week retention on the image until a Phase II was done and then the "real" retention was applied.

  • sdo's avatar
    sdo
    Moderator
    9 years ago

    Maybe I missed that - let me test again...

  • Amol_Nair's avatar
    Amol_Nair
    Level 6
    9 years ago
    If the storage server is added in netbackup then you could try running the bpstsinfo command that could help you list the images i.e. backupid of images present on the ost.. This command is usually used to compare and get a list of images present in Netbackup catalog vs images only on the storage and helps in identifying orphan images. But this could help you get the list of images that you are looking for "bpstsinfo -comparedbandstu -storage_server < storage_server > -stype < server_type > -lsuname < lsu_name >" To get the server_type and the lsu_name you can use the nbdevquery commads
  • sdo's avatar
    sdo
    Moderator
    9 years ago

    Testing with two backup images copies, after phase 1 import, I see:

    D:\>bpimagelist -idonly -d 01/01/1970 00:00:00 -option ONLY_PRE_IMPORT -L | findstr /i "^$ ^Backup Expir Copy"

Backup ID:         hserver_1438887221
Backup Time:            06/08/2015 19:53:41 (1438887221)
Expiration Time:        13/08/2015 20:13:17 (1439493197)
Maximum Expiration Time:        13/08/2015 20:13:17 (1439493197)
TIR Expiration:         01/01/1970 00:00:00 (0)
Backup Status:     0
Backup Copy:       Standard (0)
Primary Copy:      1
Resume Expiration:      01/01/1970 00:00:00 (0)
Remote Expiration Time:      01/01/1970 00:00:00 (0)
Copy number:       1
 Expiration Time:       13/08/2015 20:13:17 (1439493197)
 Copy Creation Time:       01/01/1970 00:00:00 (0)
 Copy on hold:     0

Backup ID:         hserver_1438881613
Backup Time:            06/08/2015 18:20:13 (1438881613)
Expiration Time:        13/08/2015 20:13:16 (1439493196)
Maximum Expiration Time:        13/08/2015 20:13:16 (1439493196)
TIR Expiration:         01/01/1970 00:00:00 (0)
Backup Status:     0
Backup Copy:       Standard (0)
Primary Copy:      1
Resume Expiration:      01/01/1970 00:00:00 (0)
Remote Expiration Time:      01/01/1970 00:00:00 (0)
Copy number:       1
 Expiration Time:       13/08/2015 20:13:16 (1439493196)
 Copy Creation Time:       01/01/1970 00:00:00 (0)
 Copy on hold:     0

    ....so, yes, expiration is one week in the future for the image header and the copy details...

    ...now setting one image to expire at end of year...

    D:\>bpexpdate -backupid hserver_1438881613 -d 31/12/2015 23:59:59
Are you SURE you want to change hserver_1438881613
to expire on      31/12/2015 23:59:59 y/n (n)? y​

    ...and now the imagelist command shows...

    D:\>bpimagelist -idonly -d 01/01/1970 00:00:00 -option ONLY_PRE_IMPORT -L | findstr /i "^$ ^Backup Expir Copy"

Backup ID:         hserver_1438887221
Backup Time:            06/08/2015 19:53:41 (1438887221)
Expiration Time:        13/08/2015 20:13:17 (1439493197)
Maximum Expiration Time:        13/08/2015 20:13:17 (1439493197)
TIR Expiration:         01/01/1970 00:00:00 (0)
Backup Status:     0
Backup Copy:       Standard (0)
Primary Copy:      1
Resume Expiration:      01/01/1970 00:00:00 (0)
Remote Expiration Time:      01/01/1970 00:00:00 (0)
Copy number:       1
 Expiration Time:       13/08/2015 20:13:17 (1439493197)
 Copy Creation Time:       01/01/1970 00:00:00 (0)
 Copy on hold:     0

Backup ID:         hserver_1438881613
Backup Time:            06/08/2015 18:20:13 (1438881613)
Expiration Time:        31/12/2015 23:59:59 (1451606399)
Maximum Expiration Time:        31/12/2015 23:59:59 (1451606399)
TIR Expiration:         01/01/1970 00:00:00 (0)
Backup Status:     0
Backup Copy:       Standard (0)
Primary Copy:      1
Resume Expiration:      01/01/1970 00:00:00 (0)
Remote Expiration Time:      01/01/1970 00:00:00 (0)
Copy number:       1
 Expiration Time:       31/12/2015 23:59:59 (1451606399)
 Copy Creation Time:       01/01/1970 00:00:00 (0)
 Copy on hold:     0

    ....so it does appear to have worked - but probably best to wait one day and re-check (to see if some background processes 'change' things for us)... and/or wait a week - and see if the unchanged phase 1 image expires, and hopefully the updated phase 1 image will hang around.  Hmm... I have a VM - I'll shutdown, snapshot, reboot, change date to two weeks in the future, stop/restart NetBackup, and see if image still exists...

  • ianhoskins's avatar
    ianhoskins
    Level 4
    9 years ago

    Yea I looked at that option earlier but unfortunatly -media_id is required.  Since it hasn't done a Phase I yet there is no Media ID defined for it