jameer's profile - activity

Hi Fredrik,

The mentioned UI issue has been fixed in our recent builds and updated the same on our website. You can download the build from the following URL, https://sg-build-release.s3.amazonaws.com/products/vembu/VembuRecoveryTools/VembuUniversalExplorer.exe

Hi Phani,

We have tested the basic functionalities by running the Vembu NetworkBackup client application under the non-root user account and all the basic backup & recovery cases are working fine as expected. Hence you can run the Vembu NetworkBackup client under any non-root user.

However, after automatic software update, the installer will start the application as a root user as per the design. In this case, you have to stop the Vembu NetworkBackup client application and start it under non-root user account after software upgrade or you should disable automatic software update and do manual upgrade whenever we release new updates.

Hi Phani,

Thanks for your details. As we said, currently we are testing the Linux Vembu NetworkBackup builds using non-admin user accounts. We will update our results ASAP.

Meanwhile, please note that Vembu NetworkBackup won't work as 'pull' model. All the backup configurations (including scheduling details) will be stored in agent's internal database and once the schedule time reached, the agent will read the data (modified bytes in case of incremental) which is configured for backup and then send the data to the VembuBDR backup server and the data will be compressed & encrypted during the data transfer. Since its working in Push method, you can restrict the inbound connections to the particular machine (since there won't be any communications from the external systems required) to make it secure.

Hi Phani,

We have this option ( "sh startVembuNetworkBackup.sh <username>" ) in the startup script in order to run the Vembu NetworkBackup agent in a specific user account (admin users). In addition, you should have the root privilege to run this script.

Regarding non-admin user account, we have not yet fully tested this case in our test environment. But however, if this option working in your environment, kindly go ahead and let us know, if you face any issues in that. We will also cover all the cases related to running application in non-admin user account and update the status in this forum thread.

Hi Gabriel,

Generally performance of the backup/restore depends on multiple factors like below,

1. Network performance (based on available bandwidth and network traffic).
2. Hard disk performance in both client and server - the backup/restore performance will be poor if the hard disk is old and is extremely fragmented.
3. System resources like Memory/CPU.
4. Source/Target location type (NAS/SAN/DAS). If the location is network drive then the performance could be low relatively.

So, please check the above and send us the details to analyse this issue.

Meanwhile, please note that if you are backing upto a remote server and trying to restore Exchange server data from Client side recovery, you can restore the same data from Backup Server side itself using our Server side restore. Then you can ship the data to client side through a USB / External drive. This will avoid the data transferred through the network and speed up your restore process

Hi Phani, Like we posted earlier in this thread we are currently analyzing the possibilities to run the entire solution in a non root user. Once we come up the solution we will update it in this thread. For your information Vembu NetworkBackup agent need chroot privileges to run the webservices. We haven't tested the Vembu NetworkBackup by running the apache in root user and run the Vembu NetworkBackup agent in non root user. Hence we request you to wait until we finalize the steps to run Vembu NetworkBackup agent in non root user.

Hi Narsihma, Currently we are running apache services in Jailed environment, which needs admin privilege to start or stop those services. This is the main reason we need root privilege to run our services. We are analyzing the possibilities to run the entire solution in a non admin user and we will update you soon once we implement it in our product. We will keep you update the status in this thread regarding the progress.

Hi,

Thanks for point out the problem in our filter configuration. We have tested your filter configuration in our test lab and files contains "~$" are not excluded in backup. We will fix this issue in our next update. As a work around we recommend you to use filter only with "~". Please configure the filter "Exclude specific files configured in this backup schedule that matches the text pattern "starts with ~" and apply this rule to all levels of sub-folders.". This kind of filter helps you to exclude the files which start with "~".

Hi Roz,

To restore the production server backed up data to the DR SQL server, please do restore from the backup server and move that restored data to the DR SQL server. To export the restored data to the MSSQL database, please follow the below steps in your DR SQL server.

1. Open SQL management studio.
2. Connect the particular SQL instance.
3. Create one database with the database name available in the production server.
4. Right click the newly added database.
5. Go to "Task -> Restore -> Files and Filesgroups".
6. Please choose "From Device" option.
7. Click the box at the right corner.
8. Then Click add button.
9. Choose file type as "All Files(*)".
10. Choose the restored *.sqbk file.
11. Then click "OK" button. Now that file will added in the list and then click "OK".
12. In the list of file it will add, and click the check box near the file.
13. Click the "Option" tag on top of left side in the restore wizard. If you need to restore the database multiple files, then you need to first restore the full backup data alone by choosing the Recovery option 'Leave the database nonoperational, and do not roll back uncommitted transactions. Additional transaction logs can be restored.(RESTORE WITH NORECOVERY)' and then restore the differential backup data by choosing the recovery option 'Leave the database ready to use by rolling back uncommitted transactions. Additional transaction logs cannot be restored.(RESTORE WITH RECOVERY)'.

Hi, Currently MAC OS Sierra is not supported. We are currently working on supporting the same and try to support as quick as possible.

Hi Mr.Technocracy,

After you install the Vembu BDR360 agent in your backup server, you need enable it in your Vembu BDR360 account. To enable, please login to your Vembu BDR360 account and navigate to settings. It will list all the backup server in your account, here you can enable the backup server for which you want to manage from Vembu BDR360.

Hi Todd, We have tested our product upto Mac OS (10.10.5) X Yosemite. We will check our product with Mac OS sierra (10.12) and update you with our result.

Hi Gabriel, To provide you a better solution, kindly update us, the exact error message which you are getting while replicating the data.

Hi, To give you proper solution, please update the VembuBDR crash print by following the below step. 1) Stop VembuBDR, if it is already running. 2) Open a command prompt with administrator privileges and go to <vembubdr_home> folder and start VembuBDR by executing the following command: "bin\VembuBDR.exe". Wait till the VembuBDR application get crash. 3) Update the last few lines of the prints available in the command prompt. It will help us to analyze this crash and provide you a proper solution.

