Re: Active data

2017-01-11 Thread Karel Bos
Would expect not as the whole point of the active data pool was having active 
verslons on disk and inactive data on cheaper tape. Container is disk only and 
dedupe needs repeating blocks of data to be effective.

K



> Op 11 jan. 2017 om 20:09 heeft David Ehresman  
> het volgende geschreven:
> 
> In a TSM 7.1.7 server, can a container stgpool be used as an activedata 
> stgpool?
> 
> David


Active data

2017-01-11 Thread David Ehresman
In a TSM 7.1.7 server, can a container stgpool be used as an activedata stgpool?

David


Re: Why the constant mention of repair in container storage pools.

2017-01-11 Thread Deirdre O'Callaghan
Thank you for your feedback about repairing storage pools and the upgrade
process. You can repair deduplicated data extents in a directory-container
storage pool by using the REPAIR STGPOOL command. This is a similar feature
to the RESTORE STGPOOL command in DISK and SEQUENTIAL type storage pools.
For more information about repairing storage pools, see:
https://www.ibm.com/support/knowledgecenter/en/SSEQVQ_8.1.0/srv.solutions/t_msdisk_stgp_repair.html

With IBM Spectrum Protect Version 7.1.7 and later, you can protect
directory-container storage pools by copying the data to container-copy
storage pools, where the data is stored on tape volumes. For more
information about copying directory-container storage pools to tape
volumes, see
https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.admin/t_contcp_stgpool_protect.html

I hope this answers your question and thank you again for your comments.
Deirdre O'Callaghan
Information developer for IBM Spectrum Protect


ANS1311E (RC11) Server out of data storage space - container pool

2017-01-11 Thread Schaub, Steve
BA client 7.1.3
TDP client 7.1.4
TSM server 7.1.7

Doing some testing of SQL TDP with container pools.  Getting ~ 95% data 
reduction (client level compression & dedupe).
Seeing this ANS1311E error on a 3TB database.
It should barely fit the free space in the container pool if dedupe/compression 
is ignored, and easily fit once dedupe/compression are factored in.

My question is whether there is a client/server version combination that is 
smart enough to know that based on the compress/dedupe a backup is getting, to 
go ahead and attempt the backup?
Is there a TDP 8.1 coming out anytime soon?

Thanks,

Steve Schaub
Systems Engineer II, Backup/Recovery
Blue Cross Blue Shield of Tennessee


--
Please see the following link for the BlueCross BlueShield of Tennessee E-mail 
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm


protect stg + replicate node

2017-01-11 Thread rou...@univ.haifa.ac.il
Hi to  all

A question to people using PROTECT STG and REPLICATE  NODE what will be the 
best practice to use in the target side for STGPOOL

One STG  for the protect stg and another STG for the replicate nodes , or only 
one for everything ???

Both TSM servers version 7.1.7  with O.S Windows 2012 64B

Best Regards

Robert


Oracle TDP backups and Replication

2017-01-11 Thread Zoltan Forray
Folks,

The deeper we get into TSM replication, the more issues we find.  This one
popped-up on multiple Oracle systems after I turned on replication for them.

System owner is having issues with Oracle TDP backups failing.  The basic
symptom is:

01/10/2017 15:38:58 ANS4058I A write failure occurred while attempting to
save node replication failover values to the options file
01/10/2017 15:40:12 ANS0361I DIAG: dbOpen(): error opening/creating lock
file '/opt/tivoli/tsm/client/api/bin64/tsmnrtable.DB.Lock'
01/10/2017 15:40:12 ANS2124W Client node replication table is locked by
another process.

Doing research on the errors I see this is common when a server has
multiple TSM nodes, which all of our Oracle DB systems do.  The suggested
solution is the addition of the NRTABLEPATH keyword to each stanza in the
dsm.sys, which we have done.

But, this doesn't seem to do anything if you run multiple Oracle backups
simultaneously, which we do via cron.

We are using the latest Spectrum Protect Oracle TDP.  Base client is still
7.1.6.

Turning off replication for the Oracle node eliminates the problem.

I did see another suggestion to change the nrtable attributes to 777, which
we are going to try today.

Any thoughts/suggestions?  Is this scenario simply not do-able?

--
*Zoltan Forray*
Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator (in training)
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html