Hey friends,
we are a small organization, so running a D4ds VM 24/7 just to use it for an hour five days a week for backing up our Microsoft 365 tenant seems both overkill and unnecessarily expensive.
Has anyone here automated this process and can point me in the right direction? (Starting Azure VM -> doing the backup -> shutdown & deallocate Azure VM)
-
noniqu
- Novice
- Posts: 5
- Liked: never
- Joined: Mar 06, 2023 12:02 pm
- Contact:
-
Polina
- Veeam Software
- Posts: 3832
- Liked: 956 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Start Azure VM, Run Veeam Backup Job, then Shutdown VM
It's hardly possible. Your repository is associated with a proxy or a proxy pool, so at one proxy must be there an cannot be deleted (though technically you can shut it down when not needed). At the same time, if your organization is really small, you can use all-in-one installation where controller and proxy roles are co-existing on one machine.
Does it make sense?
Does it make sense?
-
noniqu
- Novice
- Posts: 5
- Liked: never
- Joined: Mar 06, 2023 12:02 pm
- Contact:
Re: Start Azure VM, Run Veeam Backup Job, then Shutdown VM
Yes that does make sense and we have indeed an All in one setup that we run on an Azure VM.
I was just wondering if someone here had automated peiodically starting an Azure VM -> run the backup and then shut down and deallocate and could give some insights on how they did it.
I was just wondering if someone here had automated peiodically starting an Azure VM -> run the backup and then shut down and deallocate and could give some insights on how they did it.
Who is online
Users browsing this forum: No registered users and 19 guests