Udhaya's profile - activity

2018-06-29 14:04:32 -0600 answered a question ECCN for BDR Suite

Hi,

Regarding your query, please contact our Technical Support Team at vembu-support AT vembu.com

2017-10-31 07:41:58 -0600 received badge  Teacher (source)
2017-10-27 08:36:18 -0600 commented answer Servers Deactivated

Hi,Further to our previous reply, by using Vembu BDR Free edition, you can perform image level backups for Windows Server/Desktops, VMware VMs & Hyper-V VMs (Disk level/VM level backups) and file/application level backups from Windows Desktops & Workstations at free of cost. In case of file/application level backups (Vembu NetworkBackup) for Windows Servers, you have to purchase license from Vembu Portal(portal.vembu.com). The page which you have mentioned actually refers to the Windows Server Disk Image backup, we will clearly mention the same on that page shortly.

2017-06-12 10:05:50 -0600 answered a question Incremental retention

Hi,

We recommends you to use 'GFS Retention' policy to achieve your requirement. With GFS retention, you can configure 'Weekly Merge' option for your backup jobs where the incremental will be merged on weekly basis and you can have all recovery points for the particular week.

If you have configured backup jobs with 'GFS Retention' option, you can edit the backup job and change the required configuration. Please note that if you have already configured backup jobs with 'Basic Retention' option, you can not change retention policy to GFS for the existing backups. You have to create a new backup and set the GFS retention based on your need.

2017-05-02 07:44:27 -0600 received badge  Associate Editor (source)
2017-05-02 07:44:27 -0600 edited answer Next schedule backup - 1st Jan 1970 05:30:00

Hi,

Normally, this incorrect next schedule time issue will be fixed once after editing the backup schedule. Since this issue is not resolved after editing the backup schedule, we provide you the manual steps to update Next Scheudle Time value in database.

Please follow the below instructions

1) Stop the VembuNetworkBackup Application running in the Client machine.

2) Now, open the command prompt (administrator command prompt) and go to the "<vembu_home>" location [By default, it will be 'C:\Program Files\Vembu\VembuNetworkBackup' ] and execute this command "lib\sqlite\sqlite3.exe data\sgclient.db " to open the database.

(here we assume, you have not changed the dbstorage location path and db files are present under <vembu_home>\data folder)

3) Execute the below query in database in order

i) To Get the Backup Config ID Select BACKUPCONFIGID from BACKUPCONFIG where BACKUPNAME=<backup_name>;

ii) To Update the current time as Next schedule time
update BACKUPSCHEDULES set NEXTSCHEDULETIME=(SELECT strftime('%s', 'now')) where BACKUPCONFIG_ID= <backup_config_id>;

iii) To confirm that current time is updated, please execute the below query select datetime(NEXTSCHEDULETIME, 'unixepoch', 'localtime') from BACKUPSCHEDULES WHERE BACKUPCONFIG_ID =<backup_config_id>;

4) Execute '.q' to close the database.

5). After that, start VembuNetworkBackup and resume/schedule the backups.

If the problem still exists, please send the result of last query (query mentioned in point iii), which will help us to give the suitable solution.

2017-04-07 03:07:26 -0600 answered a question Vembu BDR - Image backup Seed Image

Hi,

Curently we do not have option to seed Image based backup jobs in the Backup Server. In order to perform Image based backups, we insists customers to deploy the backup server locally (on-premise) and we feel there is no need of seed option in this deployment.

2017-03-29 07:24:57 -0600 edited answer What can cause "Missed Schedule" or the "Backup Socket" to be idle for 30 minutes?

Hi,

@Missed schedule report for backup jobs

Normally this error reported when the backup job does not scheduled as per the scheduled time. For example, if the backup job set to run daily at 9 AM and if the Vembu BDR backup server will not receive the backup job until 10 AM, this error will be reported for the backup job.

Also, if the time zone settings in the backup server and client differs, this issue occurs. Please check the both the cases and let us know your findings.

@backup Socket was idle for more than 30 mins

The error "Backup Socket was idle for more than 30 mins" occurs when the Vembu-OnlineBackup Client losses the network connection and the Vembu BDR Server has timed out after 30 minutes. If connection between the client and server is alive, Vembu-OnlineBackup client will send the KEEP_ALIVE packets periodically and server will not timed out. Hence we believe, that this problem can be caused due network connection issue at the client side.

Normally, if backup fails, Vembu-OnlineBackup will allow to reschedule the process automatically after 5 minutes from the client. So, backup will get successfully completed in your environment for the next schedule. Please check whether all the configured files has been transferred successfully from your client to the backup server.

