Feature request: Export backup to other location.

[BoRiisDK]

Hi

We have an arrangement with some of our customers that we give them a yearly backup on a NAS. Currently we solve this by attaching the NAS to Veeam and create a backup copy job with only 2 restore points. (1 is not possible)

Would it be possible to have the Export backup feature allow for exporting to a different repository or SOBR than where the original backup is located? This would save us from allowing room for the VIB file the Backup copy job creates. Perhaps even making the Export feature work as a Backup copy job with support for running outside normal backup operations when the ressources allow for it.

Thanks

[HannesK]

Hello,
that feature request makes sense to me. Thanks for bringing it up.

Best regards,
Hannes

[FedericoCoppola]

Hi all,
I must export a backup of a specific virtual machine from a Copy backup job.
This backup job on a full disk.
Is possible change path of exporting backup? During the wizard there Is any option about Path.

Thanks
Federico

[wishr]

Hi Federico,

The exported backup will be saved to the same repository where the source backup files reside. Currently, you cannot specify an alternate location. Once exported you can transfer it wherever required. We've noted your post as a FR.

Thanks

[FedericoCoppola]

Hi wishr, thanks so much

Federico

[frankive]

+1 for this feature request.
Perhaps this can be done today with powershell?

[oleg.feoktistov]

Hi Frank, gentlemen,

By design, it works likewise in powershell - the cmdlet allows saving backup exports to the same repository only. So, I noted it as a Feature Request for powershell also. Thank you!

However, as it turned out, you can map a folder located on different repository to the backup server as a network share
and then pass it to the cmdlet as UNC path.

Code: Select all

net use '\\192.168.0.80\c$\temp'
$backup = Get-VBRBackup
Export-VBRBackup -Backup $backup[1] -Dir '\\192.168.0.80\c$\temp'

I just tested it and the export worked.

Kind regards,
Oleg

[FedericoCoppola]

Thanks, I will export using powershell soon as possible.

Best regards
Federico

[frankive]

Thanks! Exporting to a UNC share solved the case for me.
But keep the feature as a request in the gui/powershell for native export backup to any location.

[ftravinsky]

Year 2020 and the feature still not available.
I'm populating my second target repository..

Firstly, I have to burn my spinning drives to read and write to the same repo, then move the exported data to second repo.
Aborting and going UNC way.

[veremin]

Thanks for the feedback, just marked this (ability to specify path for exported backups) as an enhancement for future product versions.

[Markush-VE]

any news on that? would be especialy useful when using Storeonce catalyst repositorys

[Seve CH]

Hello,

In some cases, backups need to be exported. If I am not mistaken, there are the following options:
- Veeam ZIP: This is an active full backup to somewhere else.
- Backup Export: This makes a synthetic full from a restore point to the same repository where the original backup was. It doesn't seem to use Block Cloning. Restore points need to be selected for each VM.
- Navigate (if possible) through Veeam backup files and pick the required ones (identify backup chains, copy full + increments, etc.)

I would like to be able to do as follows:
Export a backup anywhere: Same repo, another repo or a folder, like Veeam ZIP.
Possibility to:
Select the origin of the data:

• Existing restore points (and which one)

• Existing restore point + run a new incremental without impacting the backup chain

• Active full (with or without CBT reset)

All of this per VM or for a list of VMs (export restore point in X time range, for instance)
Select the target:

• A Veeam repository

• A shared folder

• A local folder

And use or not block cloning if available.

Business case 1:
VM A Backup at T.
VM A crashes and corrupts at T+20 hours
We need to recover a backup from T.

The VM A was still running for 20 hours. We would like to be able to export that VM in Veeam format just in case we need in future to try to recover some data from there.

We have restored VM A. Veeam will start a new backup chain. We would like to export the state of the backup at T which might be an incremental.

Business case 2:
We want to replace the archiving storage.
We would like to export a lot of VMs from a specific restore point (a specific day, for instance).
The source is deduplicating storage, object storage, cloud storage, etc. so file copy is not possible.
The target could be somewhere else: local hard disk, a network share or a Veeam Repository.
We need to select a lot of VMs, so we would like to be able to select a time-range to export the backups and not having to cherry-pick the restore point per VM.

Business case 3:
We are required to provide (litigation, legal constraints, etc.) a specific restore point from deduplicating/object/cloud storage. So it needs to be exported to USB disks.

Business case 4:
We are require to hold a specific backup restore point for some time. It can stay on the same storage system as the source backup. We do not want to double our space usage on ReFS or XFS storage storing a full new backup chain: We would like to be able to export a backup using a synthetic full using block-cloning.

Business case 5:
We want to export the current state of a huge VM.
We do not want to read the full VM from production.
Maybe:
It is offsite -> WAN traffic
The main storage is slow (per se or just it is slow because it is damaged)
The VM is huge and there are little changes
We would like to do a Veeam ZIP, but seeding the backup with existing restore points. This is something similar to replication seeding from existing backups.

With the current situation, with some kung-fu, we would be able to achieve somehow these business cases. But not everybody can do kung-fu. It would be great to be able to do that from Veeam console.

Best regards

[foggy]

Thank you for such detailed feedback, much appreciated. Merging your post to a similar existing discussion for easier demand tracking.

[ChuckS42]

Yah, +1000 here. Just now decided to write new exported backups to a different, non-replicated share on my ExaGrids, and was very disappointed to find that I could not. Now it'll take a lot longer to do the job.

[mikeely]

+1 here also. Definitely a nice-to-have for us.

[mihalevskiy]

Will you add this feature?

[foggy]

Hi Andrei, we have this request on the list of future enhancements but cannot share any particular ETA at the moment. Thanks!

[frankive]

Come on Veeam
We often have to export point in time backup to external usb disk for customers.
We need the abilty to export backups fro ma certains restore point to a usb-drive.

The best workaround for now is just to choose Restore Vm files, then I can restore the files directly to the usb-drive.

[wishr]

Hi Frank,

Unfortunately, we cannot share any news atm, but we are aware of the demand.

Thanks

[Gostev]

The best workaround for now is just to choose Restore Vm files, then I can restore the files directly to the usb-drive.

Why not export to the repository, and then just copy/move the produced VBK to a USB drive? Seems much easier + export to the repository should be extremely quick and require no physical disk space with ReFS or XFS repositories.

[frankive]

This particular customer I was working with had limited space in their repository and used NTFS.

Agree that exporting to same repository with REFS is the best solution if REFS is in place.

[Entropy]

Another +1 for this.

Our situation: VBR server having issues. Decide to bare metal restore the OS from backup. One of the issues is its own repo array. So export a backup from the Linux immutible repo, but that's locked down so hard the only way to get at the exported image is to sneakernet it (a building away, etc.). Whereas if I could have exported it to a USB drive on the VBR box it would have saved lots of time walking back and forth.

[Mildur]

Export to another location will be possible in our upcoming release V12.

Best,
Fabian