Hi, We backing up a couple of PB of Isilon daily that generates a couple of 100GB per day of new data. We are backing up over NFS but it is very bad solution, and it takes around 24 hours before the Isilon and TSM have identify all new files.
There is a undocumented APIs so you can identify all change files in the Isilon so you can run a selective backup, but we had a hard time to get hold of them from EMC because they are not as open as IBM is. Another way that is not recommended is to use NDMP, LOL good luck with that if you don't want to spend millions of $$$. What I try to do now instead is either replace the EMC Isilon with IBM ESS instead that is much better or try implement GPFS on top of the Isilon so we get a much better backup functionality. But that is nothing IBM have tried to get working. /Christian -----Original Message----- From: Zoltan Forray [mailto:zfor...@vcu.edu] Sent: den 25 november 2014 17:35 To: ADSM-L@VM.MARIST.EDU Subject: Re: Backing up Isilons with TSM Skylar, Can you give us details on how you setup the Isilon to give a TSM node authority to back up the individual mount points? My SAN/Isilon guy has tried setting up a standard TSM node but all attempts at backing up mounted filesystems blocks him with "access denied" errors. We are very new to Isilon so any help would be greatly appreciated. Feel free to email me directly if you want to take this discussion offline/off-list. On Fri, Nov 21, 2014 at 11:08 AM, Skylar Thompson <skyl...@u.washington.edu> wrote: > Hi Zoltan, > > We backup two large Isilon clusters (one 715TB, the other 2PB) using TSM. > We looked at NDMP at ran away quickly due to the full backup requirement. > Instead, we worked with the data owners to setup a data organization > scheme before hand, then back up individual directories as filespaces > using TSM NFS clients connected over 10GbE. Currently we have five of > these clients, and have accomodated bursts of as much as 50TB of > changed/new data in a day using them. The only nemesis we have are > folks who create lots of tiny files; fortunately, though, over time > these incidents have gotten less frequent due to education and improvements > in genomic tools. > > We've been asking for Isilon to make a native TSM client since before > they were bought by EMC, and unfortunately they're just not > intererested. Now that EMC owns them, I think the possibility of a > native client is even more remote. > > On Fri, Nov 21, 2014 at 11:00:28AM -0500, Zoltan Forray wrote: > > Anyone have experience backing up an EMC Isilon and can share > war-stories, > > methods, etc? > > -- > -- Skylar Thompson (skyl...@u.washington.edu) > -- Genome Sciences Department, System Administrator > -- Foege Building S046, (206)-685-7354 > -- University of Washington School of Medicine > -- *Zoltan Forray* TSM Software & Hardware Administrator BigBro / Hobbit / Xymon 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