Hi Mike, You can change the dump location for the existing backup by executing few SQL queries and then configuring additional full backup for that schedule before continue with the incremental backups. So that you can restore the previous full backup whenever it requires. Please refer the below KB article for more details, https://www.vembu.com/support/knowledge-base/question/115033/how-to-change-the-dump-location-for-mssql-backup/

Hi Mike,

Currently, it is not possible to edit the dump location of an existing backup via webconsole. We are currently working on this feature and it will be available in our future release. You can change the dump location for the existing backup by executing the few SQL queries then you have to configure the additional full backup for that schedule before continuing with the incremental backups. So that you can restore the previous full backup whenever it requires.

To change the default dump location in Vembu NetworkBackup, follow the steps given below:

a) Stop Vembu NetworkBackup.

b) Go the '<dbstoragelocation>/data/' and access Vembu NetworkBackup client database from command-line by running "sqlite3.exe sgclient.db".

Note : By Default the <db storagelocation=""> will be <vembu networkbackup_home="">. The DB Storage location is value of the 'Path' attribute under 'DBStorageLocation' tag in 'SGConfiguration.conf' file under the '<vembu networkbackup_home="">/conf' folder.

c) Run the following SQL Query to update Backup Location:

update PLUGINDUMPLOCATION set DUMPLOCATION='<new_dump_location>' where BACKUPCONFIGID IN (select BACKUPCONFIGID from BACKUPCONFIG where BACKUP_NAME='<backup_name>');

where, <new_dump_location &gt;="new dump location" <backup_name=""> = 'BackupName' of the backup schedule.

d) Quit the sqlite application using ".q" command

e) Start Vembu NetworkBackup Application.

You need to configure additional full backups for your plugin backup schedules by editing the backup schedule. You can do this by going to the page 'Backup -> List Backup Schedules -> <backup_name> -> Edit Backup configuration (Action for the particular backup schedule)' and enable 'Run additional full backup after saving this configuration'.

