Feature request -

[Relaxe]

These are feature request. I’m unsure it’s the right place to post, be here they are:

Hello,
I am a new paid-license user, doing simple Veeam stuff.
Large Backup Job -> LocalDisk + S3 (SOBR).
It may be pretentious of me, but I believe I have a use case that is basic and close to most of your users.

I have feature requests from my limited experience, and they hurt.
Mostly because I tried other backup software, and they all had these features built-in.
I know most of these have workarounds, but I want to be the "IT Hero" by doing other things than fiddle with my backup system.

1- Direct object storage.
I have heard this will be available in v12.
Simply be able to either “backup job -> Object storage”, without all the SOBR shenanigans.
I would, personally, do:
Backup All -> Local Disk
Copy Backup: Local Disk –> S3
Once per 180 days: Backup All -> Glacier.
If Veeam is serious about cloud storage, this is a must.

2- Reform of the AWS section
There is a lot of confusion around the S3/Glacier stuff.
Currently, it’s 2 different wizards with different checkboxes that affect the storage tier.
Some storage tier are not even accessible trough that.
I wish you could have an “Amazon S3/Glacier object” wizard and have a drop-down list for the storage tier.
You can make it much simpler.
See here: https://www.reddit.com/r/Veeam/comments ... e_done_it/
If Veeam is serious about cloud storage, this is a must.

3- Internet Network throttling.
I backup a LARGE file server.
Doing SOBR, it just saturates my internet uplink. This is very bad for my users, having to wait trough 24h+ of internet sluggishness.
The "internet" rule in Global Network Trafic Rule does not work for some reason.
If Veeam is serious about cloud storage, this is a must.

4- Exclude disk from Complete VM restore
I just survived a bad sector on a disk. Veeam restored the VM.
That machine was a large file server (5TB), and the affected disk was the OS disk (60GB)
When going to restore individual VM files (only the appropriate VHDX), I had trouble making Hyper-V re-register the thing (I’m no wizard).
I ended up doing the “complete VM restore” that worked flawlessly, but I wish I could have excluded the 5TB drive from that restore. It would have been much faster.
There is a “Restore to a new location, or with different settings” in the Wizard that would be perfect to place the option, it lists the datastores. It only needs checkboxes!
Again about cloud storage, selective restore is crucial to reduce downtime.

Thanks!

[Mildur]

Hi Jerome

1- Direct object storage.

Yes, direct to object storage is coming. If you want to use Archive Object Storage, a SOBR is most likely still required.
We can provide more information on how it works when V12 is released.

2- Reform of the AWS section

Thanks for the request. AWS S3 and AWS S3 requires different configuration steps when you add them in Veeam. For example the archive tier requires a helper appliance. That's why we use different wizards to display this options.

3- Internet Network throttling.

If it doesn't work, have you considered to open a support case to get it analyzed? Please provide the case number in this topic if you do so.

4- Exclude disk from Complete VM restore

Were the bad sectors on the VM disk or on the physical disk of the hypervisor? If there were on the VM disk, have you considered using Quick Rollback? With Quick Rollback, only changed blocks would have been restored. And if you have used VM Files Restore, you could restore the VHDX to the original location. The VM should be powered down first. After the restore, I don't expect any issue that the vm will start with the restored VHDX.
Either way, thanks for the request.

Thanks
Fabian

[Relaxe]

Hello Fabian,
Thanks for the informative answers!

2- Reform of the AWS section
Thanks for the request. AWS S3 and AWS S3 requires different configuration steps when you add them in Veeam. For example the archive tier requires a helper appliance. That's why we use different wizards to display this options.

Ok, but as a user, I am completely oblivious to this fact. Having those words in the wizard would have helped me a lot. Something like "Welcome to the AWS storage wizard. First create an S3 bucket, then select the type of storage. Note that when selecting Glacier tiers Veeam will install the required helper appliance".
I reiterate: Installing an S3/Glacier storage for Veeam left me fell very frustrated. Veeam assumes you are a Veeam expert, Amazon assumes you have an AWS degree. There are a lot of "what why how" that are left unanswered by the official documentation. I strongly believe that Veeam should take actions to make this whole ordeal more user friendly. Beginning with the S3 ang Glacier Wizards. (ok ok, sorry for ranting again).

3- Internet Network throttling.
If it doesn't work, have you considered to open a support case to get it analyzed? Please provide the case number in this topic if you do so.

Case number: ---

4- Exclude disk from Complete VM restore
have you considered using Quick Rollback?

No, I have not. Seems like a good method tho.
If I get it right, I could have switch my hard drives with a new blank with the same letter as the old, started "quick restore", then Veeam would repopulate the directory structure with all the files at the correct place. It would of course scan the "large archive" drives, but it would have been much quicker. I will surely try it when the next disaster strikes

#Number removed by MOD

[Mildur]

I strongly believe that Veeam should take actions to make this whole ordeal more user friendly. Beginning with the S3 ang Glacier Wizards. (ok ok, sorry for ranting again).

No worries. This is the right place to tell us if something isn't right or can be done better.
We are always glad about any feedback from our customers.
We will take your feedback and discuss it internally.

Case number: ---

Can you check again? Case Numbers are starting with #05. #02 are contract numbers.

No, I have not. Seems like a good method tho. If I get it right, I could have switch my hard drives with a new blank with the same letter as the old, started "quick restore", then Veeam would repopulate the directory structure with all the files at the correct place.

Quick restore copies changed blocks from the restore point back to the original vm. It doesn't copy files. So it's a really fast method. But it only works if you restore to the original VM. And for Hyper-V, only the entire VM is possible. With vSphere, you could restore a single disk with Quick Rollback enabled.

[Relaxe]

>>Case Numbers are starting with #05. #02 are contract numbers.
Oups! Case number: #05572785