2017-03-27 02:30:38 -0600 commented answer Does Venbu actually work with Linux?

It seems, UnixODBC is already installed in your machine and when we type 'obdcinst -j' command, it looks like that system search the odbc.ini file inside the /etc location. And there is no content in the /etc/odbc.ini file. During Vembu BDR installation, we have created the odbc.ini file inside /usr/local/etc/ location. Since, /etc/odbc.ini file is empty, you faced the db connection issue in your machine. So we have created a soft link for odbc.ini in your machine by running the following command, ln -s /usr/local/etc/odbc.ini /etc/odbc.ini Now, Vembu BDR is running and the db connection issue resolved. We will handle this case in our installer in our next update v3.8.

2017-03-24 05:45:08 -0600 answered a question Vembu 3.7 strange issues

Hi,

Please find our replies for the reported queries inline below.

-->After installing the fix of 3.7 to both BDR and ODR, inspite of services running, Unable to login to console

Please provide us the exact error message which you are getting while logging into Vembu BDR Backup Server console and server.log file to analyse this issue further. If you are getting 'Unable to login' error even if Vembu BDR service is running, then there is a possibility of database updates in progress for the previous interrupted jobs. If it takes more time, then please send us the above requested details for debugging purpose.

-->Also there are many postgres instance found running.

We have noticed that there are 72 instance of postgresql is running in your machine. Please note that for each new connection, postgresql will start a new process and normally that process will get closed when we close the respective connection. During backup/recovery process, there could be many db connections get established and will get closed when the backup/recovery process get completed. Also, in Vembu BDR, we have few threads which are active forever, and they will use some database connections. So, number of postgresql connections 72 is normal only.

-->Vembu Virtual Drive is GONE

Once Vembu BDR application is started, we will check and update the databases if previous db metadata files present in the location. Once after that, Vembu Virtual Drive will be listed in the explorer. It Virtual drive is not listed in explorer for more time even the BDR service is running, then please try to stop and then start the Vembu BDR service in your machine once and then verify whether Vembu Virtual Drive is listed in Windows explorer.

If the problem persists, please run Vembu BDR in command line (in administrative prompt) and send us the prints and screenshot of the explorer to analyse the issue.

-->I am looking at Windows application logs and notice, that every time Vembu server is rebooted – Apache Service triggers 2 exactly same errors on startup – is it normal?

${SRVROOT} is variable used in apache webserver configuration to mention the document root path, which we didn't use in our Vembu BDR web server configuration. This will create an undefined error in windows application log. This is a warning message and it will not affect the Vembu BDR web server. We will fix the same in our next release.

2017-03-23 01:57:49 -0600 answered a question Network Backup 3.5 -> 3.6 upgrade failure

Hi,

Normally the particular error message would occur if the status of previous migration is not updated properly in database. We have fixed similar type of issue already and we recommends to use the below build to avoid this upgrade issue in your environment.

Vembu NetworkBackup Windows Build

Vembu NetworkBackup Windows Build XML for Software Update

2017-03-22 04:52:44 -0600 commented answer Error while getting/Inserting client token::Error in inserting client uuid into DB

We believe that you are looking 'Server Management' option in VMBackup Client console and please be informed that the particular option is available only in Vembu BDR Backup Server console. As we mentioned in our earlier post, please remove the client entries from backup server console and try to register VMBackup client with same client id again . If still issue persists, please send us the following details to vembu-support AT vembu.com email id to provides you solution at the earliest. 1. Screen shot of exact error message from VMBackup Client. 2. Screen shot of 'Management ->Server Management ->Client Management' page from Backup Server.

2017-03-22 03:37:04 -0600 answered a question Error while getting/Inserting client token::Error in inserting client uuid into DB

Hi,

From your post, we believe that you had configured Hyper-V backup jobs from VembuVMBackup client with client ID 'HVHOST' and then you had re-installed the VMBackup client with client ID 'HVHOST1'. Here we are suspecting that during VMBackup re-installation you might proceeded with option 'Rename the old files from the installation location' and the client configuration files might not be renamed successfully which may leads this issue in your end.

Hence, we suggest you to remove VMBackup installation folder manually and proceed the re-installation again. Also, we recommends you to remove the particular client entries from Backup Server console by navigating 'Management ->Server Management ->Client Management' page. It will remove both client and its backup related entries from Backup Server properly. Then you can configure backup from the VMBackup client without any issues.

2017-03-01 04:24:54 -0600 answered a question Want to move MogoDB off C: drive

Hi,

Please refer the below link to move MongoDB from C: drive to another drive with enough space. https://www.vembu.com/support/knowled...

2017-02-20 12:01:19 -0600 commented answer Unable to login

