08-28-2015 05:18 AM
Hi All,
I noticed that many of the expired imges are still visible in the Client Backup View and from restore but not visible in catalog and we could see the image details using bpimagelist command . Any idea why these images are still reported.
08-28-2015 05:23 AM
Question.....why do you think the images are expired, if you can see them with bpimagelist?
08-28-2015 05:27 AM
Please show us what you see - post output of one image-id that seems to be expired:
bpimagelist -backupid <client_10-digit-number> -L
08-28-2015 05:31 AM
Yes, those images already expired as per retention and not visible in catalog. but i am not sure why those images are still appering in restore window.
08-28-2015 06:14 AM
I think what you may be missing is changing the 'copy' number in the catalog GUI function / view.
It sounds like the images are definitely there - but you are probably not selecting the correct copy number for the catalog view.
08-28-2015 06:32 AM
Client: XXXXXXX
Backup ID: XXXXXXX
Policy: XXXXXXX
Policy Type: Oracle (4)
Proxy Client: (none specified)
Creator: oracle
Name1: (none specified)
Sched Label: Default-Application-Backup
Schedule Type: UBAK (2)
Retention Level: 2 weeks (1)
Backup Time: Wed Jan 29 18:50:23 2014 (1391039423)
Elapsed Time: 307 second(s)
Expiration Time: INFINITY (2147483647)
Compressed: no
Client Encrypted: no
Kilobytes: 52256
Number of Files: 1
Number of Copies: 2
Number of Fragments: 2
Histogram: 0 0 0 0 0 0 0 0 0 0
DB Compressed: no
Files File Name: XXXXXXX
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: Wed Dec 31 19:00:00 1969 (0)
Keyword: XXXX
Ext Security Info: no
File Restore Raw: no
Image Dump Level: 0
File System Only: no
Object Descriptor: (none specified)
Previous BI Time: Wed Dec 31 19:00:00 1969 (0)
BI Full Time: Wed Dec 31 19:00:00 1969 (0)
Request Pid: 0
Backup Status: 0
Stream Number: 0
Backup Copy: Standard (0)
Files File size: 647
PFI type: 0
IMAGE_ATTRIBUTE: 0
Primary Copy: 1
Image Type: 0 (Regular)
Job ID: 1795995
Num Resumes: 1
Resume Expiration: Wed Dec 31 19:00:00 1969 (0)
Data Classification: (none specified)
Data_Classification_ID: (none specified)
Storage Lifecycle Policy: XXXXXXX
Storage Lifecycle Policy Version: 0
STL_Completed: 3
Remote Expiration Time: Wed Dec 31 19:00:00 1969 (0)
Origin Master Server: (none specified)
Origin Master GUID: (none specified)
Snap Time: Wed Dec 31 19:00:00 1969 (0)
IR Enabled: no
Client Character Set: 0
Image On Hold: 0
Indexing Status: 0
Copy number: 1
Fragment: 1
Kilobytes: 52256
Remainder: 0
Media Type: Disk (0)
Density: qscsi (0)
File Num: 0
ID: @aaaay
Host: XXXXXXX
Block Size: 262144
Offset: 0
Media Date: Wed Dec 31 19:00:00 1969 (0)
Dev Written On: -1
Flags: 0x0
Media Descriptor: 1;XXXXXXX
Expiration Time: Wed Feb 12 18:50:23 2014 (1392249023)
MPX: 0
retention_lvl: 2 weeks (1)
Try to Keep Time: Wed Feb 12 18:50:23 2014 (1392249023)
Copy Creation Time: Wed Jan 29 18:55:30 2014 (1391039730)
Data Format: Tar
checkpoint: 0
resume num: 0
Key tag: *NULL*
STL tag: *NULL*
Copy on hold: 0
Copy number: 2
Fragment: 1
Kilobytes: 52256
Remainder: 0
Media Type: Disk (0)
Density: qscsi (0)
File Num: 0
ID: @aaaaI
Host: XXXXXXXX
Block Size: 262144
Offset: 0
Media Date: Wed Dec 31 19:00:00 1969 (0)
Dev Written On: -1
Flags: 0x0
Media Descriptor: 1;XXXXXXXX
Expiration Time: Fri May 02 19:50:23 2014 (1399074623)
MPX: 0
retention_lvl: 3 months (5)
Try to Keep Time: Fri May 02 19:50:23 2014 (1399074623)
Copy Creation Time: Tue Feb 11 11:28:27 2014 (1392136107)
Data Format: Tar
checkpoint: 0
resume num: 1
Key tag: *NULL*
STL tag: *NULL*
Copy on hold: 0
I have checked all the copies in netbackup catalog but its not listing in catalog....
08-28-2015 09:01 AM
Ok - that's pretty wierd. Looks like they should have expired a long time ago.
My guess is that the Storage Servers, or disk pools, that were @aaaay and @aaaal were removed and that image cleanup has never been able to tidy-up.
If you run:
nbdevquery -liststs nbdevquery -listdp nbdevquery -listdv -dp my_dp_name -stype my_dp_type
...do you see the disk pool monikers @aaaay and @aaaal ?
.
Also, it might be worth running an "nbcc" consistency check, which is documented in the commands reference manual.
08-30-2015 02:26 AM
Retention Level: 2 weeks (1)
Backup Time: Wed Jan 29 18:50:23 2014 (1391039423)
Elapsed Time: 307 second(s)
Expiration Time: INFINITY (2147483647)
Storage Lifecycle Policy: XXXXXXX
Storage Lifecycle Policy Version: 0
Looks to me like a unfinisched SLP - what SLP does XXXXXXX point to ?
A backup image under SLP control will have infinity retension until it is successful compleated, first then is the orginal retension applied.
The "Retention level 2 weeks" is the default level, but overridden by SLP retention.
08-30-2015 04:24 AM
Which is weird because:
STL_Completed | 3 | The status of the Storage Lifecycle processing for the image: 0 = NOT SLP MANAGED, 1 = NOT STARTED, 2 = IN PROCESS, 3 = COMPLETED. |
09-03-2015 12:33 AM
Agree, we need the user to provide more details.