BACKINT call was not successfull

2011-03-23 Thread Yudi Darmadi 
Hai All,

Need some advice about TDP SAP-Oracle.
I got this error when running backfm, "BACKINT call was not successfull". Does 
anyone solve this problem before? 

In TSM actlog: ANR0480W Session 48843 for node MYNODE (TDP R3 AIX) terminated - 
connection with client severed.

Here's the TSM Environment:
TSM Server V5.5.3.0 - Win2k3
TSM CLient V5.5.2.0 - AIX5.3
TDP SAP V5.5.0.0 
SAP- Oracle version : SAP R3 4.7 ext 200, Oracle 9.2.0.7.0
Kind Regards,



Yudi Darmadi

+62 819 055 30830

Tsm v6 migration question

2011-03-23 Thread Lee, Gary D. 
We are preparing to migrate our tsm v5,5,4 system to 6.2.2.


Are there any rules of thumb for relating db size in v5.5.4 with what we will 
need under v6?

I assume it will be somewhat larger being a truly relational structure.

Thanks for any help.


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

Re: Tsm v6 migration question

2011-03-23 Thread J. Pohlmann 
Gary, please take a look at

http://www-01.ibm.com/support/docview.wss?uid=swg21421060&myns=swgtiv&mynp=O
CSSGSG7&mync=E

I found that the actual amount of space for the DB has been , 2 X. I
generally recommend that a file system of 3 X the v5 database be set aside.

Regards,

Joerg Pohlmann

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Lee, Gary D.
Sent: Wednesday, March 23, 2011 10:44
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Tsm v6 migration question

We are preparing to migrate our tsm v5,5,4 system to 6.2.2.


Are there any rules of thumb for relating db size in v5.5.4 with what we
will need under v6?

I assume it will be somewhat larger being a truly relational structure.

Thanks for any help.


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

Re: Tsm v6 migration question

2011-03-23 Thread Anders Räntilä 
My experience from the latest upgrades are that the database will 

grow by 10% when upgrading from 5.5 to 6.2.2.2.

 

2 days ago upgraded a 5.5 server to 6.2.2.2 and this happened 

with the database size:

 

 

**

*** ---> Q DB F=Dfrom TSM 5.5

**

 

 

Available Assigned  Pct  Max.   

Space Capacity  Util  Util  





   (MB)  

-  - - 

  120,000  120,00   74.2  74.2  


 

 

This is 120GB*74.2% = 89GB used

 

**

*** After the upgrade to 6.2.2.2 

**

 Database Name: TSMDB1

Total Size of File System (MB): 737,233

Space Used by Database(MB): 97,216

 

 

All the upgrades I've done during the last 6 months show the same pattern.

 

When TSM 6.1 was released IBM said the DB would grow approx. 3x (300%), 

but that doesn't seem to be the case today.

 

Of course if you start adding features like dedup the DB will grow. I 

have one installation that was 40GB in 5.5 and today is around 800GB.

This growth is mostly caused by dedup (add 1TB of DB disk and save 75TB 

of stgpool disk)

 

 

-Anders Räntilä

 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

RÄNKAB - Räntilä Konsult AB  

Klippingvägen 23

SE-196 32 Kungsängen

Sweden

 

Email: and...@rantila.com  

Phone: +46 701 489 431

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=