Veeam Backup & Removable Media (rotated drives)

[bunger]

Just curious for those of you using rotating external drives - is your Veeam server a physical server or a VM and if it is a VM, how are you dealing with the speed issues associated with USB pass-through?

Thanks
Bill

[pitchpartners]

I have the same problem when I use a USB hard drive.

The temporary solution (hopefully temporary) I've found, is to delete the job was done the day before.
1) go to "Backup & Replication"
2) go to the subfolder "Backup"
3) Right click on the job
4) Select "Remove from backups"

The problem is I need to do this every day

Once again I will ask, are you simply running a full backup every night? If so, the registry key will still work. Simply configure the job to run an active full every night with the registry key and all is good.

You could also easily script the "Remove from backups" tasks via PowerShell and have the server automatically do this just prior to the backup run.

So you are saying the registry key DOES work on v6 in this following job configuration?

[tsightler]

In my testing, using this methodology, it worked fine. I wasn't using an external drive, but rather a folder. I removed the entire folder, and on the next night the folder was recreated, the entry was removed from the "Backups" and a new full backup was run without error. If your doing a full backup each night, this is easy to implement and not that different from V5.

[mbelcourt]

Just curious for those of you using rotating external drives - is your Veeam server a physical server or a VM and if it is a VM, how are you dealing with the speed issues associated with USB pass-through?

Thanks
Bill

My Veeam server (v6) is on VM. My external drive is on physical server with Veeam Proxy. I not tested yet with USB pass-through.

[mbelcourt]

If there are people who want the script (Powershell) to automate the deletion of backups instead to do it manually.

Code: Select all

Add-PSSnapin   VeeamPSSnapin
$smtpServer = "10.10.10.10"
$msg = new-object Net.Mail.MailMessage
$smtp = new-object Net.Mail.SmtpClient($smtpServer)
$msg.From = "FlushBackup@test.com"
$msg.To.Add("me@test.com")
$msg.Subject = "enter your subject"
$msg.IsBodyHTML = $true
$msg.Body = Get-VBRBackup | ConvertTo-Html
$smtp.Send($msg)

get-vbrbackup | remove-vbrbackup -Confirm:$false

[bunger]

My Veeam server (v6) is on VM. My external drive is on physical server with Veeam Proxy. I not tested yet with USB pass-through.

What kind of through-put speeds are seeing to the hard drive?

Thanks
Bill

[mbelcourt]

My Veeam server (v6) is on VM. My external drive is on physical server with Veeam Proxy. I not tested yet with USB pass-through.

What kind of through-put speeds are seeing to the hard drive?

Thanks
Bill

It's between 25 to 29 MB/s

[mbiesheuvel]

I have the same problem when I use a USB hard drive.

The temporary solution (hopefully temporary) I've found, is to delete the job was done the day before.
1) go to "Backup & Replication"
2) go to the subfolder "Backup"
3) Right click on the job
4) Select "Remove from backups"

The problem is I need to do this every day

Once again I will ask, are you simply running a full backup every night? If so, the registry key will still work. Simply configure the job to run an active full every night with the registry key and all is good.

You could also easily script the "Remove from backups" tasks via PowerShell and have the server automatically do this just prior to the backup run.

So you are saying the registry key DOES work on v6 in this following job configuration?

Ok! I do not want (and can't) to use it. At some companies we have a very big site where a full backup takes like 20 hours. It's impossible to do this every night and then also need to copy the big file to e-sata disk. I just want the old option back! Please!

[foggy]

Michel, let me ask you once again as you haven't specified the clear answer previously: have you tried the solution given above by Anton: to create subfolders on the newly inserted drives for each job to put backups into?

[pitchpartners]

Thank you all for trying to help but these 'work arounds' are not good enough.
I am going to roll back to version 5 and keep an eye on this forum. As much as I do not want to, if it's not fixed we will be looking at other vendors for clients who are required to use rotational removable media.
Rob

[tsightler]

Could you please be specific about what "work around" is not acceptable. As far as I can tell, except for requiring the sub-folder to exist, the behavior is exactly the same as V5 when using this registry key. Are you finding that not to be the case?

[pitchpartners]

Could you please be specific about what "work around" is not acceptable. As far as I can tell, except for requiring the sub-folder to exist, the behavior is exactly the same as V5 when using this registry key. Are you finding that not to be the case?

Your right, there's not much difference. v5 is still awkward but I did have that working with regular intervention. v6 I started copying the previous nights backup files from USB, locally and then copying back to the next scheduled backup USB. This work around seem to work, but I was having to do this for every job every day. I found like with v5 I still had to delete old data off the USB's as they were not being removed. Backup jobs should require setting up, tweeking and then forget about until an error is reported but it's possible I am missing something...?

[tsightler]

That's what I'm trying to understand. I'm able to get V6 to behave exactly like V5 using the same registry key as with previous versions. The only difference is that I have to remove both the VBK and VBM files and leave the job subfolder in place. With previous versions there was no subfolder and no VBM file, but otherwise it seems identical. I'm trying to understand what's so bad about V6 compared to V5 if the only difference is having to delete one extra file and leave a subfolder around. Honestly, with a single script automated via Task Manager, this becomes a completely automated process with either version.

[ThomasMc]

Don't forget to use -FromDisk in the Remove-VBRBackup to delete completely

[tsightler]

If you're using the registry hack, you don't even need this since the chain is automatically started from scratch each time the directory is detected as empty. All previous entries are automatically deleted. A simple script that simply deletes the files 5 minutes prior to the backup starting is all that's really needed.