none
How to disable Tape Inventory? RRS feed

  • Question

  • I have Monthly backup job which writes around 2TB data to a single tape from different PGs (CO-located to a single Tape)

    Since 2 TB data is from 16 Protection groups so its take around two days to complete. Today is 2nd of July and tape job was about to finished, 1900 GB was written and few data was left. Suddenly Tape inventory run and below error occured :

    Status: Active

    Tape Library : Hewlett Packard MSL G3 Series library  (x64 based)

    Tape: Hosted: Monthly Backup-00000014 (FQG667L5)

    Description: Detailed tape inventory failed Operation failed since the slot 22 in library Hewlett Packard MSL G3 Series library  (x64 based) was empty. This tape is currently present in Drive Hewlett Packard LTO Ultrium-5 drive 

    This tape in slot 22 was in use and when this error occured, current tape was marked offsite ready by DPM (Write Period I have set is 5 Days) and now other remaining data is being started to written another tape with Tape Level Hosted: Monthly Backup-00000003. I dont know what happend, last month it went smoothly. can anybody guide me here what could be issue? If with tape inventor, can I disable this?


    Wednesday, July 2, 2014 8:06 PM

Answers

  • It doesnt matter if you have one Job, specially you have a lot of Tape Jobs starting at 11:00 PM every month, cause DPM is scheduling a Job each DS.

    Write Period starts with the written Data to Tape, so thats th cause of this.

    the best should be to cancel the Tape Jobs for this Datasource.

    At the End of this Month, go to Monitorring, create a View for the planned Tape Jobs and cancel the Jobs for this Server


    Seidl Michael | http://www.techguy.at | twitter.com/techguyat | facebook.com/techguyat

    Tuesday, July 15, 2014 6:25 AM

