-
- Enthusiast
- Posts: 66
- Liked: 10 times
- Joined: Jan 26, 2016 2:48 pm
- Full Name: Plandata Datenverarbeitungs GmbH
- Contact:
long term feature request: use policy based settings!
Hi!
I would like to make a long term feature request:
What i like about veeam is the simplicity of backup, not 10 different agents vor all application, it's all on VM level and all in one software.
What i don't like about veeam is the Gui. I don't like to configure settings and shedules in 25 jobs, thats annoying. And there is one simple solution for this --> Work with "policies" and attach the policies to jobs....
That would solve so much things, and would make configuration so much easier!
Example:
you have daily, weekly and monthly jobs for 25 remote offices:
no i have to configure 25 jobs for daily, 25 weekly and 25 monthly, every job a shedule, evry job different settings on different parts of the GUI.
When working with policies, i would create three policies and attach the policies to the job, finished! When changing omething, i could change it globaly in the policy.
And if you just give the opportunity to overwrite a policy in the job settings, you have both: simplicity and flexibility!
I know this is a long term change for a bigger realease, but maybe you could think about that!
I would like to make a long term feature request:
What i like about veeam is the simplicity of backup, not 10 different agents vor all application, it's all on VM level and all in one software.
What i don't like about veeam is the Gui. I don't like to configure settings and shedules in 25 jobs, thats annoying. And there is one simple solution for this --> Work with "policies" and attach the policies to jobs....
That would solve so much things, and would make configuration so much easier!
Example:
you have daily, weekly and monthly jobs for 25 remote offices:
no i have to configure 25 jobs for daily, 25 weekly and 25 monthly, every job a shedule, evry job different settings on different parts of the GUI.
When working with policies, i would create three policies and attach the policies to the job, finished! When changing omething, i could change it globaly in the policy.
And if you just give the opportunity to overwrite a policy in the job settings, you have both: simplicity and flexibility!
I know this is a long term change for a bigger realease, but maybe you could think about that!
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: long term feature request: use policy based settings!
Hi!
Thanks for the kind words and interesting request.
Now you can just clone existing job and change a single value in it (object(s)/schedule/target) if needed. So creation of 25 jobs will take about 5 to 10 minutes.
If you have policies, you don`t want VMs to be backed up at the same time. Veeam can automatically distribute backup over a day, but how would you like it to work if backup of all VMs exceed backup window?
Thanks for the kind words and interesting request.
Now you can just clone existing job and change a single value in it (object(s)/schedule/target) if needed. So creation of 25 jobs will take about 5 to 10 minutes.
If you have policies, you don`t want VMs to be backed up at the same time. Veeam can automatically distribute backup over a day, but how would you like it to work if backup of all VMs exceed backup window?
-
- Veteran
- Posts: 370
- Liked: 97 times
- Joined: Dec 13, 2015 11:33 pm
- Contact:
Re: long term feature request: use policy based settings!
I love this idea.
For most of us it's not about creating the jobs, it's about making changes once they are already setup and running. For example say you've just added some more disk space to your repo and want to keep more restore points... editing of every job, or you've had to specify which proxies jobs use so backup jobs don't try and use your hotadd proxies that are for replication when you have SAN connected proxies, and you need to replace one of those proxies, again editing every single job.
If all this was in a global policy it would simplify all of that.
For most of us it's not about creating the jobs, it's about making changes once they are already setup and running. For example say you've just added some more disk space to your repo and want to keep more restore points... editing of every job, or you've had to specify which proxies jobs use so backup jobs don't try and use your hotadd proxies that are for replication when you have SAN connected proxies, and you need to replace one of those proxies, again editing every single job.
If all this was in a global policy it would simplify all of that.
-
- Enthusiast
- Posts: 66
- Liked: 10 times
- Joined: Jan 26, 2016 2:48 pm
- Full Name: Plandata Datenverarbeitungs GmbH
- Contact:
Re: long term feature request: use policy based settings!
Yes, thats exactly what i have in mind!
-
- Veteran
- Posts: 361
- Liked: 109 times
- Joined: Dec 28, 2012 5:20 pm
- Full Name: Guido Meijers
- Contact:
Re: long term feature request: use policy based settings!
Smells like Rubrik...
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: long term feature request: use policy based settings!
Thanks for good use cases Dave.
The request is taken into account!
The request is taken into account!
Who is online
Users browsing this forum: alxz89, Bing [Bot] and 124 guests