• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.


    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

I don't think I like directory storage pools anymore


ADSM.ORG Senior Member
A couple years ago I setup a SP server in Azure to handle SQL backups. At the time you could not allocate disks to the VM that were large enough to use for back-end storage so I configured it to use Azure fileshares for a directory storage pool. Needless to say the performance using NAS-based storage for a directory storage pool wasn't that great, but it worked and our client count was low.

Fast forward to today and my client count has increased and Azure now allows 32TB disks to be attached to the VM. So, in an effort to improve performance I attached 4x32TB disks to the VM and created a new directory storage pool called AZUREDISK. My old NAS-based pool is called AZUREFILE and I would like to get rid of it.

By now you have probably guessed where this is going. I want to decommission my old AZUREFILE storage pool and to do that I need to move everything out of the AZUREFILE pool. Without a 'MIGRATE' capability for directory pools it make the process difficult.

Since I am only using this SP server to do TDP SQL backups I thought I could just modify my copygroup to point to the new AZUREDISK storage pool and wait for retention and the new SQL backups to all start showing up in my new pool. For the most part that is exactly what happened, however there are 100's of objects remaining in the old pool that have not expired/moved into the new pool. I run regular queries looking for backup objects that are beyond our retention period and these queries do not list any outdated objects. So somehow these objects in my old AZUREFILE storage pool are getting updated, but not getting moved into the new pool.

So a couple questions:
1) Anyone know why SQL/TDP backups would keep these old objects current and not relocate them?
2) Anyone know any tricks to migrate data from one directory storage pool to another?


TSM noob with 12 years expirience
ADSM.ORG Moderator
If your retention setings are low, just make new nodes, and delete old data when retention has passed.

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 18.4%
  • Keep using TSM for Spectrum Protect.

    Votes: 60 61.2%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.2%
  • Other (please comement)

    Votes: 8 8.2%

Forum statistics

Latest member