Free security audit tool! Click here

Our Customers include:

Dbvisit testimonials
Was it Einstein who once said "Things should be as complex as they need to be, but no more ..."?
I'm sure he would think that Dbvisit hit the mark! As the solution takes a complex problem and distills it down to reliable, cost effective, and easy to use product. It works as advertised, the manual is comprehensive/to the point, and the support is great!
If anyone is considering this product, give it a try, it sells itself.

Joe Lennert
Senior Software Developer
Alcatel-Lucent - USA
Dbvisit is exactly as advertised: a high-value, highly reliable, easy to install and easy to configure disaster recovery solution - at a fraction of the cost of using Oracle's disaster recovery solution.
We set up both onsite and offsite standby servers and pretty much forget about them.
Dbvisit just works.
Highly recommended.

Michael J. Muha, Ph.D.
Manager, Information Systems & Hosting
WorkForce Software - USA
Dbvisit is a wonderful cost saving Oracle disaster recovery solution for those companies with Standard Editions of Oracle. It was easy to install and I received above and beyond customer service. I definitely recommend Dbvisit.

Laura Quinlan
Sr. Oracle DBA
Neovera - USA

more


Get free Dbvisit trial.

Dbvisit Changes and new features

5.3.02 (16 August 2010)

New features:
  1. ASM support. The standby database can now be created in ASM as well, Oracle’s proprietary file system format. This completes the types of standby databases that can be created with Dbvisit.
  2. Templates. To make the disaster recovery process simpler, faster and more convenient for DBAs the Dbvisit standby database creation wizard now includes the option to create a template. This template stores all the information on how the standby database was created. When the standby database needs to be recreated, for example after a failover situation, this template can be used for fast and simple recreation.
  3. Transportable Media support. Some databases are too large to transfer across the network. Now the Dbvisit standby database creation process includes an option to interface with a local removable disk. This disk can then be manually transported to the remote site where the creation of the standby database can be restarted and completed.
  4. Ability to customize the standby pfile/spfile settings before creation of the standby database. These settings will be saved in the template for easy recreation of the standby database.
  5. Dbvisit installation, upgrades and creation of standby databases can now be scripted to run in batchmode for simple and efficient deployment.
  6. Rsync transfer method. DBAs now have the ability to use Rsync as the data transportation mechanism on Linux and Unix, facilitating efficient restarts when there are network issues or large file transfers.
  7. Oracle database parameters for the standby database can now be customized and saved in the template.
Fixes:
  1. Dbvisit now recognises special characters @(ORACLE_SID) and ?(ORACLE_HOME) in database files names.
  2. Improved algorithm of parsing of SQL commands output to detect errors.

5.2.30 (27 July 2010)

New features:
  1. Allow the use of other external non sendmail clients on Linux/Unix. Use MAILCFG_SENDMAIL_CLIENT to set the full path of the client.
  2. Update Dbvisit man pages.
Fixes:
  1. Correct default Oracle password file for Windows.
  2. In some cases, Oracle SID information was not obtained from registry in Windows 64bit.
  3. Improve error message when Oracle Windows service cannot be stopped or started.
  4. Improve locking mechnism on Windows. In some cases the pid lock file does not get removed after successfully running Dbvisit.
  5. Activation of standby database may not update the Dbvisit repository correctly. Initiating a Graceful Switchover after failover may result in error: ORA-00001: unique constraint (DBVISIT.DBV_TRANSFER_LOG_PK) violated This has been fixed.
  6. Change creation of tempfile from bytes to Mb. If the file is too big then error "ORA-02237: invalid file size" may result. This has been fixed.
  7. If SOURCE or DESTINATION host names are set to long names, then Dbvisit does not use the correct starting sequence after graceful switchover.

5.2.29 - Development release

5.2.28 (18 June 2010)

New features:
  1. Allow for Data Guard configurations to co-exists with Dbvisit.
    - Allow for VALID_FOR parameter.
    - Ignore standby redo log files in controlfile creation.
