none
Can I write to custom tape (slot) from DPM. RRS feed

  • Question

  • All tape backups are optimized/co-located to single tape label since we are using 15TB tapes so we use them fully. 

    I am getting below error for one protection group, it's direct data being written from data source to tape and no disk backup is in picture. I am not sure if this is due to tape full (but tape is not showing offsite ready) or anything else. 

    Is there any way to choose different tape to pickup with co-located tape label, as of now when I am triggering tape job, it's picking same tape which is close to full. 

    Thanks

    Vijay 

    Monday, March 16, 2020 12:25 PM

Answers

  • The MTATempStore$ is a scratch space, it is primarily used to store temporary tape catalog files during a tape backup, and other temporary files.

    You should keep ~5GB or more free on the C-drive if possible, so you should have sufficient space for that, DPM is not complaining about the disk space for this.

    You could also try cleaning up the DPM error log files in the C:\Program Files\Microsoft System Center \DPM\DPM\Temp folder, then give it another go.


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by V Jay Rana Thursday, March 19, 2020 12:06 PM
    Wednesday, March 18, 2020 11:22 AM

All replies

  • Hi Vijay,

    DPM does not have provisions of specifying which tape slot or barcode is used for a protection groups. 

    By default (when no tape co-location set is created) each protection group will use a separate tape. The tape label created by default is the name of the Protection Group+Sequence number so once a tape is allocated to a protection group, you can visually know which tape was written to by that PG.  

    If you enable tape co-location by making a PSget, then you can allow multiple PG's to use the same tape. In that case, you can look at the far right column titled Protection Group to see which PG's are using that tape. The tape label in that case will be the protection group name that first wrote a data set on that tape.  

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, March 16, 2020 12:37 PM
  • Thanks Leon. 

    The data I want to write is 265 GB and if I don't co-locate it, it will use 15 TB tape so I am trying to write it co-located labelled tape. 

    Out of 265 GB, DPM completing tape job writing only 187 GB data with above warning. I am not sure if this is due to tape or what. Storage pools have enough space available. Have you seen this warning before ?

    Monday, March 16, 2020 12:44 PM
  • I believe this warning is referring to your tape storage.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, March 16, 2020 1:07 PM
  • Thinking so, I have started writing to another tape instead of co-located one, will see how it goes. 
    Monday, March 16, 2020 1:51 PM
  • Let us know how everything goes!

    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, March 16, 2020 1:52 PM
  • Tried writing to another tape but job completed with same warning. Also, it didn't write full size of data (265GB), it wrote only 187 GB.


    Tuesday, March 17, 2020 10:26 AM
  • And how much space is available on this tape?

    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, March 17, 2020 10:29 AM
  • Only 1 TB is used out of 15 TB. I dig up bit more into this, went to warning monitor and it's shows some more info, 


    I realized now why it's happening but want to know how to fix. Here's what I did - 

    On this protected server, agent was already installed and DPM is backing up it's E: drive fine since long. I have had take backup of some data which is in detached disk (this is vmware VM), so I attached that disk as F: drive to this protected server. Now OS of protected system is detecting that F: drive fine but seems DPM is not happy with F: drive. I also checked below forum. 

    https://social.technet.microsoft.com/Forums/en-US/4b5ce47d-996f-4c0b-8865-224f46596f8c/dpm-2012-r2-mtatempstore-permissions?forum=dataprotectionmanager

    The source location I hided is also on DPM \\DPMSERVER\MTATempStore$\*****

    1. Where to add those permissions, on DPM server or protected client ? 

    2. how to rebuild catalog. 

    Thanks


    • Edited by V Jay Rana Tuesday, March 17, 2020 11:23 AM
    Tuesday, March 17, 2020 11:20 AM
  • Make sure the local SYSTEM (NT AUTHORITY\System) account has Full Control NTFS permissions on the F-drive.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, March 17, 2020 12:05 PM
  • Thanks Leon, just did that. On other hand how to rebuild catalog. Before triggering job once again I want to make sure I also do recatalog as tape job is long time taking task and don't want to get it failed after 16 hours :)
    Tuesday, March 17, 2020 12:13 PM
  • Try first by running the DPM job again, as it should now have permissions to the F-drive, check the outcome.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, March 17, 2020 12:22 PM
  • Job failed again with same warning, only 187 GB written out of 265 GB. 

    Where does it asking space for, MTATempStore$ is in C: drive of DPM Server and there is 25GB free space of this physical DPM server's C: drive. I searched this MTATempStore$ is required for tape backups but don't know how it operates and where it's asking space for.

    Wednesday, March 18, 2020 10:46 AM
  • The MTATempStore$ is a scratch space, it is primarily used to store temporary tape catalog files during a tape backup, and other temporary files.

    You should keep ~5GB or more free on the C-drive if possible, so you should have sufficient space for that, DPM is not complaining about the disk space for this.

    You could also try cleaning up the DPM error log files in the C:\Program Files\Microsoft System Center \DPM\DPM\Temp folder, then give it another go.


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by V Jay Rana Thursday, March 19, 2020 12:06 PM
    Wednesday, March 18, 2020 11:22 AM
  • I made up free space to 40 GB on C: drive and cleaned up Temp folder where's MTATempStore$ is referring to, re-triggered tape job and will see how it goes. 
    Wednesday, March 18, 2020 1:10 PM
  • This time job completed with out warning, but data written is 187 GB. I think it's compressed or something as there's no any warning or error in job and it's showing completed. While going to recovery tab I am able to browse data folders and sub-folders underneath from tape but size isn't showing. I see I have marked 'Compress Data' option in long term for this protection group. Should I consider this completed successfully ?
    Thursday, March 19, 2020 11:55 AM
  • If you have compression enabled the size is likely due to that.

    If the job didn't return any error/warning it was successful.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, March 19, 2020 12:01 PM
  • Thanks Leon for help throughout this :) 
    Thursday, March 19, 2020 12:07 PM
  • Glad to help, you're welcome!

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, March 19, 2020 12:13 PM