Re: Monthly Archives
1997-04-24 16:13:00
Subject: |
Re: Monthly Archives |
From: |
"Siska, Bob" <BSISKA AT NCS DOT COM> |
Date: |
Thu, 24 Apr 1997 13:13:00 PDT |
"EXPort Node" with "FILEData=BACKUPActive" is what you're looking for. But
be aware that it is a time- and resource-consuming process. It has some
advantages: you can Import to an empty database, or to another database,
even to one on a different platform.
Bob Siska
National Computer Systems
Iowa City
----------
From: owner-adsm-l
To: ADSM-L
Subject: Monthly Archives
Date: Thursday, April 24, 1997 11:46AM
A Business Requirement: To create an Archive of all data across all
platforms (UNIX, Novell, NT) after the close of business on the last
business day of each month. This is in addition to the normal daily
incremental backup.
Problem: 1.5 Tb of data -- inadequate time. Is it "really" necessary to
resend the data across the network when it already exists on tape (onsite
backup and offsite copy)?
Possible solution: On a weekend (or other ADSM server low utilization
window), restore data for one node to a given point in time onto DASD; write
an archive tape from the restored DASD; delete restored data from DASD;
repeat cycle until all nodes completed.
Are there any other solutions or options?
"Export Server" of data is not a viable option because exported files are
not managed to ADSM and you must "Import Server" all files in order to
restore a few to a given node.
Solutions surrounding restoring the ADSM database to a prior point in time
is not a viable option because it in effect brings the server down (it's
used extensively) and is simply a lot of work, not to mention being messy.
|
|
|