- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Archivelog directly to TAPE
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2005 06:33 PM
тАО10-27-2005 06:33 PM
Firstly,can I archive directly to TAPE as a secondry archive log destination as below
set log_archive_dest_1 = /dev/rmt/0m:100M
Having done this, is this affects performance on oracle database at peak hours
Secondly,in case of some reason(E.g say DAT drive may be corrupted) suppose secondry archive destination may not be available and as such is oracle database would be in halt state?..
Waiting for reply
Rgds,
Mehul
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2005 07:30 PM
тАО10-27-2005 07:30 PM
SolutionFirst: your destination must be the no-rewind device, otherwise, each copy will overwrite the previous one.
Second: you can control the number of required successfull copies with log_archive_min_succeed_dest.
I must say, that I would not favor to do it this way, because it would be very difficult to "find" a specific log if this is required for whatever reason. You might need to keep track with which log the archiver did start and how many redologs have been written.
Get a second disk of some GB and do a migration to tape from there.
It will be easier to be managed.
Best regards
Volker
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2005 09:13 PM
тАО10-27-2005 09:13 PM
Re: Archivelog directly to TAPE
I would not recommend to archive directly to tape :
1. Recovery time would take much longer as you would have to take the archive back from a tape
2. You may create archiver busy wait and therefore impact database performance and availability.
Also, the tape drive does not have resilience you can have if your disk system is raided or if you mirror the disks dedicated for archive.
Regards
Jean-Luc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2005 09:16 PM
тАО10-27-2005 09:16 PM
Re: Archivelog directly to TAPE
I would also advise to read Metalink Note:45042.1 " Archiver Best Practices "
Regards
Jean-Luc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2005 11:29 PM
тАО10-27-2005 11:29 PM
Re: Archivelog directly to TAPE
as mentioned by Jean-luc, you should archive to a rather fast device. Because during high load, it may impact on performance.
As for the archive destination not being available, as long as you have one destination available, your database will not hang! Error messages will be automatically logged in you alert.log.
also have a look atthe backup and recovery guide at http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/index.htm
good luck!
kind regards
yogeeraj