Re: protect stg + replicate node

2017-01-12 Thread Stefan Folkerts
I would always go for the protect stgpool and replicate node combination if storagepool layout allows, it's faster and during protect stgpool you have less databack locking so less issues with other processes. On Wed, Jan 11, 2017 at 5:13 PM, rou...@univ.haifa.ac.il < rou...@univ.haifa.ac.il>

Re: DECOMMISSION NODE

2017-01-12 Thread Zoltan Forray
It won't continue. When I canceled the processes, it said something about undoing the decommissioning. However, when I just tried to restart the DECOMMISSION NODE, it errors saying the node is already decommissioned? Looking back in the logs, it says the decommission ended with "completion

Re: DECOMMISSION NODE

2017-01-12 Thread Zoltan Forray
This node has >230M objects (both offsite and onsite) and total occupancy of 12TB. It got to ~80M when I had to kill it. Sure wish I knew if it was going to start all over again or pick-up where it left off? I have more maintenance on this TSM server scheduled for Tuesday and if it starts all

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

2017-01-12 Thread Del Hoobler
Hi Steve, We don't want to change existing behavior or any customer using this could break. We won't get into designing it on the ADSM-L. :-) Thanks for the RFE! Del "ADSM: Dist Stor Manager" wrote on 01/12/2017

Re: DECOMMISSION NODE

2017-01-12 Thread Skylar Thompson
Bummer, I guess I've never tried canceling the process. It sounds like a bug to me, as other processes in TSM are supposed to be transactional and incremental. On Thu, Jan 12, 2017 at 03:44:24PM -0500, Zoltan Forray wrote: > It won't continue. When I canceled the processes, it said something

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

2017-01-12 Thread Schaub, Steve
Del, I opened an RFE for this, #99603. Thanks, -steve Although now I'm wondering if the 2 couldn't just be merged into one parm? If the percentage was identifying the estimated percentage of data sent after data reduction, 25 would tell TSM to take 25% of the actual data size to use for its

Re: DECOMMISSION NODE

2017-01-12 Thread Skylar Thompson
The scan portion probably will take the same amount of time, but the heavy-hitting part (marking active objects as inactive) should pick up where it left off. On Thu, Jan 12, 2017 at 03:00:08PM -0500, Zoltan Forray wrote: > This node has >230M objects (both offsite and onsite) and total occupancy

Re: restructuring tsm db into several smaller filesystesm

2017-01-12 Thread Krzysztof Przygoda
Hi Gary You can do it backup .. drop .. restore way but you might also try way which is possible to be done even on working server. 1. add new storage paths by extend dbspace 2. from db2 run rebalance on each tablespace eg: db2 alter tablespace LARGESPACE1 rebalance and then reduce max on each:

Re: restructuring tsm db into several smaller filesystesm

2017-01-12 Thread PAC Brion Arnaud
Hi Gary Here, the corresponding documentation : http://www-01.ibm.com/support/docview.wss?uid=swg1IC78489 http://www-01.ibm.com/support/docview.wss?uid=swg21611157 Cheers. Arnaud -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Krzysztof

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

2017-01-12 Thread Del Hoobler
Hi Steve, Yes... something along the lines of what was done for growth during backups (i.e. the reverse problem): /ADJUSTKBtsmestimate=numkb /ADJUSTPERcenttsmestimate=numpercent Reference: http://www.ibm.com/support/knowledgecenter/SSER7G_8.1.0/db.sql/dps_ref_opt_backupoptional.html

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

2017-01-12 Thread Del Hoobler
Hi Steve, It's a great question. Data is a funny thing... it can dedup/compress really well one day.. then not very much the next (for example, if database maintenance or re-orgs are done). As it stands right now, Spectrum Protect has to assume it won't dedup to make sure there is a enough

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

2017-01-12 Thread Schaub, Steve
Thanks, Del. An interim solution might be a cfg parm that allows us to specify a percentage of data reduction that TDP would use. So we could tell TDP to assume a 75% total data reduction to factor into its calculation. -steve -Original Message- From: ADSM: Dist Stor Manager

DECOMMISSION NODE

2017-01-12 Thread Zoltan Forray
Anyone out there using the DECOMMISSION NODE command? I tried it on an old, inactive node and after running for 4-days, I had to cancel it due to scheduled TSM server maintenance. My issue is, since it was only 35% finished (based on the number of objects processed), will it start from the

Re: DECOMMISSION NODE

2017-01-12 Thread Matthew McGeary
Hello Zoltan, I use it every day, mostly because of changes to our VMware environment (VMs seem to breed like rabbits and die like fruit flies.) It never seems to take much time in those cases, but the object count and data stored in those cases isn't typically very large. I've never tried

Re: DECOMMISSION NODE

2017-01-12 Thread Skylar Thompson
We recently ran it on a node with ~6 million objects, and it worked fine. I think it ran for about an hour before completing, but it definitely thrashed the database. On Thu, Jan 12, 2017 at 02:14:37PM -0500, Zoltan Forray wrote: > Anyone out there using the DECOMMISSION NODE command? I tried it