5546
Pager:8777372280
John.R.O'[EMAIL PROTECTED]
-Original Message-
From: Mark Stapleton [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 05, 2001 9:23 AM
To: [EMAIL PROTECTED]
Subject: Re: Backing up exchange servers using Veritas interface to TSM
"O'Connell, John R" wrote:
Thanks, This is a great article. I have been going round and round
with my NT group here. They keep insisting that they need to run weekly
archives of 40 - 80GB systems every week over a 100mb ethernet network. I
am almost at point where I will have to split the server our current data
We are going to start backing up our MS exchange servers. I would
prefer to use the TDP for M/S exchange. Our exchange & NT people would
prefer Veritas because it does mailbox or brick level backups. They would
use the VERITAS to TSM interface to store the backups on our TSM server. Is
We have noticed a problem between MCAFEE Virus Scan & TSM client
either 3.7.2 or 4.1.1. What happens is a backup is initiated either through
the scheduled or on demand, the registery gets backed up, and shortly after
the TSM client will not transfer any data. The TSM client times out (In
I would suggest running a archive. I have to do this for all of my
NT systems. Once a week I have a multiple archive schedules that run a
archive and the archive copygroup is set for 90 days.
John R. O'Connell
Phone:408-492-2042
Pager:408-949-1432
John.R.O'[EMAIL PROTECTED]
-Origi
Thanks for the replies. All of them have helped.
John R. O'Connell
Phone:408-492-2042
Pager:408-949-1432
John.R.O'[EMAIL PROTECTED]
-Original Message-
From: Richard Smith [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 27, 2000 6:56 AM
To: [EMAIL PROTECTED]
Subject: Re: Bare
We currently have an open PMR for trying to restore a registry on a
NT system. It appears to me that there is a overall problem restoring NT
registry with TSM. We are about to try out Bare Metal Restore from The
Kernel Group. This product appears to works with TSM on restoring a entire
We are running TSM on a OS/390 platform. The LPAR that our
production TSM runs in has four different connections. Two are reachable by
different host names & 2 by IP address only. Clients connect in based on
what network they are connecting in from. Three connections come in on a
OSA/2
Our TSM server running on a OS/390 serves multiple customers. For
each customer I have a separate policy domain & separate archive & backup
disk storage pools and when they migrate they migrate to a common 9840
cartridge storage pool. For those who are backing up more than one customer
f
