Windows Server Backup and Oracle
-
I'm having this forwarded off to the peoples that implement this software, but am wondering if anyone has experienced this before and knows of a fix.
This is a new server that is going to be replacing an old outdated production Oracle software server.
This is the third week trying to back it up, but failed. A reboot does not help. I didn't see any related services to try starting.
The following event log screenshots are on the VM itself, but the event log errors on the Hyper-V host correspond to the below errors.
-
Never seen that before. Does the backup work after the VM is shutdown?
-
@black3dynamite said in Windows Server Backup and Oracle:
Never seen that before. Does the backup work after the VM is shutdown?
It most likely will then. But If possible, management would most likely prefer this not be the only server that has to be shut down once a week to be backed up.
The old Oracle server being replaced does not have this issue, and it's running Windows Server 2003. This one is 2012 R2 (because it has to be and they won't support 2016... not my call)
-
It looks like it can't create a snapshot, possibly a lock issue on the database. Have you tried installing Veeam just as a test, and see if it succeeds? Wondering if it is an application issue.
-
In NOARCHIVELOG mode the database must be shut down before you can back it up. I recommend you to change the database mode to ARCHIVELOG so you can perform an online backup.
There are many documents and blog posts about it, but this may help you:
https://www.veritas.com/support/en_US/article.000011425 -
@dave_c said in Windows Server Backup and Oracle:
In NOARCHIVELOG mode the database must be shut down before you can back it up. I recommend you to change the database mode to ARCHIVELOG so you can perform an online backup.
There are many documents and blog posts about it, but this may help you:
https://www.veritas.com/support/en_US/article.000011425Awesome, that looks promising.
I'm not responsible for the Oracle side of things, so I will pass this on to those in charge of that as a recommended change.
I just deal with the Windows Server / VM & hypervisor back-end of it.
-
@tim_g said in Windows Server Backup and Oracle:
@dave_c said in Windows Server Backup and Oracle:
In NOARCHIVELOG mode the database must be shut down before you can back it up. I recommend you to change the database mode to ARCHIVELOG so you can perform an online backup.
There are many documents and blog posts about it, but this may help you:
https://www.veritas.com/support/en_US/article.000011425Awesome, that looks promising.
I'm not responsible for the Oracle side of things, so I will pass this on to those in charge of that as a recommended change.
I just deal with the Windows Server / VM & hypervisor back-end of it.
But what Backup system/software are you using?
-
But what Backup system/software are you using?
I know that the question is not for me but... That is an interesting one. I have used a few (from BackupExec to Veeam) and of course, Oracle's RMAN. Oracle database in a beast and in my experience it doesn't matter what backup software you use; you need play by their rules.
In this case, it seems like the backup software is just trying to use Oracle's VSS writer to backup. I have done that and recovered databases like that, but in ARCHIVELOG mode. In this case the VSS writer is chocking on NOARCHIVELOG.
In the end, I usually have 2 backups:
- RMAN
- Something else that backs up at least the RMAN backups; sometimes in addition to its own backup.
Call me paranoid.
-
@dbeato said in Windows Server Backup and Oracle:
@tim_g said in Windows Server Backup and Oracle:
@dave_c said in Windows Server Backup and Oracle:
In NOARCHIVELOG mode the database must be shut down before you can back it up. I recommend you to change the database mode to ARCHIVELOG so you can perform an online backup.
There are many documents and blog posts about it, but this may help you:
https://www.veritas.com/support/en_US/article.000011425Awesome, that looks promising.
I'm not responsible for the Oracle side of things, so I will pass this on to those in charge of that as a recommended change.
I just deal with the Windows Server / VM & hypervisor back-end of it.
But what Backup system/software are you using?
It's in the title :winking_face:
-
@tim_g said in Windows Server Backup and Oracle:
@dbeato said in Windows Server Backup and Oracle:
@tim_g said in Windows Server Backup and Oracle:
@dave_c said in Windows Server Backup and Oracle:
In NOARCHIVELOG mode the database must be shut down before you can back it up. I recommend you to change the database mode to ARCHIVELOG so you can perform an online backup.
There are many documents and blog posts about it, but this may help you:
https://www.veritas.com/support/en_US/article.000011425Awesome, that looks promising.
I'm not responsible for the Oracle side of things, so I will pass this on to those in charge of that as a recommended change.
I just deal with the Windows Server / VM & hypervisor back-end of it.
But what Backup system/software are you using?
It's in the title :winking_face:
Yikes, I missed it...
-
@tim_g said in Windows Server Backup and Oracle:
@dbeato said in Windows Server Backup and Oracle:
@tim_g said in Windows Server Backup and Oracle:
@dave_c said in Windows Server Backup and Oracle:
In NOARCHIVELOG mode the database must be shut down before you can back it up. I recommend you to change the database mode to ARCHIVELOG so you can perform an online backup.
There are many documents and blog posts about it, but this may help you:
https://www.veritas.com/support/en_US/article.000011425Awesome, that looks promising.
I'm not responsible for the Oracle side of things, so I will pass this on to those in charge of that as a recommended change.
I just deal with the Windows Server / VM & hypervisor back-end of it.
But what Backup system/software are you using?
It's in the title :winking_face:
And also not really relevant. Because all backups would fail with that error unless the DB was stopped.
