Server 2008 VM w Oracle: backup question
-
@FATeknollogee said in Server 2008 VM w Oracle: backup question:
@JaredBusch said in Server 2008 VM w Oracle: backup question:
Granular DB recovery for corrupted database: hourly, because it is easy to use SQL Server Management studio to handle rollbakcs.
Smoked server acceptable recovery: daily. So this means I have SQL server create .bak files a couple times a day and then an hour later twice a day I have veeam run a backup.
I assume this is setup on a schedule using Mgmt Studio?
Yes.
-
I prefer just using Veeam rather than having a separate maintenance plan to backup the database outside of Veeam. Mainly, I guess, because of laziness, though partly because I prefer Veeam to log successful/unsuccessful backups. If I didn't use Veeam, I'd have to have another process for checking successful database backups. This is for SQL Server, but the same would apply for Oracle.
-
@JaredBusch said in Server 2008 VM w Oracle: backup question:
Yes, your point? The best, fastest, backup target is always local. This is just the application backup though. do not confuse things or leave out pieces of the puzzle. I gave an entire solution.
I understand you gave an entire solution, I was trying to ask the question in detail, hence the multi-part reply.
Also wasn't sure if it was advisable to store the app backups in the same vm, but you say that's ok
-
@FATeknollogee said in Server 2008 VM w Oracle: backup question:
@JaredBusch said in Server 2008 VM w Oracle: backup question:
Yes, your point? The best, fastest, backup target is always local. This is just the application backup though. do not confuse things or leave out pieces of the puzzle. I gave an entire solution.
I understand you gave an entire solution, I was trying to ask the question in detail, hence the multi-part reply.
Also wasn't sure if it was advisable to store the app backups in the same vm, but you say that's ok
Turn that around.
Why do you think it would not be ok? -
@Carnival-Boy said in Server 2008 VM w Oracle: backup question:
I prefer just using Veeam rather than having a separate maintenance plan to backup the database outside of Veeam. Mainly, I guess, because of laziness, though partly because I prefer Veeam to log successful/unsuccessful backups. If I didn't use Veeam, I'd have to have another process for checking successful database backups. This is for SQL Server, but the same would apply for Oracle.
You should have various other maintenance tasks setup for SQL Server anyway. Adding a backup task is simplistic. Those other tasks should be alerting on fail, and so should the backup. so really, not an issue here.
-
@JaredBusch said in Server 2008 VM w Oracle: backup question:
Turn that around.
Why do you think it would not be ok?I guess it is ok....if you lost the vm, you would have a backup of the vm, which contains the app db data
-
@FATeknollogee said in Server 2008 VM w Oracle: backup question:
@JaredBusch said in Server 2008 VM w Oracle: backup question:
Turn that around.
Why do you think it would not be ok?I guess it is ok....if you lost the vm, you would have a backup of the vm, which contains the app db data
Correct.
-
@JaredBusch said in Server 2008 VM w Oracle: backup question:
Granular DB recovery for corrupted database: hourly, because it is easy to use SQL Server Management studio to handle rollbakcs.
Smoked server acceptable recovery: daily. So this means I have SQL server create .bak files a couple times a day and then an hour later twice a day I have veeam run a backup.
Granular db (hourly) + Smoked (daily) + Veeam (twice a day) = Full protection with lots of restore point options.
Correct?
-
@FATeknollogee said in Server 2008 VM w Oracle: backup question:
@JaredBusch said in Server 2008 VM w Oracle: backup question:
Granular DB recovery for corrupted database: hourly, because it is easy to use SQL Server Management studio to handle rollbakcs.
Smoked server acceptable recovery: daily. So this means I have SQL server create .bak files a couple times a day and then an hour later twice a day I have veeam run a backup.
Granular db (hourly) + Smoked (daily) + Veeam (twice a day) = Full protection with lots of restore point options.
Correct?
Smoked is twice a day with veeam directly after because I prefer not to have to risk a full 24 hours. generally people think daily means this morning like it was, but we know that is not true.
but yes, correct.
-
Very true. You can use a traditional tool, store a backup locally then take any sort of backup of the local system that way.