ADSM-L

Re: [ADSM-L] Backing up Isilons with TSM

2014-11-21 13:37:02
Subject: Re: [ADSM-L] Backing up Isilons with TSM
From: Skylar Thompson <skylar2 AT U.WASHINGTON DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 21 Nov 2014 10:33:36 -0800
We do exactly what Wanda is suggesting as well. It works great, with the
caveat that the node holding the storage (the target of asnode=) needs to
have MAXNUMMP high enough to accomodate all the simultaneous
backups/restores going on.

On Fri, Nov 21, 2014 at 06:29:35PM +0000, Prather, Wanda wrote:
> If you are already using a backup box with multiple nodes, you already have a 
> system that works for you.
> Depends on how you want the data stored, and how you want to do restores.
> I like using PROXY relationships for this case:
>
> I have customer(s) with many TB of EMC NAS shares.
> They want the help desk to do the restores for the many users on those NAS 
> shares.
>
> We use multiple client machines, not just one, to do the backups.
> Each machine/scheduler service has a TSM node names and is attached to a 
> schedule.
> But they all have proxy authority and do their backups using 
> "asnode=ONENASNAME".
>
> So they each back up a number of shares, but all the filespaces are stored 
> under ONENASNAME.
> That way when the helpdesk goes to do a restore, they start the client with 
> "asnode=ONENASNAME".
> They see all the shares/filespaces from one nodename and can do restores for 
> any of them.
>
> But another big plus is that as the shares grow, if we need to take a machine 
> that is doing 10 of the shares and split it across 2 machines doing 5 each, 
> we do that and the location of the filespaces doesn???t change, and the 
> helpdesk doesn't have to hunt around or have a chart to find things.
>
> Useful in this setup to maintain sanity for the help desk.
> Wanda
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Zoltan Forray
> Sent: Friday, November 21, 2014 1:06 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Backing up Isilons with TSM
>
> Thanks for the feedback.  We agree on EMC - they like to sell hardware......  
> Of course they support DataDomain!
>
> No, I have never setup a "proxy relationship" - anything you can offer about 
> this process would be helpful!
>
> At this point, when it comes to any Windows users of the Isilon, we will have 
> to go the "setup a dumb server to act at the backup box for the CIFS shares" 
> like we do with lots of other EMC storage/mounts (we have one right now 
> running 40+ TSM node/clients purely for CIFS backups).  As for *NIX 
> users/mounts, no idea how they want proceed on that.
>
> Z
>
> On Fri, Nov 21, 2014 at 12:59 PM, Prather, Wanda <Wanda.Prather AT icfi DOT 
> com>
> wrote:
>
> > It's awful.
> > Only saving grace in my case is that the data is mostly images and
> > doesn't change much.
> >
> > I assume you've had experience setting up proxy relationships - use
> > many proxy machines to back up the individual shares on the Isilon, so
> > you can have them all working at once.
> > Then back up over NFS or CIFS.
> >
> > I can't believe EMC is still so far behind the times that they offer
> > no intelligent way to back up their NAS devices (e.g. Netapp Snapdiff
> > or V7Unified imbedded TSM client).
> > But then, they tell their customers that the appropriate thing to do
> > is buy a second Isilon and replicate.
> >
> > I have never understood how that is appropriate - manual deletes and
> > directory corruption replicate, too.
> >
> > W
> >
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> > Of Zoltan Forray
> > Sent: Friday, November 21, 2014 11:00 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: [ADSM-L] Backing up Isilons with TSM
> >
> > Anyone have experience backing up an EMC Isilon and can share
> > war-stories, methods, etc?
> >
> > --
> > *Zoltan Forray*
> > TSM Software & Hardware Administrator
> > BigBro / Hobbit / Xymon Administrator
> > Virginia Commonwealth University
> > UCC/Office of Technology Services
> > zforray AT vcu DOT 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
> >
>
>
>
> --
> *Zoltan Forray*
> TSM Software & Hardware Administrator
> BigBro / Hobbit / Xymon Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> zforray AT vcu DOT 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

--
-- Skylar Thompson (skylar2 AT u.washington DOT edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine