We will be assigned a range of slots. We tell them what tapes to put in
what slots, so it's under our control -- but we also have to keep track.
David Longo
cc:
Sent by: "ADSM: DistSubject: Re: vaulting
Hi everyone,
We have a small problem in that our vaulting company only references tapes
by slot number, not by volume serial number. So, we'll need to keep some
kind of database of what tapes are offsite and in which slots. We will be
using DRM, and I was thinking we could update the database w
Yes, we moved TSM off of a mainframe and onto a Sun/Solaris platform. We
are very pleased with the performance. If you have archive data then you
need to "move data" which will take a long time. For backups, we pointed
all clients away from the mainframe and to the new Sun server, so all new
ba
If you can, I would uninstall 4.2.1, then reinstall 4.1.0. Then try the
database restore. Then upgrade to 4.2.1. I don't know if that would help,
but it would eliminate the version difference as a cause of the problem.
adam
Adam Boyer
Communications Analyst
Board of Governors of the Federa
I think if the files are not owned by the user running the dsm client
(you), then you won't be able to see them. If you have root, try using
it. Otherwise, you may need to get the owner to run the dsm client.
adam
"Burden, James" wrote:
>
> Hello all,
>
> Wondering if anyone can help with th
I wanted to limit the number of people who can fire up the TSM GUI on some
NT boxes and start restoring files. I thought the best way to do this was
to set the passwordaccess option to 'prompt', and then give the password to
only a select few. My only concern is that this may affect scheduled
op
A few days ago, about 40 NT/2000 clients failed to backup. The error for
all of them was:
ANR2716E Schedule prompter was not able to contact client
CLIENT001 using type 1 (1.2.3.4 1501).
The clients are 4.2.0 and the server is 4.2.1. Not only did they fail, but
the cl
Yes, I saw something like this a week or two ago. On a Friday night all
the client schedules started to fail, giving errors like "Schedule lock
problem", etc. and some other weird stuff I've never seen before.
Because it happenned on a Friday, none of the weekend schedules, client
or admin occurr
We had this same problem, and following the instructions in the readme
didn't solve it. If those instructions don't help you, you might try
this which I found in the archives. It did the trick for us.
---
You need to run the file called "instmsiw.exe" that's within the
directory
I will be out of the office starting 11/20/2001 and will not return until
11/27/2001.
I will respond to your message when I return. If you have any questions,
please contact Stone Wang (x3731) or John Wesner (x3231).
I will be out of the office starting 11/20/2001 and will not return until
11/27/2001.
I will respond to your message when I return.
We got that error once. I opened a case with Tivoli support but they
never came up with anything. It isn't reoccurring regularly, however.
We're running TSM server 4.2.0.1 on Solaris 2.7.
adam
Matthias Feyerabend wrote:
>
> Hello,
>
> we get reproducable errors on Windows2000 Server 4.2.1.7
Hey,
Our management is wondering if it's safe to just do incrementals
forever, or whether we should try to do a forced full every few months
to keep things fresh. Our experience has been that the incremental
system works great-- we once restored a whole raid 5 array, with many
files from years a
If the filesystem is solely dedicated to TSM database volumes, does it
matter if the usage is above 90%? (an honest question)
> "PINNI, BALANAND (SBCSI)" wrote:
>
> Look for filesystem where ur db volumes are installed .
> df -k|grep
> %used should not be above 90%.
> If so expand filesystem th
Please give a more detailed account of the errors you are receiving
(such as error code, activity log entries, etc.).
adam
Nazir wrote:
>
> I have been working with TSM to make backups of my servers.
> The TSM server is on Windows NT and It is working with tapes too.
> The TSM makes backups an
DRM will delete DB backups based on the value set by:
SET DRMDBBACKKUPEXPIREDAYS
I have seen that if you prune the volume history of database entries DRM
loses track of those pruned entries.
William Boyer wrote:
>
> I believe that DRM will only expire DBBackup VIRTUAL volumes, not normal
> DB
One other question:
Did your IBM CE do any work on the library recently? In our case, we
used rs232 to talk to the LM during our evaluation. Then when we bought
the 3494, the CE came in, made some changes and rs232 stopped working.
It turns out that one of the changes included swapping out the
Hi TSM Gurus,
Due to some misunderstanding, an unnecessary 5 million files was backed up,
bloating our database by about 15 GB. I have since commenced deleting that
filespace, but it looks like the delete is not reducing the database size
nearly enough. So I am planning to do an unload/reload, a
Thank you for your response, Richard.
The reason I believe there is a compelling reason is that before this 5
million file backup, our database was about 43 GB. When the backup
finished, the database was about 62 GB. After deleting around 4 million
files, the database is still around 60 GB. Th
;ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>
03/09/2003
04:21 PM
Please
respond to
"ADSM: Dist
Stor
Hi Michelle,
Have the restores worked successfully in the past with your current
configuration? Are you backing up transaction logs? Please mention a
little bit more background info.
adam
Michelle Wiedeman
<[EMAIL PROTECTED]To: [EMAIL PRO
21 matches
Mail list logo
