sudhakarpv
asked on
RMAN Backup on Oracle 9i RAC
1) We are on Oracle 9i RAC on Windows 2000 Advanced Server with SP3
2) We have 2 nodes in the Cluster
3) The Database resides in the SAN Shared Storage Area with OCFS and we are running in Archivelog mode
4) The Archivelog's are stored on both the Servers running the 2 instances and they are located in 'F:\Archive' with the "Non-CFS Local Archiving" Mode
5) We have recently installed VERITAS NetBackup 5.1 and enabled the RMAN
6) When we performed a back up of the Database and Archivelogs by connecting from one of the instance / node, we were successful in backing up the Database but when it came to backing up the Archivelogs -- it failed showing "RMAN-06059: expected archived log not found, lost of archived log compromises recoverability".
7) Then i performed a test by connecting to both the nodes (through the NET8 Alias strings) and was successful in backing-up the Archive logs from both the nodes to Disk.
Kindly advise a strategy to perform a successful backup of Database and the Archive logs from both the Nodes ?
Thanks in Advance.
Kind Regards,
Sudhakar
2) We have 2 nodes in the Cluster
3) The Database resides in the SAN Shared Storage Area with OCFS and we are running in Archivelog mode
4) The Archivelog's are stored on both the Servers running the 2 instances and they are located in 'F:\Archive' with the "Non-CFS Local Archiving" Mode
5) We have recently installed VERITAS NetBackup 5.1 and enabled the RMAN
6) When we performed a back up of the Database and Archivelogs by connecting from one of the instance / node, we were successful in backing up the Database but when it came to backing up the Archivelogs -- it failed showing "RMAN-06059: expected archived log not found, lost of archived log compromises recoverability".
7) Then i performed a test by connecting to both the nodes (through the NET8 Alias strings) and was successful in backing-up the Archive logs from both the nodes to Disk.
Kindly advise a strategy to perform a successful backup of Database and the Archive logs from both the Nodes ?
Thanks in Advance.
Kind Regards,
Sudhakar
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi Sudhakar,
Upon my experience, your solution to set the archivelog dest to 'f:\archivelog' on the both servers is not workable when you do a crash recovery or even when you try to hot backup the whole database with rman, because both servers cann't see each other's F drive or, on the other word, both servers can't find all needed archivelogs in their local archivelog dest.
My solution: set the archivelog_dest seperately on the servers, following i'll give a sample
1. set server1's archivelog_dest to 'e:\archivelog'
2. set server2's archivelog_dest to 'f:\archivelog'
3. map the server1's drive E as server2's drive E, and set access rights properly
4. map the server2's drive F as server1's drive F, set access rights
5. done!
And you only need to backup from any one node of the 2 with RMAN and all archivelogs will be backed up in both E & F drives
Try this, hope this helps!
JC.L
Upon my experience, your solution to set the archivelog dest to 'f:\archivelog' on the both servers is not workable when you do a crash recovery or even when you try to hot backup the whole database with rman, because both servers cann't see each other's F drive or, on the other word, both servers can't find all needed archivelogs in their local archivelog dest.
My solution: set the archivelog_dest seperately on the servers, following i'll give a sample
1. set server1's archivelog_dest to 'e:\archivelog'
2. set server2's archivelog_dest to 'f:\archivelog'
3. map the server1's drive E as server2's drive E, and set access rights properly
4. map the server2's drive F as server1's drive F, set access rights
5. done!
And you only need to backup from any one node of the 2 with RMAN and all archivelogs will be backed up in both E & F drives
Try this, hope this helps!
JC.L
ASKER
Hi JC,
What you said is correct, but the concept of RAC itself means that each node will be able to read as well as write to the other node irrespective of any kind of files.
I tried mapping the server2's drive f to server1 but it didn't work.
Maybe what you said will work, by specifying different partition's for the archive log destination --- this is one probable solution.
But i need couple of days time to test and give a confirmation about the same.
Thanks & Regards,
Sudhakar
What you said is correct, but the concept of RAC itself means that each node will be able to read as well as write to the other node irrespective of any kind of files.
I tried mapping the server2's drive f to server1 but it didn't work.
Maybe what you said will work, by specifying different partition's for the archive log destination --- this is one probable solution.
But i need couple of days time to test and give a confirmation about the same.
Thanks & Regards,
Sudhakar
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi Sudhakar,
Just make clear 2 points:
1. It doesn't matter if it's drive E or F, just make sure that server1 sees server2's real local drive X as server1's mapped local X, so works have to be done to rename local conflict drive letters, and vice versa.
2. for each server the only parameter has to be set is log_archive_dest_1. For example in your spfile:
server1.log_archive_dest_1
server2.log_archive_dest_1
DO NOT also set such as server1.log_archive_dest_2
And finally, just not like what SDutta has said, you CAN backup the whole database from any one node as long as the other node's archivelog drive is available. And this is just what we are doing, and we've done restores and recoveries many times to test it so I can promise this to you.
Regards
JC.L
Just make clear 2 points:
1. It doesn't matter if it's drive E or F, just make sure that server1 sees server2's real local drive X as server1's mapped local X, so works have to be done to rename local conflict drive letters, and vice versa.
2. for each server the only parameter has to be set is log_archive_dest_1. For example in your spfile:
server1.log_archive_dest_1
server2.log_archive_dest_1
DO NOT also set such as server1.log_archive_dest_2
And finally, just not like what SDutta has said, you CAN backup the whole database from any one node as long as the other node's archivelog drive is available. And this is just what we are doing, and we've done restores and recoveries many times to test it so I can promise this to you.
Regards
JC.L
@JCL
Don't quote me wrong, this is what I said in the last sentence - "both locations must be accessible from the same machine to run the archivelog backup from that node".
Don't quote me wrong, this is what I said in the last sentence - "both locations must be accessible from the same machine to run the archivelog backup from that node".
ASKER
Hi JC,
I tried the point which you suggested above as:
Server1: log_archive_dest_1='f:\arc
Server2: log_archive_dest_2='o:\arc
Then mapped the Server2's 'O:\archive' to Server1's 'O:\' drive and tried the backup, but it is still failing as "RMAN-06726: could not locate archivelog F:\ARCHIVE\TNDC_132.ARC" because this particular archivelog is of the Server1 which got created in the Server2's location.
Is that i did any mistake while mapping the drive's or is it another mistake ? Or is it that i need to map the Server2's archive destination as '\\server2\o$' or as above as '\\server2\archive' ?
Kindly clarify how the mapping is to be done (i tried both ways but still it is erroring out) ?
Thanks & Regards,
Sudhakar
I tried the point which you suggested above as:
Server1: log_archive_dest_1='f:\arc
Server2: log_archive_dest_2='o:\arc
Then mapped the Server2's 'O:\archive' to Server1's 'O:\' drive and tried the backup, but it is still failing as "RMAN-06726: could not locate archivelog F:\ARCHIVE\TNDC_132.ARC" because this particular archivelog is of the Server1 which got created in the Server2's location.
Is that i did any mistake while mapping the drive's or is it another mistake ? Or is it that i need to map the Server2's archive destination as '\\server2\o$' or as above as '\\server2\archive' ?
Kindly clarify how the mapping is to be done (i tried both ways but still it is erroring out) ?
Thanks & Regards,
Sudhakar
ASKER
Hi JC,
One more point after giving the sharing access, i have given full access permissions in the Server2 for the 'archive' directory.
Regards,
Sudhakar
One more point after giving the sharing access, i have given full access permissions in the Server2 for the 'archive' directory.
Regards,
Sudhakar
Hi Sudhakar,
First, you should correct your parameters to:
Server1: log_archive_dest_1='f:\arc
Server2: log_archive_dest_1='o:\arc
Second, Just map the server2's drive 'O:' to server1's drive 'O:', so that server1 sees server2's 'o:\archive\' as if it's local 'o:\archive'. And again you must also map server1's drive 'F:' to server2 in the same way. The result is both servers see the same directory structure like:
f:\archive
o:\archive
Regards!
JC.L
First, you should correct your parameters to:
Server1: log_archive_dest_1='f:\arc
Server2: log_archive_dest_1='o:\arc
Second, Just map the server2's drive 'O:' to server1's drive 'O:', so that server1 sees server2's 'o:\archive\' as if it's local 'o:\archive'. And again you must also map server1's drive 'F:' to server2 in the same way. The result is both servers see the same directory structure like:
f:\archive
o:\archive
Regards!
JC.L
ASKER
Hi JC,
I have done as suggested by you - changed the Server2's archive log destination from 'f:\archive' to 'g:\archive' and mapped it to Server1 as 'g:\' and in the same way mapped Server1's 'f:\archive' to Server2 as 'f:\' and again tried to perform a backup.
This time, i again got an error as "ORA-19625: error identifying file F:\ARCHIVE\PNDC_22437.ARC"
Therefore, what do i need to do to tell RMAN that the location is changed and that the particular archive log is still present to be backed up.
Another point which i observed is: in 9.2 the moment RMAN performs a backup of the archivelogs, it updates the status as 'X' in the AL table of its schema and hence even if we try to perform a backup of the files again, it doesn't because of the 'X' status. How can we overcome this problem ?
Kind Regards,
Sudhakar
I have done as suggested by you - changed the Server2's archive log destination from 'f:\archive' to 'g:\archive' and mapped it to Server1 as 'g:\' and in the same way mapped Server1's 'f:\archive' to Server2 as 'f:\' and again tried to perform a backup.
This time, i again got an error as "ORA-19625: error identifying file F:\ARCHIVE\PNDC_22437.ARC"
Therefore, what do i need to do to tell RMAN that the location is changed and that the particular archive log is still present to be backed up.
Another point which i observed is: in 9.2 the moment RMAN performs a backup of the archivelogs, it updates the status as 'X' in the AL table of its schema and hence even if we try to perform a backup of the files again, it doesn't because of the 'X' status. How can we overcome this problem ?
Kind Regards,
Sudhakar
Hi Sudhakar,
You have misread my comments. Just map the drives from 'o:' to 'o:', 'p:' to 'p:' etc., instead of mapping 'o:\folder' to 'o:'.
For your 2nd question, so far I didn't touch that table yet. Maybe others experts can answer it.
Regards
JC.L
You have misread my comments. Just map the drives from 'o:' to 'o:', 'p:' to 'p:' etc., instead of mapping 'o:\folder' to 'o:'.
For your 2nd question, so far I didn't touch that table yet. Maybe others experts can answer it.
Regards
JC.L
ASKER
Hi JC,
Sorry, i wrote the statement wrong -- i did the mapping like what you said but while replying i wrote it the other way.
But, apart from the table, the other point i observed was regarding the message i got from the NetBackup utility -- ORA-19625: error identifying file F:\ARCHIVE\PNDC_22437.ARC -- this archivelog got created at a previous time before i changed the locations and RMAN is still looking at the old location. This archivelog was generated in the Second Server and it got created in f:\archive (the old location) -- so how can i point this change to RMAN, in turn to perform a backup of all the archivelogs generated in the Second Server.
Thanks & Regards,
Sudhakar
Sorry, i wrote the statement wrong -- i did the mapping like what you said but while replying i wrote it the other way.
But, apart from the table, the other point i observed was regarding the message i got from the NetBackup utility -- ORA-19625: error identifying file F:\ARCHIVE\PNDC_22437.ARC -- this archivelog got created at a previous time before i changed the locations and RMAN is still looking at the old location. This archivelog was generated in the Second Server and it got created in f:\archive (the old location) -- so how can i point this change to RMAN, in turn to perform a backup of all the archivelogs generated in the Second Server.
Thanks & Regards,
Sudhakar
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi JC,
Thank you for all the support and patience.
One last request, could you briefly summarise any other points to be taken care of in case any problems arise, which i may overlook.
Thanks & Warm Regards,
Sudhakar
Thank you for all the support and patience.
One last request, could you briefly summarise any other points to be taken care of in case any problems arise, which i may overlook.
Thanks & Warm Regards,
Sudhakar
ASKER
Thank you for your reply and patience.
But, i think the whole point is missed there.
First, our platform is NOT UNIX but WINDOWS.
Second, i am / was successful in doing a backup of the whole database, as well as, the Archive logs from RMAN on to a Disk.
Third and the most important one is, i wanted to know a strategy by which i can successfully perform the backup of the Database and Archivelogs from the nodes, as we are backing up only from one node?
Again, we are performing the backup ONLY from one node and thus, the NetBackup is unable to backup the archivelogs generated in the other node.
Therefore, i am looking for a probable answer / solution for the above -- that is, performing a backup of all the archive logs without the database ?
Hope i am clear in my explanation of the scenarion.
Thanks in Advance.
Kind Regards,
Sudhakar