TSM - change diskpool from internal server disk to Storage

EduardoRio

ADSM.ORG Member
Joined
Oct 15, 2018
Messages
61
Reaction score
0
Points
0
PREDATAR Control23

Hello,

I'm running a TSM 7.x with fibers connected strait to TS3200. The diskpool are on inside server disk.

But, I need to reconfigure it to use a storage, in which I'll be able to get more disk space, speed and be safer.

The question is, I'm struggling on IBM manuals to figure out how to do it. For sure it isn't just to change the connectors...

So, if any one who can help me to find the right literature or on the steps on doing it, I'll appreciate, thanks in advance!!!
Eduardo
 
PREDATAR Control23

What type of pool is it?
  1. - random disk pool
  2. - file pool without dedup
  3. - file pool with dedup
  4. - directory container pool
The instructions will vary depending on which one it is. I think you mean 1, but I want to be sure otherwise the results could be catastrophic.
 
PREDATAR Control23

Hi Marclant,
I'm not sure but the "q vol" shows:
Code:
E:\DISKPOOL\DISK1.DSM        DISKPOOL        DISK              48.8 G       0.0     On-Line
E:\DISKPOOL\DISK2.DSM        DISKPOOL        DISK              48.8 G       0.1     On-Line
E:\DISKPOOL\DISK3.DSM        DISKPOOL        DISK              48.8 G       0.0     On-Line
E:\DISKPOOL\DISK4.DSM        DISKPOOL        DISK              48.8 G       0.1     On-Line
E:\DISKPOOL\DISK5.DSM        DISKPOOL        DISK              48.8 G       0.0     On-Line
E:\DISKPOOL\DISK6.DSM        DISKPOOL        DISK              48.8 G       0.1     On-Line

and q stg f=d
Code:
Storage Pool Name: DISKPOOL
                    Storage Pool Type: Primary
                    Device Class Name: DISK
                   Estimated Capacity: 293 G
                   Space Trigger Util: 0.0
                             Pct Util: 0.0
                             Pct Migr: 0.0
                          Pct Logical: 100.0
                         High Mig Pct: 70
                          Low Mig Pct: 0
                      Migration Delay: 0
                   Migration Continue: Yes
                  Migration Processes: 1

My guess is #2
Thanks!!!!!!!!!!!!
 
PREDATAR Control23

Hi,
Simple solution:
- Attach new storage (say it ends up as f:)
- Grant tsm access to folders
-From dsmadmc:
* define vol DISKPOOL f:\diskpool\disk1.dsm f=49152
* define .... disk2....
* upd vol e:\diskpool\disk* acc=reado
* mig stg diskpool lo=0
* wait for volumes to emptyl
* del vol f:\diskpool\disk1.dsm

Check that no volumes exist on f:\diskpool\

dsmadmc q vol f:\*

Delete old files
 
Last edited:
PREDATAR Control23

My guess is #2
Thanks!!!!!!!!!!!!
Nope, #1 :)

What Trident says will work. Only caveat is that you have a tape pool that you migrate to. If you don't, let us know and we can slightly modify his instructions.
 
PREDATAR Control23

Thanks Trident and Marclant!!!

Sorry, but I've became a bit confused.
Yes I have a tape poll(TS3200 - with 43Tapes). The diskpool receive the backup from clients, than it is migrated to tapes.

q stg

Code:
Storage       Device       Estimated     Pct     Pct    Hig-   Lo-   Next Stora-
Pool Name     Class Name     Capacity    Util    Migr   h M-    w    ge Pool
                                                         ig    Mi-
                                                         Pct    g
                                                               Pct
-----------   ----------   ----------   -----   -----   ----   ---   -----------
DISKPOOL      DISK              293 G     0.0     0.0     70     0   TAPEPOOL
TAPEPOOL      DEVCLASS_-   10,831,35-     0.3     0.4     90    70
               LTO4               5 G

