Test Deduplication
Hi *SM-nerds. I just wonder if it is possible to run a deduplication Identify process on an existing File Class Storage Pool without deduplicat any data? We just want know how much data that will be deduplicate and if it worth it on this storage pool. We are running TSM 6.3.4.300 running on a Windows Server 2012. Best Regards / Med vänlig hälsning Christian Svensson __ Knarrarnäsgatan 7, Kista Entré SE-164 40 Kista Sweden Cell :+ 46-70 325 1577 E-mail: christian.svens...@cristie.semailto:christian.svens...@cristie.se Genom att säkra era data spar ni tid, tid som ni kan använda till viktigare saker.
Re: TDP for SQL 6.4.1 cross-server restore setup
Thanks for the workaround Del, this is not directed at you. Surely this would have come up and been solved in any reasonable beta test program, well before being inflicted on long-suffering customers? Sometimes I wonder if any consideration is given to those who use the product day to day. The idiotic work arounds that we have to use, that have been in the TSM for years and continue to cause wasted time and effort by everyone flabbergast me. One of my accounts has just gone off to something that promises a brand new approach. Time will tell if the reality matches the glossies, but this is exactly the sort of reason why they leave. Spleen vented, submerging again, Steve Steven Harris TSM Admin Canberra Australia On 13/02/2014 5:04 AM, Del Hoobler wrote: Hi Steve, See if this helps: http://www-01.ibm.com/support/docview.wss?uid=swg21597023 BTW... this is a known requirement. There are plans to add this function directly to the launch of the MMC soon. Thank you, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/12/2014 11:46:58 AM: From: Schaub, Steve steve_sch...@bcbst.com To: ADSM-L@vm.marist.edu, Date: 02/12/2014 12:36 PM Subject: TDP for SQL 6.4.1 cross-server restore setup Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Windows 2012, TSM TDP 6.4.1 Our DBA's do a fair amount of cross-server restores here. Since I cant depend on them editing the dsm.opt file (tried that before, ended up with a bunch of backups in the wrong place because they forgot to change it back), I came up with a little pre-launch script that allows them to pick a SQL node from our inventory to restore from, then builds a temp opt file using that node name, and launches the tdp gui using that opt file. However, now that 6.4.1 has killed off the tdp gui in favor of the mmc, I haven't been able to figure out how to achieve the same results. Can someone tell me how to launch the mmc using an alternate opt file?
Re: TDP for SQL 6.4.1 cross-server restore setup
Hello, I am sorry for problems this has caused. A fix for this is targeted for the DP/SQL 7.1.0.1 iFix. Current estimate is April. Thank you. Del - ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/13/2014 11:53:25 AM: From: Hans Christian Riksheim bull...@gmail.com To: ADSM-L@vm.marist.edu, Date: 02/13/2014 11:54 AM Subject: Re: TDP for SQL 6.4.1 cross-server restore setup Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu I agree. With the old GUI I put a link in the Public Desktop-folder for each MSSQL instance. Easy for the MSSQL-people just to double click on a named icon on their desktop which pointed to the correct configfile. Now they are copying cfg-files all around in the tdpsql directory. On one occation a configfile for an instance was emptied in this process. The backup schedule had no problem with that since it just backed up the default instance instead. So not only an inconvenience but also an added risk with the new GUI. I vote for a speedy resolve of this future improvement. Hans Chr. On Thu, Feb 13, 2014 at 12:11 PM, Steven Harris st...@stevenharris.infowrote: Thanks for the workaround Del, this is not directed at you. Surely this would have come up and been solved in any reasonable beta test program, well before being inflicted on long-suffering customers? Sometimes I wonder if any consideration is given to those who use the product day to day. The idiotic work arounds that we have to use, that have been in the TSM for years and continue to cause wasted time and effort by everyone flabbergast me. One of my accounts has just gone off to something that promises a brand new approach. Time will tell if the reality matches the glossies, but this is exactly the sort of reason why they leave. Spleen vented, submerging again, Steve Steven Harris TSM Admin Canberra Australia On 13/02/2014 5:04 AM, Del Hoobler wrote: Hi Steve, See if this helps: http://www-01.ibm.com/support/docview.wss?uid=swg21597023 BTW... this is a known requirement. There are plans to add this function directly to the launch of the MMC soon. Thank you, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/12/2014 11:46:58 AM: From: Schaub, Steve steve_sch...@bcbst.com To: ADSM-L@vm.marist.edu, Date: 02/12/2014 12:36 PM Subject: TDP for SQL 6.4.1 cross-server restore setup Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Windows 2012, TSM TDP 6.4.1 Our DBA's do a fair amount of cross-server restores here. Since I cant depend on them editing the dsm.opt file (tried that before, ended up with a bunch of backups in the wrong place because they forgot to change it back), I came up with a little pre-launch script that allows them to pick a SQL node from our inventory to restore from, then builds a temp opt file using that node name, and launches the tdp gui using that opt file. However, now that 6.4.1 has killed off the tdp gui in favor of the mmc, I haven't been able to figure out how to achieve the same results. Can someone tell me how to launch the mmc using an alternate opt file?
bfs files
Quick question. I have TSM 6.3.4 running on Windows server 2008 R2 This is coming from an inexperienced user so bear with me... I have a primary storage pool spread over two disks in the TSM server. The disks in the server are E: and F: (I don't know if this matters) In my storage pool I have many volumes 25 GB in size. I always name them VOL when I create new ones and the system appends more to the end to make the names unique. Everything seems to be functioning normally but I took a look at the storage pool volumes and I notive I have about 10 volumes I have never seen before that have names of the format 0100.BFS. I did not create these volumes and I don't know why they are there. I also notice that they end in .BFS whereas the volumes I created all have to file extension. What really bothers me is these mystery volumes range in size from 100 to 500 GB in size! Im afraid the backup will fail because the disk doesnt have room for this. I also notice that while the 25 GB volumes I create all have static sizes these mystery volumes (one of htem currently) are actually growing. Can anyone tell me... A: is this normal? B: can I get rid of these volumes somehow so the system keeps using my created 25GB volumes? C: why is one of these volumes growing in size whereas my volumes are static in size? any other information would be appreciated. Thanks! Thomas Taylor System Administrator Jos. A. Bank Clothiers Cell (443)-974-5768
Re: bfs files
Tom, BFS volumes are created by a storage pool that utilizes the filedevice type. If you take a look at your defined device classes (query devcl f=d) note the device class(es) that list a Device Type of FILE and/or DISK. Next query your storage (query stg) which will list all of the defined storage pools and device class they use. The storage pools using a device class with the type FILE are generating the BFS files. The ones listed with a device class of DISK are using the static volumes (without the BFS extension). I strongly urge that you visit the IBM Information Center, or similar doco, for your version of TSM Server to get better understanding of TSM storage . It is safe to say that the information in these volumes is backup/archive data and I would not suggest removing them. -Rick Adamson 904.783.5264 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tom Taylor Sent: Thursday, February 13, 2014 1:20 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] bfs files Quick question. I have TSM 6.3.4 running on Windows server 2008 R2 This is coming from an inexperienced user so bear with me... I have a primary storage pool spread over two disks in the TSM server. The disks in the server are E: and F: (I don't know if this matters) In my storage pool I have many volumes 25 GB in size. I always name them VOL when I create new ones and the system appends more to the end to make the names unique. Everything seems to be functioning normally but I took a look at the storage pool volumes and I notive I have about 10 volumes I have never seen before that have names of the format 0100.BFS. I did not create these volumes and I don't know why they are there. I also notice that they end in .BFS whereas the volumes I created all have to file extension. What really bothers me is these mystery volumes range in size from 100 to 500 GB in size! Im afraid the backup will fail because the disk doesnt have room for this. I also notice that while the 25 GB volumes I create all have static sizes these mystery volumes (one of htem currently) are actually growing. Can anyone tell me... A: is this normal? B: can I get rid of these volumes somehow so the system keeps using my created 25GB volumes? C: why is one of these volumes growing in size whereas my volumes are static in size? any other information would be appreciated. Thanks! Thomas Taylor System Administrator Jos. A. Bank Clothiers Cell (443)-974-5768
file system backups of a Dell NDMP Equallogic device
We have two Dell NDMP storage devices and a TSM server at both sites. We'd like to be able to root file level (image backups don't help much) backups (and restores if necessary) of the entire NDMP device to the local TSM server. Can someone point me in the right direction or tell me how they did it? NAS/NDMP is pretty new to me and from what I have read so far, the documentation talks about backing up directly to tape, which we don't have any more. All of our storage is online. What I was originally planning on doing, was creating all of the NFS shares on one linux server, and backing them up as /virtualmountpoints. I'd like to setup just one which points to the root of all the NFS systems on the NAS device but I see no way to do that either. Any help is appreciated.
Re: file system backups of a Dell NDMP Equallogic device
Op 13 feb. 2014, om 20:11 heeft Dury, John C. jd...@duqlight.com het volgende geschreven: We have two Dell NDMP storage devices and a TSM server at both sites. We'd like to be able to root file level (image backups don't help much) backups (and restores if necessary) of the entire NDMP device to the local TSM server. Can someone point me in the right direction or tell me how they did it? NAS/NDMP is pretty new to me and from what I have read so far, the documentation talks about backing up directly to tape, which we don't have any more. All of our storage is online. What I was originally planning on doing, was creating all of the NFS shares on one linux server, and backing them up as /virtualmountpoints. I'd like to setup just one which points to the root of all the NFS systems on the NAS device but I see no way to do that either. Any help is appreciated. if supported by the Dell, NDMP to disk is even simpler than NDMP to tape... just don't define any paths from the datamover to tape (which you don't have any way) -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: file system backups of a Dell NDMP Equallogic device
You don't have to use tape. You can do NDMP backups via TCP/IP to your regular TSM storage pool hierarchy. But AFAIK you still have to do it at the volume/share level that the NAS device understands, I don't think you can do it at the root. Using virtualmountpoint is for backing up incrementally at the *file* level via NFS or CIFS mounts, not NDMP, so I'm not sure which way you are headed. Question is, what are you doing this for? NDMP is a stupid, simplistic protocol. You won't like what you have to do to achieve an individual file restore. If you are trying to get DR capability to rebuild your NDMP shares in case of an emergency, it makes sense. If you are just trying to provide backup coverage to restore people's files like you would from a file server, it may not. If you want to do NDMP via TCP/IP instead of direct to tape, reply with your TSM server platform and server level, and I'll send you back the page reference in the manual you need... W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dury, John C. Sent: Thursday, February 13, 2014 2:11 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] file system backups of a Dell NDMP Equallogic device We have two Dell NDMP storage devices and a TSM server at both sites. We'd like to be able to root file level (image backups don't help much) backups (and restores if necessary) of the entire NDMP device to the local TSM server. Can someone point me in the right direction or tell me how they did it? NAS/NDMP is pretty new to me and from what I have read so far, the documentation talks about backing up directly to tape, which we don't have any more. All of our storage is online. What I was originally planning on doing, was creating all of the NFS shares on one linux server, and backing them up as /virtualmountpoints. I'd like to setup just one which points to the root of all the NFS systems on the NAS device but I see no way to do that either. Any help is appreciated.
Re: file system backups of a Dell NDMP Equallogic device
I agree with Wanda. Our strategy for our filers (BlueARC, Isilon) is to backup at the file-level exclusively, using NFS. Modern TSM servers support no-query restores well enough that we can get a restore of the latest data very quickly (make sure you have plenty of CPU and memory, along with very fast database disks). To perform the backups efficiently, you might want to think about splitting your data up into separate nodes or filespaces, backed up with independent schedules, so that you're not bottlenecked on a single component. As far as I can tell, NDMP was written by storage vendors to make one buy more expensive storage, and more of it than one needs. On Thu, Feb 13, 2014 at 09:03:15PM +, Prather, Wanda wrote: You don't have to use tape. You can do NDMP backups via TCP/IP to your regular TSM storage pool hierarchy. But AFAIK you still have to do it at the volume/share level that the NAS device understands, I don't think you can do it at the root. Using virtualmountpoint is for backing up incrementally at the *file* level via NFS or CIFS mounts, not NDMP, so I'm not sure which way you are headed. Question is, what are you doing this for? NDMP is a stupid, simplistic protocol. You won't like what you have to do to achieve an individual file restore. If you are trying to get DR capability to rebuild your NDMP shares in case of an emergency, it makes sense. If you are just trying to provide backup coverage to restore people's files like you would from a file server, it may not. If you want to do NDMP via TCP/IP instead of direct to tape, reply with your TSM server platform and server level, and I'll send you back the page reference in the manual you need... W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dury, John C. Sent: Thursday, February 13, 2014 2:11 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] file system backups of a Dell NDMP Equallogic device We have two Dell NDMP storage devices and a TSM server at both sites. We'd like to be able to root file level (image backups don't help much) backups (and restores if necessary) of the entire NDMP device to the local TSM server. Can someone point me in the right direction or tell me how they did it? NAS/NDMP is pretty new to me and from what I have read so far, the documentation talks about backing up directly to tape, which we don't have any more. All of our storage is online. What I was originally planning on doing, was creating all of the NFS shares on one linux server, and backing them up as /virtualmountpoints. I'd like to setup just one which points to the root of all the NFS systems on the NAS device but I see no way to do that either. Any help is appreciated. -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