Fixes:
  1. Remove a prompt for pfile name if PFILE is not found on the server during creation of standby database.
  2. Set SOURCE and DESTINATION variables to short server names.
  3. Change variables _SEQUENCE_LANG_NAME and _ASM_EXCLUDE to quoted strings instead of lists.
  4. Change the query to obtain archive log names to ignore log archive destinations pointing to standby locations (used by Data Guard).
  5. Oracle 8i may contain incorrect location in v$archive_dest - Fixed.
  6. Does not use the correct SQL statement to obtain the standby database sequence for Oracle 8 and 9 - Fixed.
  7. Ignore dynamic memory location parameters and parameters related to other instances in spfile/pfile when creating standby database.
  8. When LOGDIR_DR is not set correctly there was an error message about incorrect mail settings - Fixed.

5.2.27 - Development release

5.2.26 (4 May 2010)

New features:
  1. SOURCE and DESTINATION host name variables are now not case sensitive for Windows.
  2. Display a message "please wait" to the user to indicate that Dbvisit may take some time to delete old archive files when running AMM (Archive Management Module) on the primary server.
  3. Improve the ability to obtain the standby database sequence when the standby database sequence is 1.
  4. Add message to SUCCESSMAIL emails on how to turn off success mails and only email on alerts.
  5. Add option to use existing pfile/spfile on standby database during standby database creation.
Fixes:
  1. Capture more information when another instance of Dbvisit is running on Windows to ensure it can be started or not.
  2. During creation of standby database on Windows, Dbvisit may error when COMPRESS variable is set to ssh in a DDC file - Fixed
  3. Dbvisit may error with the primary and the standby databases having redo logs with the same names under different logfile group numbers during Graceful Switchover - Fixed
  4. In rare cases Dbvisit may error when trying to clean up trace files if a file has already been deleted by another dbvisit process running at the same time - Fixed.
  5. When the user renames oracle init parameters while creating standby database, Dbvisit edits both standby pfile and spfile. If the standby database uses spfile, only spfile should be edited not pfile - Fixed.
  6. Dbvisit does not capture ORA-12638 error message - Fixed.
  7. Make the global variable PFILE non case sensitive for Windows while creating a standby database
  8. While checking oracle database parameters pointing to ASM locations on primary when creating a standby database, dbvisit considers all parameters values that contain symbol + to be ASM locations which is not always the case - Fixed
  9. In some cases fuser incorrectly reports file in use on HP-UX.
  10. Remove REMOTE_LISTENER parameter from init.ora when creating standby database.

5.2.25 - Development release

5.2.24 (22 March 2010)

New features:
  1. If SUCCESS_MAILTO is set, then the Dbvisit daily heartbeat emails go to this email address instead of ADMINS.
Fixes:
  1. Dbvisit does not pick up the correct pfile to transfer to the remote server while creating standby database when the primary database does not use an spfile.

5.2.23 - Development release

5.2.22 (12 March 2010)

New features:
  1. Dbvisit now allows the Oracle admin directories on standby to be different from the primary database during creation of the Standby Database.
Fixes:
  1. Dbvisit does not pick up the correct sequence for RAC on the standby when NLS is set to Spanish.
  2. Fix issue with quotes around multiple email addresses: can't extract address at ..
  3. Improve obtaining asmcmd version for Windows.
  4. Dbvisit does not pick up the archive log destination when NLS is set to Spanish during graceful switchover.
  5. Create standby database may fail in Oracle 8i due to long tablespace names. This has been fixed.
  6. Update check and add more tracing to determine if previous Dbvisit process is still running.
  7. Update dbvisit help text.
  8. If Dbvisit is unable to create Windows Oracle service during creation of standby database, Dbvisit will suggest to create the service manually.
  9. Ignore the following SQLPLUS error message when creating Dbvisit repository using dbvisit_setup:
    Error accessing PRODUCT_USER_PROFILE
    Warning: Product user profile information not loaded!
    You may need to run PUPBLD.SQL as SYSTEM
  10. Dbvisit will detect if ORACLE_HOME_DR is set to a non-existing or not valid directory on the standby server when creating a standby database and display a warning.
  11. Dbvisit may not correctly detect the creation of Oracle Windows service in other languages during creation of standby database. This has been fixed.
5.2.21 - Development release

5.2.20 (11 January 2009)

New features:

  1. Add ENCRYPT_PASSWDS variable to specify if all passwords should be stored encrypted in the DDC file or not. To change the setting run dbvisit_setup and choose option 6.
  2. Add SWITCHOVER_WAIT_IN_SEC to control how long Dbvisit waits between each checkpoint iteration for graceful switchover. Total time Dbvisit waits for each checkpoint is set by SWITCHOVER_TIMEOUT_IN_SEC.