q stg f=d
Code:
                    Storage Pool Name: DISKPOOL
                    Storage Pool Type: Primary
                    Device Class Name: DISK
                   Estimated Capacity: 293 G
                   Space Trigger Util: 0.0
                             Pct Util: 0.0
                             Pct Migr: 0.0
                          Pct Logical: 100.0
                         High Mig Pct: 70
                          Low Mig Pct: 0
                      Migration Delay: 0
                   Migration Continue: Yes
                  Migration Processes: 1
                Reclamation Processes:
                    Next Storage Pool: TAPEPOOL
                 Reclaim Storage Pool:
               Maximum Size Threshold: No Limit
                               Access: Read/Write
                          Description:
                    Overflow Location:
                Cache Migrated Files?: No
                           Collocate?:
more...   (<ENTER> to continue, 'C' to cancel)

                Reclamation Threshold:
            Offsite Reclamation Limit:
      Maximum Scratch Volumes Allowed:
       Number of Scratch Volumes Used:
        Delay Period for Volume Reuse:
               Migration in Progress?: No
                 Amount Migrated (MB): 17,541.71
     Elapsed Migration Time (seconds): 885
             Reclamation in Progress?:
       Last Update by (administrator): ADMIN1
                Last Update Date/Time: 12/03/2018 11:05:04
             Storage Pool Data Format: Native
                 Copy Storage Pool(s):
                  Active Data Pool(s):
              Continue Copy on Error?: Yes
                             CRC Data: No
                     Reclamation Type:
          Overwrite Data when Deleted:
                    Deduplicate Data?: No
 Processes For Identifying Duplicates:
            Duplicate Data Not Stored:
                       Auto-copy Mode: Client
Contains Data Deduplicated by Client?: No
                    Storage Pool Name: TAPEPOOL
                    Storage Pool Type: Primary
                    Device Class Name: DEVCLASS_LTO4
                   Estimated Capacity: 10,831,355 G
                   Space Trigger Util:
                             Pct Util: 0.3
                             Pct Migr: 0.4
                          Pct Logical: 100.0
                         High Mig Pct: 90
                          Low Mig Pct: 70
                      Migration Delay: 0
                   Migration Continue: Yes
                  Migration Processes: 1
                Reclamation Processes: 1
                    Next Storage Pool:
                 Reclaim Storage Pool:
               Maximum Size Threshold: No Limit
                               Access: Read/Write
                          Description:
                    Overflow Location:
                Cache Migrated Files?:
                           Collocate?: Group
                Reclamation Threshold: 50
            Offsite Reclamation Limit:
      Maximum Scratch Volumes Allowed: 9,999
       Number of Scratch Volumes Used: 41
        Delay Period for Volume Reuse: 0 Day(s)
               Migration in Progress?: No
                 Amount Migrated (MB): 0.00
     Elapsed Migration Time (seconds): 0
             Reclamation in Progress?: Yes
       Last Update by (administrator): ADMIN1
                Last Update Date/Time: 12/03/2018 12:13:33
             Storage Pool Data Format: Native
                 Copy Storage Pool(s):
                  Active Data Pool(s):
              Continue Copy on Error?: Yes
                             CRC Data: No
                     Reclamation Type: Threshold
          Overwrite Data when Deleted:
                    Deduplicate Data?: No
 Processes For Identifying Duplicates:
            Duplicate Data Not Stored:
                       Auto-copy Mode: Client
Contains Data Deduplicated by Client?: No
 
PREDATAR Control23

Trident,
let me see if a understood what you said!!!

Attach new storage (say it ends up as f:)
Not sure if it will be so ease as this!

-From dsmadmc:
* define vol DISKPOOL f:\diskpool\disk1.dsm f=49152

Ok, ponting to (new) f:
f=49152 - does it means ~50GB?
* upd vol f:\diskpool\disk* acc=reado
Read only, sure?
* mig stg diskpool lo=0
Ok !
* wait for volumes to emptyl
OK!

* del vol f:\diskpool\disk1.dsm
Should I delete the new created f:\... disk1.dsm in the end?

