Hello Bruce,
I am using sysback for very long time (definately more than 10 years).
Initially it had no interface to TSM Server and I was using it on the next way:
1) configure one of the AIX servers as NIM Master;
2) configure the same server as sysback server;
3) backup system images from all AIX servers to sysback server;
4) backup system images to TSM server as a normal files.
I understand I am wasting disk space on sysback server, but I decided not to
use direct TSM interfase to backup system images, when it becomes available.
I am still using sysback integrated with NIM Server, because:
1) system images are protected by backups and archives on TSM Server;
2) all AIX systems are protected by NIM without involving TSM Server;
3) we are are planning to use system images backups/archives only in the next
cases:
a) point in time AIX recovery is required for any AIX server (just to
restore appropriate system image instead of the latest kept on NIM server
before recovery);
b) to recover any NIM server crashes (total, some disks or file systems);
c) for out-of-country disaster recovery:
- install NIM server from installation CDs:
- install TSM server from installation CDs;
- install TSM Server software;
- restore TSM database from out-of-country database backup tapes;
- restore NIM server (accept rootvg) from TSM server by using out-of
country copy pools;
- install production AIX servers by NIM server by available system
images;
- restore data on all production servers from TSM server;
- etc.
Unfortunately, I could unswer only on you first question:
In my opinion, you do not need to install sysback server on TSM Server, because:
- sysback is sending system images to TSM Server via TSM Client (it has TSM
client package itself, if it is not installed already);
- during system recovery it should by a possibility to contact TSM Server
during selecting system image.
By the way, take this information as it is, because I do not have any
experience for sysback integrated with TSM.
Regards,
Grigori
________________________________________
From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Bruce
T. Harvey [bruce.harvey.nonemployee AT PNC DOT COM]
Sent: Friday, March 05, 2010 6:14 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM Sysback using TSM Server
I've been a fan of Sysback ever since it was a customer support option,
but I've got just a couple of questions with regard to integration with
the TSM Server. I understand that you need to create a virtual tape
device on the client, that it uses separate exclude lists from the TSM
client inclexcl lists, and that it won't back up (properly) certain types
of filesystems or HSM-managed data. My questions are:
1. Do you also install Sysback on the TSM Server in addition to the
client? With stand-alone Sysback, this is true, but with the TSM
integration does the TSM server already come with the knowledge that
Sysback might be talking to it?
2. Does the TSM Scheduler initiate the backups or does the client run
a cron or scheduler job to do so using the virtual tape device? The doc
seems to indicate the latter.
3. Are the image backup sets stored as an image equivalent or as bits
and pieces of separate files? Are separate tape types used in the library
or just part of the ordinary pool?
4. Since I can't boot from tape in this scenario, are the CD and
network boot options behaving the same as with a stand-alone Sysback
server, point there and shoot until I get the Sysback boot menu? Does
this mean that Sysback needs to be installed on the Server and the client
configured so that it can boot?
There seem to be indicators, but the hard-and-fast is escaping me.
Many thanks!
Bruce
>>>
Bruce T. Harvey
PNC Bank
office 301-699-4013
mobile 443-465-1204
The contents of this email are the property of PNC. If it was not addressed to
you, you have no legal right to read it. If you think you received it in error,
please notify the sender. Do not forward or copy without permission of the
sender. This message may contain an advertisement of a product or service and
thus may constitute a commercial electronic mail message under US Law. The
postal address for PNC is 249 Fifth Avenue, Pittsburgh, PA 15222. If you do not
wish to receive any additional advertising or promotional messages from PNC at
this e-mail address, click here to unsubscribe.
https://pnc.p.delivery.net/m/u/pnc/uni/p.asp By unsubscribing to this message,
you will be unsubscribed from all advertising or promotional messages from PNC.
Removing your e-mail address from this mailing list will not affect your
subscription to alerts, e-newsletters or account servicing e-mails.
Please consider the environment before printing this Email.
"This email message and any attachments transmitted with it may contain
confidential and proprietary information, intended only for the named
recipient(s). If you have received this message in error, or if you are not the
named recipient(s), please delete this email after notifying the sender
immediately. BKME cannot guarantee the integrity of this communication and
accepts no liability for any damage caused by this email or its attachments due
to viruses, any other defects, interception or unauthorized modification. The
information, views, opinions and comments of this message are those of the
individual and not necessarily endorsed by BKME."
|