Hi. Please make sure that Vembu BDR application have full access to the particular backup repository and its running under administrator privileges. Also, kindly contact us at vembu-support AT vembu.com with 'server.log' file from '<vembu_home>\log' location which will help us to analyse this issue further.

2017-02-20 10:55:26 -0600 answered a question Unable to login

Hi,

Normally this error would occur if the configured backup repository is not available during application startup. In your case, we suspect that the name of the particular drive might be changed once you have resetted that drive which may caused this issue in your environment. Hence, we recommends you to provide "D" as driver letter for that external drive and restart Vembu BDR application to logging into webconsole.

2017-01-12 09:46:32 -0600 answered a question Write to event log

Hi,

Currently in Vembu BDR, we don't have the option to log the backup status reports in Windows events. We do have plans to integrate BDR product events in Windows. Based on the current projection, it will be available in the second quarter of 2017.

2016-11-14 05:07:37 -0600 answered a question Offsite DR to public static IP server

Hi,

To provides you better solution, please verify the following things in your environment and update us your results,

  1. Test connectivity results of Backup Server to Offsite Server
  2. Whether you can login to OffsiteDR Server console successfully
  3. Any error message while saving Offsite Copy Management setting
2016-09-15 01:07:38 -0600 answered a question Getting an error SG0302 - Problem in Accessing the backup location in server

Hi,

Normally this error would occur if the configured storage repository is not accessible by Backup Server application during backup job. Please verify the following details in your end,

1) Whether Backup Server application has enough permission to access the storage repository.

2) Whether you can able to connect the particular storage location using Windows explorer in the Backup Server machine.

3) Please check whether Vembu BDR service is running under "Local System Account", if it is 'Local System Account' then please change it to administrator account. Please follow the below steps to change the logon account type.

a) Open the Services control applet through "Control Panel -> Administrative Tools -> Services" shortcut or by running "services.msc" command in "Start ->Run" tool.

b) Select the VembuBDR service and then open its Properties dialog.

c) In the VembuBDR services Properties dialog, go to the "Logon" tab and change logon account from 'Local System Account' to 'User Account' with administrator user credentials.

d) After providing the correct user name and password details, click 'Apply' and 'Ok' to apply the changes.

e) Restart VembuBDR service.

Now schedule the backup job from Backup client and verify whether backup is running fine in your environment.

2016-08-29 03:20:32 -0600 commented answer Network Backup Client 3.5.0 Won't start

Hi, This is a known behavior of Vembu Networkbackup in Windows server 2008 R2 machines that doesn't have the required Microsoft Visual C++ 2008 Redistributable Package (x86) package. Please refer the following Knowledge base article to resolve the particular issue in your environment. https://www.vembu.com/support/knowledge-base/question/115026/vembu-bdr-webconsole-fails-to-load-after-installation/

2016-08-10 08:43:38 -0600 answered a question Backup was aborted as backup Socket was idle for more than 30 mins

The reported error "Backup was aborted as backup Socket was idle for more than 30 mins" normally occurs if the connection between Vembu Backup Agent and Vembu BDR Backup Server is closed prematurely by an external force, while Vembu Backup Agent is actively sending backupdata to the backup server. The external forces may be one of the following in the Vembu Backup Agent,

  1. NAT/Firewall configurations
  2. Low end routers/switches
  3. Intrusion detection software
  4. Internet link error

To resolve this issue, please change the 'FileAck' attribute value to 300secs under the SGTimeOutConfig tag in the Vembu_Home\conf\SGConfiguration.conf file in your client's configuration file. Then reschedule the backup again and verify whether backup goes well.

2016-08-09 09:03:39 -0600 answered a question SG0132: Invalid remote socket. An operation was attempted on something that is not a socket.

Hi,

This error message might occur due to several environmental issues like when Vembu BDR Client exits or its connection is closed when the backup is in progress. The detailed answer for the reported query can be found from the following URL,

https://www.vembu.com/community/quest...

2016-07-15 14:43:36 -0600 answered a question Does Vembu OnlineBackup not support SQL Server 2014

Hi,

Yes, currently MSSQL Server 2014 is not supported for backup in Vembu OnlineBackup. We have already added this feature in our road map list and it will be available in future release of Vembu OnlineBackup.

2016-07-12 10:35:42 -0600 commented answer Windows Server 2008 R2 P2V Boots To System Recovery

Sorry for the inconvenience caused. Please find the exact URL for the recovery CD documentation. https://www.vembu.com/guide/disk-image-backup-user-guide/getting-started.html?BaremetalRecoveryusingVembuRecov.html

2016-07-06 09:00:59 -0600 commented answer Change backup selections after initial backup - Image based backup

