ADSM-L

Re: [ADSM-L] Moving NSF backups between servers

2012-09-25 10:58:27
Subject: Re: [ADSM-L] Moving NSF backups between servers
From: Zoltan Forray <zforray AT VCU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 25 Sep 2012 10:32:57 -0400
Thanks for the response.

In reality, we are trying to move the existing backups to another TSM node
that is going to take over the NFS mountpoint once this server
is twilighted so we wont have to re-backup this mountpoint.

On Mon, Sep 24, 2012 at 9:26 AM, Allen S. Rout <asr AT ufl DOT edu> wrote:

> On 09/21/2012 09:37 AM, Zoltan Forray wrote:
> > We are twilighting our Solaris servers, especially older ones still
> running
> > Solaris 8 and older (Oracle just wants too much money these days, even
> for
> > EDU) and this question has arisen:
> >
> > *Is there a way to move an NFS filesystem's backups to another node for
> > management? Of the old Solaris boxes that I can take offline, a couple of
> > them are managing backups for our big NFS-mounted SAN storage
> filesystems.
> > Will I just have to suck up some bandwidth and re-do them all?  *
>
>
> Let me restate what I think you're asking about:
>
> You have a NAS device; I'll call it "Netapp".
>
> You have some filesystems on it.  I'll call an exemplar /local/vcu
>
> You have a solaris box that has been backing up /local/vcu by mounting
> it and adding it to the DOMAIN.
>
> You now want to keep on doing that from a different piece of hardware.
>
> If this is the case, then I think you should be mostly fine;  you may
> have some ACL issues because of some random difference between Solaris
> and (I assume) Linux NFS, but you can just define a server stanza on New
> Hardware that uses the old node name, make sure the paths are the same,
> and then soldier on.
>
> If you're using the solaris server nodename to contain the NFS
> filespaces, you might need to re-back-up the server itself.
>
> The most common problem we have with such issues is changing aggregation
> of filespaces.  i.e. we used to back up home3 and home5 from node
> proxy-01, but now we want to do home5 and home8 together on proxy-08.
> There, you've got some issues;  the fully deployed solution to that is
> to associate each filespace with its own nodename, and then you can move
> nodes _and_ filespaces around on proxy hardware to your hearts' content.
>
>
> - Allen S. Rout
>



--
*Zoltan Forray*
TSM Software & Hardware 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

<Prev in Thread] Current Thread [Next in Thread>