Hi,

You will get this error, if Vembu OnlineBackup doesn't have enough permission to access encrypted files. Please check whether you have installed Vembu OnlineBackup as an Application or Service. You can find the mode of installation by opening the following URL in the problematic machine localhost:4040/readme.html

If installed as Service, please follow the below steps:

Please check whether the logon account is "Local System Account", if it is 'Local System Account' then please change it to any administrator account. Please follow the below steps to change the logon account type.

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

2. Select the Vembu OnlineBackup service and then open its Properties dialog.

3. In the Vembu OnlineBackup services Properties dialog, go to the "Logon" tab if it is 'Local System Account' update the user logon to be of the power user or a user who has administrator privilege to run the Vembu OnlineBackup service.

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

5. Restart the Vembu OnlineBackup service.

If installed as an Application, please follow the below steps:

If Vembu OnlineBackup is installed as an application, then please make sure the current logon user account has enough privilege to access the encrypted files. Please access the files manually and check whether you are able to open the files. Either provide enough privilege to the current account or download the latest client build from your Vembu OnlineBackup login console and update the existing build as Windows Service. Please follow the below steps to do the same,

1. Download the Vembu OnlineBackup installer from Vembu OnlineBackup login console.
2. Run the installer.
3. During installation click "Advance" and choose "Install as Windows services" option and proceed the installation process.
4. Once the installation was completed, change the service logon user account to administrator account as mentioned earlier.

Hi Pcawley.

The error "Backup Request Failed for Backup [Files] to server. Failed while reconnecting - Error - no backup session available." if the client try to reconnect the backup server, but the session between the backup server and client has been expired.

During the backup process, if any socket drop happen client will try to reconnect the socket and backup server keep the backup session, so that once the client reconnect the backup server successfully the backup will resume uploading the data to the backup server. If the re-connection doesn't happen for 3 minutes the backup server will terminate the backup session and if the client reconnect the backup server successfully after 3 minutes then the backup will end up with the above error message.

To over come this case, please increase the re-connection time out values in both backup server and your client machine. Please follow the below steps to increase the time out value.

1. Stop Vembu BDR in your backup server and stop Vembu NetworkBackup in your client machine.
2. Edit 'SGConfiguration.conf' file from location '<vembu_home\conf>' in the text editor.
3. Change the attribute ServerReconnectTimeOut="600" from the <module> tag.
4. Change the attribute ClientReconnectTimeOut="600" from the <module> tag.
5. Save the file and start Vembu BDR in your backup server and Vembu NetworkBackup in your client machine.

Note: you need to change the re-connection time out values in both backup server and also in your client machine.

Hi Gowerg,

Regarding Image backups such as Disk Image, VMware and Hyper-V backups, we normally recommend to deploy VembuBDR backup server in local environment and so we are not providing seed backup feature for the image backups. However, if you want to keep another backup copy remotely, you can use our Vembu Offsite Copy feature by deploying Vembu OffsiteDR server on your offsite location. Seeding full backup data to Vembu OffsiteDR server from VembuBDR is already available in our road map, based on the current progress, we expect it to be available by end of June 2016 or early July.

Hi Mikkelwilk,

Vembu NetworkBackup doesn't allow to configure whole drive as a file backup which contain OS(by default C:\ Drive). Some files available in WINDOWS, System Volume Information, RECYCLER and pagefile.sys will be skipped, because they are in always in use and modified frequently, hence we grayed out C:\ in add file backup page.

Note: We always recommend to use VembuVM Backup to backup the entire drive as image backup, which has multiple recovery option and much faster than file backup.

Regarding your question how to avoid unwanted clients to connect the backup server. Please create firewall rules to avoid unwanted clients to connect the backup server. We are currently working on a feature called "Blocking clients" which helps to block certain client to connect the backup server and it will be available in any of our feature release.

