Stef,
Much appreciated, 5.5.4 did the trick. Just one question. For now I have to
share the netezza backups with other nodes
in the same storage pool . I plan on eventually having netezza in its own
domain. The documentation refers to setting
the default management class for the netezza backups but I cant do that without
affecting the other backups.
Since the TSM connector doesn't actually store the files on the file system
would an include in the dsm.sys still
work with the connector. And also is there a way to see the active/inactive
files via the web client.
Include /netezza/.../*.* nzmc
Node Name Type Filespace FSID Client's Name for File
Name
--------------- ---- ---------- ---- --------------------------------------
NETEZZA Bkup /Netezza 2 /netezza/CH_REPORTING/20121031111844/-
1/FULL/md/loc1/locations.txt
NETEZZA Bkup /Netezza 2 /netezza/CH_TEST/20121031111912/1/FUL-
L/data/259908.full.1.1
Thanks,
Tim
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Stef
Coene
Sent: Monday, 29 October, 2012 2:21 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: netezza nzbackup connector for TSM
On Monday 29 October 2012 18:00:08 you wrote:
> I followed the admin guide and my first error was that tsm was not
> configured right, now just native nzbackup fails Even without tsm.
> Did you have to configure tsm to run as service or just have netezza
> call it natively.
Netezza calls it natively and uses the API.
I used TSM client version 5.5. At first, I tried 6.3 but that gave an non-
descriptive error.
Stef
