-
- Influencer
- Posts: 12
- Liked: never
- Joined: Aug 25, 2016 7:10 pm
- Full Name: Megan Gee
- Contact:
Cloud repository, same Azure tenant?
Anyone here use the same Azure tenant they are backing up to host the storage repository? Just curious on the arguments for and against this setup...
-
- Product Manager
- Posts: 15125
- Liked: 3230 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Cloud repository, same Azure tenant?
Hello,
if also arguments from people who are not running the setup are okay: I would store the data outside Azure. It makes no sense to me to create such a vendor lock in.
Best regards,
Hannes
if also arguments from people who are not running the setup are okay: I would store the data outside Azure. It makes no sense to me to create such a vendor lock in.
Best regards,
Hannes
-
- Enthusiast
- Posts: 99
- Liked: 39 times
- Joined: May 09, 2016 2:34 pm
- Full Name: JM Severino
- Location: Switzerland
- Contact:
Re: Cloud repository, same Azure tenant?
Hello,
For several reasons, we aren't doing backups to cloud, but I wouldn't use as backup target the same tenant you are backing up. Reasons:
The most important one: Administrative boundaries. I do not want a global admin account/Cloud service provider support account/Internal Microsoft service account being able to delete the production data and at the same time being able to wipe/tamper with the backup storage.
Other reasons may be avoiding vendor lock-in, improving redundancy (make sure the data is not sharing any infrastructure at all), etc.
Best regards
Seve
For several reasons, we aren't doing backups to cloud, but I wouldn't use as backup target the same tenant you are backing up. Reasons:
The most important one: Administrative boundaries. I do not want a global admin account/Cloud service provider support account/Internal Microsoft service account being able to delete the production data and at the same time being able to wipe/tamper with the backup storage.
Other reasons may be avoiding vendor lock-in, improving redundancy (make sure the data is not sharing any infrastructure at all), etc.
Best regards
Seve
Who is online
Users browsing this forum: No registered users and 7 guests