cancel
Showing results for 
Search instead for 
Did you mean: 

"bpimagelist " and "bpimmedia" Showing different output after image expire

shanuintouch
Level 4

Hi All,

Thank you for your always support and guidance.

Currently I am checking some behavior for the image expiration.

I Configured the retention level for 1Day, and performed the AIR operation.

There is some strange behavior I saw in the output of "bpimagelist " and "bpimmedia".

Please see the below output

Before expiration

[root@jpvm126 ~]#  /usr/openv/netbackup/bin/admincmd/bpimagelist -L -backupid jpvm126_1487191322

Client:            jpvm126
Backup ID:         jpvm126_1487191322
Policy:            Policy_A
Policy Type:       Standard (0)
Proxy Client:      (none specified)
Creator:           root
Name1:             (none specified)
Sched Label:       Schedule_A
Schedule Type:     FULL (0)
Retention Level:   1 day (11)
Backup Time:       Thu 16 Feb 2017 02:12:02 AM IS (1487191322)
Elapsed Time:      31 second(s)
Expiration Time:   Fri 17 Feb 2017 02:12:02 AM IS (1487277722)
[root@jpvm126 ~]# /usr/openv/netbackup/bin/admincmd/bpimmedia -dp Test_Dp_A -stype NEC_HYDRA
IMAGE jpvm126 jpvm126_1487167144 Policy_A 0 0  0
FRAG 1 -2147482648 1489845544 6 Test_Dp_A Test_Lsu jpvm126 0
FRAG 1 -1 1489845544 6 Test_Dp_A Test_Lsu jpvm126 0
FRAG 1 1 1489845544 6 Test_Dp_A Test_Lsu jpvm126 0
IMAGE jpvm126 jpvm126_1487191322 Policy_A 0 0  0----------------> This is the Image
FRAG 1 -2147482648 1487277722 6 Test_Dp_A Test_Lsu jpvm126 0
FRAG 1 -1 1487277722 6 Test_Dp_A Test_Lsu jpvm126 0
FRAG 1 1 1487277722 6 
Test_Dp_A Test_Lsu jpvm126 0

 After Expiration

After expiration, I can see some strange behavior

  1. In bpimagelist i can see the information of expired image along with changed Expiration date.
  2. In bpimmedia there is no information regarding the expired image.
[root@jpvm126 ~]#  /usr/openv/netbackup/bin/admincmd/bpimagelist -L -backupid jpvm126_1487191322

Client:            jpvm126
Backup ID:         jpvm126_1487191322
Policy:            Policy_A
Policy Type:       Standard (0)
Proxy Client:      (none specified)
Creator:           root
Name1:             (none specified)
Sched Label:       Schedule_A
Schedule Type:     FULL (0)
Retention Level:   1 day (11)
Backup Time:       Thu 16 Feb 2017 02:12:02 AM IS (1487191322)
Elapsed Time:      31 second(s)
Expiration Time:   Sat 18 Feb 2017 02:12:02 AM IS (1487364122)
Maximum Expiration Time:   Thu 01 Jan 1970 05:30:00 AM IS (0)
Compressed:        no
Client Encrypted:  no
Kilobytes:         2097185
[root@jpvm126 ~]# /usr/openv/netbackup/bin/admincmd/bpimmedia -dp Test_Dp_A -stype NEC_HYDRA
IMAGE jpvm126 jpvm126_1487167144 Policy_A 0 0  0
FRAG 1 -2147482648 1489845544 6 Test_Dp_A Test_Lsu jpvm126 0
FRAG 1 -1 1489845544 6 Test_Dp_A Test_Lsu jpvm126 0
FRAG 1 1 1489845544 6 Test_Dp_A Test_Lsu jpvm126 0
[root@jpvm126 ~]#

 

So can you please make me clear about this starnge behavior(at least it is strange for me)

 

And there is one more thing, If I use NBU GUI, i can check the information through GUI catalog screen, but which command is equivalent it, bpimagelist or bpimmedia or something else?

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

When last did an Image Cleanup job run?
I would only expect complete image removal after Image Cleanup.

You also forgot to mention your version of NetBackup?
Always good to check Late Breaking News for bugs or 'known issues' with image expiration for your particular version.

View solution in original post

10 REPLIES 10

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

 

Please show us full bpimagelist output, not just a snippet. 

Dear @Marianne,

Here is the complete ouput of bpimagelist

Before expiration

[root@jpvm126 ~]#  /usr/openv/netbackup/bin/admincmd/bpimagelist -L -backupid jpvm126_1487191322

