A colleague insists that TSM service once told him that DSMCAD would be
deprecated and that we need to convert to using the TSM Scheduler
routinely.
The TSM 6.3 client manuals, however, refer to both techniques as valid
choices.
Has anyone ever been told by IBM that DSMCAD had been or will be
dep
Nope, I have not heard that. If anything, I think the polling model is
becoming deprecated, since it gives the server less control over scheduling
than the CAD model.
On Tue, Dec 03, 2013 at 09:27:54AM -0600, Nick Laflamme wrote:
> A colleague insists that TSM service once told him that DSMCAD wou
Nick,
The 6.2 Windows Backup/Archive Installation and User's Guide, page 209, says
dsmcad is the preferred scheduling method. Also, Tivoli Storage Manager
traditional scheduler services "Requires higher use of system resources when
idle" and "Restart the traditional scheduler periodically to f
Hello,
I use TSM (ADSM) since v3.x, I always used that technique.
Yesterday I tested the new migration process to tsmcli v6.4.1.5 without
problem and I WILL continue use this metod.
Simplicity and RAM consumption are the advantages of that method.
Ciao
Saluti
MT
2013/12/3 Schneider, Jim
>
In the "Client-acceptor scheduler services versus the traditional scheduler
Services" section on page 225 of the
IBM Tivoli Storage Manager for Windows Backup-Archive
Clients
Version 6.4
Installation and User's Guide
It says "Generally, using the client acceptor daemon to manage the scheduler
Ok, thanks. It looks like we're dealing with some non-technical issue here.
Thanks for the validation,
Nick
On Tuesday, December 3, 2013, Ehresman,David E. wrote:
> In the "Client-acceptor scheduler services versus the traditional
> scheduler Services" section on page 225 of the
>
> IBM Tivoli S
Nick,
Neither scheduling technique ("traditional" and "CAD-managed") is
deprecated.
Best regards,
- Andy
Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead |
stor...@us.ibm.com
IBM Tivoli Storage Manager
Hello,
We currently have a TSM instance running on a Solaris x86 machine, and we would
like to migrate it to a Red Hat Enterprise Linux server. But we are wondering
if we can restore the orginal TSM database to the other server running a
different OS (Linux)?
If it is not possible, how can we mi
I believe the platform must be the same on both the source and target end
of the database restore[1].
As an alternative to a database restore, you could use EXPORT NODE either
directly or via removable sequential media.
[1]
http://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/topic/com.ibm.itsm.srv.do
The only supported option I am aware of is when moving from TSM5 -> TSM6.3.4
I've successfully migrated from AIX TSM5 -> Linux TSM6.3.4 and if your solaris
server is TSM5.5 I would consider it.
http://pic.dhe.ibm.com/infocenter/tsminfo/v6r4/index.jsp?topic=%2Fcom.ibm.itsm.srv.upgrd.doc%2Ft_xpla
Is that just for migrating from v5 -> v6, or can you also do platform
migrations once you're already at v6 for both the source and target levels?
On Tue, Dec 03, 2013 at 04:31:45PM -0500, Shawn Drew wrote:
> The only supported option I am aware of is when moving from TSM5 -> TSM6.3.4
> I've succes
I'm looking at the 6.3.4.300-TIV-TSMAC-Windowsx64.exe download and the
README.htm for that looks like it belongs to TSM Server, not TSM AdminCenter.
The readme link "View server APARs fixed in Level 6.3.4.300" opens to
http://www-01.ibm.com/support/docview.wss?uid=swg21639086 that doesn't includ
Regards,
Unsubscribe
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Vandeventer, Harold [BS]
Sent: Wednesday, December 04, 2013 6:23 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] How to report readme error?
I'm looking at the 6.3.4.300-TIV-TSMAC
13 matches
Mail list logo
