Hi guys,
Could you please help me with some deployment issues i am currently in?
I have customer who needs to backup a physical machines with SQL databases.
Apologize for Maybe stupid question - is there any way to backup only certain databases or instances from server?
Reason is that the customer has only few databases requested for backup and a lot of dev databases which are not supposed to be backuped.
I found some solution about excluding dbs from processing, but there is problem that developers randomly creating "unknown" databases and I am not able to predict which dbs I want to exclude.
Maybe It might be done with defining dedicated credentials for only those dbs I want backup.
Right now i am looking for best solution, so any help appreciated.
Thanks for help
Regards
Martin
-
MVanek
- Influencer
- Posts: 12
- Liked: 5 times
- Joined: May 20, 2019 4:12 pm
- Full Name: Martin Vanek
- Contact:
-
Egor Yakovlev
- Veeam Software
- Posts: 2543
- Liked: 687 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: SQL granular Instance/database backup
Hi Martin.
We do not have granular backup of SQL databases as of today. I can suggest few potential workarounds here:
- Using Volume level backup in agent, you can backup only required volumes. Since you do not know exact name of dev DBs, you can ask them to create those DBs using strict path on your server, f.e. add a volume "F:\" for DevTest DBs and exclude said path from backup.
- You can perform SQL Native backup on a dedicated volume, and backup only that volume instead. In case of DB failure, you can get SQL backup back from Veeam's and restore from it using native tools.
/Thanks!
We do not have granular backup of SQL databases as of today. I can suggest few potential workarounds here:
- Using Volume level backup in agent, you can backup only required volumes. Since you do not know exact name of dev DBs, you can ask them to create those DBs using strict path on your server, f.e. add a volume "F:\" for DevTest DBs and exclude said path from backup.
- You can perform SQL Native backup on a dedicated volume, and backup only that volume instead. In case of DB failure, you can get SQL backup back from Veeam's and restore from it using native tools.
/Thanks!
-
MVanek
- Influencer
- Posts: 12
- Liked: 5 times
- Joined: May 20, 2019 4:12 pm
- Full Name: Martin Vanek
- Contact:
Re: SQL granular Instance/database backup
Hi Egor, thanks for fast response
Yes, I think that solution is suitable and looks good to me...and finally it will be best solution. As i am at the high level design now i dont have exact information about db to disk layout, but now I am afraid that current config may contain databases spread across multiple disks from what i know so far. Since its a physical machine its a little bit complicated to change volume layout
I am trying to avoid file level backup at all because I think its not optimal and comfortable enough also worse performance.
I am not db specialist, but I need to find best solution for our customer and so I asked here because my customer needs reason why use Veeam agent for his infrastructure.
Anyway thank for your time and help
//Martin
Yes, I think that solution is suitable and looks good to me...and finally it will be best solution. As i am at the high level design now i dont have exact information about db to disk layout, but now I am afraid that current config may contain databases spread across multiple disks from what i know so far. Since its a physical machine its a little bit complicated to change volume layout
I am trying to avoid file level backup at all because I think its not optimal and comfortable enough also worse performance.
I am not db specialist, but I need to find best solution for our customer and so I asked here because my customer needs reason why use Veeam agent for his infrastructure.
Anyway thank for your time and help
//Martin
Who is online
Users browsing this forum: No registered users and 17 guests