PS: in order to get the storage working and connected to the server do you think it's all about just change the fiber connections?

Thanks !
Eduardo
 
PREDATAR Control23

Trident,
let me see if a understood what you said!!!

Attach new storage (say it ends up as f:)
Not sure if it will be so ease as this!

-From dsmadmc:
* define vol DISKPOOL f:\diskpool\disk1.dsm f=49152

Ok, ponting to (new) f:
f=49152 - does it means ~50GB?
No, it is 48Gb = 48 *1024 =49152 Just a nice logical size


* upd vol f:\diskpool\disk* acc=reado
Read only, sure?
No, that was a error. It should be e:, where the old volumes exist

* mig stg diskpool lo=0
Ok !
* wait for volumes to emptyl
OK!

* del vol e:\diskpool\disk1.dsm
Should I delete the new created f:\... disk1.dsm in the end?

No, that was also a typo from me. You should delete the old volumes from TSM, the from the OS.


PS: in order to get the storage working and connected to the server do you think it's all about just change the fiber connections?

Thanks !
Eduardo

Not sure what storage you have in mind. You need to supply more info about how it is connected before we can give a suitable answer.
 
PREDATAR Control23

Should I delete the new created f:\... disk1.dsm in the end?
No, the original local volumes that you no longer want to use.

PS: in order to get the storage working and connected to the server do you think it's all about just change the fiber connections?
Fiber connection and configuring the disk at the OS level. You can only configure it in Spectrum Protect once the OS has a drive letter or a mountpoint and you can read/write to it.

Might want to create more than one LUN too for the storage pool if this is going to be a busy server. Example: F:, G:, H:, I:. Or create mountpoints: instead: C:\Diskpool\disk1; C:\Diskpool\disk2, ...

I personally prefer mountpoints, you can create human readable names that mean something, with drive letters, it's not very descriptive.
 
PREDATAR Control23

Great!!
I'll check the storage type/model and the available amount for the bkp tasks. Also, how connections are/will be made.

Thanks again!
 
PREDATAR Control23

Hello !!
Yes!
My TSM server(jacaranda) have now a disk "F:" with 2 TB, created to be used as the new "diskpool".
Some questions:

How to know if tsm have grant access to disk/folders?

The 48GB amount, for each "disk.dsm" looks like a good size for my actual diskpool. Fof the new one(2TB) it could be better to create bigger ones, about 102.400GB, and handle with less "disks"?
Where:
100*1024 = 102,400 GB
2,000,000 / 102,400 = 19 disks or volumes

I really don't know what is the best approach for the TSM on the matter. Bigger files or more files...

So, that's it!
 
PREDATAR Control23

How to know if tsm have grant access to disk/folders?

Set the acl on the top directory where tsm will write. Make sure the instance user can read/write/create/delete files

As of the size of each volume, it may vary. I have usually 16Gb volumes for my 'Diskpool'.
 
PREDATAR Control23

How to know if tsm have grant access to disk/folders?

Set the acl on the top directory where tsm will write. Make sure the instance user can read/write/create/delete files

Instead, I would login to Windows as the Instance owner, and have that create the necessary directory folder. That way, the instance owner will also be the file/directory owner.
 
PREDATAR Control23

Windows ACL's are bit more award than *IX
Regardless of the OS, the creator is by default the owner, and by default, the owner has full permissions on the directories/files it creates. I just use that method everywhere, that way I don't need to worry about ACLs.
 
PREDATAR Control23

Thanks !

I've made a test and "define vol DISKPOOL f:\diskpool\disk1.dsm " just succeed !! The new file are there !!
So, I'll create all ones with 102,400GB, upd for r/w, and start a migration after that.

May I have to stop session, migration and so on?
 
PREDATAR Control23

Hi!
20 new volumes of 102,400 GB has been created !!!
Migration in process !!
 
PREDATAR Control23

So, I would say THANK YOU!!!!!!!!!!!!!!!!

I think that all should run smooth from now(I hope!!!!) due your fantastic support !!!!

Eduardo
 
Top