djchopps0013
ADSM.ORG Senior Member
Ok so our business has made the decision that we need to archive our oracle DB's, my question is how are other shops accomplishing this? Using separate pool with long terms retentions?
Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.
It would be for RMAN created backups. So we cant just enable long retention on our current pool that would cause onsite and offsite copies of data to explode and we are at capacity on our tape library. My thoughts were to use current pool with current retention and create a second pool with like a 7 year retention to satisfy archives and have backups right to this pool once a month. Any thoughts?
ok I already see the benefit, so basically you need space available to dump to then have TSM come in and run a archive of the dump file right? Do you have this process automated?
What about large DB's? Say 500GB to 1.5TB
SAN Flashcopy/mirroring, and later a dump backup to tape might be the faster way to do this. If you don't replicate before dumping, your database server will be off the grid for sometime while you are dumping the db.
Depending on your setup (# tape drives and the such), a dump of large files to tape is not that time consuming. I have a couple of Oracle Dbs that are 3-5tb each and fulls are dumped to tape directly. If your TSM primary storagepool are big enough, you can dump to it first and then let TSM migrate it to tape...There is also LANFREE backups that could be looked into...