Hi Andrew, Yes, to stop the Vembu NetworkBackup application, just kill SGTray.exe and VembuNetworkBackup.exe and to start the application,again run those exe.

Hi Andrew,

Yes, you can stop the Vembu NetworkBackup/Vembu VMBackup running in your/remote machine using your own script.

For Windows Vembu VMBackup:

To stop the Vembu VMBackup,

1. Stop SGTray.exe
2. Stop VembuVMBackup.exe

Those exe are available in Vembu VMBackup installation location by default "C:\Program Files\Vembu\VembuVMBackup\bin". The above two exe are responsible for running Vembu VMBackup. Please create a script to stop those exe in the order mention above.

For Windows Vembu NetworkBackup:

To stop the Vembu NetworkBackup,

1. Stop SGTray.exe
2. Stop VembuNetworkBackup.exe

Those exe are available in Vembu NetworkBackup installation location by default "C:\Program Files\Vembu\VembuNetworkBackup\bin". The above two exe are responsible for running Vembu NetworkBackup. Please create a script to stop those exe in the order mention above.

For Linux Vembu NetworkBackup:

To stop the Vembu NetworkBackup, please create a script to run the script file "stopVembuNetworkBackup.sh", it will stop the Vembu NetworkBackup running in your Linux machine. This script file will be available in Vembu NetworkBackup installation location by default "/home/vembunetworkbackup/Vembu/VembuNetworkBackup/stopVembuNetworkBackup.sh"

In addition to the above, if your client are have static IP, you can bundle that IP in our internal configuration files. So that the data transfer will can only if the client are running with that particular IP. If the client connect wifi with different IP than data transfer will not happen. Please follow the below steps to bundle the IP in our internal configuration files.

1. Stop the Vembu NetworkBackup/Vembu VMBackup running in your client machine.

2. Open '<installation location="">\conf\SGConfiguration.conf' file in any text editor, by default "C:\Program Files\Vembu\VembuNetworkBackup\conf\SGConfiguration.conf"

3. Search for the tag "IPAddress", by default that tag value will be empty. Enter the IP which you want to bind. Example IPAddress="198.168.104.234".

4. Save the SGConfiguration.conf file.

5. Start client agent.

Using the above steps you can bind the Vembu NetworkBackup/Vembu VMBackup client with particular IP, if the client assign to any other IP address, Vembu NetworkBackup/Vembu VMBackup client agent won't run.

Hi Ryno,

Current version of VembuBDR doesn't have this feature. We will try to add this in our road map based on the priority, we will try to incorporate this feature in the future releases of VembuBDR.

Hi Ryno,

Currently it is not possible to disable OffsiteDR process on client level. We already have this feature in our road map based on the feasibility, we will try to incorporate this feature in the future releases.

Regards, Mohamed Jameer S.

Hi Techs,

The error message "Server Deactivated" show that the trail period of your backup server has been over. Please register your backup server with your Vembu portal account. Please follow the below steps to register your backup server with Vembu portal.

1. Login to your backup server webconsole.
2. Go to menu "Management -> Server Registration" page.
3. Click "Register" box.
4. Enter your "Email address" and "Password", which was used for Vembu portal sign up.
5. If you doesn't have Vembu account, please click "Click here" and create new Vembu account and then register your backup server.

Note: Kindly add your credit card details in your Vembu portal account. The payment process will be carried out via credit card. Until you add the credit card details in your Vembu account, the backup server will be in de-active state.

1. After you registered your backup server and added the credit card details, please run license check option available in "Management -> Server Registration" page.

After doing the above steps the backup server will reactivate.

Thanks, Jameer.

Hi, There is no limitation in our trail version. FYI the password is case sensitive, please make sure you have enter the password with case sensitive. If you still facing the problem, please contact our support team (vembu-supportATvembuDOTcom) with screenshot of the error message. They will help you to resolve this issue.

Hi Ryno,

We have released the production Vembu NetworkBackup client build for Imac OS. You can download the client builds from here

