h.wolfgruber's profile - activity

2020-04-24 05:36:55 -0600 received badge  Famous Question (source)
2020-04-13 00:09:21 -0600 received badge  Notable Question (source)
2020-04-11 15:33:19 -0600 answered a question Insufficient drive space in storage pool

#1. Should be not the cause because almost 700 GB free space on the backup storage

#2. BDR is installed on the Hyper-V host. All storage disks are local (DAS), the backup storage is connected via eSATA.

I'll send the logs to the mail address you mentioned.

Thank you!

2020-04-11 11:45:03 -0600 received badge  Popular Question (source)
2020-04-11 11:33:25 -0600 received badge  Famous Question (source)
2020-04-11 03:02:47 -0600 asked a question Insufficient drive space in storage pool

Hi,

BDR fails on incremental backup stating "Insufficient Drive space (in the configured storage pool) in backup server 127.0.0.1 to proceed the backup job [ImageBlockDataHandler.cpp:2065]".

I don't think that BDR is going to start a full backup because the backup.log says: "Incremental Info available for VM <vm name="">:: Previous Incr Num ::9::Status ::9 BackupScheduleRunner::IsthisFreshBackup] Valid Incr Info Available For VM"

The incremental backup size ist approx. 15 GB, the storage pool (eSATA drive) has more than 680 GB free space. I already freed some space on the Hyper-Vs VM space. but that didn't help.

Thank you

Hermann

2019-12-26 23:45:38 -0600 received badge  Notable Question (source)
2019-12-08 02:27:03 -0600 received badge  Popular Question (source)
2019-11-30 06:55:27 -0600 asked a question Hyper-V: Backup failure: Error While Accessing disk

Hello,

I'm using BDR 4.0.1 on Hyper-V 2016 for quite a while without any problems to backup one VM (Windows Server 2016) with approx. 1.3 TB once a week.

A few weeks ago it started failing with: "Problem while backing up the data in Client Side. Error : Backup Schedule Failed" and "Error While Accessing disk for Backup. (Refer this KB : 104050)"

The cause in the referenced KB 101050 is not applicalbe because the VM has already Version 8 and isn't migrated. It is installed from scratch on that host and never been moved.

Restarting the host and the VM several times did not help. Aside from Windows Updates there were no changes made to both the Host an the VM in the weeks before.

Does anyone know about the issue and how to solve it?

Regards, Hermann

2019-07-16 08:42:40 -0600 received badge  Famous Question (source)
2019-06-24 11:49:37 -0600 received badge  Notable Question (source)
2019-06-24 11:49:37 -0600 received badge  Popular Question (source)
2019-06-22 02:52:49 -0600 asked a question Orphaned job schedule, License question

Hello,

I'm unsing the free edition of BDR to backup my Hyper-V host. BDR ist up to date (4.0.1). Recently I deleted a job schedule and created a new one. Since that time I receive "Missed Backup Schedule" mails when the deleted job was scheduled. Neither in BDR nor in the vembu portal the schedule is visible. How can I get rid of it?

The vembu portal > License states "Over-Consumption". I'm backing up only one Hyper-V with one socket. Is this normal to the free edition?

Thank you!

Regards, Hermann

2019-01-27 13:21:10 -0600 received badge  Enthusiast
2019-01-26 07:13:50 -0600 answered a question Run Now not working

Nivas, thank you for explaining the License check.

How ever, last Friday, as advised, I delete the old backup job and ran the License check. Before creating the new Backup job I verify that the the backup is gone from the Vembu Portal, the Backup has been delete from the storage and there is no reference to the old job anymore.

The new job started as scheduled. The Backup size is approx. 1.3 TB so I expected it takes the whole night.

Today the output of the console is confusing. In Dashboard there is a green triangle, the job is still running. Detailed view states a running time of 16 hrs 50 min. and a trasferring volume of 1.21 TB, but not VMs. In Backup > List Jobs the Job has the status Idle. In Recovery the Job is marked ( Old Backup ), Job Status is Running. In Web Portal the Job is also marked _Old. Klick on the yellow qestion mark returns only one VM instead of three.

The Storage usage didn't change for hours.

There are some Services on the host which I associate with Vembu: PostgreSQL - PostgreSQL Server 9.6, VembuBDR,VembuBDR_WebServer, VembuIntegrationService. All are up and running.

The Backup run perfectly on 3.9.1 before updating to 4.0.

Any idea what's the cause and how i can solve it!

Regards, Hermann

2019-01-22 10:11:59 -0600 answered a question Run Now not working

I guess "it is necessary to perform the Run License Check before configuring the new backup job." is the cause because I didn't do License check when I create that job.

Is it neccessary just before creating a job or before change to a job as well?

Thank you for your assistance. I'll create the job this coming Friday and try the Run Now after successfull Full Backup.

2019-01-22 01:36:22 -0600 received badge  Famous Question (source)
2019-01-21 10:16:07 -0600 received badge  Editor (source)
2019-01-21 09:30:45 -0600 answered a question Run Now not working

Hello nivas,

here are the screenshots as requested. There is no Backup report available, even the Recovery menu shows 2 successfully backed-up VM.

2019-01-21 161034-Window.jpg

2019-01-21 161246-Window.png

Since there is not much loss so far, I think it's best to delete the job and create it anew. You don't need to invest alot of effort in this issue.

A question for my information.

Supposed there is a scheduled job, running once a week doing incremental backups. If I hit the Run Now button, it will start immediately an incremental backup. On the next schedule the job will run an incremental backup on regular basis. In case of Recovery I can choose from the regular and the additional backups, right?

Thank you!

Kind regards,

Hermann

2019-01-21 06:49:13 -0600 received badge  Notable Question (source)
2019-01-21 06:49:13 -0600 received badge  Popular Question (source)
2019-01-20 03:37:09 -0600 answered a question Run Now not working

No effect on refreshing the console.

I started a scheduled full backup on Friday. Because it hasn't finished until Saturday I decided to cancel it. The console statet that all 3 VM are backed up successfully but "cannot reconnect to the backup Server".

I tried to come to a clean state by runing an immediate backup.

If there is no other way I have to delete the scheduled job and create it from scratch.

2019-01-19 07:59:14 -0600 asked a question Run Now not working

Hello,

I'm using Vembu BDR 4.0 on Hyper-V 2016.

I attempt to run a job immediately by clicking "Run Now" in Backup > List Jobs.

The console states "Backup has been scheduled successfully" but nothing happen even after while.

I was expecting that this button is used for running a scheduled job outside the schedule. Am I wrong?

Hermann

Copyright © Vembu Technologies 2020. All Rights Reserved.