Hi All
I have to disagree about some things here, (not all). I run a large TSM
site, Three TSM server's in production all Microsoft NT server clients
etc, I like TSM, but we have removed TSM exchange backups to a product
called Galaxy(Comvault), you should look at what it can do, and yes I
know o
that I am having trouble with is 230 characters. That should be
well
enough under the 255 character limit. I will try the
USEUNICODEFILENAMES
parameter anyhow.
Rob Schroeder
Famous Footwear
"BURDEN,Anthony" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on
11/14/2001 05:55:17 PM
Plea
I hope this might help.
After reading Andy's last reply I did some searching (thanks Andy for
your nice reply to my last statement that I made which was wrong on my
part).I found that I was out of date on this info. I run TSM client
versions 3.1.08 and TSM 4.1.12, both of these clients continue t
I have been sort of following this thread,
This is not a very technical description, and my understanding of your
problem.
A: you restored your DB.
B: you audited your on-site tapes with the fix option
C: you try to reclaim the off-site tapes and you get "magic numbers"
What I have seen on my s
Good morning guys and girls
I think you will find that it cannot be fixed by TSM!
The problem is in NT and its limitations not TSM. NT provides you with
long file names 255chars; we all know that and we know that this
includes the path and filename combined. When TSM backs up the
directory/fil
check to see that in your opt file you have the DOMAIN option correctly
entered.
domain c: d: e: g:
or i think
domain all-local works too.
ant
-Original Message-
From: Ofer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 1 August 2001 22:18
To: [EMAIL PROTECTED]
Subject: don't backup new
My last question fetch zero replies so I will try some re-wording.
I run a TSM Server Ver 4.1.3.0 on NT4.0 service pack 6, backing up 100 odd
NT servers using TSM Client Version 4.1.2.12 on NT 2000 servers and TSM
Client Version 3.1.08 on NT 4 servers.
My problem is that when is try to backup a
Just a little issue I am having and was looking for some help/ideas.
I have a SAN that I am attempting to backup and when I schedule the backup
the NT server reboots, this happens every time I try to backup the SAN data
or just the local c drive on the W2K front end. There are no error reported
i
The steps are as follows,
1. Install the TSM exchange agent software onto a different/new exchange
server.
2. Configure the DSM.OPT file to be the sever that you need to restore.
Eg(the name of the server that has the mail box)
3. Restore the exchange private store to the new exchange server, usi
RC32 is an open file...you can not backup the page file...try excluding some
of the NT system files/directories.
-Original Message-
From: Raymond Chao [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 15 February 2001 16:07
To: [EMAIL PROTECTED]
Subject:Restored NT Node failed t
You should not really have to much of a problem,
The tsm client 4.1 is installed on the nt server and will use the system
account to backup and restore files. You do not need to grant authorities
for uses on the NT box itself. Within ADSM server you will need to set up
users and give them the pri
The only solution we have found is to reduce the length of the
directory/file name. Since NT only allows 256 chars and TSM backups up from
the root of a directory structure that is only thing that can be done. Or
you can exclude the directory from being backed up.
Feel free to e-mail me if you wo
12 matches
Mail list logo