Client:            jpvm126
Backup ID:         jpvm126_1487191322
Policy:            Policy_A
Policy Type:       Standard (0)
Proxy Client:      (none specified)
Creator:           root
Name1:             (none specified)
Sched Label:       Schedule_A
Schedule Type:     FULL (0)
Retention Level:   1 day (11)
Backup Time:       Thu 16 Feb 2017 02:12:02 AM IS (1487191322)
Elapsed Time:      31 second(s)
Expiration Time:   Fri 17 Feb 2017 02:12:02 AM IS (1487277722)
Maximum Expiration Time:   Fri 17 Feb 2017 02:12:02 AM IS (1487277722)
Compressed:        no
Client Encrypted:  no
Kilobytes:         2097185
Number of Files:   4
Number of Copies:  1
Number of Fragments:   3
Histogram:         0 0 0 0 0 0 0 0 0 0
DB Compressed:     no
Files File Name:   Policy_A_1487191322_FULL.f
Previous Backup Files File Name:   (none specified)
Parent Backup Image File Name:   (none specified)
SW Version:        (none specified)
Options:           0x0
MPX:               0
TIR Info:          0
TIR Expiration:    Thu 01 Jan 1970 05:30:00 AM IS (0)
Keyword:           (none specified)
Ext Security Info: no
File Restore Raw:  no
Image Dump Level:  0
File System Only:  no
Object Descriptor: (none specified)
Previous BI Time:  Thu 01 Jan 1970 05:30:00 AM IS (0)
BI Full Time:      Thu 01 Jan 1970 05:30:00 AM IS (0)
Request Pid:       0
Backup Status:     0
Stream Number:     0
Backup Copy:       Standard (0)
Files File size:     1100
PFI type:     0
IMAGE_ATTRIBUTE:     0
Primary Copy:      1
Image Type:        0  (Regular)
Job ID:            6
Num Resumes:       0
Resume Expiration: Thu 01 Jan 1970 05:30:00 AM IS (0)
Data Classification:    (none specified)
Data_Classification_ID: (none specified)
Storage Lifecycle Policy:    SLP_Cascade
Storage Lifecycle Policy Version:    1
STL_Completed:      3
Remote Expiration Time: Thu 01 Jan 1970 05:30:00 AM IS (0)
Origin Master Server:  (none specified)
Origin Master GUID:    (none specified)
Snap Time:      Thu 01 Jan 1970 05:30:00 AM IS (0)
IR Enabled:      no
Client Character Set:     1
Image On Hold:     0
Kilobytes Data Transferred:   0
Copy number:       1
 Fragment:         IM (-2147482648)
 Kilobytes:        1
 Remainder:        231
 Media Type:       Disk (0)
 Density:          qscsi (0)
 File Num:         0
 ID:               @aaag2
 Host:             jpvm126
 Block Size:       262144
 Offset:           0
 Media Date:       Thu 01 Jan 1970 05:30:00 AM IS (0)
 Dev Written On:   -1
 Flags:            0x100  
 Media Descriptor:        1;NEC_HYDRA;machine1;Test_Dp_A;Test_Lsu;0
 checkpoint:       0
 resume num:       0
 Key tag:          *NULL*
 STL tag:          *NULL*
 Copy on hold:     0
Copy number:       1
 Fragment:         TIR (-1)
 Kilobytes:        1
 Remainder:        76
 Media Type:       Disk (0)
 Density:          qscsi (0)
 File Num:         0
 ID:               @aaag2
 Host:             jpvm126
 Block Size:       262144
 Offset:           0
 Media Date:       Thu 01 Jan 1970 05:30:00 AM IS (0)
 Dev Written On:   -1
 Flags:            0x80  
 Media Descriptor:        1;NEC_HYDRA;machine1;Test_Dp_A;Test_Lsu;0
 checkpoint:       0
 resume num:       0
 Copy on hold:     0
Copy number:       1
 Fragment:         1
 Kilobytes:        2097184
 Remainder:        0
 Media Type:       Disk (0)
 Density:          qscsi (0)
 File Num:         0
 ID:               @aaag2
 Host:             jpvm126
 Block Size:       262144
 Offset:           0
 Media Date:       Thu 01 Jan 1970 05:30:00 AM IS (0)
 Dev Written On:   -1
 Flags:            0x0  
 Media Descriptor:        1;NEC_HYDRA;machine1;Test_Dp_A;Test_Lsu;0
 Expiration Time:  Fri 17 Feb 2017 02:12:02 AM IS (1487277722)
 MPX:              0
 retention_lvl:    1 day (11)
 Try to Keep Time:  Fri 17 Feb 2017 02:12:02 AM IS (1487277722)
 Copy Creation Time:  Thu 16 Feb 2017 02:12:33 AM IS (1487191353)
 Data Format:      Tar
 checkpoint:       0
 resume num:       0
 Copy on hold:     0

After expiration

[root@jpvm126 ~]#  /usr/openv/netbackup/bin/admincmd/bpimagelist -L -backupid jpvm126_1487191322