Fixes:
  1. When standby redo logs are using OMF, graceful switchover may fail. This has been fixed.
  2. When log_archive_format on Windows contains %S, the sequence number can be truncated by Oracle. Ensure that Dbvisit also truncates the number the same way.
  3. Running dbvisit_setup: Update Dbvisit Database configuration (DDC) file may error for older DDC files.
  4. Improve error message for ORA-27048.
  5. Improve error message for creation of standby when datafile contains spaces.
  6. Improve message for error 5005 when standby controlfile does not contain the archive log sequence.
5.2.19 - Development release

5.2.18 (24 November 2009)

New features:

  1. Allow for multiple archive log destinations in AMM (Archive Management Module) processing (AMM_PROCESS_MULTIPLE_ARCH_DEST).
  2. Improve restartability of standby database creation. Standby Database is now shutdown after all the standby database parameters are obtained.
  3. Graceful switchover synchronisation process now includes retries if there are network issues.
  4. Improve remote checksum processing. If remote checksum process fails, then only checksum process is repeated, not the whole transfer process.
  5. Allow for decimal numbers for DAYS_TO_KEEP_ARCHSOURCE and DAYS_TO_KEEP_ARCHDEST. For example 3.5 days.
  6. Detect Oracle XE admin location for Linux.
  7. Check for Standby archive log destination during graceful switchover. If location does not exist, then exit as switchover will not be successful.
  8. Reduce number of trace file that Dbvisit keeps on server: NUM_TRACE_TO_KEEP = 100, DAYS_TO_KEEP_TRACE = 10
  9. Check that Database is in archivelog mode.
  10. Allow for Database which has been recovered with point-in-time recovery with resetlogs where SCN may be lower than current SCN.
  11. Allow for "-" in the DDC file. Example: dbv_prod-vm2.env
Fixes:
  1. Improve duplicate archive log handling for OMF files. Include a unique identifier to ensure the same file does not get renamed more than once.
  2. Add check for ORA-00342: archived log does not have expected resetlogs SCN.
  3. If same archive log is needed more than once by standby database for non RAC, ensure archive log can be compressed.
  4. Allow for multiple NLS_LANGUAGE setting during RAC processing.
  5. Add 24hour time clock to trace file.
  6. Fixed calling AMM from dbv_functions -A
  7. Improve error message in Windows if during standby database creation the standby database fails to start.
  8. Fixed issue if first_change# is displayed as float, then graceful switchover was not successful.
  9. Allow for different instance_name to database_name for graceful switchover.
  10. Notify if create standby database process is not able to remove file on standby database.
  11. Allow for %d log_archive_format.
  12. Check and report if "ORA-00332: archived log is too small" is found.
5.2.17 - Development release

5.2.16 (18 September 2009)

New features:

  1. Graceful Switchover for ASM and RAC. RAC database will become a single instance database during switchover. After switchover database can be converted to a RAC database again.
    Note: The Oracle ASM instance needs to be version 11gR1 or higher. The Oracle database itself can be Oracle 10g or higher.
  2. Upgrade Bitvise WinSSHD to 4.28 and Tunnelier to 4.29 for Windows only.
  3. Improve error message when standby fails to start during standby database creation.
  4. Add message to remove old archives when activating standby database.
  5. Add smtp authentication and other advanced Mail settings.
    See MAILCFG_AUTH_USE and MAILCFG_AUTH_PASSWD settings.
  6. Attach trace files to email when Dbvisit errors to forward to Dbvisit support. Set filesize limit of 768000 bytes for attachments.
  7. Database files are tested for correct location during creation of standby database. If not correct then user is asked to rename them.
  8. Standby redo log names are tested for correct location during graceful switchover.
  9. Add variable SEND_MAIL_FLAG_DR to turn off mailing from standby server.
  10. Add ability to manually email trace files as attachments with option:
    dbv_functions -m tracefilename
Fixes:
  1. Check if Oracle database admin directories exists before creating the standby database.
  2. Fixed Dbvisit repository create error in Oracle 8i.
  3. Add check for ORA-00344: unable to re-create online log when activating standby database.

5.2.15 (20 July 2009)

