Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

unable to increase retention period of backup image

Created: 20 Apr 2013 • Updated: 20 Apr 2013 | 7 comments
This issue has been solved. See solution.

Hi Fellas

master , media, client OS linux  NBU ver 7.1.0.2 , backup goes to data domain box model number DD670 -- copy 1, then duplication to tape. copy 2 n copy 3. customer requested to increase retention period of backup image which is on DD box. 

first used bpimagelist to determine images for particular client.

then used bpexpdate -recalculate -backupid <servername_134665620821> -copy 1 -d 09/02/2013 13:00:00 -force .it executed successfully. but problem is when i tried to cross verify after 4 hrs that retention period increased on backup image or not it still shows the same retention period.

could not understand why it is so even though bpexpdate was successfully executed.

 

???????????

Operating Systems:

Comments 7 CommentsJump to latest comment

RamNagalla's picture

what is the primary copy, bpimagelist shows the primary copy when you run the command with -U

show us the output of below command

bpimagelist -backupid <backupid> -L

rookie11's picture

output:

 

[root@master admincmd]# sudo ./bpimagelist -backupid servername_134665620821 -L | more
 
Client:            servername
Backup ID:         servername_134665620821
Policy:            policyname
Policy Type:       NDMP (19)
Proxy Client:      (none specified)
Creator:           root
Name1:             (none specified)
Sched Label:       FULL
Schedule Type:     FULL (0)
Retention Level:   5 weeks (0)
Backup Time:       Wed 17 Apr 2013 10:20:13 AM ED (134665620821)
Elapsed Time:      607 second(s)
Expiration Time:   Wed 22 May 2013 10:20:13 AM ED (1369232413)
Compressed:        no
Client Encrypted:  no
Kilobytes:         47583574
Number of Files:   843447
Number of Copies:  2
Number of Fragments:   4
Histogram:         -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
DB Compressed:     yes
Files File Name:   policyname_134665620821_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:    Wed 31 Dec 1969 07:00:00 PM ES (0)
Keyword:           REQ000000379854
Ext Security Info: no
File Restore Raw:  no
Image Dump Level:  0
File System Only:  no
Object Descriptor: (none specified)
Previous BI Time:  Wed 31 Dec 1969 07:00:00 PM ES (0)
BI Full Time:      Wed 31 Dec 1969 07:00:00 PM ES (0)
Request Pid:       0
Backup Status:     0
Stream Number:     0
Backup Copy:       Standard (0)
Files File size:     40511449
PFI type:     0
IMAGE_ATTRIBUTE:     0
Primary Copy:      1
Image Type:        0  (Regular)
Job ID:            2325015
Num Resumes:       1
Resume Expiration: Wed 31 Dec 1969 07:00:00 PM ES (0)
Data Classification:    BC
Data_Classification_ID: EBDBF76A6F6611E09FE22EFCD366722F
Storage Lifecycle Policy:    DD-ndmp-full
Storage Lifecycle Policy Version:    9
STL_Completed:      3
Remote Expiration Time: Wed 31 Dec 1969 07:00:00 PM ES (0)
Origin Master Server:  (none specified)
Origin Master GUID:    (none specified)
Snap Time:      Wed 31 Dec 1969 07:00:00 PM ES (0)
Copy number:       1
 Fragment:         TIR (-1)
 Kilobytes:        116310
 Remainder:        585
 Media Type:       Disk (0)
 Density:          qscsi (0)
 File Num:         0
 ID:               @aaaab
 Host:             mediaserver
 Block Size:       262144
 Offset:           0
 Media Date:       Wed 31 Dec 1969 07:00:00 PM ES (0)
 Dev Written On:   -1
 Flags:            0x0
 checkpoint:       0
 resume num:       0
 Key tag:          *NULL*
 STL tag:          0
Copy number:       1
 Fragment:         1
 Kilobytes:        47467264
 Remainder:        0
 Media Type:       Disk (0)
 Density:          qscsi (0)
 File Num:         0
 ID:               @aaaab
 Host:             mediaserver
 Block Size:       262144
 Offset:           0
 Media Date:       Wed 31 Dec 1969 07:00:00 PM ES (0)
 Dev Written On:   -1
 Flags:            0x0
 Expiration Time:  Mon 01 Jul 2013 10:10:00 AM ED (1372687800)
 MPX:              0
 retention_lvl:    5 weeks (0)
 Try to Keep Time:  Wed 22 May 2013 10:20:13 AM ED (1369232413)
 Copy Creation Time:  Wed 17 Apr 2013 10:30:20 AM ED (1366209020)
 checkpoint:       0
 resume num:       0
Copy number:       2
 Fragment:         TIR (-1)
 Kilobytes:        116311
 Remainder:        0
 Media Type:       Media Manager (2)
 Density:          hcart (6)
 File Num:         2
 ID:               WD1028
 Host:             usa0300lx878
 Block Size:       262144
 Offset:           185423
 Media Date:       Wed 17 Apr 2013 10:36:54 AM ED (1366209414)
 Dev Written On:   21
 Flags:            0x0
 Media Descriptor:        ?
 checkpoint:       0
 resume num:       0
 Key tag:          *NULL*
 STL tag:          *NULL*
Copy number:       2
 Fragment:         1
 Kilobytes:        47467264
 Remainder:        0
 Media Type:       Media Manager (2)
 Density:          hcart (6)
 File Num:         1
 ID:               WD1028
 Host:             usa0300lx878
 Block Size:       262144
 Offset:           2
 Media Date:       Wed 17 Apr 2013 10:36:54 AM ED (1366209414)
 Dev Written On:   21
 Flags:            0x0
 Media Descriptor:        ?
 Expiration Time:  Wed 22 May 2013 10:20:13 AM ED (1369232413)
 MPX:              0
 retention_lvl:    5 weeks (0)
 Try to Keep Time:  Wed 22 May 2013 10:20:13 AM ED (1369232413)
 Copy Creation Time:  Wed 17 Apr 2013 10:59:41 AM ED (1366210781)
 checkpoint:       0
 resume num:       0
 
RamNagalla's picture

hi,

you have 2 copies for the image servername_134665620821, and both images are with the retenction level 0 , 5 weeks.

backup date:- Wed 17 Apr 2013 10:20:13 AM ED (134665620821)

copy 1 expire date is :- "Expiration Time:  Mon 01 Jul 2013 10:10:00 AM ED (1372687800)"  --> around 10 weeks from backup

copy 2 expire date is :- Expiration Time:  Wed 22 May 2013 10:20:13 AM ED (1369232413)-----> 5 weeks from backup date

so its been chaged and updated... you would need to make sure and cross check that its not been updated again with in the 4 hours..(check with your team)

 

 

SOLUTION
SamRose's picture

 

hi guys

i need your help anyone of you there, i have server windows7 ultimate 64bit, C\:drive-500GIG, D:\Drive-500GIG(Archive), S:\Drive(RAID5)-4T(Storage), I take image for back up using Norton ghost 11.0 is no problem. now I re-image the server there have problem in the hard drive, the D:\Drive become S:\Drive, and the S:\Drive become D:\Drive is twisted by itself, i have 3 times to re-image is the same result. why is twisted by itself? i need your helf guys.thnz

rookie11's picture

it means when i ran bpimagelist backupid -U 

 

it showed retention period of only primary copy

RamNagalla's picture

yes.. it does..

hope it answers your questions..