If i have a backup job that targets a SQL or other Application aware process, is there any way to get more granular than setting all the DBs within to back up with the same retention / settings?
It seems I have to set the lowest common denominator. For example if i have 1 database that i want to back up in a job with 1 year retention (just an example) that means ALL databases get the same treatment. Even though it is overkill.
Any way to be more granular? Skip database X as its QA, back up Y for longer term, etc.
-
- Enthusiast
- Posts: 83
- Liked: 13 times
- Joined: Feb 02, 2017 6:31 pm
- Contact:
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Per Database Application aware processing?
Hello,
This request appears quite often and we think about possible different options to address it in one of our future versions but I'm not ready yet to provide any estimations.
Thanks!
This request appears quite often and we think about possible different options to address it in one of our future versions but I'm not ready yet to provide any estimations.
Thanks!
Who is online
Users browsing this forum: No registered users and 23 guests