Thanks Dave, that explains everything!
On 5/21/06, David Longo <[EMAIL PROTECTED]> wrote:
I started a thread on this about 9 months ago.
Short summary: The "tsm barocde length" on AIX is
for LTO1 and LTO2 tapes only - note comment by that on your lsattr output.
The outout is corect, LTO1/2 w
This information is not correct.
You can schedule a Data Protection for Exchange node.
Use the ACTION=COMMAND type schedule.
There is an appendix in the Data Protection for Exchange
User's Guide that shows you exactly how to do it.
Thanks,
Del
I can understand how it can be a little confusing,
but if the management classes were used how you suggest,
it would contradict the whole basis of management classes
in the backup copy groups. This is backup, not archive.
That means each backup object on the TSM server, with
the same name, gets th
Hello,
We upgraded TSM from 5.2 to 5.3.3 over the weekend.
We also upgraded AIX on that server from 5.2 to 5.3.3
After the AIX upgrade, TSM aborts on startup from /etc/inittab
However, opening a terminal window an enetering the same startup brings
up TSM with no problem. In fact, it is still r
Without resulting messages or AIX Error Log problem indications, we
can't provide a lot of assistance, but these thoughts...
- It's not a good idea to direct service messages to the console,
both because they become lost and because there can be issues
with the console. It's better to hav
Hi TSMers,
I have looked through the archive and docu but did not find :
Scenario:
nodes at a local tsm-server with only disk-cache (limited space) and
migrating data via server-server to a remote-tsm-server
having the tapes (with much more space)
the question is now:
is it possible to make use
the conslog shows:
1148172312 May 20 20:45:12 tsmserv syslog:err|error syslogd: unkn
own priority name "*": errno = 2
the entry in /etc/inittab has remained much the same since ADSM 3
TSM was upgraded and brought up prior to the AIX upgrade, so it
appears to be something related to the AIX upg
Larry - Review your /etc/syslog.conf file...
The 5.3 AIX level may be more stringent about its historic contents,
or the AIX 5.3 install may have changed something in it.
It sounds like there is an asterisk in a Priority position in the file.
Richard Sims
On May 22, 2006, at 10:23 AM, Lawrenc
Just finished doing the same thing.
We created a new TSM server on RH Linux 4 (We had too many issued with
Windows not wanting to share Fibre-Channel attached tape drives) and
either:
1. Performed EXPORT TO SERVER
2. Created new same named nodes and then deleted the old backups from the
zOS ser
>> On Mon, 22 May 2006 16:14:28 +0200, Rainer Wolf <[EMAIL PROTECTED]> said:
> the question is now:
> is it possible to make use of the group-collocation-feature when
> having disk-cache as Primary StoragePools and the next-storagepool
> is on a remote-tsm-server's virtual volumes ?
I think you
On Fri, May 19, 2006 at 10:05:38PM -0400, Allen S. Rout wrote:
> > I have questions about server sizing and scaling. I'm planning to
> > transition from Networker to TSM a client pool of around 300 clients,
> > with the last full backup being about 7TB and almost 200M files. The
> > TSM server pl
> Is there an updated Faq that addresses the unix client JBB?
No, not at this time.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
IBM Tivoli Storage Manag
>> On Mon, 22 May 2006 11:57:20 -0500, Dave Mussulman <[EMAIL PROTECTED]> said:
> On Fri, May 19, 2006 at 10:05:38PM -0400, Allen S. Rout wrote:
> I don't have a lot of a priori knowledge of TSM, so any sizing
> recommendations I've seen have come from the Performance Guides,
> interviews with a f
With 200M files and only 7TB you must have many small files. To guess
at how many objects will be in your DB you could use the file count from
an incremental backup. Just multiply by your retention and add the base
count.
For comparison purposes I have 149M objects in a 71% used 94GB DB. The
so
14 matches
Mail list logo
