Rodrigo,
I don't understand your question:
But my gathering data from the db tape will ADD data to the db or
REPLACE / OVERWRITE data on the db ?
Steffan
Rodrigo Cordovil Gazzaneo wrote:
>
> >Rodrigo,
> >1. right; no node or other exports are necessary if you have a backup of
> >your database.
>
> Ok. I take daily db backups and my backup window probably wouldn't allow to
> have extra processing and tapes.
>
> But my gathering data from the db tape will ADD data to the db or REPLACE /
> OVERWRITE data on the db ?
>
> Thanks, Steffan
> Sorry for the mess of ideas !
>
> Rodrigo
>
> >2. If a device address changes (like a tape drive was cabled out of
> >sequence or the number of drives is different or the library scsi
> >address changes, etc.) you will have to modify device configuration to
> >reflect the 'new' environment.
> >
> >Steffan
> >Rodrigo Cordovil Gazzaneo wrote:
> >>
> >> Hi,
> >>
> >> >1. The database backup contains all nodes information so separate
> >> >is not required/necessary.
> >>
> >> So I just need to keep an up-to-date version of my Database, I don't
> >> to keep "exporting" nodes besides my daily DB Backup. Right ?
> >>
> >> >2. Volume history & device configuration. While no modificati
> >> >necessary to volume history, device configuration is quite likely
> >> >different on a different machine (even with the same library and
> >> >drives). You must modify device configuration to enable the datab
> >> >be restored.
> >>
> >> How do you mean modify ? Add to the device configuration file of one
> >> the entries to the other ?
> >>
> >> In one box I have :
> >>
> >> /* IBM AdStar Distributed Storage Manager Device Configuration */
> >> DEFINE DEVCLASS 3590DEVCLASS DEVTYPE=3590 FORMAT=3590C MOUNTLIMIT=DRI
> >> MOUNTWA
> >> IT=60 MOUNTRETENTION=60 PREFIX=L6 LIBRARY=3590LIB
> >> DEFINE DEVCLASS RECLAIMCLASS DEVTYPE=FILE MAXCAPACITY=1843200K MOUNTL
> >> DIRE
> >> CTORY=/local/adsm/reclaim
> >> DEFINE LIBRARY 3590LIB LIBTYPE=SCSI DEVICE=/dev/rmt0.smc
> >> DEFINE DRIVE 3590LIB 3590DRV DEVICE=/dev/rmt0 ELEMENT=16 ONLINE=Yes
> >> /* LIBRARYINVENTORY SCSI 3590LIB L60000 41 101*/
> >> /* LIBRARYINVENTORY SCSI 3590LIB L60001 40 101*/
> >> /* LIBRARYINVENTORY SCSI 3590LIB L60002 39 101*/
> >> /* LIBRARYINVENTORY SCSI 3590LIB L60003 37 101*/
> >> /* LIBRARYINVENTORY SCSI 3590LIB L60004 38 101*/
> >> /* LIBRARYINVENTORY SCSI 3590LIB L60005 36 101*/
> >> /* LIBRARYINVENTORY SCSI 3590LIB L60006 35 101*/
> >> /* LIBRARYINVENTORY SCSI 3590LIB L60007 34 101*/
> >> /* LIBRARYINVENTORY SCSI 3590LIB L60008 32 101*/
> >> /* LIBRARYINVENTORY SCSI 3590LIB L60009 33 101*/
> >>
> >> The other says ...
> >>
> >> /* IBM AdStar Distributed Storage Manager Device Configuration */
> >> DEFINE DEVCLASS 3590CLASS DEVTYPE=3590 FORMAT=3590C MOUNTLIMIT=2
> >> MOUNTWAIT=60 MO
> >> UNTRETENTION=60 PREFIX=L5 LIBRARY=3494LIB
> >> DEFINE LIBRARY 3494LIB LIBTYPE=349X DEVICE=/dev/lmcp0 PRIVATECATEGORY
> >> SCRATC
> >> HCATEGORY=401
> >> DEFINE DRIVE 3494LIB 3590DRV1 DEVICE=/dev/rmt2 ONLINE=No
> >> DEFINE DRIVE 3494LIB 3590DRV2 DEVICE=/dev/rmt3 ONLINE=No
> >>
> >> Sorry they are not on-line ... I am running some maintanence ...
> >>
> >> How do I change it so I can read the tapes of my first library on the
> >> second (the 3494) ?
> >>
> >> best regards,
> >> Rodrigo
> >>
> >> >Steffan
> >> >Rodrigo Cordovil Gazzaneo wrote:
> >> >>
> >> >> >Your details are a bit hazy, I hope this'll fix you up..
> >> >>
> >> >> I hope so !
> >> >>
> >> >> >You can get away with using the "original" data tapes by
> >> >> >1) Steps to take on the original site...
> >> >> >run a FULL backupDB (BACKUPFULL in volhist)
> >> >> >collect the "original" data tapes
> >> >> >collect volhist and devcnfg and options files
> >> >> >(i.e. Volume History and Device Config files)
> >> >>
> >> >> Seems okay until now. Shouldn't I export the node so my clie
> >> >> could be imported on the remote site ? Just knowing volhist
> >> >> is enough ?
> >> >>
> >> >> >2) Steps to take on the remote site....
> >> >> >put volhist and devcnfg and options on the remote system
> >> >> >put "original" tapes into the library/drive as needed
> >> >> >modify devcnfg "inventory"(if needed) and "define" lines
> >> >> >reflect the configuration/inventory on the remote site.
> >> >>
> >> >> Modify ? Merge both the files ? Include the lines regarding
> >> >> the other server's files ?
> >> >>
> >> >> >run restore db (pit restore - select date of you last ba
> >> >>
> >> >> When I restore DB I overwrite the prior DB ? I don't want it
> >> >> the definitions and the last backup data to this second serv
> >> >>
> >> >> >And you should be set for the most part. You can get sim
> >> >> >with Export/Import server, DUMP/LOAD/AUDIT DB, DRM PREPA
> >> >> >etc.
> >> >>
> >> >> I thought DRM covered ADSM Server crash. I am not worried wi
> >> >> crash, my problem is client crash, and transporting data in
> >> >> server can be replicated elsewhere.
> >> >>
> >> >> It's like plain tape situation. You backup one box, move the
> >> >> another site and write it down on other server. I want to ma
> >> >> ADSM. That's why I thought of Export / Import.
> >> >>
> >> >> I don't want to overwrite the DB on the second site. I want
> >> >> it.
> >> >>
> >> >> >....THE END...
> >> >> >Now the solution to the tape-tape copy w/one drive is th
> >> >> >Setup migration from Tape(Old Tape)->Disk then from D
> >> >>
> >> >> Like reclamation ... I will probably do this : Switch my rec
> >> >> to my scratch pool area when making copies. But it is going
> >> >>
> >> >> Thanks,
> >> >>
> >> >> Rodrigo
> >> >>
> >> >> >ADSML
> >> >> >> -----Original Message-----
> >> >> >> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM DOT MAR
> >> >> >> Rodrigo Cordovil Gazzaneo
> >> >> >> Sent: Monday, August 30, 1999 7:16 PM
> >> >> >> To: ADSM-L AT VM.MARIST DOT EDU
> >> >> >> Subject: Exporting client nodes with limited resour
> >> >> >>
> >> >> >>
> >> >> >> Sorry, I forgot to add the subject before
> >> >> >>
> >> >> >> Hi ADSM / TSM gurus ,
> >> >> >>
> >> >> >> I need to implement a solution for a ADSM client cr
> >> >> >> Exchange Server). The problem is that the failover
> >> >> >> located at another site, covered by another ADSM Se
> >> >> >> there isn't enough network band to run server to se
> >> >> >> communication, so I will need to Import / Export no
> >> >> >> (sometimes the lowest latency comm "media" availabl
> >> >> >>
> >> >> >> For export, I began running the preview and obvious
> >> >> >> mass of data was indicated for migration. The FILED
> >> >> >> reduced the size for only the necessary to recover
> >> >> >> but I had yet another issue ...
> >> >> >>
> >> >> >> The first server (that contains the node data) has
> >> >> >> 3590-B11 drive installed, so I can't make tape to t
> >> >> >> Here is my question :
> >> >> >>
> >> >> >> Can I use the data tapes themselves for export ? I
> >> >> >> generating a tape containing the definitions for th
> >> >> >> node and moving it together with the data tapes (I'
> >> >> >> track of them with q volume and q content).
> >> >> >>
> >> >> >> If not, what other options do I have ?
> >> >> >>
> >> >> >> I have 2 stupid ideas :
> >> >> >>
> >> >> >> - move client's latest data from tape to disk (don'
> >> >> >> if I have space for it ...) and export it.
> >> >> >>
> >> >> >> - during the weekend (probably the WHOLE weekend !)
> >> >> >> a server to server copy, what would be like passing
> >> >> >> through a needle's hole ... might not work with dat
> >> >> >>
> >> >> >> Last option : buy another tape drive ...
> >> >> >>
> >> >> >> Can anyone help me ? Or am I in big trouble ?
> >> >> >>
> >> >> >> best regards,
> >> >> >> Rodrigo
> >> >> >>
|
