Well I do not see any problem
The column 17 of any FRAG line is the same (1564717873). The same is the column 16 of the IMAGE line. The column 17 of every FRAG x 1 shows the expiration of the copy x.. bpdbm -ctime 1564717873 1564717873 = Fri Aug 2 06:51:13 2019 Run the command bpimmedia mediaid 061454 and observe the output. If you are using the same tape form backups then what you see is correct. Netbackup will use the same tape for duplications and backup, if it is in the same pool and the same retention level. stefanos From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of thomas.sch...@cortalconsors.de Sent: Thursday, September 15, 2011 9:27 AM To: smpt Cc: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Antwort: RE: bpduplicate - IMAGE and TAPE expire question Hi Stefanos. Thanks for your help. 1, Here the bpduplicate without the greps's bpimagelist -l -backupid myserver_xxxxxxxxxx IMAGE myserver 0 0 7 myserver_xxxxxxxxxx Retention_10J 0 *NULL* NetBackup Daily-Full 1 7 1249357873 11 1564717873 0 0 49760 17 4 4 1 Retention_10J_1249357873_INCR.f *NULL* *NULL* 0 1 0 0 0 *NULL* 0 0 0 538976288 0 0 0 *NULL* 0 0 0 *NULL* 472142 2 0 963 0 0 *NULL* *NULL* 0 0 0 HISTO -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 FRAG 1 1 49760 0 2 14 48 070725 media04 262144 7247241 1315735343 14 64 *NULL* 1564717873 0 65543 0 0 0 1 0 1315987690 0 b1f5640e72aa51f7bf01ea5ba3cb92819981e1a287c584cfbe11709799a557f4 *NULL* FRAG 2 1 49760 0 2 20 23 20471L media01 262144 1237520 1249331194 2 0 *NULL* 1564717873 0 65543 0 0 0 1 0 0 0 *NULL* *NULL* FRAG 3 1 49760 0 2 21 25 050328 media01 262144 1818959 1248649440 9 0 *NULL* 1564717873 0 65543 0 0 0 1 0 0 0 *NULL* *NULL* FRAG 4 1 49760 0 2 14 81 061454 media04 262144 7415348 1313879116 12 64 *NULL* 1564717873 0 65543 0 0 0 1 0 1315987690 0 0e803d0f3114779d5d6a0b2e9339e505683f8fca4f0be4a6b3b8caaa5771a59c *NULL* 2, Retentionlevels 0 31536000 1 4 1 year 1 1209600 2 2 2 weeks 2 2678400 1 3 1 month 3 8035200 3 3 3 months 4 189216000 6 4 6 years 5 8035200 3 3 3 months 6 16070400 6 3 6 months 7 315360000 10 4 10 years 8 31536000 1 4 1 year 9 2147483647 -1 -1 infinity 10 604800 1 2 1 week 11 63072000 2 4 2 years 12 94608000 3 4 3 years 13 259200 3 1 3 days 14 86400 1 1 1 day 15 946080000 30 4 30 years 16 346896000 11 4 11 year 17 2147483647 -1 -1 infinity 18 2147483647 -1 -1 infinity 19 2147483647 -1 -1 infinity 20 157680000 5 4 5 years 21 189216000 6 4 6 years 22 220752000 7 4 7 years 23 252288000 8 4 8 years 24 283824000 9 4 9 years 25 0 0 0 expires immediately 3, I used DSSU -> Disk Staging FRAG 1 = Disk Stage FRAG2 = LTO/3 ( Datacenter 1 ) FRAG3 = LTO/3 ( Datacenter 2 ) after duplication the FRAG 1 is deleted ( normal Netbackup feature ) Now i start the migration from LTO/3 to LTO/5 based on FRAG3 and Netbackup creates FRAG1 and FRAG4 on LTO/5. After successfull migration i delete FRAG2 and FRAG3. 4, My bpduplicte DATE=`date '+%d.%m.%y-%H:%m:%S.dup'` DUPE=/opt/openv/netbackup/bin/admincmd/bpduplicate OUTPUT=/opt/Migrate/Log $DUPE -cn 3 -M <NBUMASTER-SERVER> -number_copies 2 -dstunit Migrate-M04-local,Migrate-M04-remote -dp ENCR_Originale_10J,ENCR_Duplicates_10J -owner *ANY*,*ANY* -fail_on_error 0,0 -rl -1 -set_primary 1 -L $OUTPUT/$DATE -Bidfile /opt/Migrate/2009/bid -fork "smpt" <sm...@peppas.gr> 15.09.2011 08:13 An <thomas.sch...@cortalconsors.de>, <veritas-bu@mailman.eng.auburn.edu> Kopie Thema RE: [Veritas-bu] bpduplicate - IMAGE and TAPE expire question Can you post the command you use to duplicate the image and the retention level list Please post also the command ##bpimagelist -l -backupid myserver_xxxxxxxxxx (without the frep and the awk). Something is not ok. It seems that the first copy is on LTO5. Do you use staging or SLP? stefanos From: veritas-bu-boun...@mailman.eng.auburn.edu [ <mailto:veritas-bu-boun...@mailman.eng.auburn.edu> mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of thomas.sch...@cortalconsors.de Sent: Thursday, September 15, 2011 8:11 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] bpduplicate - IMAGE and TAPE expire question During data migration of retention 10 year IMAGES from LTO/3 to LTO/5 I noticed the old IMAGES (2009), written on the tape expires in 2021 and not in year 2019. I use Netbackup Enterprise Server 7.0.1, and in the version 6.0MP7 it works propertly. I will say I do this migration not the first time. Example: 1, Take a look an the migrated IMAGE myserver_xxxxxxxxxx from 08/04/2009. ##bpimagelist -U -backupid myserver_xxxxxxxxxx Backed Up Expires Files KB C Sched Type Policy ---------------- ---------- -------- -------- - ------------ ------------ 08/04/2009 05:51 08/02/2019 17 49760 N Differential Retention_10Year Here we see that the IMAGE is written in the year 2009 and expire in the year 2019. This is correct! 2, Now we search the written LTO/5 Tapes: ##bpimagelist -l -backupid myserver_xxxxxxxxxx | grep FRAG | awk '{print $9}' 070725 -> This is a new LTO/5 Tape 20471L -> old LTO/3 Tape ( First copy ) 050328 -> old LTO/3 Tape 061454 -> also a new LTO/5 Tape 3, Take a look on the expire date of the tapes ##bpmedialist -m 070725 Server Group = UNRESTRICTED_SHARING_GROUP id rl images allocated last updated density kbytes restores vimages expiration last read <------- STATUS -------> ---------------------------------------------------------------------------- ---- 070725 7 71 09/11/2011 12:02 09/15/2011 00:11 hcart2 2782457576 0 70 09/11/2021 05:22 N/A FULL ENCRYPTION ##bpmedialist -m 061454 Server Group = UNRESTRICTED_SHARING_GROUP id rl images allocated last updated density kbytes restores vimages expiration last read <------- STATUS -------> ---------------------------------------------------------------------------- ---- 061454 7 82 08/21/2011 00:25 09/14/2011 20:14 hcart2 1927440342 0 81 09/11/2021 05:20 N/A FULL ENCRYPTION We see that the expire date of the LTO/5 Tapes is in the Year 2021 and not in the Year 2019. What is my ( or the Netbackup ) problem ? Cortal Consors S.A. Zweigniederlassung Deutschland, Bahnhofstraße 55, D-90402 Nürnberg, HR Nürnberg B 20075, USt-IdNr. DE225900761 Sitz der Cortal Consors S.A.: 1, boulevard Haussmann, F-75318 Paris cedex 09, Registergericht: R.C.S. Paris 327 787 909 Président du Conseil d'Administration (Verwaltungsratsvorsitzender) und Directeur Général (Generaldirektor) der Cortal Consors S.A.: Olivier Le Grand Leitung der Zweigniederlassung Deutschland: Hugues Colmant (CEO), Kai Friedrich, Richard Döppmann Before printing, think about environmental responsibility! Bitte denken Sie über Ihre Verantwortung gegenüber der Umwelt nach, bevor Sie diese E-Mail ausdrucken. Cortal Consors S.A. Zweigniederlassung Deutschland, Bahnhofstraße 55, D-90402 Nürnberg, HR Nürnberg B 20075, USt-IdNr. DE225900761 Sitz der Cortal Consors S.A.: 1, boulevard Haussmann, F-75318 Paris cedex 09, Registergericht: R.C.S. Paris 327 787 909 Président du Conseil d'Administration (Verwaltungsratsvorsitzender) und Directeur Général (Generaldirektor) der Cortal Consors S.A.: Olivier Le Grand Leitung der Zweigniederlassung Deutschland: Hugues Colmant (CEO), Kai Friedrich, Richard Döppmann Before printing, think about environmental responsibility! Bitte denken Sie über Ihre Verantwortung gegenüber der Umwelt nach, bevor Sie diese E-Mail ausdrucken.
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
