Re: adsm3.1 to tsm 3.7 gotcha
2000-03-20 15:21:53
We don't have any DRM or server-to-server licenses but are managing to
exchange DB backups b/w 2 ADSM servers manually.
Our environment is
OS = SUN Solaris v2.6
ADSM = v3.1.2.1
2 x 3590 (B11s) with a 10-slot ACL SCSI library each
We set up the following manual DB exchange between our servers to save
having to use one scratch cart per day in our 10 slot stackers for DB
backups, as we use almost all the 10 carts daily for archive/backup. If we
used one cart per day, and kept each for one week we practically had to
devote one whole stacker to DB backups unless we checked out the cartridge
each day and replaced it.
We were able to do it by
o writing the DB backups to disk (COMMAND = backup db type=full
devclass=dbbackup)
o then using a UNIX script to transmit them to the second server
o Once there they are archived (retention period = one week) and deleted
by the second server (COMMAND = -archm=MC1WEEKA -delete -filesonly)
We do this both ways between the two servers. So we are able to retain
copies of our DB at both sites, doing away with the need for copying the db
backup carts and sending them offsite.
DEVCLASS=DBBACKUP is as follows
adsm> q devclass dbbackup f=d
Device Class Name: DBBACKUP
Device Access Strategy: Sequential
Storage Pool Count: 0
Device Type: FILE
Format:
Est/Max Capacity (MB): 500.0
Mount Limit: 1
Mount Wait (min):
Mount Retention (min):
Label Prefix:
Library:
Directory: /opt/IBMadsm-c/backup
Server Name:
Retry Period:
Retry Interval:
Last Update by (administrator): ADMIN
Last Update Date/Time: 03/10/2000 10:56:21
Hope this helps.
Rik
Reinhard Mersch <mersch AT UNI-MUENSTER DOT DE> on 16/03/2000 23:42:24
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Rik Foote/WestpacTrust/NZ)
Subject: Re: adsm3.1 to tsm 3.7 gotcha
WHAT?
If I just want to exchange DB backups between TSM servers, I need DRM?
This is not true, is it?
And if my 3.1 servers now have the licenses for server-to-server, and I buy
the upgrade to TSM 3.7, I will lose that feature? Tivoli, you do not mean
that seriously, do you?
Cook, Dwight E writes:
> Well, (yes I'm getting slow in my old age) getting around to
performing
> upgrades to TSM 3.7
>
> This might have already been touched on...
>
> ADSM with the server-to-server license allowed for virtual volumes for
what
> ever use...
>
> now in the new TSM if your virtual volumes are data base backup volumes
> and/or copy storage pool volumes you must have the DRM license...
>
> I think this is a little low budget... I've got about a total of 7 GB of
(10
> year archive data) across 12 adsm servers where I have copy storage
pools on
> different servers... mixed-n-matched all over the place... and now I'm
going
> to have to pull those copy storage pools back onto the same server !
>
> I don't use DRM 'cause we have our adsm servers located remote to the
> clients they backup already...
> and I'd just do this remote copy storage pool so we would have the data
> basically in 3 locations... on the client, on the remote adsm server
(which
> would be the client's primary server) and on yet another remote adsm
server
> just for grins (and to make the lawyers happy) and now ARGH !
>
> Well, I guess we could spend TONS of $$$$ for a license that we wouldn't
use
> 99% of its functionality...
>
> OK, I'd better shut up before I get kicked off the list for my whining
:-(
>
> later,
> Dwight
>
> BP-Amoco
--
Reinhard Mersch Westfaelische Wilhelms-Universitaet
Reinhard Mersch Westfaelische Wilhelms-Universitaet
Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum
Roentgenstrasse 9-13, D-48149 Muenster, Germany Tel: +49(251)83-31583
E-Mail: mersch AT uni-muenster DOT de Fax:
+49(251)83-31653
The views expressed in this document do not necessarily reflect those of
Westpac Banking Corporation
Westpac Banking Corporation is incorporated in New South Wales, Australia
|
|
|