Aloha
is there a possibility to restore singe or multipl files from the tsm
administration console on the server.
with regards
MNibble
--
definitiv! business applications GmbH & Co. KG
Fresnostrasse 14 - 18
Hello,
one reason why I updated to version 5.3 was that there is the
possibility to create collocation groups.
I have now packed all small servers (about 20 of them) in one group,
about 10 medium servers in another group and I made groups for large
servers with about 1-3 nodes each. So now no s
I would guess that the TDP account for SQL Server just has to be a
member of the db_backupoperator role in each database. Once you give it
this role in each database (including model) it will automatically have
this role in any new database (because new databases start off as copies
of model).
Ho
TSM has been able to connect to an STK library running ACSLS since V5.1. New
in V5.3 is the ability to share the library between two or more TSM instances
within TSM. Prior to V5.3 you had to purchase EDT to share drives in an STK
library controlled by ACSLS.
I haven't seen anything posted a
Run a backup of C:\documents and settings\. Under this folder in subfolders
you will see *.dat and *.dat.log files. These can not be backed up unless you
have OFS running. This will help you verify that OFS is working correctly
Thomas Rupp <[EMAIL PROTECTED]> wrote:According to
"IBM Tivoli St
Folks,
I remember seeing an email previously announcing that TSM Ver 5.3
and ACSLS is not supported at this time.
Am I correct?
Thanks!
DaveZ
I have been handed a TSM system in the past week that has been running for
a year. IT has collocation = yes for TAPEPOOL and COPYPOOLS. this system
is running TSM 5.2.2.
We have run out of tapes as the setting for collocation (yes) is trying to
use a tape for each node (as I understand it, ,,pl
You da man :-)
Exactly 3 entries deleted that I didn't want. Seems so obvious that I
should have tried that. But that's easy to say in hindsight.
Thanks,
Ed
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Mark D. Rodriguez
Sent: Thursday, August
Edward,
I would like you to try re-running the command without specifying the
"devclass", i.e:
delete volhist todate=04/30/2005 type=dbb
The "devclass" parameter is superfluous in this case. Although, it's a
good habit there is no need to quote the date in this command.
--
Regards,
Mark D. R
Bill, off-hand I don't know why those mutex-related messages came up. If
those can be reliably reproduced, then a call to technical support might
be in order (sorry, but there are a lot of unknowns that prevent an "aha,
here is your problem" kind of answer). But I don't see how those messages
would
Thanks for the info. I will have to keep an eye out for that situation
the next time I upgrade. The Backup Series numbers (405, 409, 410) are
lower than the lowest number of the current backups (574 to 593). So
that doesn't match your problem.
I guess I should also mention this is an AIX server
Edward,
I had a similar problem a while ago. It turned out it was related to
doing a TSM server upgrade. What had happened was it reset the "Backup
Series" number. Then my old DBB backups would not go away since their
sequence number was higher than the most recent one. Try looking at the
"Ba
In the dsmerror.log file these messages came up when I was installing the
services with dsmcutil.exe. The services installed and are
functioning, but during installation the message came up that it failed to
validate the password with the TSM server.
08/24/2005 13:11:13 Mutex lock failed: 6.
08/
Rick,
What you are trying to do is going to take a little bit of work to get
it done. Although you provided us with quite a bit of information I
don't think I have all that I need to help you through this. Also, this
is going to be kind of involved so if you would prefer you can send me a
note
I have two TSM 5.3 servers, one local(TSM1) and one remote(TSM2), running
on AIX. TSM2 has two tape libraries, 3583L1 and 3583L2. TSM1 sends the data
in COPYPOOL1 to TSM2 which stores the data in 3583L2POOL. This has been
working well for a couple of years. Now, I need to send data from COPYPOOL2
Was looking to do this because of
1. Upgrade of the TSM binary will not upgrade all of TSM servers at Once.
If I want to apply a patch I can try it on one TSM server that is less
critical and run it for couple of days before applying it to other servers
(don't have QA box with 100's of clients and
I am having a problem deleting some old volhist entries where the target
was a device class of file.
"q volhist type=dbb" output shows 3 old entries from when I was playing
around with "File Device Class" and did a few "backup db
devclass=FILE_DEVCLASS type=full" commands.
Here is a sample volhis
Open File Support (OFS) operates on a volume-level basis, i.e., all files
on the volume are eligible. There is no indication of which files were
"open" at the time they were backed up.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail:
==> On Thu, 25 Aug 2005 10:41:20 -0400, Tae Kim <[EMAIL PROTECTED]> said:
> I am in a process of splitting up my TSM 5.2.2.4 server on AIX 5.2 ML5 and I
> was wondering if anyone uses separate binaries for each TSM instances that
> are on the same physical server. I know that multiple TSM instan
Hi all,
I am in a process of splitting up my TSM 5.2.2.4 server on AIX 5.2 ML5 and
I was wondering if anyone uses separate binaries for each TSM instances
that are on the same physical server. I know that multiple TSM instances
can share the same binary but I would like to use different binaries
I don't have any answer to help you, but we have 2 TSM 5.2.2.2 servers
on Win2003.
Never had this problem.
They are dedicated TSM servers though - no other applications.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Vincent RATAJSZCZAK
Sent: Thursd
Hi all TSM lovers =)
I'm having a quiet annoying problem with my 5.2.2 TSM servers.
Since we are now under Windows 2003 with TSM 5.2.2 (before NT server and
5.1.5), we have a strange behaviour with the pooldisk.
Sometimes, we may have to stop the "TSM Server" service, and then to
restart it (af
TSM serv = 5.2.2.0
TSM TDP = 5.2.1.0
I'll spare you the political details, but our SQL Server admin is claiming
that NIST standard required him to remove SQL access from the SYSTEM
account. We created a specific AD id and have been testing, but he wants to
not grant this id SA priv, for the same
> ...
> tsm: DS3>upda drive 3494 3590_p4 wwn=50050763004060d6
> ANR8420E UPDATE DRIVE: An I/O error occurred while accessing drive
> 3590_P4.
> ANS8001I Return code 3.
You probably have path definition problems.
See the description of that msg in ADSM QuickFacts.
The attached macro will allow you
I quite agree with your comments, IBM have regressed with the new
interface, it's much more complicated than it needs to be.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
PAC Brion Arnaud
Sent: 25 August 2005 12:33
To: ADSM-L@VM.MARIST.EDU
Subje
Bill, off-hand the only TSM client component could (hypothetically) cause
of a blue-screen would be the LVSA module, tsmlvsa.sys. When you installed
the backup-archive client, did you configure it to use online image backup
or open file support?
Otherwise I can't think of anything that TSM could d
Kathy,
Many, many thanks for your help, I'll sleep a litle bit wiser tonight !
However I'm still wondering why IBM engineers built such a
complicated/unusable interface :
- old web interface : 3 clicks, 10 seconds and immediate visibility of
the action schedule I created
- new interface 11 cli
Hi TSM'ers,
1. I moved to TSM 5.3.1.0 yesterday on an H70-AIX-box ( 5300-02 )
from TSM 5.1.9 AIX 4330-11
2. 99% of the migration worked well and in expected time
3. This morning I found a pecularity with resp to 3590-drives in a
3494-library, which is FC-connected to
According to
"IBM Tivoli Storage Manager for Windows: Backup-Archive Clients Installation
and User's Guide" page 62:
Some applications can create files and open these files in such a
way as to deny access to all other processes on a Microsoft Windows
operating system. ...
The following is the
Hello,
I'm testing with the OFS option on Windows and I try to left some files
open, like Access, Word, Excel, text-file on a file-server, but so far I
didn't get any open file messages.
Now I'm wondering for what kind of files (and when they appear as open
during back-up) you can use the OFS op
Bill
I recently suffered from a blue screen on backup and posted the fix a
few days earlier. However, it was with a W2K3 server. I have asked
around and people seem to remember that it also happened on W2K servers.
The culprit was Symantec AV s/w. The essence of the posting follows. It
may not be
31 matches
Mail list logo
