SCCM 2012 R2 - backup SQL necessary?
Are SQL backups necessary for SCCM 2012 R2?
We have Veeam backup which backups our SCCM server (there's only one server).
On top of that, I understand there is a built-in Backup mechanism within SCCM, which could be utilized.
If Veeam and/or the built in backup mechanism of SCCM are utilized, is there any need to backup the SQL databases specifically, regardless if they are in "SIMPLE" recovery mode?
SQL is on the local SCCM by the way. I'm not sure if that makes a difference but I wanted to point that out.
SCCM is not using a SQL server instance on another server. SCCM Configuration manager 2012 R2 and SQL 2012 R2 are both on the same server working together.
We have Veeam backup which backups our SCCM server (there's only one server).
On top of that, I understand there is a built-in Backup mechanism within SCCM, which could be utilized.
If Veeam and/or the built in backup mechanism of SCCM are utilized, is there any need to backup the SQL databases specifically, regardless if they are in "SIMPLE" recovery mode?
SQL is on the local SCCM by the way. I'm not sure if that makes a difference but I wanted to point that out.
SCCM is not using a SQL server instance on another server. SCCM Configuration manager 2012 R2 and SQL 2012 R2 are both on the same server working together.
Vitor Montalvão
It's a bare metal backup?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
With Veeam there is Application restore and it supports SQL database, and Exchange items (like mailboxes), or user accounts in things like a Domain Controller.
That's why I wasn't sure if Veeam has been factored into any Microsoft documentation when it comes to a "restore".
SCCm and SQL are both on the same server.
So if I had to restore the VM, I'm not sure if that would actually break it since I'm restoring via Veeam. Or if I'd have to restore the VM from Veeam and then do an additional SQL restore/repair from a separate SQL-based backup not done by Veeam..
That's why I wasn't sure if Veeam has been factored into any Microsoft documentation when it comes to a "restore".
SCCm and SQL are both on the same server.
So if I had to restore the VM, I'm not sure if that would actually break it since I'm restoring via Veeam. Or if I'd have to restore the VM from Veeam and then do an additional SQL restore/repair from a separate SQL-based backup not done by Veeam..
So, you're not really backing up the databases but all VM, right?
With that configuration can you restore to a point in time?
With that configuration can you restore to a point in time?
ASKER
Yeah Veeam backs up the server incrementally, every day, full backup once a week.
It has "Application aware" backup checked, and appears to have builtin SQL log truncation.
But really, I don't know best practice to restore if the VM was, say, deleted.
I could restore the VM but don't know if SCCM is supposed to carry on working, or if confimgr clients on end workstations would be corrupted or disconnected, if SQL would be working, etc.
It has "Application aware" backup checked, and appears to have builtin SQL log truncation.
But really, I don't know best practice to restore if the VM was, say, deleted.
I could restore the VM but don't know if SCCM is supposed to carry on working, or if confimgr clients on end workstations would be corrupted or disconnected, if SQL would be working, etc.
Yeah Veeam backs up the server incrementally, every day, full backup once a week.So I don't think you can recover to a point in time but only to a specific day which means that worst case scenario is that you can loose a full working day of data.
It has "Application aware" backup checked, and appears to have builtin SQL log truncation.How it does the SQL Log truncation if it doesn't run database backups? Also, mind that if databases are in full recovery model and there's no transaction log backup the databases tlog files will grow until fill all your disk.
ASKER
I don't know how the Veeam technology works, it just backs up virtual machines and has an "Application aware" feature.
It truncates logs on servers like Exchange as well.
So I'm able to use Veeam VM backup for our Exchange server without having to use any other backup tools. I thought the same logic would apply here for SCCM but there doesn't seem to be a clear answer.
It truncates logs on servers like Exchange as well.
So I'm able to use Veeam VM backup for our Exchange server without having to use any other backup tools. I thought the same logic would apply here for SCCM but there doesn't seem to be a clear answer.
So if your VM crashes tomorrow early on the morning are you able to recover all emails until the crash time or you are only able to recover until today's emails?
ASKER
If it's Exchange, I could either have another Exchange server standing by, and I could do a database or bulk mailbox restore to a different server. Or I could just restore the whole VM to the previous night's backup.
The backups are just nightly.
The backups are just nightly.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok I see what you mean. I guess it depends on expected recovery in DR scenario.
Difference of a few hours may be acceptable if restoring the point in time of the last few hours is too complicated to restore without further interrupting the business.
I don't think that's feasible given the lack of storage I have either.
In terms of databases, I see what you mean now. I'm still not sure what that translates to in a recovery scenario. Would it mean 1.) restore the VM via Veeam, then 2.) restore the more current SQL database backup to get the last few hours or so?
Otherwise it's probably better to just simply have a replica of the server with full backup every 2 hrs, or at least with SCCM installed so I could just import the SQL backups to it if the other SCCM VM went down.
Difference of a few hours may be acceptable if restoring the point in time of the last few hours is too complicated to restore without further interrupting the business.
I don't think that's feasible given the lack of storage I have either.
In terms of databases, I see what you mean now. I'm still not sure what that translates to in a recovery scenario. Would it mean 1.) restore the VM via Veeam, then 2.) restore the more current SQL database backup to get the last few hours or so?
Otherwise it's probably better to just simply have a replica of the server with full backup every 2 hrs, or at least with SCCM installed so I could just import the SQL backups to it if the other SCCM VM went down.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok great, thank you for the advice and answers to this question.