Scratch Media is 0mb

[gasead]

Hi, Can anyone help me with this please? I have been trying to resolve the issue for a few days now by trawling through the Internet but without any success. By the way I am new to TSM. I have a Tape Library with one LTO6 tape drive installed. I have configured the library and the drive and defined paths to both. I have created domain, policyset, managementclass, storagepool etc..etc.. all looks OK. I have checked in 3 x LTO6 media as scratch. I can see the media in my storagepool but the capacity of the media in the storagepool is 0mb. When I try to run a backup it fails for 'server out of backup storage space. It seems strange that the media is 0mb and the backup fails for server out of backup storage space so I am assuming they could be linked. I really would appreciate any thoughts from anyone on the forum as to what I can do to resolve this.

Thanks.

 

[moon-buddy]

How did you setup the environment?

Traditional setup: TSM backups up to disk and disk migrates to tape. See if migration has been defined.

If you do not use disk, see that the primary backup storage pool has been set to tape, and that scratch parameter for that tape pool has been set properly. This can be a very high number avoiding 'storage pool' errors.

 

[gasead]

Hi,

Thx for the quick reply, it's very much appreciated. Please see the output from my query of the storagepool:

FINCHER> query stgpool POOL_MSL6480-LTO6 format=detailed
Storage Pool Name: POOL_MSL6480-LTO6
Storage Pool Type: Primary
Device Class Name: LTO6
Estimated Capacity: 0 M
Space Trigger Util:
Pct Util: 0
Pct Migr: 0
Pct Logical: 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?: No
Reclamation Threshold: 60
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed: 9,999
Number of Scratch Volumes Used: 0
Delay Period for Volume Reuse: 0 Day(s)
Migration in Progress?: No
Amount Migrated (MB): 0
Elapsed Migration Time (seconds): 0
Reclamation in Progress?: No
Last Update by (administrator): TSMADMIN
Last Update Date/Time: 2016-01-07, 12:30:00
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

 

[moon-buddy]

Please answer my questions;

Do you backup to disk first?

Have you defined copy properly (see help define copy - this sets where to put the backup data)?

Activated policy/ies?

 

[marclant]

What's the destination for your backup copygroup of the active management class?

If it's to a disk pool, you should update that disk pool so that the next pool is: POOL_MSL6480-LTO6 Like moon-buddy said, backups would go to disk then migrate to tape. That's the best setup because that means you can have more clients than tape drive backing up at the same time.

 

[gasead]

Thanks for the replies.

I do not backup to disk first I want it to go directly to my tape media. I am in a lab environment so configuring TSM for optimum performance is not an issue at the moment. Ideally I just want to save a few files to tape and then restore them.

My copygroup syntax is as follows:

def copygroup DOM_MSL6480-LTO6 PS_MSL6480-LTO6 MG_MSL6480-LTO6 dest=POOL_MSL6480

As you are probably aware from the above DOM refers to my domain, PS refers to my policyset, MG refers to my management class and POOL refers to my storage pool.

 

[marclant]

That doesn't tell us if that copygroup is active or not. Would need:
q mgmt f=d
q co f=d

 

[gasead]

the output of q mgmt. f=d and q co f=d:

FINCHER> q mgmt f=d
Policy Domain Name: DOM_MSL6480-LTO6
Policy Set Name: ACTIVE
Mgmt Class Name: MG_MSL6480-LTO6
Default Mgmt Class ?: Yes
Description:
Space Management Technique: None
Auto-Migrate on Non-Use: 0
Migration Requires Backup?: Yes
Migration Destination: SPACEMGPOOL
Last Update by (administrator): TSMADMIN
Last Update Date/Time: 2016-01-07, 12:33:44
Managing profile:
Changes Pending: No

Policy Domain Name: DOM_MSL6480-LTO6
Policy Set Name: PS_MSL6480-LTO6
Mgmt Class Name: MG_MSL6480-LTO6
Default Mgmt Class ?: Yes
Description:
Space Management Technique: None
Auto-Migrate on Non-Use: 0
Migration Requires Backup?: Yes
Migration Destination: SPACEMGPOOL
Last Update by (administrator): TSMADMIN
Last Update Date/Time: 2016-01-07, 12:33:44
Managing profile:
Changes Pending: No

