We do this also with over 150 sites. Normal file restores are not a problem
but if the box fails or corrupts itself then we rebuild a box here and let
them run over the WAN until we can ship it out over the weekend. For boxes
coming in over the wan I have a client option set that makes sure they use
compression since some of our links are very slow (56K) Its all been working
well here for years.
The only warning I would give is if you are using any type of connect agent
you may want to make sure you are using a fast enough link. The exchange
agent especially is not very forgiving of "bumps" in the network. I believe
this is a safety mechanism built into the agent that protects the integrity
of the stores. When we first started using Exchange some backups would take
over 36 hours. Any "bump" in the network would cause the whole thing to
fail and we would have to start all over again. Now all sites that warrant
their own Exchange Server automatically get their own TSM server.
Jack
-----Original Message-----
From: David Nash [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 04, 2001 1:07 PM
To: [EMAIL PROTECTED]
Subject: Re: Backup of Remote Sites
The boxes range in size for 1G to 45G. But, the
amount of daily change is small. I really like the
idea of having the data here. That way, if we need to
we can rebuild the box here and take it to the remote site.
--David Nash
Systems Administrator
The GSI Group
----- Original Message -----
From: "Cook, Dwight E" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 04, 2001 11:37 AM
Subject: Re: Backup of Remote Sites
> Client compression would be very helpful...
> How big are the boxes ? ? ?
> and a full restore would take time but the data would be there.
> I've backed up NT boxes from Atlanta GA into Tulsa OK (I'm pretty sure
the
> nodes are still registered...)
> they run fine but my network speeds are a little better than what you've
> mentioned.
> Ya know... it wouldn't hurt to toss on the client and do an initial test
and
> see.
> Worst case, you delete its data from the server and delete the client.
> Always a bottle neck somewhere :-(
>
> Dwight
>
> -----Original Message-----
> From: David Nash [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 04, 2001 10:50 AM
> To: [EMAIL PROTECTED]
> Subject: Backup of Remote Sites
>
>
> I have a question for all of the *SM/Network experts
> out there. We have a central office that we just
> started using TSM at. We also have several remote
> offices that are connected to central office via
> dedicated lines. Theses sites currently are running
> their own backups via NTBackup. We are concerned that
> these backups are unreliable/not offsite/not being done.
> The dedicated lines are mostly 256Kbs lines but a few
> are smaller. Is it a good idea to try to back up these
> sites across the WAN using *SM? We realize that the first
> backup would take a while, but after we suffer through that,
> the amount of changed data would be small. Is it a good
> idea in this case to turn on client compression? Any
> suggestions would be appreciated.
>
> Thanks,
>
> --David Nash
> Systems Administrator
> The GSI Group
>
>