All replies

  • Hi,

     A tape inventory will not effect current tape backup jobs.  It really sounds like the tape filled up and we had to start another.  The DPMRA errlog files will detail tape switch.

    Find /i "NeedMoreMedia = [1]" dpmra*.errlog

    Right above that entry, you should see an error code look for "0x8007044C"  which means The physical end of the tape has been reached.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, July 2, 2014 10:10 PM
    Moderator
  • Hello Mike,

    I tried above command but no any log found with above mentioned comment. Tape capacity is 3 TB and write period is 5 days, last month tape was marked offsite ready after 5 days, but now its offsite ready at 2TB only and its 2nd of July only.

    C:\Program Files\Microsoft System Center 2012\DPM\DPM\Temp>Find /i "NeedMoreMedi
    a = [1]" dpmra*.errlog

    ---------- DPMRA0.ERRLOG

    ---------- DPMRA1.ERRLOG

    ---------- DPMRA10.ERRLOG

    ---------- DPMRA100.ERRLOG

    ---------- DPMRA101.ERRLOG

    ---------- DPMRA102.ERRLOG

    ---------- DPMRA103.ERRLOG

    ---------- DPMRA104.ERRLOG

    ---------- DPMRA105.ERRLOG

    ---------- DPMRA106.ERRLOG

    ---------- DPMRA107.ERRLOG

    ---------- DPMRA108.ERRLOG

    ---------- DPMRA109.ERRLOG

    ---------- DPMRA11.ERRLOG

    ---------- DPMRA110.ERRLOG

    ---------- DPMRA111.ERRLOG

    ---------- DPMRA112.ERRLOG

    ---------- DPMRA113.ERRLOG

    ---------- DPMRA114.ERRLOG

    ---------- DPMRA115.ERRLOG

    ---------- DPMRA116.ERRLOG

    ---------- DPMRA117.ERRLOG

    ---------- DPMRA118.ERRLOG

    ---------- DPMRA119.ERRLOG

    ---------- DPMRA12.ERRLOG

    ---------- DPMRA120.ERRLOG

    ---------- DPMRA121.ERRLOG

    ---------- DPMRA122.ERRLOG

    ---------- DPMRA123.ERRLOG

    ---------- DPMRA124.ERRLOG

    ---------- DPMRA125.ERRLOG

    ---------- DPMRA126.ERRLOG

    ---------- DPMRA127.ERRLOG

    ---------- DPMRA128.ERRLOG

    ---------- DPMRA129.ERRLOG

    ---------- DPMRA13.ERRLOG

    ---------- DPMRA130.ERRLOG

    ---------- DPMRA131.ERRLOG

    ---------- DPMRA132.ERRLOG

    ---------- DPMRA133.ERRLOG

    ---------- DPMRA134.ERRLOG

    ---------- DPMRA135.ERRLOG

    ---------- DPMRA14.ERRLOG

    ---------- DPMRA15.ERRLOG

    ---------- DPMRA16.ERRLOG

    ---------- DPMRA17.ERRLOG

    ---------- DPMRA18.ERRLOG

    ---------- DPMRA19.ERRLOG

    ---------- DPMRA2.ERRLOG

    ---------- DPMRA20.ERRLOG

    ---------- DPMRA21.ERRLOG

    ---------- DPMRA22.ERRLOG

    ---------- DPMRA23.ERRLOG

    ---------- DPMRA24.ERRLOG

    ---------- DPMRA25.ERRLOG

    ---------- DPMRA26.ERRLOG

    ---------- DPMRA27.ERRLOG

    ---------- DPMRA28.ERRLOG

    ---------- DPMRA29.ERRLOG

    ---------- DPMRA3.ERRLOG

    ---------- DPMRA30.ERRLOG

    ---------- DPMRA31.ERRLOG

    ---------- DPMRA32.ERRLOG

    ---------- DPMRA33.ERRLOG

    ---------- DPMRA34.ERRLOG

    ---------- DPMRA35.ERRLOG

    ---------- DPMRA36.ERRLOG

    ---------- DPMRA37.ERRLOG

    ---------- DPMRA38.ERRLOG

    ---------- DPMRA39.ERRLOG

    ---------- DPMRA4.ERRLOG

    ---------- DPMRA40.ERRLOG

    ---------- DPMRA41.ERRLOG

    ---------- DPMRA42.ERRLOG

    ---------- DPMRA43.ERRLOG

    ---------- DPMRA44.ERRLOG

    ---------- DPMRA45.ERRLOG

    ---------- DPMRA46.ERRLOG

    ---------- DPMRA47.ERRLOG

    ---------- DPMRA48.ERRLOG

    ---------- DPMRA49.ERRLOG

    ---------- DPMRA5.ERRLOG

    ---------- DPMRA50.ERRLOG

    ---------- DPMRA51.ERRLOG

    ---------- DPMRA52.ERRLOG

    ---------- DPMRA53.ERRLOG

    ---------- DPMRA54.ERRLOG

    ---------- DPMRA55.ERRLOG

    ---------- DPMRA56.ERRLOG

    ---------- DPMRA57.ERRLOG

    ---------- DPMRA58.ERRLOG

    ---------- DPMRA59.ERRLOG

    ---------- DPMRA6.ERRLOG

    ---------- DPMRA60.ERRLOG

    ---------- DPMRA61.ERRLOG

    ---------- DPMRA62.ERRLOG

    ---------- DPMRA63.ERRLOG

    ---------- DPMRA64.ERRLOG

    ---------- DPMRA65.ERRLOG

    ---------- DPMRA66.ERRLOG

    ---------- DPMRA67.ERRLOG

    ---------- DPMRA68.ERRLOG

    ---------- DPMRA69.ERRLOG

    ---------- DPMRA7.ERRLOG

    ---------- DPMRA70.ERRLOG

    ---------- DPMRA71.ERRLOG

    ---------- DPMRA72.ERRLOG

    ---------- DPMRA73.ERRLOG

    ---------- DPMRA74.ERRLOG

    ---------- DPMRA75.ERRLOG

    ---------- DPMRA76.ERRLOG

    ---------- DPMRA77.ERRLOG

    ---------- DPMRA78.ERRLOG

    ---------- DPMRA79.ERRLOG

    ---------- DPMRA8.ERRLOG

    ---------- DPMRA80.ERRLOG

    ---------- DPMRA81.ERRLOG

    ---------- DPMRA82.ERRLOG

    ---------- DPMRA83.ERRLOG

    ---------- DPMRA84.ERRLOG

    ---------- DPMRA85.ERRLOG

    ---------- DPMRA86.ERRLOG

    ---------- DPMRA87.ERRLOG

    ---------- DPMRA88.ERRLOG

    ---------- DPMRA89.ERRLOG

    ---------- DPMRA9.ERRLOG

    ---------- DPMRA90.ERRLOG

    ---------- DPMRA91.ERRLOG

    ---------- DPMRA92.ERRLOG

    ---------- DPMRA93.ERRLOG

    ---------- DPMRA94.ERRLOG

    ---------- DPMRA95.ERRLOG

    ---------- DPMRA96.ERRLOG

    ---------- DPMRA97.ERRLOG

    ---------- DPMRA98.ERRLOG

    ---------- DPMRA99.ERRLOG

    ---------- DPMRACURR.ERRLOG

    C:\Program Files\Microsoft System Center 2012\DPM\DPM\Temp>

    Thing I noticed, Tape was marked offsite ready when above error occurred (Inventory error) which I mentioned in initial comment.

    • Edited by V Jay Rana Wednesday, July 2, 2014 10:26 PM
    Wednesday, July 2, 2014 10:24 PM
  • This is the tape which was in drive at inventory time and was marked offsite ready : 



    • Edited by V Jay Rana Wednesday, July 2, 2014 10:32 PM
    Wednesday, July 2, 2014 10:31 PM
  • Hi,

    See if you can find any "0x8007045D" errors.

    Find /I "0x8007045D" dpmra*.errlog


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, July 2, 2014 10:33 PM
    Moderator
  • Same result, nothing found with this error :

    C:\Program Files\Microsoft System Center 2012\DPM\DPM\Temp>Find /I "0x8007045D"
    dpmra*.errlog

    ---------- DPMRA0.ERRLOG

    ---------- DPMRA1.ERRLOG

    ---------- DPMRA10.ERRLOG

    ---------- DPMRA100.ERRLOG

    ---------- DPMRA101.ERRLOG

    ---------- DPMRA102.ERRLOG

    ---------- DPMRA103.ERRLOG

    ---------- DPMRA104.ERRLOG

    ---------- DPMRA105.ERRLOG

    ---------- DPMRA106.ERRLOG

    ---------- DPMRA107.ERRLOG

    ---------- DPMRA108.ERRLOG

    ---------- DPMRA109.ERRLOG

    ---------- DPMRA11.ERRLOG

    ---------- DPMRA110.ERRLOG

    ---------- DPMRA111.ERRLOG

    ---------- DPMRA112.ERRLOG

    ---------- DPMRA113.ERRLOG

    ---------- DPMRA114.ERRLOG

    ---------- DPMRA115.ERRLOG

    ---------- DPMRA116.ERRLOG

    ---------- DPMRA117.ERRLOG

    ---------- DPMRA118.ERRLOG

    ---------- DPMRA119.ERRLOG

    ---------- DPMRA12.ERRLOG

    ---------- DPMRA120.ERRLOG

    ---------- DPMRA121.ERRLOG

    ---------- DPMRA122.ERRLOG

    ---------- DPMRA123.ERRLOG

    ---------- DPMRA124.ERRLOG

    ---------- DPMRA125.ERRLOG

    ---------- DPMRA126.ERRLOG

    ---------- DPMRA127.ERRLOG

    ---------- DPMRA128.ERRLOG

    ---------- DPMRA129.ERRLOG

    ---------- DPMRA13.ERRLOG

    ---------- DPMRA130.ERRLOG

    ---------- DPMRA131.ERRLOG

    ---------- DPMRA132.ERRLOG

    ---------- DPMRA133.ERRLOG

    ---------- DPMRA134.ERRLOG

    ---------- DPMRA135.ERRLOG

    ---------- DPMRA14.ERRLOG

    ---------- DPMRA15.ERRLOG

    ---------- DPMRA16.ERRLOG

    ---------- DPMRA17.ERRLOG

    ---------- DPMRA18.ERRLOG

    ---------- DPMRA19.ERRLOG

    ---------- DPMRA2.ERRLOG

    ---------- DPMRA20.ERRLOG

    ---------- DPMRA21.ERRLOG

    ---------- DPMRA22.ERRLOG

    ---------- DPMRA23.ERRLOG

    ---------- DPMRA24.ERRLOG

    ---------- DPMRA25.ERRLOG

    ---------- DPMRA26.ERRLOG

    ---------- DPMRA27.ERRLOG

    ---------- DPMRA28.ERRLOG

    ---------- DPMRA29.ERRLOG

    ---------- DPMRA3.ERRLOG

    ---------- DPMRA30.ERRLOG

    ---------- DPMRA31.ERRLOG

    ---------- DPMRA32.ERRLOG

    ---------- DPMRA33.ERRLOG

    ---------- DPMRA34.ERRLOG

    ---------- DPMRA35.ERRLOG

    ---------- DPMRA36.ERRLOG

    ---------- DPMRA37.ERRLOG

    ---------- DPMRA38.ERRLOG

    ---------- DPMRA39.ERRLOG

    ---------- DPMRA4.ERRLOG

    ---------- DPMRA40.ERRLOG

    ---------- DPMRA41.ERRLOG

    ---------- DPMRA42.ERRLOG

    ---------- DPMRA43.ERRLOG

    ---------- DPMRA44.ERRLOG

    ---------- DPMRA45.ERRLOG

    ---------- DPMRA46.ERRLOG

    ---------- DPMRA47.ERRLOG

    ---------- DPMRA48.ERRLOG

    ---------- DPMRA49.ERRLOG

    ---------- DPMRA5.ERRLOG

    ---------- DPMRA50.ERRLOG

    ---------- DPMRA51.ERRLOG

    ---------- DPMRA52.ERRLOG

    ---------- DPMRA53.ERRLOG

    ---------- DPMRA54.ERRLOG

    ---------- DPMRA55.ERRLOG

    ---------- DPMRA56.ERRLOG

    ---------- DPMRA57.ERRLOG

    ---------- DPMRA58.ERRLOG

    ---------- DPMRA59.ERRLOG

    ---------- DPMRA6.ERRLOG

    ---------- DPMRA60.ERRLOG

    ---------- DPMRA61.ERRLOG

    ---------- DPMRA62.ERRLOG

    ---------- DPMRA63.ERRLOG

    ---------- DPMRA64.ERRLOG

    ---------- DPMRA65.ERRLOG

    ---------- DPMRA66.ERRLOG

    ---------- DPMRA67.ERRLOG

    ---------- DPMRA68.ERRLOG

    ---------- DPMRA69.ERRLOG

    ---------- DPMRA7.ERRLOG

    ---------- DPMRA70.ERRLOG

    ---------- DPMRA71.ERRLOG

    ---------- DPMRA72.ERRLOG

    ---------- DPMRA73.ERRLOG

    ---------- DPMRA74.ERRLOG

    ---------- DPMRA75.ERRLOG

    ---------- DPMRA76.ERRLOG

    ---------- DPMRA77.ERRLOG

    ---------- DPMRA78.ERRLOG

    ---------- DPMRA79.ERRLOG

    ---------- DPMRA8.ERRLOG

    ---------- DPMRA80.ERRLOG

    ---------- DPMRA81.ERRLOG

    ---------- DPMRA82.ERRLOG

    ---------- DPMRA83.ERRLOG

    ---------- DPMRA84.ERRLOG

    ---------- DPMRA85.ERRLOG

    ---------- DPMRA86.ERRLOG

    ---------- DPMRA87.ERRLOG

    ---------- DPMRA88.ERRLOG

    ---------- DPMRA89.ERRLOG

    ---------- DPMRA9.ERRLOG

    ---------- DPMRA90.ERRLOG

    ---------- DPMRA91.ERRLOG

    ---------- DPMRA92.ERRLOG

    ---------- DPMRA93.ERRLOG

    ---------- DPMRA94.ERRLOG

    ---------- DPMRA95.ERRLOG

    ---------- DPMRA96.ERRLOG

    ---------- DPMRA97.ERRLOG

    ---------- DPMRA98.ERRLOG

    ---------- DPMRA99.ERRLOG

    ---------- DPMRACURR.ERRLOG

    C:\Program Files\Microsoft System Center 2012\DPM\DPM\Temp>


    Thing to notice is Last month tape lebel was Hosted: Monthly Backup-00000013, this month it is Hosted: Monthly Backup-00000014 and pending data after offsite ready is written with tape lebel Hosted: Monthly Backup-00000003. Shouldn't be it Hosted: Monthly Backup-00000015?

    • Edited by V Jay Rana Wednesday, July 2, 2014 10:45 PM
    Wednesday, July 2, 2014 10:41 PM
  • Hi,

    Have to mark it up as unsolved mystery, now get back to real work... lol.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, July 2, 2014 10:51 PM
    Moderator
  • Boss gonna shout on me in next morning, that for just 106 GB you used a another full tape :D. Anyway Thanks for your help, If I find anything I will post here.
    Wednesday, July 2, 2014 10:57 PM
  • Hi

    please post your CoLocation Settings


    Seidl Michael | http://www.techguy.at | twitter.com/techguyat | facebook.com/techguyat

    Monday, July 7, 2014 11:15 AM
  • Here is Optimization settings..

    16 Protection groups > Co-located to a single tape, only have 1 monthly backup job which runs at 1st of every month. 3 TB is tape capacity.

    Monday, July 7, 2014 7:52 PM
  • Same result, nothing found with this error :

    C:\Program Files\Microsoft System Center 2012\DPM\DPM\Temp>Find /I "0x8007045D"
    dpmra*.errlog

    ---------- DPMRA0.ERRLOG

    ---------- DPMRA1.ERRLOG

    ---------- DPMRA10.ERRLOG

    ---------- DPMRA100.ERRLOG

    ---------- DPMRA101.ERRLOG

    ---------- DPMRA102.ERRLOG

    ---------- DPMRA103.ERRLOG

    ---------- DPMRA104.ERRLOG

    ---------- DPMRA105.ERRLOG

    ---------- DPMRA106.ERRLOG

    ---------- DPMRA107.ERRLOG

    ---------- DPMRA108.ERRLOG

    ---------- DPMRA109.ERRLOG

    ---------- DPMRA11.ERRLOG

    ---------- DPMRA110.ERRLOG

    ---------- DPMRA111.ERRLOG

    ---------- DPMRA112.ERRLOG

    ---------- DPMRA113.ERRLOG

    ---------- DPMRA114.ERRLOG

    ---------- DPMRA115.ERRLOG

    ---------- DPMRA116.ERRLOG

    ---------- DPMRA117.ERRLOG

    ---------- DPMRA118.ERRLOG

    ---------- DPMRA119.ERRLOG

    ---------- DPMRA12.ERRLOG

    ---------- DPMRA120.ERRLOG

    ---------- DPMRA121.ERRLOG

    ---------- DPMRA122.ERRLOG

    ---------- DPMRA123.ERRLOG

    ---------- DPMRA124.ERRLOG

    ---------- DPMRA125.ERRLOG

    ---------- DPMRA126.ERRLOG

    ---------- DPMRA127.ERRLOG

    ---------- DPMRA128.ERRLOG

    ---------- DPMRA129.ERRLOG

    ---------- DPMRA13.ERRLOG

    ---------- DPMRA130.ERRLOG

    ---------- DPMRA131.ERRLOG

    ---------- DPMRA132.ERRLOG

    ---------- DPMRA133.ERRLOG

    ---------- DPMRA134.ERRLOG

    ---------- DPMRA135.ERRLOG

    ---------- DPMRA14.ERRLOG

    ---------- DPMRA15.ERRLOG

    ---------- DPMRA16.ERRLOG

    ---------- DPMRA17.ERRLOG

    ---------- DPMRA18.ERRLOG

    ---------- DPMRA19.ERRLOG

    ---------- DPMRA2.ERRLOG

    ---------- DPMRA20.ERRLOG

    ---------- DPMRA21.ERRLOG

    ---------- DPMRA22.ERRLOG

    ---------- DPMRA23.ERRLOG

    ---------- DPMRA24.ERRLOG

    ---------- DPMRA25.ERRLOG

    ---------- DPMRA26.ERRLOG

    ---------- DPMRA27.ERRLOG

    ---------- DPMRA28.ERRLOG

    ---------- DPMRA29.ERRLOG

    ---------- DPMRA3.ERRLOG

    ---------- DPMRA30.ERRLOG

    ---------- DPMRA31.ERRLOG

    ---------- DPMRA32.ERRLOG

    ---------- DPMRA33.ERRLOG

    ---------- DPMRA34.ERRLOG

    ---------- DPMRA35.ERRLOG

    ---------- DPMRA36.ERRLOG

    ---------- DPMRA37.ERRLOG

    ---------- DPMRA38.ERRLOG

    ---------- DPMRA39.ERRLOG

    ---------- DPMRA4.ERRLOG

    ---------- DPMRA40.ERRLOG

    ---------- DPMRA41.ERRLOG

    ---------- DPMRA42.ERRLOG

    ---------- DPMRA43.ERRLOG

    ---------- DPMRA44.ERRLOG

    ---------- DPMRA45.ERRLOG

    ---------- DPMRA46.ERRLOG

    ---------- DPMRA47.ERRLOG

    ---------- DPMRA48.ERRLOG

    ---------- DPMRA49.ERRLOG

    ---------- DPMRA5.ERRLOG

    ---------- DPMRA50.ERRLOG

    ---------- DPMRA51.ERRLOG

    ---------- DPMRA52.ERRLOG

    ---------- DPMRA53.ERRLOG

    ---------- DPMRA54.ERRLOG

    ---------- DPMRA55.ERRLOG

    ---------- DPMRA56.ERRLOG

    ---------- DPMRA57.ERRLOG

    ---------- DPMRA58.ERRLOG

    ---------- DPMRA59.ERRLOG

    ---------- DPMRA6.ERRLOG

    ---------- DPMRA60.ERRLOG

    ---------- DPMRA61.ERRLOG

    ---------- DPMRA62.ERRLOG

    ---------- DPMRA63.ERRLOG

    ---------- DPMRA64.ERRLOG

    ---------- DPMRA65.ERRLOG

    ---------- DPMRA66.ERRLOG

    ---------- DPMRA67.ERRLOG

    ---------- DPMRA68.ERRLOG

    ---------- DPMRA69.ERRLOG

    ---------- DPMRA7.ERRLOG

    ---------- DPMRA70.ERRLOG

    ---------- DPMRA71.ERRLOG

    ---------- DPMRA72.ERRLOG

    ---------- DPMRA73.ERRLOG

    ---------- DPMRA74.ERRLOG

    ---------- DPMRA75.ERRLOG

    ---------- DPMRA76.ERRLOG

    ---------- DPMRA77.ERRLOG

    ---------- DPMRA78.ERRLOG

    ---------- DPMRA79.ERRLOG

    ---------- DPMRA8.ERRLOG

    ---------- DPMRA80.ERRLOG

    ---------- DPMRA81.ERRLOG

    ---------- DPMRA82.ERRLOG

    ---------- DPMRA83.ERRLOG

    ---------- DPMRA84.ERRLOG

    ---------- DPMRA85.ERRLOG

    ---------- DPMRA86.ERRLOG

    ---------- DPMRA87.ERRLOG

    ---------- DPMRA88.ERRLOG

    ---------- DPMRA89.ERRLOG

    ---------- DPMRA9.ERRLOG

    ---------- DPMRA90.ERRLOG

    ---------- DPMRA91.ERRLOG

    ---------- DPMRA92.ERRLOG

    ---------- DPMRA93.ERRLOG

    ---------- DPMRA94.ERRLOG

    ---------- DPMRA95.ERRLOG

    ---------- DPMRA96.ERRLOG

    ---------- DPMRA97.ERRLOG

    ---------- DPMRA98.ERRLOG

    ---------- DPMRA99.ERRLOG

    ---------- DPMRACURR.ERRLOG

    C:\Program Files\Microsoft System Center 2012\DPM\DPM\Temp>

    Thing to notice is Last month tape lebel was Hosted: Monthly Backup-00000013, this month it is Hosted: Monthly Backup-00000014 and pending data after offsite ready is written with tape lebel Hosted: Monthly Backup-00000003. Shouldn't be it Hosted: Monthly Backup-00000015

    Monday, July 7, 2014 8:02 PM
  • Please to a right click on the two tapes and check the Backup Time, are they different more than 5 Days?

    Seidl Michael | http://www.techguy.at | twitter.com/techguyat | facebook.com/techguyat

    Wednesday, July 9, 2014 5:14 AM
  • I See. When I check Tape content backup time I found 2 DB backup time is different...

    Since I have one tape job only (Monthly) which starts 11:00 PM on 1st of every month. The target server occupying these 2 databases is under maintenance since 19/6 so the latest express full backup time is 6/19. Backup time of all others databases is 7/1 I think it shouldn't affect Offsite ready parameter since Write Period counting starts from first backup content written to tape. I have set write period 5 days, last month it went successfully marking tape offsite ready on 6/6 at 10:00 PM. This month tape marked offsite ready on 2nd day only. I am in India and DPM is in US so cant check tape capacity myself to ensure but checked with remote resources tapes capacity is 3 TB.

    Could you explain this..Total protection groups co-located to single tape are 16. last month it used tape label Hosted: Monthly Backup-00000013, this month it used Hosted: Monthly Backup-00000014 with sequential naming tape label and after writing 2,018,635.00 MB of 14 protection groups to this, marked it offsite ready on 2nd day and then started to write another tape labelled Hosted: Monthly Backup-00000003 for remaining 2 protection groups. Anyhow it marked offsite ready on just 2nd day, The next tape label to use shouldn't be Hosted: Monthly Backup-00000015? Why does it used 00000003?

    Note : Customized tape Label in all co-located protection group is Hosted: Monthly Backup


    • Edited by V Jay Rana Wednesday, July 9, 2014 8:52 PM
    Wednesday, July 9, 2014 5:22 PM
  • The Backup Time will not provide the Time the DS was copied to Tape, thats the Time of the last correct DS on Disk, which is copied to tape.

    In Case you have 5 Days write Period, an DPM saved the old DS (12 Days) on tape, Tape was marked a offsite Ready.

    For the Naming thing: The Naming of the Tape will provided by the first Protectiongroup on your Tape, in case the rest DS from different Protectiongroup, so there was a different Number. Numbers will count each Protectiongroup, doesnt matter the Names are the same for each PG.

    Hope that helps.


    Seidl Michael | http://www.techguy.at | twitter.com/techguyat | facebook.com/techguyat

    Sunday, July 13, 2014 10:41 AM
  • I agreed that's the Time of the last correct DS on Disk, which is copied to tape. But as I mentioned I have only one tape job which runs 11:00 PM of 1st of every month, So why it doesn't treat write period of 5 days from 1st to 6th of month since data to tape is written on 1st. Write period doesn't start with first dataset written to tape?

    If it starts with last correct DS on disk, then why it doen't expire after 5 days (19th+5 = 24th) ? Why it kept for 12 days.

    This server would be off for this month as well, So before tape job start next month, should I unprotect this server for moment?

    Tuesday, July 15, 2014 1:18 AM
  • It doesnt matter if you have one Job, specially you have a lot of Tape Jobs starting at 11:00 PM every month, cause DPM is scheduling a Job each DS.

    Write Period starts with the written Data to Tape, so thats th cause of this.

    the best should be to cancel the Tape Jobs for this Datasource.

    At the End of this Month, go to Monitorring, create a View for the planned Tape Jobs and cancel the Jobs for this Server


    Seidl Michael | http://www.techguy.at | twitter.com/techguyat | facebook.com/techguyat

    Tuesday, July 15, 2014 6:25 AM