Policy Domain Name: STANDARD
Policy Set Name: ACTIVE
Mgmt Class Name: STANDARD
Default Mgmt Class ?: Yes
Description: Installed default management class.
Space Management Technique: None
Auto-Migrate on Non-Use: 0
Migration Requires Backup?: Yes
Migration Destination: SPACEMGPOOL
Last Update by (administrator): SERVER_CONSOLE
Last Update Date/Time: 2016-01-07, 11:42:59
Managing profile:
Changes Pending: No

Policy Domain Name: STANDARD
Policy Set Name: STANDARD
Mgmt Class Name: STANDARD
Default Mgmt Class ?: Yes
Description: Installed default management class.
Space Management Technique: None
Auto-Migrate on Non-Use: 0
Migration Requires Backup?: Yes
Migration Destination: SPACEMGPOOL
Last Update by (administrator): SERVER_CONSOLE
Last Update Date/Time: 2016-01-07, 11:42:59
Managing profile:
Changes Pending: No



FINCHER> q co f=d
Policy Domain Name: DOM_MSL6480-LTO6
Policy Set Name: ACTIVE
Mgmt Class Name: MG_MSL6480-LTO6
Copy Group Name: STANDARD
Copy Group Type: Backup
Versions Data Exists: 2
Versions Data Deleted: 1
Retain Extra Versions: 30
Retain Only Version: 60
Copy Mode: Modified
Copy Serialization: Shared Static
Copy Frequency: 0
Copy Destination: POOL_MSL6480-LTO6
Table of Contents (TOC) Destination:
Last Update by (administrator): TSMADMIN
Last Update Date/Time: 2016-01-07, 12:35:47
Managing profile:
Changes Pending: No

Policy Domain Name: DOM_MSL6480-LTO6
Policy Set Name: PS_MSL6480-LTO6
Mgmt Class Name: MG_MSL6480-LTO6
Copy Group Name: STANDARD
Copy Group Type: Backup
Versions Data Exists: 2
Versions Data Deleted: 1
Retain Extra Versions: 30
Retain Only Version: 60
Copy Mode: Modified
Copy Serialization: Shared Static
Copy Frequency: 0
Copy Destination: POOL_MSL6480-LTO6
Table of Contents (TOC) Destination:
Last Update by (administrator): TSMADMIN
Last Update Date/Time: 2016-01-07, 12:35:47
Managing profile:
Changes Pending: No

Policy Domain Name: STANDARD
Policy Set Name: ACTIVE
Mgmt Class Name: STANDARD
Copy Group Name: STANDARD
Copy Group Type: Backup
Versions Data Exists: 2
Versions Data Deleted: 1
Retain Extra Versions: 30
Retain Only Version: 60
Copy Mode: Modified
Copy Serialization: Shared Static
Copy Frequency: 0
Copy Destination: BACKUPPOOL
Table of Contents (TOC) Destination:
Last Update by (administrator): SERVER_CONSOLE
Last Update Date/Time: 2016-01-07, 11:42:59
Managing profile:
Changes Pending: No

Policy Domain Name: STANDARD
Policy Set Name: STANDARD
Mgmt Class Name: STANDARD
Copy Group Name: STANDARD
Copy Group Type: Backup
Versions Data Exists: 2
Versions Data Deleted: 1
Retain Extra Versions: 30
Retain Only Version: 60
Copy Mode: Modified
Copy Serialization: Shared Static
Copy Frequency: 0
Copy Destination: BACKUPPOOL
Table of Contents (TOC) Destination:
Last Update by (administrator): SERVER_CONSOLE

Last Update Date/Time: 2016-01-07, 11:42:59
Managing profile:
Changes Pending: No

 

[marclant]

What domain is the node you are using part of? Sounds like it's part of STANDARD by your observations.

 

[gasead]

FINCHER> query node
Node Name Platform Policy Domain Name Days Since Last Access Days Since Password Set Locked?
FINCHER WinNT STANDARD <1 <1 No

Do I need to define my node to point to my created domain?

 

[marclant]

No, just need to update the node to use the other domain. HELP UPDATE NODE.

OR, you could update the copy group in the STANDARD domain and change the destination to the tape pool. (Don't forget to activate the policy after).

 

[gasead]

You are correct, the Policy Domain was pointing to Standard and not DOM_MSL6480-LTO6. Backups are now working. I can't workout why Standard was being used and not DOM_MSL6480-LTO6 because as far as I am concerned I didn't use Standard in any of my configuration commands.

I really appreciate the time and inputs you guys have given me.

 

[marclant]

When you register a new node, if you do not specify the DOMAIN option, it defaults to STANDARD.