Fixes:

  1. Create standby database fix. If the size of the tablespace is displayed as a float instead of number, then the insert into the Dbvisit repository fails. This has been fixed.
  2. Improve error message when controlfile is a backup controlfile.
  3. If the word export is used too many times in the DDC file, then assumes the DDC file is from Dbvisit version 3. This has been fixed.
  4. Improve message when standby database has insufficient SGA size.

5.2.14 (12 June 2009)

New features:

  1. Provide the ability to logon with sys user and password. This can be used when sysdba logon without password cannot be used or when SQLNET.AUTHENTICATION_SERVICES= (NTS) cannot be set.
  2. Improve message for error 837, sqlplus not found.
  3. Improve message for ORA-01031: insufficient privileges.

5.2.13 (3 May 2009)

Fixes:

  1. Fix issue with removing trace files on standby server. If the ORACLE_SID on the standby is different to the ORACLE_SID on primary primary server then trace files were not removed. This is now fixed.
  2. Graceful Switchover may fail in Oracle 9i with error: ORA-00271: there are no logs that need archiving. This has been fixed.

5.2.12 (21 April 2009)

New features:

  1. Provide improved feedback when PATH setting is not correct for Windows.
Fixes:
  1. Include 5.2 User Manual for Windows Installer.

5.2.11 (6 April 2009) (pre-release)

New features:

  1. Automatically creates standby database from primary database. Standby database can be created from normal file system database, or from ASM or RAC databases. To create standby database run dbvisit_setup and choose option 7.
  2. Automatically run command dbv_oraStartStop update_ddc_file after activation of standby database to automatically reverse Dbvisit settings to enable instant reversing of the Dbvisit process (after standby database is rebuild).

5.1.28 (6 April 2009)

Fixes:

  1. Add specific SP2-0734 error.
  2. Ignore set pause on setting in login.sql.

5.1.27 (20 March 2009)

New features:

  1. Add variable SEND_HEARTBEAT_DR to allow to turn off heartbeat separately for standby server. SEND_HEARTBEAT is used for the primary server.
  2. Display message to add tempfile(s) to database when open in READ ONLY mode and after activation of standby database.
Fixes:
  1. Dbvisit fails to obtain ASM archive log when ASM flash recovery is used.
  2. Change default srvctl.exe to srvctl.bat for Windows Rac.
  3. Allow for German language feedback in Oracle RAC.
  4. Graceful switchover, in some cases the new primary database does not require recovery although the Oracle feedback specifies that it does stopping graceful switchover processing. This has been fixed.

5.1.26 (8 December 2008)

New features:

  1. Add a workaround for Oracle bug "Create Control File fails with ORA-600 [kccscf_1]" during graceful switchover. See metalink: 387210.1
  2. Added SUCCESS_MAILTO, to be able to separate the success emails from the failure emails. If this is set to an email address, then all successful Dbvisit emails will be sent to this email address. Failure or unsuccessful emails will be to the email address specified by ADMINS.
  3. Added variables:
    MAILSUBJECT_PREFIX_LOG_GAP_REPORT
    MAILSUBJECT_PREFIX_SUCCESSFUL
    MAILSUBJECT_PREFIX_HEARTBEAT
    These variables can be used to set a prefix for the email subject line. This can then be used to set filtering rules for emails.
Fixes:
  1. Correctly identify the log file when using ASM and the archive is no longer available through v$archive_log.
  2. Fix undefined subroutine message in dbv_functions.
  3. For Oracle 8i only: Create controlfile may fail under Graceful Switchover.

5.1.25 (1 September 2008)

New features:

  1. Add dbv_function -Q to replace current standby controfiles on standby database with new standby controlfile from primary database.
  2. Add graceful switchover check to ensure redo log numbers are the same between primary and standby databases.
  3. Add variable ALERT_IF_STDBY_READ_ONLY. This determines whether to alert or not if Dbvisit is run on the standby server and standby database is in READ ONLY mode.

Fixes:

  1. Allow for Oracle feedback in German to be interpreted correctly.
  2. Correctly interpret ORA-01115 error (IO error reading block from file).
  3. Fix for RAC TAKEOVER_SID, destination host not correctly obtained in some circumstances.
  4. Fix for graceful switchover when data files are in ASM but redo files are not. Dbvisit would incorrectly error that redo files are in ASM.

