Discussions specific to object storage
Post Reply
v.eremin
Product Manager
Posts: 16134
Liked: 1315 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: 9.5 Update 4 - Azure Blob Storage

Post by v.eremin » Oct 24, 2018 11:56 am

a) technically would already be possible to do a restore/IR of a VM directly to azure with "full speed", bypassing slower internet links (so that the data would be directly written/read from azure to azure)
As long as you use Azure proxy in this scenario, traffic should stay isolated to Azure. Thanks!

thomas321
Influencer
Posts: 16
Liked: never
Joined: Jan 11, 2017 5:05 pm
Full Name: T
Contact:

Re: 9.5 Update 4 - Azure Blob Storage

Post by thomas321 » Oct 29, 2018 10:47 am

Hi guys,

just to recap:

Our current understanding is that Veeam will be able to move backups/restore points to blob once a certain retention time is hit.

Examples:
a) 60 restore points should be kept on local NAS, archive is enabled for everything older 30 days
This means up to 30 days/restore points will not be replicated off-site?!
This is critical in case of a site disaster scenario as the recent restore points are not off-site

b) 60 restore points should be kept on local NAS, archive is enabled for everything older 1 day
This means up to 1 days/restore points will not be replicated off-site?!
This will allow quick replication to off-site but will make common restores very slow and expensive
as we would have only 1 restore point on-site?!

Is this correct?

Thanks!

Gostev
SVP, Product Management
Posts: 24017
Liked: 3254 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: 9.5 Update 4 - Azure Blob Storage

Post by Gostev » Oct 29, 2018 2:29 pm

Replicating backups off-site is a totally separate process that is handled by Backup Copy jobs in Veeam. Backup Copy jobs will continue to operate normally whether or not you enable archiving of older backups to an object storage, creating and maintaining the required number of backups off-site.

MikePettit
Influencer
Posts: 13
Liked: 1 time
Joined: Jun 04, 2015 11:56 pm
Full Name: Michael Pettit
Contact:

Re: 9.5 Update 4 - Azure Blob Storage

Post by MikePettit » Oct 29, 2018 6:23 pm

Hi Thomas,

Yes, you can move backups to the blob after a certain retention has hit with scale out repositories. However, based on your examples and concerns, I think you want to use copy jobs.

a) Yes, if you setup a scale out repository that has a 30 day retention, and you had 60 restore points, it would move 30 days to the blob and keep 30 days onsite. As you mentioned, this would not be good if there was a disaster and you counted on these backups for restoration, as they'd be 30 days old at best.

b) This is where it gets interesting. The only backups that can be moved via scale out repository are any backups that come before the last full backup. Meaning that if you wanted to have the data moved every day, you will need to do full backups every day. In essence, the previous backup chain must be closed by another full backup in order for it to move. There must always be a full backup onsite. So that presents two problems for this scenario. One, you have to do full backups every day. Two, you would only have one backup copy onsite.

Based on your concerns, I think you want to use copy jobs. That will backup the data locally and then copy the data to the cloud, leaving a current set locally and an almost-current set in the cloud. You could probably mix in the archiving piece to keep older backup sets, but your primary goal seems to need copy jobs.

Therein lies the problem that we face today, we cannot target azure blob with copy jobs. We can target azure VMs with data disks, a much more expensive option, which is what I'm doing right now. Or you can setup a Service Provider storage and have the copy job target that. There are some decent options there.

Gostov has given us hope that copy jobs will eventually be able to send data to azure blob and perhaps other archive tiers. But hopefully it's not too late.

alesovodvojce
Enthusiast
Posts: 34
Liked: 2 times
Joined: Nov 29, 2016 10:09 pm
Contact:

[MERGED] Azure as a backup destination - best practice

Post by alesovodvojce » Oct 30, 2018 11:14 am

In near future will Veeam announce Azure for SOBR (Scale-out Backup repositories).
This way to have infinite backup storage and use Azure as a capacity tier. More details somewhere here on forums.

There are several best practices to build Veeam backup system onprem right.
For instance not to join VBR server to Active directory and to choose different passwords from other servers on the network. So even if the domain get compromised, the backups still should remain safe.

We have hybrid AD scenario (onpremise + Azure AD) and thinking about backups to coud-Azure.
Should we use the same Azure environment for backups or create new, isolated one?
And any other best practices?


Best, Petr

P.Tide
Product Manager
Posts: 4943
Liked: 418 times
Joined: May 19, 2015 1:46 pm
Contact:

[MERGED] Re: Azure as a backup destination - best practice

Post by P.Tide » Oct 30, 2018 12:56 pm

Hi,
Should we use the same Azure environment for backups or create new, isolated one?
Personally I would go with an isolated one. From my point of view the fact that the other AD is on Azure does not make a big difference in case it got compromised.

Regarding other best practices, please use our forum search engine, here are some examples:

veeam-tools-for-microsoft-azure-f36/off ... 48905.html
vmware-vsphere-f24/best-practice-for-se ... 44351.html

Thanks!

alesovodvojce
Enthusiast
Posts: 34
Liked: 2 times
Joined: Nov 29, 2016 10:09 pm
Contact:

Re: 9.5 Update 4 - Azure Blob Storage

Post by alesovodvojce » Oct 30, 2018 2:11 pm

I did search prior asking, but cannot find any coherent source of recommendation. Still see it missing. Thanks @PTide for the other point.

networkup
Influencer
Posts: 14
Liked: never
Joined: Oct 09, 2018 1:03 pm
Full Name: Adam Wilkinson
Contact:

Re: 9.5 Update 4 - Azure Blob Storage

Post by networkup » Dec 11, 2018 10:13 am

any estimates on a release date yet please?

Gostev
SVP, Product Management
Posts: 24017
Liked: 3254 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: 9.5 Update 4 - Azure Blob Storage

Post by Gostev » Dec 11, 2018 5:42 pm

We've shipped the first release candidate build for internal and private beta use by our systems engineers a few days ago, which means the RTM build should be out in the next few weeks.

crackocain
Service Provider
Posts: 117
Liked: 9 times
Joined: Dec 14, 2015 8:20 pm
Full Name: Mehmet Istanbullu
Location: Turkey
Contact:

Re: 9.5 Update 4 - Azure Blob Storage

Post by crackocain » Dec 11, 2018 5:47 pm

Hi

What kind of blob storage is supported?

-Block Blobs
-Azure Data Lake Storage
-Managed Disks
-Files

https://azure.microsoft.com/en-us/prici ... s/storage/
IBM, EMC, Huawei Storage Specialist - VMCEv9 - Dosbil - Turkey

Gostev
SVP, Product Management
Posts: 24017
Liked: 3254 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: 9.5 Update 4 - Azure Blob Storage

Post by Gostev » Dec 11, 2018 5:52 pm


crackocain
Service Provider
Posts: 117
Liked: 9 times
Joined: Dec 14, 2015 8:20 pm
Full Name: Mehmet Istanbullu
Location: Turkey
Contact:

Re: 9.5 Update 4 - Azure Blob Storage

Post by crackocain » Dec 11, 2018 6:00 pm

Hi Anton

Thank you for your response. I'm enter the pricing link and Blob options came out. It's confusing :)

Block Blobs(0.002$) is enough? Or we must buy the Files? (0.06$)

Thank you.
IBM, EMC, Huawei Storage Specialist - VMCEv9 - Dosbil - Turkey

v.eremin
Product Manager
Posts: 16134
Liked: 1315 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: 9.5 Update 4 - Azure Blob Storage

Post by v.eremin » Dec 12, 2018 10:23 am

Block Blobs(0.002$) is enough?
Enough. Thanks!

gummett
Veeam Software
Posts: 29
Liked: 5 times
Joined: Jan 30, 2017 9:23 am
Full Name: Ed Gummett
Contact:

Re: 9.5 Update 4 - Azure Blob Storage

Post by gummett » Dec 13, 2018 9:43 am

Please note that 'ARCHIVE' class block blobs can't be written to or read from, only HOT and COLD.
From https://azure.microsoft.com/en-us/prici ... age/blobs/: "For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, and DeleteBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete"
Ed Gummett
Systems Engineer UK & Ireland
Veeam Software

crackocain
Service Provider
Posts: 117
Liked: 9 times
Joined: Dec 14, 2015 8:20 pm
Full Name: Mehmet Istanbullu
Location: Turkey
Contact:

Re: 9.5 Update 4 - Azure Blob Storage

Post by crackocain » Dec 13, 2018 9:51 am

Hi Ed

We are evaluating Cool type blob. Availability and latency restrictions. Archive Blob maybe use tiering.

Thank you.
IBM, EMC, Huawei Storage Specialist - VMCEv9 - Dosbil - Turkey

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest