Hi Steve,
Thanks for your help !
I have a problem with your proposal to "delete contents of db, active log and
archive log directories" : how are you doing this ? Is it just "rm -R *" in the
respective directories ?
Cheers.
Arnaud
*
yes Arnaud,
I just ran rm -Rf * as the instance owner
Steve.
On 22/02/2011 9:02 PM, PAC Brion Arnaud wrote:
Hi Steve,
Thanks for your help !
I have a problem with your proposal to "delete contents of db, active log and archive log
directories" : how are you doing this ? Is it just "rm -R *"
Steve,
I cannnot believe it is that simple (for once with DB2/TSM !)
Thanks again for your help ;-)
Cheers.
Arnaud
**
Corporate IT Systems & Datacenter Responsible
Panalpina Management Ltd., Basle, Switzerland,
CIT D
Steve,
I'm now facing another issue: formatting is ending with following error:
ANR0367W The server failed to format the database TSMDB1. This database name
already exists.
ANR2678E Server database format failed.
Any idea on this ?
Arnaud
*
first: db2 drop db tsmdb1, or dsmserv removedb tsmdb1, then delete the leftovers
On 22 feb 2011, at 08:57, Steven Harris wrote:
> I just did this
>
> shutdown TSM
> delete contents of db, active log and archive log directories, run
> dsmserv format.
>
> Regards
>
> Steve.
>
>
> On 22/02/201
Hi Remco,
Thanks for your hints !
I choosed option "db2 drop db TSMDB1", which worked, then removed the contents
of DB, LOG and LOGARCH directories, then issued "dsmserv format ..." which
worked too ! So far so good !
I'm now facing next issue : trying to use "dsmadmc" to enter TSM, I'm unable
Hi,
Maybe you can try this: stop tsm server1 service, then start the tsm on
foreground, from server/bin directory, run dsmserv. Then try to update the
administrator and password from the server console, halt, then start the
service in background as normal process.
Yudi Darmadi
http://www.npp-a
Hi all,
Anyone out there successfully installed and configured TSM Server 6.2.x.x on a
CENTOS box?? I was hoping that, being based on Red Hat and allit should
work
Any information is appreciated.
Regards,
Mario
Hi all,
I have TDP SQL 5.5.4.0 installed on a Windows 2008 x64 boox running SQL Server
2008. I am getting the RIGH0053E error when trying to open the TDPSQL GUI.
I have double checked all pre-reqsand everything is in place. The
tdpsql.cfg file is NOT present at the appropriate directory thoug
Mario,
Check this:
http://adsm.org/forum/showthread.php?22078-Error-TSM-for-MS-SQL
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 02/22/2011
08:32:11 AM:
>> From: Mario Behring
>> To: ADSM-L@vm.marist.edu
>> Date: 02/22/2011 08:50 AM
Hello,
we are testing full backup and full restore of VMware virtual machines
using TSM client 6.2.2 and vStorage API with VMware 4.0.
We installed a extra physical backup proxy server with SAN and LAN
connection to VMware and LAN connection to the TSM server.
Sometimes the data goes over the SAN
Hi Mario,
I've got a working TSM 6.2.2.2 on a CentOS 5.5 (64-bit) VM running.
There were no problems installing/configuring it (though slow, because of
limited resources of the VM (only 3GB)).
I recommend that you give at least 8GB (12GB if running64-bit)) to the
CentOS box.
Richard.
2011/2/22
Hello,
I forgot to tell: The Backup using the SAN is 3 times faster (15 to 45
MB/sec); so we want to force using the SAN.
Any ideas?
Thanks in advance!
Andreas.
TSM
Gesendet von: Andreas Boesler
22.02.2011 18:29
An: ADSM-L@VM.MARIST.EDU
Kopie:
Thema: full backup
I can also confirm that I've had it working fine in test. You're obviously
gonna have support issues if you want to lo a call with IBM though.
Steven
I've got a working TSM 6.2.2.2 on a CentOS 5.5 (64-bit) VM running.
There were no problems installing/configuring it (though slow, because of
Andreas,
A full proxy backup will typically choose SAN if is able. I would double-check
to make sure all of the VMWare host luns are zoned to the proxy correctly, this
is typically what causes these backups to drop back to LAN.
Steve Schaub
Systems Engineer II, Windows Backup/Recovery
BlueCross B
Sometimes the data goes over the SAN between the backup proxy server and
VMware and sometimes the data goes over the LAN between the backup proxy
server and VMware.
Please don't take this the wrong way :) but are you sure its the link from
VMware to the proxy sometimes going over the LAN and not
Hi Everyone,
I'm backing up a 2TB filesystem through NAS NDMP protocol and it did not write
the TOC. How can I find out why it didn't write the table of contents? I
don't see an error as to why it didn't write the TOC.
Any suggestions?
Thanks in advance!
Thi
>> On Tue, 22 Feb 2011 15:20:53 -0500, "Moyer, Joni M"
>> said:
> I'm backing up a 2TB filesystem through NAS NDMP protocol and it did
> not write the TOC. How can I find out why it didn't write the table
> of contents? I don't see an error as to why it didn't write the
> TOC.
"Me Too". But
Hi Allen,
Do you put TOC=preferred? Or TOC=YES? I have the same TSM release on an AIX
5.3 server and I have an EMC NS704G. Are you ever able to back it up? Just
thought I'd ask.
Thanks!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Alle
Some sample messagesjust in case they help.
ANR1108W,srverr # The server is unable to create a table of contents for
node CNASELDNP0991DM2, file space /root_vdm_5/dnp
1acifs03 in storage pool ONSITE_DISK.
ANR1112W,nsaerr # No table of contents destination storage pool
available for backup se
Hi Richard,
I found it!
Date/Time Message
--
02/22/11 08:29:43 ANR4949E The server is unable to write to table
NDMP.Image.Contents(TEMP) because there is not enough
Joni, Allen,
A lack of available temporary space in the TSM server database could
account for no TOC being created. But indeed, if the TOC cannot be created
then TSM should issue some kind of message. If nothing in the activity log
hints at the issue, then the only thing I can suggest would be to
Hi Andy,
If I did get the message I had below, what is the resolution to the issue?
Increasing the size of the TSM database? Or could this be a different issue?
This TSM database was only allotted 25 GB and I can extend it if necessary.
Just let me know what your thoughts are.
Thanks!
Dat
It is generally illuminating to enable logging of the NDMP session on the
filer, and watch the results as an NDMP backup is run.
IIRC, if there is not enough space on the filer to create the TOC, the
error will be as you describe below.
[RC]
From:
"Moyer, Joni M"
To:
ADSM-L@VM.MARIST.EDU
Date
Hi Joni,
Yes, if you look up the ANR4949E message (you can do "help anr4949e" or
"help 4949" from the admin command line interface), it will indicate that
extending the database size is the way to go.
Best regards,
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
25 matches
Mail list logo