5.1.24 (28 July 2008)

New features:

  1. Add variable APPLY_DELAY_LAG_MINUTES. This creates a time delay between the archiving of a redo log at the primary database and the application of the archive log on the standby database. Note that the archive logs are still transferred to the standby server as normal without delay.
  2. Add variabiable TRANSFER_LOG_GAP_THRESHOLD to report on the difference between the last archived sequence on the primary and the last sequence transferred to the standby server.
  3. Add variables AMM_START_AFTER_EACH_APPLY and AMM_START_AFTER_EACH_TRANSFER Normally the Archive Management Module (AMM) to manage the archive log files is started at the end of Dbvisit processing. These variables allows the AMM module to be started during Dbvisit processing. This may be necessary due to space restrictions. Use with caution! Archives may be deleted before being applied.
  4. Add variable AMM_PERC_FULL_WAIT_MILLISEC. This is used in the Archive Management Module (AMM) to ensure that the percentage full disk space displays the correct value. For some volume managers it takes a little time to display the correct status after files have been removed. This variables ensures there is some delay before Dbvisit calculates the free space again. Default is 250 milliseconds.
  5. Add variable AUTO_START_STANDBY_DB. Automatically start the standby database if standby database is down and dbvisit -i or dbvisit -R command is given on the primary server. These Dbvisit commands require the standby database to be up.

Fixes:

  1. Add autoextend settings to creation of OMF tempfile.
  2. Fix upgrade issue from version 4.0. to 5.1.
  3. Fix add datafile issue for Oracle 8 and 9 introduced in 5.1.23.

5.1.23 (19 June 2008)

New features:

  1. Add new database connection mode which is determined by variables DB_CONNECTION_MODE and DB_CONNECTION_MODE_DR. The database connection modes are:
    Dedicated: By default Dbvisit connects with the dedicated connection mode. The dedicated connection mode initiates a database connection each time information is requested from the database. The connection is closed after each request.
    Shared: A database connection is opened once at the start of Dbvisit. This connection is used (shared) for all information requested from the database. At the end of Dbvisit processing, the connection is closed.
  2. Added option LOGGING_LEVEL=important to limit the messages being logged to the Dbvisit log file (dbvisit.hist).
  3. Improved the feedback when Dbvisit cannot find the correct archive log file to transfer.
  4. Specify that dbv_oraStartStop update_ddc_file command should be run after activate standby database command.

Fixes:

  1. Fix issue during Graceful Switchover if an OMF tempfile is used. The tempfile is no longer created with storage information.
  2. In rare cases, Dbvisit may wait indefinitely on a archive log file that is in use. This has been fixed.
  3. Ensure dbv_functions -N option to display transfer table works correctly when using multiple databases.
  4. AMM threshold processing does not stop after reaching specified threshold percentage. This has been fixed. Note that Dbvisit will always ensure the archive has transferred before deleting.

5.1.22 (Internal release)

New features:

  1. Add CHECKPOINT option of Ignore. This disables checkpoint processing completely and will not force the generation of a new archive log file.
  2. Add new method to obtain filesystem disk space information for Unix and Linux. The external df command is not longer required. This is only used in the Dbvisit archive log management module (AMM).

Fixes:

  1. Improved error message for error 460 if no archive log file is found on server.

5.1.21 (3 April 2008)

New features:

  1. Improve error message when an incorrect tablespace is chosen during installation.
  2. Do not error when Oracle gives warning message: "Error accessing PRODUCT_USER_PROFILE", unless ALERT_ON_WARNING = Yes. Default is ALERT_ON_WARNING = No.
  3. Dbvisit log files (dbvisit.hist and arch_management.log) are now managed according to LOG_FILE_ROTATE_MAX and LOG_FILE_SIZE_MAX_MB settings.
  4. Use SHA-1 digest algorithm as default for checksum calculation.

Fixes:

  1. Correctly interpret ORA-01122 error.
  2. Fix message: undefined call to apa_add_datafile.
  3. Fix graceful switchover issue when ORACLE_SID on the standby database is different to ORACLE_SID on the primary server.
  4. Fix applying one log file at a time for RAC standby database.

5.1.20 (19 February 2008)

