We do it for some small machines. It works. The answer is, of course "it
depends on your situation."
These are small machines that aren't terribly critical - if we lost one, we
could take 24 hours to rebuild it and the users would still be happy (give
that their other choice is to have to recustomize).
If your clients are very large, or very time critical, it is less likely to
work for you.
Maybe this is a case where you want to back up just a few directories, not
the whole C: drive.
I would definitely turn on client compression.
This is also a good case for trying to use backupsets.
If they need a massive restore, you create a backupset on your end,
cut a CD, then fed-ex it overnight, and restore it there from the CD.
Just depends on what your requirements are for that system.
And giving it a try is harmless, the TSM backups won't interfere with their
current NT backups.
So you could also do both - use the ntbackup for local stuff, then use the
TSM backup as a failsafe/offsite backup in case the local is indeed
unreliable/not done.
Try one and see how it works out!
-----Original Message-----
From: David Nash [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 04, 2001 11: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
