Re: Can't find node
Hello, Do you still have a tsm schedule defined for the node? q sche * nodename* -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of r4mzeso Sent: Wednesday, February 05, 2014 5:26 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Can't find node Select node_name, tcp_name from nodes where tcp_name='xxx.domain.com' also tried Select node_name, tcp_name from nodes where tcp_name='xxx' No match found usin this criteria. I dont know why tsm still try to connect to this node, 1) On node xxx I removed all TSM files, I removed all entries from register, I removed also all TSM services. 2) TSM server was restarted, node xxx was restarted and still q actlog gives me 02/05/2014 10:27:26 ANR8212W Unable to resolve address for domain. 02/04/2014 10:27:57 ANR8214E Session open with xxx.domain.com failed due to connection refusal. (SESSION: 14) Any ideas? +-- |This was sent by r4mz...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Informal Poll: General question about use of policysets
Same here, one policy set per domain. -Nick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Saturday, February 01, 2014 11:08 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Informal Poll: General question about use of policysets We use one policy set per domain. We haven't come across a need for more than that. Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Friday, January 31, 2014 4:22 PM To: ADSM-L@VM.MARIST.EDU Subject: Informal Poll: General question about use of policysets The TSM books show that you can have multiple policysets per domain. I don't mean just the active vs inactive, but you can have multiple policysets like NORMAL, OFFHOUR, WEEKEND, within one domain, and switch them back and forth. I've never done that, or had a reason to. Seems inordinately confusing to me. All my customers just have one policyset per domain, with the active and inactive copy. The inactive is the one you update, then you validate it and activate it. Can I get some feedback on what other people do? Do you have just one unique policyset per domain? Or what is your use case for having multiples? Thank you!!! Wanda **Please note new office phone: Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.comhttp://www.icfi.com | 410-868-4872 (m) ICF International | 7125 Thomas Edison Dr., Suite 100, Columbia, Md |443-718-4900 (o) - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Question: V6.3 or V7.1 for a new system?
I would go with 7.1, I have it on 4 Windows 2008 R2 servers without any problems. The DB improvements are great, and the use of the Ops Manager has already provided to be very useful. :) All the best with the upgrade. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Nachtwey, Bjoern Sent: Friday, January 31, 2014 5:27 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Question: V6.3 or V7.1 for a new system? Dear all, reading the discussion about TSM 7.1 - should I upgrade or not seems to give me the answer for the question which version should I take for a completely new installation: for a new installation take TSM 7.1. but -- maybe some remarks are not given, what if so? therefore I do ask: Does anyone have remarks, experiences that suggest to take V6.3 instead of V7.1? Please tell me! We're going to use Linux on Dell R620 servers, i6k libraries and lto5/6 drives. thank you for any comment best regards Bjørn
Re: How well do .pst files dedup?
Hi Wanda, I've had very good dedup savings with PSTs in general. I've deployed client side deduplication across all remote sites, and I wouldn't have had backups complete if it wasn't for deduplication. What used to take upwards of 3 or 4 days to backup is now complete in a few hours. PST's are a nightmare for more organizations, and this solution proved useful to us for the time being. With is a summary from a heavy load remote site. Last I checked when I was doing the initial testing (last year) that server alone had over 200 pst change on a daily basis with most over 5GB and upwards of 20GB. You would need a beefy tsm server to handle the overhead. For my data, as of last week I have 17TB in de duplicated savings across the storage pools. Hope that helps, 01/24/2014 00:13:01 --- SCHEDULEREC STATUS BEGIN 01/24/2014 00:13:01 Total number of objects inspected: 741,410 01/24/2014 00:13:01 Total number of objects backed up:1,572 01/24/2014 00:13:01 Total number of objects updated: 0 01/24/2014 00:13:01 Total number of objects rebound: 0 01/24/2014 00:13:01 Total number of objects deleted: 0 01/24/2014 00:13:01 Total number of objects expired: 93 01/24/2014 00:13:01 Total number of objects failed: 4 01/24/2014 00:13:01 Total objects deduplicated: 955 01/24/2014 00:13:01 Total number of bytes inspected: 1.05 TB 01/24/2014 00:13:01 Total number of bytes processed: 1.45 GB 01/24/2014 00:13:01 Total bytes before deduplication:345.70 GB 01/24/2014 00:13:01 Total bytes after deduplication: 1.51 GB 01/24/2014 00:13:01 Total number of bytes transferred: 1.45 GB 01/24/2014 00:13:01 Data transfer time:1,484.90 sec 01/24/2014 00:13:01 Network data transfer rate:1,030.55 KB/sec 01/24/2014 00:13:01 Aggregate data transfer rate: 94.09 KB/sec 01/24/2014 00:13:01 Objects compressed by: 26% 01/24/2014 00:13:01 Deduplication reduction: 99.57% 01/24/2014 00:13:01 Total data reduction ratio: 99.87% 01/24/2014 00:13:01 Elapsed processing time: 04:31:02 01/24/2014 00:13:01 --- SCHEDULEREC STATUS END 01/24/2014 00:13:01 --- SCHEDULEREC OBJECT END NODENAME_INCR 01/23/2014 19:30:00 01/24/2014 00:13:01 Scheduled event 'NODENAME_INCR' completed successfully. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Friday, January 24, 2014 3:44 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] How well do .pst files dedup? Anybody looked in detail at how well .pst files dedup with TSM - (client or server-end)? **Please note new office phone: Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.comhttp://www.icfi.com | 410-868-4872 (m) ICF International | 7125 Thomas Edison Dr., Suite 100, Columbia, Md |443-718-4900 (o)
Re: TSM 7.1
As an added fyi, my upgrade of 2 out of 4 tsm (6.3.3) servers to 7.1 went very well, and the new Ops Center is performing as expected from my earlier lab testing. I do wish that I can override some or most of the thresholds, it is not a priority but would be an added feature. For example under Storage Devices, I have critical alerts due to 1 available directory. We use XIV attached LUN's, and they can handle a very heavy load, it would be nice to be able to override this, but it is not show stopper by an means. There are two items I encountered when upgrading. The first was easy to resolve, and it had to do with TSM being shipped with a free trial of DB2 Connect. The license expires, and needs to be removed/re-registered. (http://www-01.ibm.com/support/docview.wss?uid=swg21636492myns=swgtivmynp=OCSSGSG7mync=E) The other problem I wasn't able to overcome was when running the install gui. During the pre-check it will verify the instance credentials, in my case it is loading .\tsminst1 and there is no way to change it. The correct id name is just tsminst1. I'll will open a ticket tomorrow with support. So far the upgrade is going very smooth, and as planned. -Nick Nick Marouf | Systems Administrator Consultant PA Department of Transportation | Bureau of Infrastructure and Operations 1400A North Cameron St | Harrisburg PA 17103 Phone: 717.346.5547 | Fax: 717.346.5530 www.dot.state.pa.us
Re: TSM 7.1
Thank You Harmeet, I'm looking at upgrading to 7.1 for both clients and Servers. All my lesser environments are auto-deployed with the 7.1 client for a burn in period, and there have been no issues to date. -Nick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Harmeet Sian Sent: Thursday, January 16, 2014 5:51 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 7.1 I've been labelled a maniac for rolling out fresh 7.1 to several clients instead of trusted 6.3.4 but not a single one has had any issue. I was hoping I could do more with the op center but the dashboard is making clients go weak at the knees. Also the TSM4VE updates have somehow made this a much more reliable product - no more blank screens in vCenter or inability to edit jobs. Also loving the separate interface without having to load vCenter or mess about with -optfile and shortcut settings. I did have issues upgrading one TSM server (6.3.4 but this guy has seen upgrades all the way from 6.2 days) but I was able to roll back painlessly - even without a DB backup ( upgrade process be damned... its just 'next', 'next', 'next' right?? :) ). I then followed the upgrade guide properly and still had issues so I'm suspecting the server itself has something fundamentally wrong with it. All the installations I have had have been on Win 2008r2 or 2012 with ample memory and processor (128GB RAM or above, 16 cores etc). I'm currently looking at how the hub/spoke replication works but given my experience so far I expect to be pleasantly surprised. All-in-all this is been such a good experience compared to TSM6.1. Harmeet Sian SENIOR SYSTEMS ENGINEER The Missing Link Network Integration Pty Ltd a 9-11 Dickson Ave Artarmon NSW 2064 p 1300 865 865 os +61 2 8436 8585 w themissinglink.com.au -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Marouf, Nick Sent: Thursday, 16 January 2014 9:32 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 7.1 Hello, I wanted to see what the general feedback is on TSM 7.1? I haven't seen many reported problems. -Nick __ This email has been scanned by The Missing Link's Email Security System - Powered by Symantec.cloud. For more information please email supp...@themissinglink.com.au __ CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify The Missing Link immediately. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of The Missing Link. _ This email has been scanned by The Missing Link's Email Security System - Powered by Symantec.cloud. For more information please email supp...@themissinglink.com.au __
TSM 7.1
Hello, I wanted to see what the general feedback is on TSM 7.1? I haven't seen many reported problems. -Nick
Re: TSM 7.1
Thank You Zoltan. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Thursday, January 16, 2014 9:59 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 7.1 We have installed it on 5-systems, 3-Linux 2-Windows. We had installer issues on one of our Windows 2012 servers (Error 2869. The dialog SetupError has the error style bit set, but is not an error dialog). Ended up having to completely uninstall, delete and reinstall. On Thu, Jan 16, 2014 at 5:32 AM, Marouf, Nick c-nimar...@pa.gov wrote: Hello, I wanted to see what the general feedback is on TSM 7.1? I haven't seen many reported problems. -Nick -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services 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
Re: POLL: Backing up Windows Systemstate
In our current environment, we've never had a requirement to restore a system state. However, there are engineers that requested the ability to have it available. Instead of using TSM's systemstate backup option, I've excluded it in the dsm.opt and use Microsoft's preferred and recommended method for backing up system state. If you haven't seen this before, this quote is good to note: When performing a VSS backup or restore, the Windows system state is defined as being a collection of several key operating system elements and their files. These elements should always be treated as a unit by backup and restore operations. What this means it is all or nothing when it comes to System State backups and restores. I found that using the built in Microsoft feature is the best, and most accurate method. (2008 Servers) I currently have it part of a scheduled job, but you can just as easily add it as a pre-task in the tsm client as well, this will allow the system state backup to be as close to the tsm disk backup. To enable it in Windows you need to add these Add these features: You will need to add under windows 2008 Features the Windows Server Backup Features which includes Windows Server Backup and Command Line Options. The actual backup commands go something like this :: Decide how many versions to keep Wbadmin delete systemstatebackup -backuptarget:E: -keepversions:1 -quiet :: Take a new system state backup wbadmin start systemstatebackup -backupTarget:d: -quiet The only catch is that is has to back up to a non OS drive. And it will take grow to approx. 12GB+ If you wish to restore a system state backup, you must first reboot the server into Directory Services Restore Mode (DSRM). Once in DSRM, you would open a command prompt with administrator rights and use the following commands to start the restore. C:\Users\adminWBADMIN GET VERSIONS Once we have located the version identifier, we can initiate the restore by using the following command: WBADMIN START SYSTEMSTATERECOVERY -version: version id Hope that helps, -Nick Also check out this Technical Exchange from IBM on the subject. http://www-01.ibm.com/support/docview.wss?uid=swg27023299 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Grigori Solonovitch Sent: Friday, January 10, 2014 3:29 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] POLL: Backing up Windows Systemstate We are backing up Systemstate on all Windows servers because of using TBMR for restoring system images in case of system crash. Sometimes it is painful due to big number of files, problems with VSS, etc. Problems with VSS are resolved by installing hot fixes or involving MS support. Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: 09 01 2014 9:12 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] POLL: Backing up Windows Systemstate A question about backing up systemstate, which seems to give us numerous headaches. Do you backup systemsstate on your Windows servers and WHY? My Windows folks constantly contact me about errors backup up and getting failures related to the systemstate files/process or VSS. For example, today's headache is a 2008 box failing with *System Writers 'system writer' do not exist * and yes, doing a vssadmin list writers does not list system writers. They have been fighting this since November, with no solution to fixing this problem. All hits/suggested solutions from Google searches have been tried, to no avail. I don't thing the server owners are willing to do a complete rebuild. The simple solution would be to NOT backups systemstate. For a simple 2008 server, what do we lose by not backing up systemstate? -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services 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 Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from
Re: Deduplication number of chunks waiting in queue continues to rise?
Hi Wanda, I'm using Deduplication and have found that tsm life would be much easier if the stg pool was kept smaller under 3TB in size. I haven't done enough testing with this, and I know it is slightly counterproductive to achieve the highest deduplication savings. But it sure does make the administrative side much cleaner and easier to work. Keeping the storage pool smaller does create offsite copies and reclamation faster. It is a divide and conquer. I do have a storage pool that does take longer to reclaim, and this seems to clear up every Sunday as we generally have very little incoming client backups on that day. I'm using client side deduplication to leverage the client processing; and In order to protect against stale or duplicate chunk collisions I keep the cache databases set very low where the clients on average have to reset that cache every few days. Deduplication is very important for me, Please keep me in the loop when you come closer to a resolution. tsm: TSMC04PSHOW DEDUPDELETEINFO Dedup Deletion General Status Number of worker threads : 8 Number of active worker threads : 1 Number of chunks waiting in queue : 1967534 tsm: TSMC04Pq db f=d Database Name: TSMDB1 Total Size of File System (MB): 1,148,760 Space Used by Database(MB): 304,105 Free Space Available (MB): 6,755,930 Total Pages: 33,625,117 Usable Pages: 33,623,517 Used Pages: 33,620,309 Free Pages: 3,208 Buffer Pool Hit Ratio: 98.0 Total Buffer Requests: 21,032,020,059 Sort Overflows: 0 Package Cache Hit Ratio: 99.8 Last Database Reorganization: 12/16/2013 18:21:53 Full Device Class Name: 3592DEV Number of Database Backup Streams: 1 Incrementals Since Last Full: 0 Last Complete Backup Date/Time: 12/19/2013 10:12:53 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Erwann Simon Sent: Friday, December 20, 2013 12:33 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Deduplication number of chunks waiting in queue continues to rise? Hi Wanda, Expire Inventory is queuing chunk for deletion. See the Q PR output when, at the end of the expire inventory process, the total numbers of nodes have been reached. No more deletion of objects occurs, but SHOW DEDUPDELETEINFO shows that the deletion threads are still working, queuing and deleting chunks. This activity does not appear externally and consumes most of the expire inventory time. Let's try with deduplication disabled (dedup=no) for that pool (?). Regards, Erwann Prather, Wanda wanda.prat...@icfi.com a écrit : TSM 6.3.4.00 on Win2K8 Perhaps some of you that have dealt with the dedup chunking problem can enlighten me. TSM/VE backs up to a dedup file pool, about 4 TB of changed blocks per day I currently have more than 2 TB (yep, terabytes) of volumes in that file pool that will not reclaim. We were told by support that when you do: SHOW DEDUPDELETEINFO That the number of chunks waiting in queue has to go to zero for those volumes to reclaim. (I know that there is a fix at 6.3.4.200 to improve the chunking process, but that has been APARed, and waiting on 6.3.4.300.) I have shut down IDENTIFY DUPLICATES and reclamation for this pool. There are no clients writing into the pool, we have redirected backups to a non-dedup pool for now to try and get this cleared up. There is no client-side dedup here, only server side. I've also set deduprequiresbackup to NO for now, although I hate doing that, to make sure that doesn't' interfere with the reclaim process. But SHOW DEDUPDELETEINFO shows that the number of chunks waiting in queue is *still* increasing. So, WHAT is putting stuff on that dedup delete queue? And how do I ever gain ground? W **Please note new office phone: Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.com ICF International | 443-718-4900 (o) -- Erwann SIMON Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.
Re: Deduplication number of chunks waiting in queue continues to rise?
I can second that Sergio, Backup stgpools to copy tapes is not pretty, and is an intensive process to rehydrate all that data. The one extra thing I did was split the database across multiple folder for parallel I/O to the Database. That has worked out very well, and I currently have it setup to span across 8 folders, with an XIV backend that can take a beating. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Sergio O. Fuentes Sent: Friday, December 20, 2013 12:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Deduplication number of chunks waiting in queue continues to rise? Client-side dedup and simultaneous-write to a copy pool are mutually exclusive. You can't do both, which is the only theoretical way to enforce deduprequiresbackup with client-side dedup. I suppose IBM could enhance TSM to do a simultaneous-like operation with client-side dedup, but that's not available now. So, I'm not sure how the TSM server enforces deduprequiresbackup with client-side dedup. Ever since 6.1 I have always set that to NO anyway. I have dealt with the repercussions of that as well. Backup stgpool on dedup'd stgpools is not pretty. I have made some architectural changes to the underlying stgpools and the 'backup stgpools' run pretty well, even with 1TB SATA drives. Two things I think helped quite a bit: 1. Use big predefined volumes. My new volumes are 50GB. 2. Use many filesystems for the devclass. I have 5 currently. I would use more if I had the space. Thanks! Sergio On 12/20/13 11:35 AM, Prather, Wanda wanda.prat...@icfi.com wrote: Woo hoo! That's great news. Will open a ticket and escalate. Also looking at client-side dedup, but I have to do some architectural planning, as all the data is coming from one client, the TSM VE data mover, which is a vm. Re client-side dedup, do you know if there is any cooperation between the client-side dedup and deduprequiresbackup on the server end? I have assumed that the client-side dedup would not offer that protection. W -Original Message- From: Sergio O. Fuentes [mailto:sfuen...@umd.edu] Sent: Friday, December 20, 2013 10:39 AM To: ADSM: Dist Stor Manager Cc: Prather, Wanda Subject: Re: [ADSM-L] Deduplication number of chunks waiting in queue continues to rise? Wanda, In trying to troubleshoot an unrelated performance PMR, IBM provided me with an e-fix for the dedupdel bottleneck that it sounds like you're experiencing. They obviously will want to do their due-diligence on whether or not this efix will help solve your problems, but it has proved very useful in my environment. They even had to compile a solaris e-fix for me, cause it seems like I'm the only one running TSM on Solaris. The e-fix was very simple to install. What you don't want to do is go to 6.3.4.2, unless they tell you to because the e-fix is for that level (207). Don't run on 6.3.4.2 for even a minute. Only install it to get to the e-fix level. Dedupdel gets populated by anything that deletes data from the stgpool, I.e. move data, expire inv, delete filespace, move nodedata, etc. We run client-side dedupe (which works pretty well, except when you run into performance issues on the server) and so our identifies don't run very long, if at all. It might save you time to run client-side dedupe. BTW, when I finally got this efix and TSM was able to catch-up with the deletes and reclaims as it needed to, I got some serious space space back in my TDP Dedup pool. It went from 90% util to 60% util (with about 10TB of total capacity). What finally really got me before the fix was that I had to delete a bunch of old TDP MSSQL filespaces and it just took forever for TSM to catch up. I have a few deletes to do now, and I'm a bit wary because I don't want to hose my server again. I would escalate with IBM support and have them supply you the e-fix. 6.3.4.3 I don't think is slated for release any time within the next few days, and you'll just be struggling to deal with the performance issue. HTH, Sergio On 12/19/13 11:35 PM, Prather, Wanda wanda.prat...@icfi.com wrote: TSM 6.3.4.00 on Win2K8 Perhaps some of you that have dealt with the dedup chunking problem can enlighten me. TSM/VE backs up to a dedup file pool, about 4 TB of changed blocks per day I currently have more than 2 TB (yep, terabytes) of volumes in that file pool that will not reclaim. We were told by support that when you do: SHOW DEDUPDELETEINFO That the number of chunks waiting in queue has to go to zero for those volumes to reclaim. (I know that there is a fix at 6.3.4.200 to improve the chunking process, but that has been APARed, and waiting on 6.3.4.300.) I have shut down IDENTIFY DUPLICATES and reclamation for this pool. There are no clients writing into the pool, we have redirected backups to a non-dedup pool for now to try and get this cleared up. There is no client-side dedup here, only
Re: Deduplication number of chunks waiting in queue continues to rise?
Hi Skylar ! Yes that would be the easy way do it, there is an option to rebalance the I/O after you add the new file systems to the database. I had already setup TSM before the performance tuning guideline was released. Doing this way, will require more storage initially and running db2 rebalancing command line tools will spread out the DB I/O load Using IBM XIV's that can handle very large IO requests, in our specific case there was no need to provide physically-separate volumes. I've seen one TSM instance crank upwards of 10,000 IOPS leaving an entire ESX cluster in the dust. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Skylar Thompson Sent: Friday, December 20, 2013 2:28 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Deduplication number of chunks waiting in queue continues to rise? While we don't do deduplication (tests show we gain less than 25% from it), we also split our DB2 instances across multiple, physically-separate volumes. The one thing to note is that you have to dump and restore the database to spread existing data across those directories if you add them post-installation. On Fri, Dec 20, 2013 at 02:23:34PM -0500, Marouf, Nick wrote: I can second that Sergio, Backup stgpools to copy tapes is not pretty, and is an intensive process to rehydrate all that data. The one extra thing I did was split the database across multiple folder for parallel I/O to the Database. That has worked out very well, and I currently have it setup to span across 8 folders, with an XIV backend that can take a beating. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Sergio O. Fuentes Sent: Friday, December 20, 2013 12:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Deduplication number of chunks waiting in queue continues to rise? Client-side dedup and simultaneous-write to a copy pool are mutually exclusive. You can't do both, which is the only theoretical way to enforce deduprequiresbackup with client-side dedup. I suppose IBM could enhance TSM to do a simultaneous-like operation with client-side dedup, but that's not available now. So, I'm not sure how the TSM server enforces deduprequiresbackup with client-side dedup. Ever since 6.1 I have always set that to NO anyway. I have dealt with the repercussions of that as well. Backup stgpool on dedup'd stgpools is not pretty. I have made some architectural changes to the underlying stgpools and the 'backup stgpools' run pretty well, even with 1TB SATA drives. Two things I think helped quite a bit: 1. Use big predefined volumes. My new volumes are 50GB. 2. Use many filesystems for the devclass. I have 5 currently. I would use more if I had the space. Thanks! Sergio On 12/20/13 11:35 AM, Prather, Wanda wanda.prat...@icfi.com wrote: Woo hoo! That's great news. Will open a ticket and escalate. Also looking at client-side dedup, but I have to do some architectural planning, as all the data is coming from one client, the TSM VE data mover, which is a vm. Re client-side dedup, do you know if there is any cooperation between the client-side dedup and deduprequiresbackup on the server end? I have assumed that the client-side dedup would not offer that protection. W -Original Message- From: Sergio O. Fuentes [mailto:sfuen...@umd.edu] Sent: Friday, December 20, 2013 10:39 AM To: ADSM: Dist Stor Manager Cc: Prather, Wanda Subject: Re: [ADSM-L] Deduplication number of chunks waiting in queue continues to rise? Wanda, In trying to troubleshoot an unrelated performance PMR, IBM provided me with an e-fix for the dedupdel bottleneck that it sounds like you're experiencing. They obviously will want to do their due-diligence on whether or not this efix will help solve your problems, but it has proved very useful in my environment. They even had to compile a solaris e-fix for me, cause it seems like I'm the only one running TSM on Solaris. The e-fix was very simple to install. What you don't want to do is go to 6.3.4.2, unless they tell you to because the e-fix is for that level (207). Don't run on 6.3.4.2 for even a minute. Only install it to get to the e-fix level. Dedupdel gets populated by anything that deletes data from the stgpool, I.e. move data, expire inv, delete filespace, move nodedata, etc. We run client-side dedupe (which works pretty well, except when you run into performance issues on the server) and so our identifies don't run very long, if at all. It might save you time to run client-side dedupe. BTW, when I finally got this efix and TSM was able to catch-up with the deletes and reclaims as it needed to, I got some serious space space back in my TDP Dedup pool. It went from 90% util to 60% util (with about 10TB of total capacity). What finally really got me
delete volhist
Hello, Can someone maybe provide a bit more clarification on this technote? http://www-01.ibm.com/support/docview.wss?uid=swg21653710myns=swgtivmynp=OCSSGSG7mync=E We generally set the DRM with SET DRMDBBACKUPEXPIREDAYS and then after tapes moved to vault for the day, run the following commands delete volhist type=ALL todate=TODAY-180 delete volhist type=DBB todate=TODAY-3 Should I be concerned? Thank You, -Nick Nick Marouf | Systems Administrator Consultant PA Department of Transportation | Bureau of Infrastructure and Operations 1400A North Cameron St | Harrisburg PA 17103 Phone: 717.346.5547 | Fax: 717.346.5530 www.dot.state.pa.ushttp://www.dot.state.pa.us/
Re: Moving from TSMV5 to V6 / question on DIRMC
Hi Rainer, We had to use DIRMC, even though I've heard the same that it is no longer needed. Some of the servers I backup are so large that without DIRMC, the restores would take a substantial time to complete, I've also had an issue were the GUI had stopped working, and enabling DIRMC on these very large server solved the problem (http://www-01.ibm.com/support/docview.wss?uid=swg21162784 ) With only 3 servers using DIRMC, using your query below I have over 5,000,000 objects in the dirmc stg pool. This really saves time for laying out the directory structure when restoring large folders/subfolder. As far using a different nodeblock format, IBM preferred format is native. Are you seeing considerable changes with the nonblock option? What would be the benefit of the two stage storage pool? Are both using a devclass of disk? -Nick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rainer Wolf Sent: Wednesday, October 30, 2013 6:54 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Moving from TSMV5 to V6 / question on DIRMC Hello All, we are currently using tsm V5 Server and soon will be moving to TSM V6, starting again from scratch with a brandnew ts3500 library and the new 3592-c drives. The new TSM-Server Setups are to be reviewed and now I have some questions on the DIRMC feature which we distribute so far via server defined clientoptionset. on dirmc there are two reasons for me why using it: a) some tape mounts can be avoided using online pools of directories,links,... ...we have not much drives b) the roughly quite easily producable output on the balancing between 'normal files' and 'directories + 0-byte-files + links + ...' can be shown with simple 'per-storage-pool-basis' ( select sum(num_files),stgpool_name from occupancy group by stgpool_name ) or simply can be displayed on a 'per-node-basis' ( with simly 'query occu stg=diskdirpool' Especially the feature b) has often directly helped finding the basic source of occuring strange problems. One question now is : with TSM 6 thre may be no need to use dirmc anymore, is it possibe that directory-entries ( with extended acl-info) are then always stored in the database and never going to tapes ? If it is okay and not quite abnormal to use the dirmc then the other question is: is it still okay to use the following way defining a 2-Stage- Storagepool-setup and using the 'DATAFormat=nonblock' for the file-volumes fetching those dikdir data ? like define stg filedirs FILEDIR maxscr=0 reused=3 hi=100 lo=30 COLlocate=group reclaim=100 DATAFormat=nonblock define STG DISKDIRS DISK hi=60 lo=20 nextstg=filedirs any hints are welcome Rainer -- Rainer Wolf eMail: rainer.w...@uni-ulm.de kiz - Abt. Infrastruktur Tel/Fax: ++49 731 50-22482/22471 Universitaet Ulm
Re: Backing up Windows scheduled tasks in 2003 2008
You could always create a prescheduled job to export all tasks, those could be imported back if there is a problem down the road. Take a look at http://community.spiceworks.com/scripts/show/1474-export-and-import-all-scheduled-tasks-in-windows-server-2008-windows-7 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Alex Paschal Sent: Wednesday, October 23, 2013 4:55 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backing up Windows scheduled tasks in 2003 2008 Hi, Steven. There are some drawbacks to backing up the *.job files from the c:\windows\tasks directory, especially with regard to passwords, but necessary, you should be able to back up those *.job files by using a prescheduled command to copy the *.job files from the c:\windows\tasks directory to some other directory that you can back up, say, q:\important\tasks. Your backup job can then pick them up from there. Alternatively, you might consider using a batch file containing schtasks commands to redefine your tasks whenever you need to. This way you can store your passwords in the task definition. On 10/23/2013 7:50 AM, Steven Langdale wrote: Hello all I have a requirement to backup scheduled tasks on a couple of windows servers. I though I may be able to get away with just C:\Windows\Tasks (and a list of the relevant passwords), but that dir is an OS exclude on 2008 (only one I've tried so far) Has anyone else needed to do this? If so, how did you go about it? My current test platform is 2008 + 6.4.0.11 client Thanks Steven
Re: Sequential dedup pool doesn't seem to reclaim as it should
Hi Wanda From personal experience my reclaims show a similar behavior, and from what I understand that used tape count will keep on increasing. The amount of time it takes to dehydrate data from disk to copy when doing a reclaim will impact the reclaim operation and of course the amount of volumes that it will leave behind with data it needs. The only time I find reclaim operations completing is during the weekends. Does anyone have any recommendations? I've personally come to the conclusion that having smaller stg pools is key to more efficient reclaims on deduped pools -Nick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Thursday, June 06, 2013 7:49 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Sequential dedup pool doesn't seem to reclaim as it should TSM 6.3.3 on Win2K8-64 I have a sequential pool on disk with DEDUP=yes. (Happens to be for TSM-VE data, but I don't think that's relevant.) Settings are below. There is 1 identify duplicates process always active. Reclaim threshold is set to 20. Every night the clients back up. At 4am we start the backup stgpool to a tape copy pool. When that is in process, several reclaims kick in on their own. But once those are finished, they don't ever crank up again later in the day. Every day it leaves several volumes above the reclaim threshold. Right now there are 5. *Identify Duplicates is finished and idle. *No client activity. *Backup stgpool file-ve copypool returns no data to be copied. It has been that way for the last 9 hours. If I start the reclaim myself with reclaim stgpool file-ve threshold=20, it runs just fine. But it won't reclaim (and therefore dedup) on its own. Shouldn't it? I'd like to have those volumes empty (and deduped) before the next backup cycle. I can force it by scheduling the extra reclaim command, but I don't understand why it doesn't kick off on its own more than once a day? tsm: LFTSMq stgpool file-ve f=d Storage Pool Name: FILE-VE Storage Pool Type: Primary Device Class Name: ONLINEFILE Estimated Capacity: 20,447 G Space Trigger Util: 68.3 Pct Util: 68.3 Pct Migr: 68.3 Pct Logical: 89.3 High Mig Pct: 98 Low Mig Pct: 70 Migration Delay: 0 Migration Continue: Yes Migration Processes: 1 Reclamation Processes: 2 Next Storage Pool: Reclaim Storage Pool: Maximum Size Threshold: No Limit Access: Read/Write Description: Dedup VE pool Overflow Location: Cache Migrated Files?: Collocate?: No Reclamation Threshold: 20 Offsite Reclamation Limit: Maximum Scratch Volumes Allowed: 0 Number of Scratch Volumes Used: 0 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): WANDA Last Update Date/Time: 05/29/2013 10:25:01 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?: Yes Processes For Identifying Duplicates: 1 more... (ENTER to continue, 'C' to cancel) Duplicate Data Not Stored: 20,588 G (60%) Auto-copy Mode: Client Contains Data Deduplicated by Client?: No Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.com ICF International | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135 (o)
Re: Antwort: [ADSM-L] Now that I have a TS3500 - I have questions
Hello Zoltan, Congrats! For checkin I use the following checkin libv 3584lib search=bulk checkl=barcode status=Scratch waitt=0 bulk means to check the Virtual I/O slots or entry doors. The YES option is only needed if you want to scan the entire library. With ALMS option that your library has the physical library is also keeping track of the tape locations, and sending this to the tsm server when you checkin. I would also add the waitt=0 option, so you don't have to wait the default 60 minutes, you can then check the logs for any details related to the checkin. For the split libraries that you have setup, you can assign and probably should assign a tape range associated with each virtual library. That should take care of the unassigned tapes that you are seeing. Ultimately, you should be able to insert a mix and match of volumes, and the library will assign each of those tapes to its respective virtual library. Then you run the tape checkin that assign a status of scratches to them. Take a look at the following online library settings under Cartridges - Cartridge Assignment Policy -Nick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dierk Harbort Sent: Tuesday, May 28, 2013 9:28 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Antwort: [ADSM-L] Now that I have a TS3500 - I have questions Hi Zoltan, for checkin I would recommend to fill the I/O slots and then do checkin libvol libname search=bulk checklabel=barcode status=what you need, scratch or private I can't say anything to virtual libs regards Dierk | | Von: | | --| |Zoltan Forray zfor...@vcu.edu | --| | | An:| | --| |ADSM-L@VM.MARIST.EDU, | --| | | Datum: | | --| |28.05.2013 15:17 | --| | | Betreff: | | --| |[ADSM-L] Now that I have a TS3500 - I have questions | --| | | Gesendet | | von: | | --| |ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU | --| Our new TS3500 was installed this weekend (replacing our 17-year old 3494) and I have lots of questions about how things should be done/configured and why it is doing what it is doing. First off, the library is configured as 2-virtual librarys, each side with fixed drive assignments and each side managed by a separate TSM server. 1. Per other discussions, I configured 255 Virtual IO. We also configured/enabled Insert Notification. However, some tapes keep being inserted unassigned while most are properly assigned to the right library?. Why? 2. What is the proper CHECKIN command options for doing mass checkins from the IO/VIO slots?SEARCH=BULK or SEARCH=YES - CHECKLABEL=YES or CHECKLABEL=BARCODE? The book says for a SCSI library you can't specify SEARCH=YES and CHECKLABEL=NO -- *Zoltan Forray* TSM Software Hardware
Re: New guide for optimizing Tivoli Storage Manager performance
Thank you Andy, This redbook is definitely a light reading compared to the rest of the TSM rebooks. :) Thank you for all the fine tuning information being placed in once place. I wanted to ask is anyone on the list using Dedup technology with an 8 LUN database backend as recommended in the article. Is there any readily available data to show the performance enhancements? I'm currently setup with 4 folders under one LUN, with multiple paths to the SAN. I have yet to see any negative performance or IO bottlenecks. E:\Database\Server01\DB001 E:\Database\Server01\DB002 E:\Database\Server01\DB003 E:\Database\Server01\DB004 Assuming the benefits are huge, a database backup and restore with a dir input file is the only clean way to split it up over multiple luns instead of folders. Thanks for any feedback, -Nick Nick Marouf | Systems Administrator Consultant PA Department of Transportation | Bureau of Infrastructure and Operations 1400A North Cameron St | Harrisburg PA 17103 Phone: 717.346.5547 | Fax: 717.346.5530 www.dot.state.pa.us -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Andrew Raibeck Sent: Tuesday, April 16, 2013 3:54 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] New guide for optimizing Tivoli Storage Manager performance Hello TSM community, I would like to draw your attention to a newly published guide for optimizing Tivoli Storage Manager performance. This guide is oriented toward TSM version 6.3 and 6.4, and supersedes the previous performance tuning guides. The guide features a whole new approach to: * Configuration best practices for the server database, storage pools, clients, and more * Guidance for identifying performance bottlenecks in the environment * Flowcharts and graphics that illustrate key processes and practices This blog post from one of our senior Information Development leads provides a nice introduction and link to the new guide: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Storage%20Manager/page/Optimizing%20performance%20for%20servers%20and%20clients We hope you find this useful. - Andy Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli Documentation Central/page/Tivoli Storage Manager Product Wiki: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home
