riyazudeen.hameed's profile - activity

Hi,

Thank you for reaching out Vembu Community Forum.

From the provided information, we noticed that Vembu BDR build number is not updated properly. We request you to perform ontop installation of our latest version v3.8 over the v3.7 and ensure version and build number gets updated properly as specified in the below technical article (Refer: page 3).

https://www.vembu.com/pdf/release-not...

Vembu BDR v3.8 build download:
https://sg-build-release.s3.amazonaws...

Once upgraded successfully, we request you to reschedule the backup job from the client.

Also, regarding the Portal query we would like to inform you that for the Vembu BDR Free Edition backups, the license information will be shown as over-consumed status in Vembu portal (in order to differentiate the backups from licensed version). However, please be rest assured that configured backups will run normally.

Yes, you can still recover the server.However ‘Plugin-data’, ‘data’ and ‘conf’ folders contains configuration details so we request to provide the same Vembu BDR ID during the install on the new system. Also those folders contains VMWare and HyperV Host details incase VMWare/HyperV backups are configured from the Vembu BDR server so you need to reconfigure the provided VMware and HyperV Host details after the rebuild. Please be rest assured that configured VMware/HyperV backups will be available in the Vembu BDR server for restore.

Hi Vaibhav ,

Thank you for reaching out our Vembu Community Forum.

A hardware failure or a system crash in the machine running the Vembu BDR backup server may lead to a loss of the Vembu BDR application and its PostGres back-end server installations. However, the backup data might still be intact if the storage was in a separate storage device. In that case, it is possible to rebuild the Vembu BDR backup server completely provided the backup data and the database dump file are intact in the backup storage location.

In re-building a Vembu BDR backup server, you need to have the following:

1. Backup storage targets which holds backup data (i.e., sgstorage folder from all backup data storage drives attached earlier).When more than one drive is configured for storage, make sure you have all of them.For example, when E and H drives are configured as storage drives,then make sure you have both E:\sgstorage, H:\sgstorage .
2. ‘Plugin-data’, ‘data’ and ‘conf’ folders (Taken from ‘VembuBDR-Home’ which typically will be C:\Program Files\Vembu\VembuBDR).

3. Dumped Server Configuration Database file

   By default, the Vembu BDR backup server’s configurations are stored in a database that is dumped daily. This file is dumped under the path given during installation for the backup storage location. For e.g.
   E:\sgstorage\Default_Repo\SGDatabase.sql

Steps to Rebuild Backup Server

Rebuilding the backup server is a two-step process:

1. Installation of Vembu BDR and PostGres database.
2. Importing of Vembu BDR backup server database

Installation of Vembu BDR and PostGres database.

1. Download BDR server installer from Vembu Downloads and make sure the version is same as Vembu BDR running earlier

2. Run the installer with administrator privileges. Note: Once installation completes, make sure Vembu BDR service is NOT started. If started, then stop the service.

   Open ‘Vembu BDR-Home’ location and replace the following sub-folders with the sub-folders copied earlier : ‘data’, ‘Plugin-data’ and ‘conf’

3. Now make sure you configure the same drive letters for storage location and avail in same location as configured earlier. Say like same E and H drive as mentioned in earlier steps.

Importing of Vembu BDR backup server database

1) Open CMD prompt with administrator privileges and run below command from PostgreSQL installation location to create the database " SGDatabase"

a) psql -Upostgres
It will ask for postgres password and after entering the password execute the below command to create database

b) create Database SGDatabase

2) Now exit from postgres terminal and run the below command to import the database psql -Upostgres SGDatabase <dumpfile location="" ex:="" psql="" -upostgres="" sgdatabase="" &lt;="" f:\sgstorage\default_repo\sgdatabase.sql<="" p="">

It will ask for postgres password and after entering the password check the import process. After importing the databases please start Vembu BDR service and ensure the backups are resumed and running successfully.

Note : By default, the Vembu BDR backup server’s configurations are stored in a database that is dumped daily.So the backup details after the last dump time will not be populated.

We have integrated the requested feature to create users with 'Read-only' privilege in our upcoming release of Vembu BDR v3.8 which is expected for GA by mid/end of next week.

Hi,

Yes, you can license Vembu BDR suite for free usage and it is not mandatory to update Credit card details if you are using free edition. Vembu BDR Suite comes with a 30 days of full feature trial during evaluation period. Once the trial expires, you can either opt for free or paid edition of Vembu BDR Suite.

Inorder to license our product for FREE usage then we request to register your Vembu BDR server with our Portal and then click on bottom left notification icon to activate "Vembu Free Version".

Also,please refer the below document to know about the comparison/restrictions of free Vs paid edition. https://www.vembu.com/pdf/datasheet/v...

For Hyper-V Backup, you need to backup locally to a Vembu BDR Server and from the local backup server you can replicate the data to an offsite datacenter using Vembu OffsiteDR. Alternatively the data can be replicated to our Vembu Cloud using Vembu CloudDR. The OffsiteDR and Vembu CloudDR replication are WAN Optimized, hence there is no file size restriction with HyperV Backup jobs.

Hope you have pointed and deleted the inactive job from the test server's Recovery page now. As informed earlier, backup job might not be deleted from the test server due to server unavailability or some other reason during the deletion of backup job from the client.

Hi,

Hope you have pointed and deleted the inactive job from the test server's Recovery page now. As informed earlier, backup job might not be deleted from the test server due to server unavailability or some other reason during the deletion of backup job from the client.

Hi,

Reported issue occurs if the "Next schedule time" is not updated properly in the database.We request you to edit and save the backup job to update 'next schedule time' automatically.

Please follow the below steps to resolve the issue.

1. Click on Backup ---> List of Backups.
2. Click on "Edit" next to the backup which has incorrect/old time updated.
3. Click 'Next' till the last step and save the configuration as before.
4. Once configuration is saved, please click on "Run Now" icon and wait for the backup job to complete.
5. Now check the "Next Scheduled time". It should be updated properly.

Hi,

Yes, if the initial full backup got interrupted due to connection loss or some other reason and once the next backup schedule starts, we will report it as 'incremental schedule' and the backup will start from where it left off. Also during this incremental schedule, the files which were not sent during the first full backup schedule will be transferred fully.

Regarding the restore point, even if the full backup is interrupted (with few files get transferred), we will create a restore point for the files transferred during the particular schedule.

Hi,

We feel sorry for the issue happened.We request you to download the Vembu BDR setup from the below link and proceed with the installation.

http://sg-build-release.s3.amazonaws....

If issue still persists,we request you to provide us the teamviewer access of your machine by sending an email to vembu-support@vembu.com. So that we can look into your environment and find the cause to help you with the resolution on the same as early as possible.