Client:            jpvm126
Backup ID:         jpvm126_1487191322
Policy:            Policy_A
Policy Type:       Standard (0)
Proxy Client:      (none specified)
Creator:           root
Name1:             (none specified)
Sched Label:       Schedule_A
Schedule Type:     FULL (0)
Retention Level:   1 day (11)
Backup Time:       Thu 16 Feb 2017 02:12:02 AM IS (1487191322)
Elapsed Time:      31 second(s)
Expiration Time:   Sat 18 Feb 2017 02:12:02 AM IS (1487364122)
Maximum Expiration Time:   Thu 01 Jan 1970 05:30:00 AM IS (0)
Compressed:        no
Client Encrypted:  no
Kilobytes:         2097185
Number of Files:   4
Number of Copies:  0
Number of Fragments:   0
Histogram:         0 0 0 0 0 0 0 0 0 0
DB Compressed:     no
Files File Name:   Policy_A_1487191322_FULL.f
Previous Backup Files File Name:   (none specified)
Parent Backup Image File Name:   (none specified)
SW Version:        (none specified)
Options:           0x0
MPX:               0
TIR Info:          0
TIR Expiration:    Thu 01 Jan 1970 05:30:00 AM IS (0)
Keyword:           (none specified)
Ext Security Info: no
File Restore Raw:  no
Image Dump Level:  0
File System Only:  no
Object Descriptor: (none specified)
Previous BI Time:  Thu 01 Jan 1970 05:30:00 AM IS (0)
BI Full Time:      Thu 01 Jan 1970 05:30:00 AM IS (0)
Request Pid:       0
Backup Status:     0
Stream Number:     0
Backup Copy:       Standard (0)
Files File size:     1100
PFI type:     0
IMAGE_ATTRIBUTE:     0
Primary Copy:      1
Image Type:        0  (Regular)
Job ID:            6
Num Resumes:       0
Resume Expiration: Thu 01 Jan 1970 05:30:00 AM IS (0)
Data Classification:    (none specified)
Data_Classification_ID: (none specified)
Storage Lifecycle Policy:    SLP_Cascade
Storage Lifecycle Policy Version:    1
STL_Completed:      3
Remote Expiration Time: Thu 01 Jan 1970 05:30:00 AM IS (0)
Origin Master Server:  (none specified)
Origin Master GUID:    (none specified)
Snap Time:      Thu 01 Jan 1970 05:30:00 AM IS (0)
IR Enabled:      no
Client Character Set:     1
Image On Hold:     0
Kilobytes Data Transferred:   0

 

 And one more thing after expiration, there is no information regariding the copy.

Nicolai
Moderator
Moderator
Partner    VIP   

A Netbackup image under  SLP control will have infinity retention until SLP has been completed.

When you expire a image or a copy of a image, all references in Netbackup will be removed as well.

But yes, it do look a bit funny having a image with 0 copies.

@Nicolai,

Sorry for my lack of understanding.

I am still confused about what is happening :(


@Nicolai wrote:

A Netbackup image under  SLP control will have infinity retention until SLP has been completed.

When you expire a image or a copy of a image, all references in Netbackup will be removed as well.

But yes, it do look a bit funny having a image with 0 copies.



As i set expiration fro 1 day, so images should be removed from the NBU, as it was deleted from the storage deivce.

So doesn't it make inconsistent? On storage device there is no image, but in bpimagelist, it is available where as in bpimmedia it is not.

can you please make me more clear?

And i asked one more thing do you any idea about equivlaent command for GUI catalog screen?

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

When last did an Image Cleanup job run?
I would only expect complete image removal after Image Cleanup.

You also forgot to mention your version of NetBackup?
Always good to check Late Breaking News for bugs or 'known issues' with image expiration for your particular version.

Nicolai
Moderator
Moderator
Partner    VIP   

As Marianne also mention, I suspect it's related to image cleanup. By default Netbackup carry out image clean every 12 hours. 

You can start iameg clean by runnign the follwoing commands:

bpimage -cleanup -allclients
nbdelete -allvolumes -force

Nicolai
Moderator
Moderator
Partner    VIP   

There are no 100% GUI equivalent to bpimagelist or bpimmedia.

Under reports some bpimmedia like report can be found (e.g images on disk)

Hi @Marianne,

Thanks for your suggestions.

I am using NetBackup 7.7.3. Is there any image expiration issue in this version?

 Hi @Nicolai

I executed

bpimage -cleanup -allclients
nbdelete -allvolumes -force

But still the result is same.

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I don't see any image cleanup issues in LBN.
All LBN links: http://www.veritas.com/docs/000040237

7.7.3 Late Breaking News: http://www.veritas.com/docs/000108139

I see that the STL_Completed status is 3 ( COMPLETED ) 
But there may still be cleanup of SLP info that has not yet completed. Not quite sure how that works.

If this image is still around in another 12 hours, I suggest you log a Support call with Veritas.
(They will probably ask for lots of logs at max logging levels...) 

Dear @Marianne and All,

 

Thanks for your support.

All the expired images has been cleaned up. I think, NBU took some time to clean the images.