@ryno, Thanks for pointing out the mistake. We have replaced the new document and you can refer the link ( https://www.vembu.com/wp-content/uploads/2016/01/VembuBDR-AutomaticSoftwareUpdate.pdf ). please make use of it.

Hi Dhoefer, Can you please update, are you able to telnet the ports 32004, 31005 and 31007 of your offsite client via Microsoft Direct Access?

Can you please update us whether you are using "SQL server Authentication" or "windows Authentication" to connect the SQL instance in "SQL Server Connection Properties".Also please check the below details and update us. 1) Vembu product name and Build Number details. 2) OS Details [32/64-bit architecture]. 3) MSSQL Server Version and its Details[32/64-bit]. The above details will help us to provide you a suitable details.

Hi James,

From the details you have updated, we believe that Vembu NetworkBackup doesn't have access to backup the encrypted files. To over come this permission problem, please change Vembu NetworkBackup logon account to any administrator account, who have the access to backup the encrypted files. 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 Vembu NetworkBackup service and then open its Properties dialog.

c) In the Vembu NetworkBackup services Properties dialog, go to the "Logon" tab if it is 'Local System Account' or any other user, update the user logon to be of the power user or a user who has administrator privilege (who has full permission to backup the encrypted file) to run the Vembu NetworkBackup service.

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

e) Restart the Vembu NetworkBackup service.

Hi J.seddon,

Thanks for your update. From the details you have update us, the backup was skipped due to insufficient permission. To over come this case, please change Vembu NetworkBackup logon account to any administrator account (who has enough permission to access all the files configured for the backup). 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 Vembu NetworkBackup service and then open its Properties dialog.

c) In the Vembu NetworkBackup services Properties dialog, go to the "Logon" tab if it is 'Local System Account' update the user logon to be of the power user or a user who has administrator privilege (who has enough permission to access all the files configured for the backup) to run the Vembu NetworkBackup service.

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

e) Restart the Vembu NetworkBackup service.

Note: Do the above changes in your client machine.

Hi J.seddon, You can get the reason for the skipped file from the file available in the following location on your client machine "<vembu networkbackup="" home="" folder="">\VembuNetworkBackup\report\backup\<backup name="">-<backup server="">-skipped.lst" by default "C:\Program Files\Vembu\VembuNetworkBackup\report\backup\<backup name="">-<backup server="">-skipped.lst". You can open this file using any text editor.

The backup was reported as partially, if one or more files was skipped during the backup. You can view the the reason for the files skip in backup server console as well as your client webconsole. To view from backup server console: Login to backup server console go to menu "Reports -> Historical reports -> choose client name and choose backup name -> expand the backup report by clicking '+' -> click "view" in skipped files count" here you can find the reason for skipped files. To view from client console: Login to client console, go to menu "Reports -> Backup Reports -> Backup name -> View in skipped files count" here you can find the reason for skipped files. To know more infromation about reason for the skipped, kindly update us the error message in skipped files report or update us the screen shot of the error.

Hi,

Please try the following steps to enable the NFS drive.

1. Stop the Vembu VMbackup service running in your backup server
2. Create the directory "toStartNFSServer" under "VembuVMBackup" in root location. You can use the command "sudo mkdir -p /VembuVMBackup/toStartNFSServer"
3. Restart the NFS services by running the command "sudo service nfs-kernel-server restart"
4. Start the Vembu VMbackup service in your backup server
5. Now try to enable NFS.

@aweber1nj we need to analyze your backup server environment, to check why the volume is not available in "Storage Management" and "Repository Management" page. Can you please contact our support team via our support mail ID vembu-support AT vembuDOTcom.

As per the design, the first 30 days will be the trial period and the portal will show server as in "Evaluation Mode". It is mandatory to add credit card details in your account on or before the 30 days of trail period. Since you are using only physical server, we will not do any charges, but as per the design you need to update the credit card detail in order to upgrade your account from trial account to registered one.