Hi
Are there any fancy ways to use exclusions.
A client uses another product for SQL backup management (actually quite a lot of them do), so no veeam in use for Logs and fulls. We want to exclude all the SQL files as well because of their cluster setup, BUT, as with all things IT, we dont want to exclude master and msdb.
They are all in the same directory as the user databases, rather annoyingly. So my solutions are 1) get the client to place them in different directories, or figure out a smarter way for exclusions, not to exclude certain files.
Any tricks here I could use? Any tricks you could add on at some point?
Kind Regards
-
- Veeam ProPartner
- Posts: 76
- Liked: 7 times
- Joined: Apr 14, 2011 3:20 pm
- Full Name: Matthew Ogden
- Contact:
-
- Product Manager
- Posts: 5797
- Liked: 1215 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: File Exclusions getting complex requirements
Most easy step would be to place the DB's you do want to backup in a different directory because other options may make it more complex (then it already is ).
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Veeam Software
- Posts: 856
- Liked: 154 times
- Joined: Feb 16, 2012 7:35 am
- Full Name: Rasmus Haslund
- Location: Denmark
- Contact:
Re: File Exclusions getting complex requirements
Did you look into database exclusions as well: https://www.veeam.com/kb2110
Rasmus Haslund | Twitter: @haslund | Blog: https://rasmushaslund.com
-
- Veeam ProPartner
- Posts: 76
- Liked: 7 times
- Joined: Apr 14, 2011 3:20 pm
- Full Name: Matthew Ogden
- Contact:
Re: File Exclusions getting complex requirements
This is what we usually do, but I think its relatively easy for Veeam to add a better exclusion method (exlude all except this etc).vmniels wrote:Most easy step would be to place the DB's you do want to backup in a different directory because other options may make it more complex (then it already is ).
The problem is it requires DB admins to make changes, and now infrastructure admins have to force them to do this. I think viewing them as seperate functions, (or view veeam as the 2nd arrival) might be easier for infrastructure admins
Who is online
Users browsing this forum: Bing [Bot], veremin and 273 guests