New features:

  1. Allow for a standby database control file which was not created at the same time as the standby database.
  2. Allow for an alternative internal method to find the last archived log.
  3. Allow for tracing of Bitvise sftpc and sexec software (Windows Only).
  4. Improve performance of internal checksum routine.
  5. Allow for external checksum utility for Windows.
  6. Add option to dbvisit_setup to check for repository version.
  7. Enable the use of RESYNCH_SEQ_OFFSET = 0
  8. Add setting MAILCFG_SMTP_SERVER_DR to allow for different smtp server for standby server.

Fixes:

  1. dbvisit_setup does not write or update DDC file if option "No review of all variables" is chosen. This is now fixed.
  2. Alert if temp directory does not exist.
  3. Improved error message if ORACLE_HOME is not found on standby server.
  4. Windows 2000 fix for executing Bitvise sftpc copy function.
  5. Fix date stamp in email headers when using internal Dbvisit mail. Date was one day behind server date.
  6. Activate standby database command in batch mode does not activate the standby database, but opens the standby database in READ ONLY mode. The activate command in interactive mode does work. This has been fixed.
  7. Database tempfile does not get applied to the new primary database during switchover in some cases. This has been fixed.
  8. If temp directory contains spaces then graceful switchover will stop (Windows only). This has been fixed.
  9. Resolve core dump issue on AIX.

5.1.19 (15 January 2008)

New features:

  1. Automatic trace file management. Trace files will be deleted according to new Dbvisit Database Configuration (DDC) settings NUM_TRACE_TO_KEEP and DAYS_TO_KEEP_TRACE. Default settings are: NUM_TRACE_TO_KEEP=200 and DAYS_TO_KEEP_TRACE=15 Least restrictive setting applies between DAYS_TO_KEEP_TRACE and NUM_TRACE_TO_KEEP. To turn off, set to 0.
  2. Graceful switchover - If standby database redo log name format is in OMF format and primary database is non OMF format, then use primary database name redo format.
  3. AMM processing now ignores the following directories: lost+found,onlinelog,backupset,autobackup,backuppiece,flashbacklog, imagecopy,controlfile,datafile.
  4. Added variable INITIATE_DBVISIT_ON_STANDBY. Default = No. Setting this to Yes will initiate Dbvisit on the standby server as the last step of running Dbvisit on the primary server. Setting this to Yes, will mean Dbvisit should no longer be scheduled on the standby server (as it is now initiated from the primary server). Dbvisit will no longer function as two independent processes with independent alerting and a new strategy must be in place to ensure that notification is received in case of a failure. It is therefore recommended to set ARCHIVE_LOG_GAP_THRESHOLD and to schedule the Dbvisit archive log gap report (dbvisit -i) on the primary to alert if the standby database gets too far behind the primary database.
  5. Added variable ARCHIVE_LOG_GAP_THRESHOLD. Default = 0. Dbvisit will alert if the archive log gap from the Dbvisit archive log gap report (dbvisit -i) exceeds this value (ARCHIVE_LOG_GAP_THRESHOLD). To turn off alerting, set ARCHIVE_LOG_GAP_THRESHOLD to 0.
  6. Added variable SEND_LOG_GAP_WITH_HEARTBEAT. Default = No. Determines if the Dbvisit archive log gap report will be included in the daily heartbeat email.
  7. Unix/Linux only. Add initial network setup test. If remote shell method, or network is not configured correctly, Dbvisit will provide more detailed error message.

Fixes:

  1. Graceful Switchover processing fix with more than 9 redo log groups. Controlfile was not created correctly.
  2. Allow for ORACLE_SID length > 9 characters.
  3. For some terminal types the enter key had to be pressed before Dbvisit displayed more license information when updating the license.
All brand names and trademarks are the property of their respective owners.
Specifications are subject to change without notice.

Copyright 2000-2010 Avisit Solutions Limited

About us | Blog | Partners | Contact us | Oracle RAC | Graceful Switchover
Reporting Database | Multiple Standby Databases | Manage Archive Logs | DataGuard
Documentation | Forum | Pricing | Support | Dbvice | Video tutorials
Dbvisit Next Steps
Free trial - Download Now
Why Disaster Recovery?
Order Now
Contact Us
Highlights
Dbvisit Intro Video (3 min)
Dbvisit datasheet/White papers
Dbvisit tutorial videos
Dbvisit screenshot tour
Dbvisit vs Data Guard
Specifications
Dbvisit Support