Hi, Yes, the disk image backup will complete successfully once disk order are up in correct order in your environment.

2016-06-27 08:04:13 -0600 answered a question Change backup selections after initial backup - Image based backup

Hi,

From your details we suspect that your Disk Image backup got failed due to any one of the below issue,

1) After initial full backup, Disk Order has been changed in your source machine. [configured iSCSI drive order]

(or)

2) Change in Volume GUID of the configured drives.

Can you please check whether the backup got failed due to any one of the above scenarios. If this is the case, you ave to configure a new backup as we wont allow to edit the backup job now.

If this is not the case, please update us the below details to analyze the issue,

  1. Results of the following commands in Vembu ImageBackup internal database which is available in <installation_location>.

    Open sgclient.db in command prompt by using sqlite.exe which is available in <installation_location>/lib/sqlite, and then execute the below commands.

    select * From BMR_BACKUP_INFO;

    select * from BMR_DEVICE_PARTITIONS;

  2. Results of "mountvol" command from your machine.

2016-01-19 01:02:40 -0600 edited answer Upgrade appliance from 3.1.1 to 3.1.3

Hi Gowerg,

From your query we believe that you have updated the Vembu BDR server with out any issues and while checking the version of the build from user interface you are getting the error message as mentioned in your query. We believe that the version check happened during back end database update and that is the reason for this issue. Kindly follow the below steps in your environment and update us the status.

  • Restart Vembu BDR application
  • Clear browser cache and try login the console and check the build number.
  • If the same issue reoccurs. Please do check the permission for Vembu BDR application running user to restart the Apache instance and provide necessary permission for the user.
2016-01-04 06:48:53 -0600 answered a question Client Download files

@Jim, We have updated the automatic software document with Vembu BDR Suite v3.1.3 release changes and you can now download v3.1.3 builds from the available download links.

2015-11-18 07:54:29 -0600 commented answer Application aware process failure

Hi Tom, Thanks for briefing the issue. Yes, a known issue exists in reports for VMware backup plugin where VMBackup logs warning for VMs which isn't configured with VM Guest OS credentials as the option 'Application Aware Image Process' is enabled at backup level. We're already working on this issue and will be fixed in our upcoming releases. For your information, this doesn't affect the backup process and they will complete successfully.

2015-11-17 07:24:03 -0600 answered a question Application aware process failure

Hi Tom

Normally this error would come during backup if VM Guest OS credentials are not provided for the configured virtual machine in 'Settings->VMware Guest Credentials' page after enabling 'Application aware image process' option for the particular VMware backup job. Hence, we request to verify the following details in your end and update us the same.

  1. Did you get any error message while configuring VM Guest OS credentials
  2. Have you changed VM Guest OS credentials after performing backup job
2015-10-27 06:50:37 -0600 answered a question Unable to process the SQL Server database details

Hi Madison,

Normally this issue would occur, if environment variable for OSQL path was not properly set in your client machine. Please do check and verify the below cases.

  1. Verify whether OSQL utility path is set correctly in system environment variables. Vembu NetworkBackup uses OSQL utility to backup the sql databases. The default OSQL path is "C:\Program Files\Microsoft SQL Server\90\Tools\Binn".

  2. Verify whether SQLVDI.DLL is registered properly in Registry. Vembu NetworkBackup uses SQLVDI.DLL to dump the SQL databases. To register the SQLVDI.DLL, please run the following command in your machine.

    Regsvr32 "C:\Program Files\Microsoft SQL Server\80\COM\SQLVDI.DLL" - This is default path.

  3. Error might be raised due to lack of permission to connect the MSSQL Server. Please check the NetworkBackup logon user have enough permission to access the SQL databases.

Please verify aforementioned scenarios in your machine and check whether you are able to edit the backup job successfully.

2015-10-26 06:47:34 -0600 answered a question virtual machines backup support

Hi Miller,

Vembu VMbackup does not support backup of virtual machines from VMware Workstations. VMBackup supports the following VMware environments for both Backup and Replication.

VMware vSphere 4.x,5.x and 6.x

vCenter Server 5.x and 6.x

ESX(i) 4.x,5.x and 6.x

2015-10-20 08:47:57 -0600 edited answer Retention is in progress. Backup request rejected from the server Amazon Cloud

Hi Joel,

Usually once the backup completes, the cleaning of all the excessive versions process will be started in Vembu Cloud Server hosted in Amazon. The time taken for the retention process depends on the size of the data available in Vembu Cloud. So we request you to wait for certain time period and then reschedule the backup job again.

Copyright © Vembu Technologies 2020. All Rights Reserved.