NovaStor FAQs

You can NOT back up/restore Windows using the file backup (tab "Backup") without additional procedures. The file backup method does not include any boot information of a Windows installation! Therefore, please remove the Windows system and program directories from the file backup:

C:\ProgramDataC:\Program FilesC:\Program Files (x86)C:\Windows

Please also remove these files from the backup (if exist on C:):C:\bootmgrC:\BOOTNXT

This saves space on the target disk and also time during the file backup.

To back up the system itself (i.e. the Windows installation), use Image Backup (Start Screen => Image Backup = DR) to create an image of the drive containing the Windows installation. The user data on other drives or partitions can then be backed up using the "Backup" tab.

More information about Image Backup (DR) can be found in the NovaBACKUP manual and on the NovaStor Support website.

The Error fffffffe : Backup Failed error in your backup logs means one of the following:

the drive ran out of space during your backup

the connection was lost to the USB hard drive device (i.e. USB Sleep settings)

or the filesystem rejected a packet sent to the drive (MBR vs GPT)

the connection was lost to the Network Storage location

Contents

Available Free Space

Keep 15% Free Space available on your Storage Device

GPT Requirement

Connection lost (USB Sleep or hub)

Prevent Windows from Turning Off USB Devices

NIC (Network Interface Controller) Sleep settings

Network Attached Storage Power Settings

Available Free Space

You need enough space available on the destination storage device to store the uncompressed version of your backups, as compression cannot be predicted, plus some space to transfer the data to it.

If there are any files inside of the Recycle Bin that are on this drive, from any machine deleting files for example, they will count towards the actual available space that is not reported to the user by Windows. Windows removes these files from the properties when viewing the contents, but when software requests to write data to a drive, and files are inside the Recycle Bin on the destination drive, the available space is actually the displayed space minus the size of files in the Recycle Bin.

From Remo Software

...external hard drives do have a recycle bin. You may not have seen it because it is hidden by default. To view the recycle bin on the hard drive, follow the instructions below.

Go to Start and select Control Panel

Then select Folder Options

In the View tab, click on Show hidden files and folders

Remove tick mark against Hide protected operating system files

Now you should be able to see the Recycle bin and access its contents. You can also delete them here if you wish.

Keep 15% Free Space available on your Storage Device

If your drive runs out of space while a backup is being performed, the backup file that was in progress will be corrupted, and will not be able to be imported into the software to recover data from in the future.

GPT Requirement

NovaBACKUP supports drives that are 2TB or larger in size, but those drives must be converted to GPT (GUID partition table) partitions as Windows has a limit of 2TB partition using MBR (Master Boot Record).

This requirement typically has a greater impact on Image based backups as opposed to File based backups, which means that your non-Image based backups may have been working fine without the GPT setting in place on the destination storage device.

NOTE: Image Backup requires GPT (GUID) partition style to work effectively if utilizing a 2TB or larger hard drive as the destination storage device for your images.

Here is the link to the Knowledge Base article to check and set your hard drive to GPT instead of MBR: GPT Requirement Guide.

Connection lost (USB Sleep or hub)

Here is the text from our Knowledge Base article titled " Disable USB sleep settings (to correct backup device issues) "

WARNING:DO NOT USE A USB HUB, CONNECT THE USB DRIVE DIRECTLY TO A USB PORT ON THE PC. NovaBACKUP does not support connecting a USB hard drive through a USB hub. This will cause backup errors to occur and most likely will cause the backup job to stop mid-way through.

If you seem to have trouble with USB external hard drive disconnecting or going to sleep prior to, during or after a backup follow this guide to disable various Windows sleep settings that might be enabled and causing interruption:

It may be that your USB destination storage device is going to sleep at some point either during the backup job or after. Make sure that Sleep mode is turned off for the USB port devices in "Control Panel ->Device Manager -> Universal Serial Bus controllers" area. Click on each device under that section and check if there is a Power Management tab that exists in each device and if it does, then in each case, uncheck the "Allow the computer to turn off this device.." property in each case and click OK to save that change.

Next in the Windows Power Options (Power Management) area, "Control Panel -> Power Options" click on Advanced to go to the Advanced Power Management options, you may have to click on "Change plan settings" on the plan that you are using and then after that click "Change advanced power settings". Locate the "USB settings" section and then expand that section. Disable the "USB selective suspend setting" to set it to "Disabled" instead of the default which is "Enabled". Now locate the "Hard disk" section and disable the "Turn off hard disk after" setting so that it is set to "0" which is disabled. Now locate the "Sleep" section and disable all of the Sleep settings here to set them all to disabled for testing purposes.

Prevent Windows from Turning Off USB Devices

To prevent Windows from managing power to your USB controller or devices, follow these steps:

Open Device Manager by typingdevice managerin theStart>Searchpanel.

The Device Manager window will open. Expand theUniversal Serial Bus controllersbranch, then double-click theUSB Root Hub device, and choose thePower Managementtab.

Turn off theAllow the computer to turn off this device to save powerbyuncheckingthe box then click the OK button:

Repeat the step on each USB root hub or do it only for USB ports that you want to be permanently powered on. If you experience lost USB connections or power from a USB port to your auxiliary device, try the steps above then idle the device and wait for a few minutes to confirm that the problem has gone away.

Screenshot instructions from helpdeskgeek.com/how-to

NIC (Network Interface Controller) Sleep settings

Here is the text from our Knowledge Base article titled " Disable Network Interface Card (NIC) sleep settings (to correct backup device issues) "

If you seem to have trouble with NETWORK connected NAS (Network Attached Storage), SAN or network share going to sleep prior to, during or after a backup follow this guide to disable various Windows sleep settings that might be enabled and causing interruption with communicating to the network based storage destination device:

It may be that your NETWORK based destination storage device is going to sleep at some point either during the backup job or after. Make sure that Sleep mode is turned off for the primary, LAN based (Local Area Network), Network Interface Card (NIC) devicein the Control Panel -> Device Manager-> "Network adapters" area. Double-click on the Network Interface Card (NIC/Network Adapter) device that your computer utilizes for communication to the network share/NAS/SAN, I.E. your primary network adapter, and in the "Power Management" tab shown after double-clicking the adapter in the list, un-check the "Allow the computer to turn off this device.." property in each case and click OK to save that change. Repeat this process for your other Physical Network Interface Cards listed in the "Network adapters" area that could be utilized. If you only use a single Network Adapter on the computer in question, where NovaBACKUP software is installed on, for your network then you only need to turn off the Power Management feature for the one adapter that you utilize for network communications on your LAN.

Then in Windows Power Options (Power Management) area and click on Advanced to go to the Advanced Power Management options, you may have to click on "Change plan settings" on the plan that you are using and then after that click "Change advanced power settings". Locate the "Hard disk" section and disable the "Turn off hard disk after" setting so that it is set to "0" which is disabled. Now locate the "Sleep" section and disable all of the Sleep settings here to set them all to disabled for testing purposes. Locate the "PCI Express -> Link State Power Management" section and change the setting here to "Off". Save the changes by clicking "OK" button, if prompted save the changes and exit out of the Power Options area.

Network Attached Storage Power Settings

If your destination storage device is a NAS (Network Attached Storage) or SAN you may need to disable power management and sleep setting on that actual device's administrative management settings area. This settings area is usually a web based interface, check to see if Power Management / Sleep is enabled and disable it and save that change. Also make sure to update the Firmware utilized by the NAS or SAN as it will need to have the latest firmware installed and would be a first step in diagnosing an issue with your NAS for instance if we find that it is having trouble we would want to have the firmware updated to proceed with troubleshooting. The firmware is update-able from the NAS's administrative web based interface.

NovaBACKUP PC/Server/BE v18.x and newer

In general, you can use a simple boot medium for all systems. The simple boot medium contains many generic drivers, but drivers for newer hardware may be missing or the generic drivers may not work properly with the existing hardware. To avoid this, we recommend to use an extended boot medium when image backups/restores fail. Always include the following drivers for a system in an extended boot medium:

-SATA/RAID driver- Chipset- LAN- USB(2+3)- possibly graphics card (for laptops with high res)

Download the drivers from the manufacturer's website. The boot medium is based on Windows PE 10 (2018-06-01, NovaBACKUP v19.1.xxxx and newer). You need the appropriate drivers for Windows 10 or Server 2012 generation or newer. If drivers are no longer available for your system, try using Windows 8.x or earlier generation drivers. Extract the zip archives into own directories. Include the drivers in an extended boot medium, see description in the NovaBACKUP manual:

http://novabackup.novastor.de/support/data-backup-guides-manuals/

Some manufacturers deliver the drivers as exe files. In some cases these files can also be unpacked by a zip packer, other exe files offer additional options to unpack into a directory and not install immediately. Please read the instructions of the respective manufacturer (e.g. readme files).

As of version 19.2.1001, drivers can also be integrated after booting. In the interface of the Image Backup there is a tab "Driver". You can then select the drivers via a USB stick. This assumes, however, that the USB ports are recognized by the boot medium. It can happen that the simple boot medium does not recognize the USB ports and therefore no USB stick can be used. Therefore, even with the new version, an extended boot medium with beforehand integrated suitable hardware drivers is more advantageous.

AMo

There is currently nothing a customer needs to do to transfer a license key from one machine to another except to make sure the key is no longer in use at the original location.

The best way to ensure the key is no longer is use is to uninstall the software on the first machine before installing it on the new machine and activating your license key.

All NovaStor products come with free evaluation periods lasting at least two weeks, and are complete versions of the software for that time, to allow you a seamless transfer period.

If you are concerned that a previous machine shows up on your lifetime activations on the NovaCare status page, fear not!

Only concurrent activations will count towards your license limit, and the displayed number is the number of unique hardware keys have been activated by your license key.

Again, all a customer needs to do is stop using their license key on the original machine and activate it on the new one.

Current NovaBACKUP Version: 19.4.1119

NOTE: Use the "Check for Updates" button in the Help menu of the software to find the latest version available. It can take about a week for you to be able to obtain the current version after it has been announced, using "Check for Updates" in the software.

Download NovaBACKUP PC/Server/Business Essentials Here

Download NovaBACKUP CMon (Central Monitoring Console) Here

CMon is only compatible with NovaBACKUP v18.0 and above.

CMon is intended to be installed on Windows Server Operating Systems

Issues Installing NovaBACKUP? Start Here: Installation ends prematurely on client install

NovaBACKUP Granular Restore: 21.0.1.54276

You are required to register for the tool via the Help -> On The Web -> Granular Restore for MS SQL and Exchange menu entry inside your activated NovaBACKUP Business Essentials program.

Changelog

Please see the following for an at-a-glance overview of what was added or removed from the software:

NovaBACKUP Major Version Highlights

Jump to a Release

Current NovaBACKUP Version / Changelog

Version 19.x

19.4.1119

19.4.923

19.3.408

19.2.1001

19.1.1423

19.0.712

Version 18.x

Unsupported NovaBACKUP Version / Changelog Archive

Version 17.x

Version 16.x

Version 15.x

Other Notes

Version 19.x

19.4.1119

Release Date: 21NOV2019

Fixed Bugs

Fixed an issue where the cloud/xSP device can misread the computer/domain name and cause a full backup

Fixed displaying the Size and Free fields for xSP/Cloud devices in the Available Devices list in the Devices tab

Fixed displaying the storage gauge in the status bar

Fixed refreshing the Available Devices list in the Devices tab and storage gauge in the status bar when a cloud/xsp device is added and removed

<top>

19.4.923

Release Date: 24SEP2019

Fixed Bugs

Fixed backup client progress bar not updating.

<top>

19.4.916

Release Date: 20SEP2019

General features and fixes:

Added support for Windows 10 August 2019 and September 2019 Cumulative updates.

Fixed issue with scheduled jobs that failed to not run again until they were modified.

Fixed issue if no medium is inserted into LTO tape drive, NovaBACKUP client would wait forever.

Fixed issue when utilizing environment variables in the backup job/script.

Fixed issue with Custom Commands impersonation levels (Run As).

Fixed NovaBACKUP GUI crashes after installing July 2019 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4507460).

Install August 2019 CU for Server 2016 to fix this. Read here.

Fixed Tab order is wrong when configuring Email notification/reports in the backup client.

Removed Windows XP & Windows Server 2003 specific code and support.

We removed old code in the engine to take advantage of newer libraries, allowing for a smaller footprint and more reliability.

LogCollector related features and fixtures

New feature to collect logs for support tickets integrated in to the backup client in Help > Run Log Collector.

Added support in LogCollector Utility to request from WMI a list of Installed Programs.

Fixed issues with LogCollector Utility copyingProgramData\..\..\Temp\files. It only copies .log files now.

Image backup related features and fixes:

Fixed issue retention does not delete differential Image Backup files.

Fixed issue VHD and VHDX created by Image Backup does not boot.

Fixed issue where a Scheduled Image Backup fails to start if nsService is running as a user account.

Fixed issue where the progress bar in the Support tab during image backup shows no progress or flashes.

Fixed issue where Image Backup creates a temp file named "Temp131975668423224168" in root dir C: and backup destination device; the file could only be deleted after reboot. It no longer creates this file.

CMon related features and fixes:

New feature to query the Application Update Server to check for updates to CMon.

New feature to be able to send a welcome email to a newly created CMon user.

Added the ability for CMon admin to generate a report for all CMon users via "Export to CSV" button.

Added the ability for a CMon user to generate a report for their cloud storage accounts

Added a global option to disable CMon user registration.

Added feature to allow an admin to change the Storage Server Group when adding a new user.

Added feature to allow a CMon user to change the restorable window, number of computers, and quota settings for their cloud storage accounts.

Added feature to create a unique Storage Server group for each CMon user.

Added more remote manager like functionality to support MSP's that want to manage cloud accounts.

Fixed issue with intermittent errors adding Cloud Storage device through the Cloud button.

Fixed deleting a Cloud Storage account throws an error and doesn't delete the Cloud Storage Account.

Fixed HTTP Error 400. The request URL is invalid error when a license key is appended with a new line character.

Fixed issue with registered user goes to not enabled when it should stay as enabled.

Fixed issue ManagementServer.Service.ScheduledTask.exe taking excessive CPU time.

Cloud (xSP) related features and fixes:

Added "undelete" feature to backup server storage restore utility.

Added optimizations to the code for Cloud (xSP) Storage Server device, to improve performance and stability.

Fixed issue with local Cloud (xSP) device restore does not allow for restoration of different versions, only latest version is restored.

Fixed issue with Cloud (xSP) local data restore, when changing the device configuration to restore from local storage instead of the Storage Server for Cloud (xSP) data restore.

Fixed issue trying to restore an Cloud (xSP) backup to an alternate location on a different volume fails.

Fixed issue Scheduled Cloud (xSP) backup when using the option to use my current windows credentials passes nothing when connected via RDP.

Fixed blocking dialog box, stating A connection could not be established to the Backup Server.., in the client when backing up to Cloud (xSP) Storage Server that is not available, as it stops other backups.

Fixed issue Cloud (xSP) Storage Server configuration manager 'Tools' menu in account properties cannot handle username with a space.

Fixed issue Cloud (xSP) Storage Server move user data cannot handle paths over 255 characters.

Fixed issue Cloud (xSP) Storage Server account roll-ups, if canceled midway through roll-up, can put accounts over quota.

Fixed issue Cloud (xSP) clients that pull a license from the Storage Server can sometimes expire and not pull a new license.

Fixed issue exception AssertionFailed0 : assertion violation for expression 'tokenHandle != INVALID_HANDLE_VALUE'.

What's new in Granular Restore 21.0.1.54276 ?

Granular Restore 21.0.1.54276 contains support for newer Exchange Server versions, improvements in functionality and bug fixes.

You can check your installed version from within the Granular Restore application to see what version is installed.

NovaBACKUP will support Exchange Server 2019 backups starting in NovaBACKUP 19.5.

New major features and improvements:

Numerous fixes related to reading Exchange 2019 databases.

Optimization of the execution time of operations.

Fixes associated with previous versions.

Known Issues

When Importing a backup, which already has an entry on the Restore tab from a different location, the software is unable to replace the existing entry, but indicates the Import operation was successful.

To Import a backup that was moved, delete the reference to the entry on the Restore tab that was originally written to a different location before performing the Import operation

This specific build (v19.4.916) has a known display issue for the overall "Progress" bar when running a file backup or copy job. If the "Completed Files" count is increasing, the job is moving data.

<top>

19.3.408

Release Date: 11APR2019

Fixed Bugs

Fixed issues where failed backup jobs added to the scheduler using "One Time" mode repeat immediately after completing.

xSP client: Fixed issues where the backup client can't connect to the backup server using Windows credentials and Remote Desktop.

<top>

19.3.311

Release Date: 13MAR2019

NovaBACKUP 19.3 Release Notes (PDF)

General features and fixes

Added support for Windows Server 2019 and Fall Windows 10 patch

New feature to show the "Maximum number of activations" for a license key in the Help > About area

Suppress warning messages in logs related to having multiple connections to the same network location

The software will no longer automatically hold any failed job for any reason, all completed jobs will be rescheduled according to their schedule settings

Fixed LogViewer unable to display non UTF-8 characters that are valid in Windows

Fixed displaying the number of skipped files and the duration of the backup in the job log summary tab

Fixed issues displaying the elapsed time in logs

Fixed issues with System State restore

Fixed BackupClientAgent crashes when laptop goes to sleep during backup by closing laptop lid

Fixed logs of copy jobs not showing amount of data copied

Image backup related features and fixes

New feature to create an image backup directly to VHDX format

New feature to convert an existing image backup to VHDX format

Fixed issues when performing an image backup with more than one disk selected

Fixed issues with image backup retention if underscore character in the image backup name

Fixed issues when creating differential images on systems with UEFI boot mode

CMon related features and fixes

New feature for users to sign up and create cloud storage accounts in the CMon interface

Fixed issues with backup client agents sending logs to CMon

Fixed issues with backup client agents sending logs from jobs with long names to CMon

Fixed issues where CMon may report out of memory errors with many agents connected at the same time

Fixed issues when installing CMon and using a web server port other than port 80

Fixed CMon displaying UTC instead of localized time (on Dashboard only)

xSP related features and fixes

Fixed System State - System Volume failing to backup

Fixed issues when backing up from NAS or network location to an xSP/cloud device

Fixed cloud storage account quota size indicated in the backup client

Fixed cleaning up temporary files

Fixed performance issues restoring from a cloud device

Fixed issues when storage server work directory is on a NAS

Fixed issues when installing the storage server without the database

Fixed issues with SQL and Exchange backups to xSP/cloud device

Fixed issues displaying the size of SQL and Exchange backups

Fixed issues with System State restore

Fixed issues when backing up from NAS or network location to an xSP/cloud device

Fixed issues where the storage server may report "Storage corruption detected" and "Unable to delete file" errors

Fixed issues retaining the user and master log directories when upgrading the storage server

Fixed issues with storage server if storage drive is disconnected

Fixed issues with the staging directory when backing up to an xSP device

Fixed issue where the xSP client could not restore to two drives at the same time i.e. C & D

Fixed issue where the storage server would hold onto a bad file and not release the handle on the file until the backup server service was restarted.

What's new in Granular Restore 20.4.4.54016 ?

NovaBACKUP Granular Restore 20.4.4.54016 Release Notes (txt)

Granular Restore 20.4.4.54016 contains support for newer Exchange Server versions, improvements in functionality and bug fixes. You can check your installed version from within the Granular Restore application to see what version is installed.

New major features and improvements:

Support work with Exchange Server version 2013 CU21

Support work with Exchange Server version 2010 Update Rollup 24

Improved work with recurring items

Improved work in reading of attachments for Exchange Server databases

Improved restoring into live Exchange Server

Fixed bugs:

Fixed UI bugs

Fixed displaying embedded images in item preview

SQL Server - fixed displaying "date"/"datetimeoffset"/"datetime2"/"datetime" data type values

Known Issues

Creating Image Boot Media using the "Simple" mode requires the presence of Windows installation files on the system. If these files are missing, use the "Advanced" mode to create the image boot media.

Mounting Image Backups greater than 2TB crashes the system (BSOD) when running on Windows 7, Windows Server 2008, or Windows Server 2008 R2.

Mounting of large DR Images fails if files become larger than 3TB.

<top>

19.2.1001

Release Date: 01OCT2018

Fixed Issues / Bugs

Fixed issues when saving xSP device settings to BackupClient.ini

xSP Staging setting was not being properly put in the backupclient.ini, so staging for xSP device did not work without manual intervention.

Fixed issues when creating an image backup on a machine with more than one Disk selected

Image backup was only backing up Disk 0 no matter the Disk(s)/partition(s) selected

<top>

19.2.815

Release Date: 12SEP2018

NovaBACKUP 19.2 Release Notes (PDF)

Whats new in NovaBACKUP 19.2?

Displaying the number of skipped files and the duration of the backup in the job log summary tab.

Fixed issue where the log viewer may crash when viewing some logs.

Fixed issues when backing up from OneDrive and Open File Backup is enabled.

Fixed issues when Advanced verify tries to verify directories.

Fixed job status counters and estimates to be more accurate than it was before.

Displaying the number of skipped files and the duration of the backup in the job log summary tab.

Image backup related features and fixes

Completely new boot media that fixes a large number of issues that have been reported.

New feature to create an image backup from within the boot media.

New feature to create a clone of a disk from within the boot media.

New advanced boot media will utilize the latest ADK.

Optimized determination of used sectors on image backup.

Updating storage only when changes occur on image backup.

Fixed issues where simple boot media was not an option on some systems where it should have been.

Fixed issues with Boot CD due to automatic repair, after system recovery, or duplication.

Fixed issues where restore aborts when GPT layout is created.

Fixed issues where the installation is prevented on Windows Server 2008.

Fixed issues where the creation of the sector-based image was not terminated.

Fixed issues where the disk mapping is incorrect on HPE Logical Volume Manager.

Fixed issues with GPT disks without an MSR partition in Logical Volume Manager.

Fixed a bug whereby the user couldn't exit from Image Backup if an error occurred during boot media creation.

xSP related features and fixes

Improved performance when backing up large files with xSP. Seeing upwards of a 20% backup speed increase on xSP

Updated default backup client exclusion list.

Fixed handling of file name collision in backup server

Added support for selecting reparse points, OneDrive, and de-duplicated files.

Fixed issue when changing temp folder and existing xSP device properties

Fixed issue when backing up to an xSP device related to VSS snapshots.

Fixed issue when importing staged backups

Fixed issues when deleting files from the xSP server

Fixed issue where the work directory isn't persisted during an upgrade of the backup/storage server.

Fixed issues which may cause the backup client service to fail when backing up to xSP.

Fixed issues which may cause dropped network connections when backing up to xSP.

Fixed issues when trying to back up to an xSP device on certain files.

Whats new in Granular Restore 20.4.3.57013 ?

Support added for SQL Server version 2017.

Support added for Exchange Server version 2016 CU7, CU8, CU9, and CU10.

Support added for Exchange Server version 2013 CU20.

Improved restoring contact's items.

Improved restoring into live Exchange Server.

Improved restoring items from database Exchange Server version 2016 CU7.

Resolved problems with search.

Improved restoring items' properties.

Resolved problems with restoring items to live Exchange Server.

Resolved problems with displaying data.

Resolved problems with counting of items

Known Issues

Creating Image Boot Media using the "Simple" mode requires the presence of Windows installation files on the system. If these files are missing, use the "Advanced" mode to create the image boot media.

Mounting Image Backups greater than 2TB crashes the system (BSOD) when running on Windows 7, Windows Server 2008, or Windows Server 2008 R2.

<top>

19.1.1423

Release Date: 23FEB2018

NOTE: If you experience a failed installation of NovaBACKUP v19.1.x, where the installation or upgrade ends prematurely please first make sure that you have obtained the latest version of NovaBACKUP 19.1.1423 and that is the version that you are attempting to install. If that installation fails then you can attempt the fix that we have for this by reading the Knowledge Base article here.

Fixed Issues / Bugs

Fixed issue with Default Settings could not be saved.

Fixed issue where Time Mode Restore would Crash the "NovaStor NovaBACKUP Backup/Copy Engine" (nsService.exe) during scan.

<top>

19.1.1410

Release Date: 10FEB2018

Fixed Issues / Bugs

Fixed issue with xSP Storage Server license monitor client (data usage reporting).

<top>

19.1.1408

Release Date: 08FEB2018

Fixed Issues / Bugs

Fixed xSP Backup Server service crashing related to SSL certificate verification during license reporting

<top>

19.1.1407

Release Date: 07FEB2018

Fixed Issues / Bugs

Resolved issues when trying to install NovaBACKUP xSP custom backup client on a system with the .NET Framework v2-3.x installed

<top>

19.1.1406

Release Date: 06FEB2018

Fixed Issues / Bugs

Fixed uninstall failure when trying to uninstall DR (Disaster Recovery) Drivers which would allow NovaBACKUP to uninstall but not re-install when updating.

Fixed CustomAction UninstallVDDriver error 1603

<top>

19.1.1402

Release Date: 06FEB2018

NovaBACKUP 19.1 Release Notes (PDF)

Whats new in NovaBACKUP 19.1?

Updated Image Backup System

Added direct to Microsoft VHD (Virtual Hard Disk) feature to scheduled and on-demand image backup.

Updated Image Backup Boot Disk creation to use the latest Windows 10 ADK, which works on all currently supported Operating Systems. This ADK has support for newer hardware drivers than previous.

The Advanced Boot Disk function now reads the path of the installed Microsoft ADK or AIK directly via the local machine's registry for Advanced Boot Disk creation. If the Windows ADK or AIK is installed already, and detected, it will not prompt you to browse to that path when creating an Advanced Boot Disk.

Updated CMon with a New HTML User Interface and other improvements detailed in the section below.

Updated Granular Restore application with fixes detailed in the Fixed Issues / Bugs section.

Removed FTP code and support in NovaBACKUP backup client version 19.1 and newer.

Whats new in CMon 19.1?

Added the ability to monitor progress of ongoing backup on specific agents on demand.

Added high level dashboard statistics.

Added searching and filtering in the Agents and Groups screen.

Added the following fields to the Agents and Groups view: backed up data for last backup, files backed up for last backup, how long last backup took.

Added a connected column to the Agents and Groups view.

Added a setting for Time/Date format in the settings of the CMon.

Added a setting for Time Zone that dates and times should be displayed in.

Fixed Issues / Bugs

Fixed issue with file backup unable to backup encrypted files.

Fixed issue with some Windows 10 applications from the Microsoft Store cannot be backed up, the error was client file is busy, retry.

Fixed issue where Image Backup Fails to NAS with DuplicateTokenEx Error.

Fixed issue with access token errors in scheduled image backup jobs.

Fixed issue with VMware Plugin Restore if the backup was encrypted then performing the VMware Import of encrypted backup fails.

Fixed issue where unable to backup System State when some Windows applications are installed.

Fixed issue with not able to span tape when the backup job is scheduled.

Fixed issue that caused many error events that were being created in the Windows event log if an attempt to clear the archive bit on files fails. These types of errors will no longer be logged.

Fixed issues when trying to select a large number of files for restore.

Fixed chaining problem that caused some files or folders to become corrupted when mounting an incremental image backup.

Fixed system crash when mounting disk images larger than 2TB on Windows 8.x, Windows 10, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016.

Fixed directly generated VHD files not the same as those converted from native format (converted files were bootable, while directly generates files were not).

Fixed Microsoft SQL Backup fails if System State Temp files cannot be deleted due to a long file path.

Fixed issues with Granular Restore including resolving problems with search, connection to 2013-2016 Exchange Server with impersonation rights, improved restoring items' properties, resolved user interface problems, resolved problems with recovering attachments, resolved installer problems, improved work with PST files.

Fixed issue where the un-installer does not remove DR Drivers when you un-install NovaBACKUP.

Fixed issue with xSP Storage Server with NFS fails with error "A low disk space condition (<100MB) was detected on volume", even though disk space was not an issue.

Fixed CMon may not automatically purge log entries in the database older than the specified number of days in the configuration.

Removed check in xSP to upgrade storage to FastBIT 3.

System Requirement NovaBACKUP

Added support for SQL Server 2017 in the NovaBACKUP backup client, xSP Storage Server, xSP Application Updater, and xSP Remote Manager.

Changed the xSP Storage Server so that newer clients can talk to older xSP Storage Servers.

Removed requirement in xSP Storage Server installation for Microsoft .NET 3.51.

Removed requirement in xSP Storage Server installation to replace SQL Server 2008 R2 Express with SQL.

Removed Support for Windows Server 2003 and Windows XP. You will not be able to install NovaBACKUP on Windows Server 2003 or Windows XP OS with NovaBACKUP v17.6, and newer.

Removed Windows XP and Windows Server 2003 code in NovaBACKUP backup client completely in this release.

Removed Support for Windows Vista.

You will not be able to install NovaBACKUP on Windows Vista with NovaBACKUP 19.0 and newer

<top>

19.0.712

Release Date: 13JUL2017

Two issues were fixed solely with the backup client in v19.0.712 which are detailed below. There were no new features in this release.

Fixed issues / bugs NovaBACKUP

Fixed issue with incomplete copyright notice on the backup client splash screen.

No longer creates logging errors in the Windows event log if an attempt to clear the archive bit on files fails. No longer creates summary messages in the NovaBACKUP backup logs if an attempt to clear the archive bit on files fails.

The errors in the Windows event log (Application logs) would contain entries with event Source = nsService.exe. Example log entry is shown at the bottom. This item also fixes a NovaBACKUP job logs related issue with Full and Incremental file backups where those two methods of file backup were displaying messages or warnings in the backup job logs having to do with the fact that if selected files were protected files, which most anti-virus and anti-malware software now does not allow changing the archive bit property on files that anti-virus software utilize, would cause the job status to show additional messages such as "Summary message limit exceeded. 38 additional messages saved in C:\ProgramData\NovaStor\NovaStor NovaBACKUP\Logs\5968f9b3.events.xml", in order to see all of those 38 messages you would have to open the "*events.xml" file, as they won't be displayed directly in the LogViewer application when viewing that log inside NovaBACKUP. The messages have to do with files that in this example are all owned by the popular and often utilized anti-malware software called Malwarebytes, this software protects all of its own files. There are log messages and event log entries for each one of the files that this software contains where the archive bit was attempted to be set and since the files were protecting themselves then NovaBACKUP could not make the archive bit change to the file. In this case, when using an earlier version prior to v19.0.712, even if all files were backed up successfully, because the archive bit could not be set on these protected files that were part of the selection to backup. This is because the Full and Incremental file backup modes utilize the archive bit for each file that is backed up and if the archive bit cannot be set, since the file is protecting itself from that type of property change, NovaBACKUP cannot apply that archive bit file property change and causes that type of log entry to be shown for that reason. An example Windows event log such as this would occur for each file that is part of an antivirus or anti-malware software's own file set, if that software protects its own files from modification including modifying the archive bit, in this case we can see that the popular and often utilized Malwarebytes anti-malware program is protecting its own files as to cause this event log entry to be created in the example below: Exception 'Base:104'

(executive.cpp(1674) unexpected failure)

UnableToSetAttributes : Unable to set attributes for file

'C:\Program Files\Malwarebytes\Anti-Malware\scenegraph\softwarecontext.dll'

--> CHECKPOINTED AT executive.cpp(1646)

--> THROWN FROM FileSystem\Files.cpp(451)

CAUSED BY Win32Error : Function: SetFileAttributes, error = 0x80070005,

Access is denied.

--> THROWN FROM FileSystem\Files.cpp(446)

<top>

19.0.531

Release Date: 07JUN2017

New Features NovaBACKUP

Improved performance of import and restore operations for file-based backups

Increased speeds when scanning, indexes are now stored with backup media

Import now takes minutes (previous versions could take hours)

New logic prevents users from incorrectly selecting "overwrite media" on incremental backups

Removed the check for application updates before each backup runs except when backing up to an xSP storage device

Added Korean language support

System Requirement NovaBACKUP

NovaBACKUP requires GUID (GPT) partition style to be set for a destination storage device that is an external hard drive which is 2TB or larger in physical size. Please read our Knowledge Base article on this subject which contains instructions on how to verify if your drive is the older MBR partition style and how to set the drive to GUID (GPT). If you rotate/swap external hard drives, be sure to check each drive to verify that it is using GUID (GPT). If this requirement is not in place, and you are using a external hard drive that is 2TB or larger, but not set to GUID (GPT), then your backups will most likely randomly fail. We cannot support NovaBACKUP in your environment if this requirement is not met.

Certified for Windows 10 and supports Microsoft Windows 10 Creators Update

Removed Support for Windows Server 2003 and Windows XP.

You will not be able to install NovaBACKUP on Windows Server 2003 or Windows XP OS with NovaBACKUP v17.6, and newer.

Removed Support for Windows Vista.

You will not be able to install NovaBACKUP on Windows Vista with NovaBACKUP 19.0 and newer

New Features NovaBACKUP Granular Restore v20.2.0.55471

Support work with Exchange Server version 2016 CU3 and 2016 CU4.

Support work with Outlook 2016 PST files.

Added feature to search and highlight in items preview.

Improved working with SQL Server files.

Minor improvements in user interface.

New Features NovaStor Log Collector v19.1.608.1

Replaced the NovaStorLoggingApp_x64.exe and NovaStorLoggingApp_x86.exe programs with NovaStor Log Collector (LogCollector.exe). The new Log Collector tool will execute quicker and be more accurate with the data compiled in the resulting logs .ZIP file.

There is now no need to have separate x64 (64-bit) and x86 (32-bit) editions of the log collector tool. The new tool is an all-in-one executable.

Support added for Windows 10 Creators Update (Windows 10 Version 1703). The previous NovaStor LogCollector.exe program would fail if executed on that OS.

The download link to get the current version of NovaStor Log Collector is: http://novastor.com/LogCollector.

Fixed issues / bugs NovaBACKUP

Backup no longer hangs on Outlook PST files with VSS OFF (skips locked PST files)

Fixed issue where retention doesn't delete files on a 32-bit Operating System

Fixed issue where scheduled incremental image backups fail after a full backup is run

Fixed issue where the setup installer fails to install the ext file system driver if the code signing certificate has expired, which causes the installation to roll back

Fixed localization of reports with text corrections to UI (German; Copy Settings)

Fixed issues when restoring from xSP where client cannot restore file following DST time change

CMon now automatically re-establishes connection to the server should it become disconnected

CMon now maintains server settings even if .NET 4 is not installed (rather than reverting to default)

Known Issues NovaBACKUP

Creating boot CDs with the "Simple" mode requires the presence of Windows installation files on the system. If these files are missing, use the "Advanced" mode to create a boot CD.

A backup client with a newer major version cannot connect to an older NovaBACKUP Storage Server (xSP Device).

Notes

All installations require an Administrator Account and cannot be installed under a Limited User Account. All installations require a TCP/IP network with active Internet connection for service, support, and software activation.

There were changes to the CMon (Central Monitoring Console) application and you should definitely upgrade to CMon v19.0.531 if you are going to utilize it with NovaBACKUP 19.0.531. Please upgrade over the top of your existing installation of CMon to update it.

<top>

Version 18.x

18.7.1723

Release Date: 25MAY2017

New Features NovaBACKUP

Improved backup speed. Actual performance increase varies depending on the hardware and configuration, but is expected to average roughly 10% when backing up to external devices such as USB or NAS drives.

Advanced Backup Verification of back-up data files (optional). The backup jobs perform double-data reads and comparison at a low-level.

Single pass image recovery scans the last full image backup, then goes through each subsequent incremental image backup to acquire any later file revisions for a seamless System Image recovery process.

Added ability to specify a custom subject line in existing email notification settings (excluding virtual machine backup jobs)

'Shutdown' and 'Restart' options added to backup jobs (excluding virtual machine backup jobs)

Removed Express Wizard from NovaBACKUP version 18.0 and newer.

Numerous Stability Improvements

System Requirement NovaBACKUP

NovaBACKUP requires GUID (GPT) partition style to be set for a destination storage device that is an external hard drive which is 2TB or larger in physical size. Please read our Knowledge Base article on this subject which contains instructions on how to verify if your drive is the older MBR partition style and how to set the drive to GUID (GPT). If you rotate/swap external hard drives, be sure to check each drive to verify that it is using GUID (GPT). If this requirement is not in place, and you are using a external hard drive that is 2TB or larger, but not set to GUID (GPT), then your backups will most likely randomly fail. We cannot support NovaBACKUP in your environment if this requirement is not met.

Removed Support for Windows Server 2003 and Windows XP.

You will not be able to install NovaBACKUP on Windows Server 2003 or Windows XP OS with NovaBACKUP v17.6, and newer.

New Features NovaBACKUP Granular Restore v20.1.0.55021

Support for search queries with the operator "LIKE" in SQL tables.

Improved working with incomplete and deleted items.

Improved working with items and attachments with special characters.

Fixed issues / bugs NovaBACKUP

Fixed issue where the time-based restore tab was not showing all the expected tick marks when initially displayed, and was not correctly filtering the file set for the selected date and time.

Fixed issue when trying to restore data to network locations.

Fixed issue where a backup could fail if no network is available on systems that use double-byte character sets (for example, Japanese or Korean).

Fixed issue when trying to import backup if data is encrypted.

Fixed issue that may have occurred when attempting to span tapes.

Fixed issue when trying to create Simple Mode Boot disc.

Fixed issue where Image Backup failed to write boot image directly to optical media.

Improved error handling to fix issue where error alert was generated by a restore from user with invalid credentials.

Fixed issue where the wrong default value for backup retention setting is used when creating a new retention job.

Fixed localization issues for some languages and references to Disaster Recovery versus Image Backup.

Disabled JavaScript error dialogs that may appear in embedded web browsers.

Removed analytics, which was causing warnings with some security software products.

Fixed issues when opening log files that were created in a different date time format than what is currently configured on the system.

Fixed issue where CMon is not able to show log details of Image Jobs.

Fixed issue when restoring drive from image backup where the partition drive letters have changed from their original drive letters

Fixed issue where the Virtual Dashboard may produce an error message after performing an upgrade from or to a custom backup client build

Fixed issue when the context menu is not displayed properly on Windows 10 when right-clicking in the Open dialog.

Fixed issue where the setup installer failed to install the optional VMware related virtual disk mount and ext file system driver if the code signing certificate was expired, which causes the entire NovaBACKUP Backup Client installation to roll back; this could occur on fresh and upgrade installs.

Fixed issues / bugs NovaBACKUP Granular Restore v20.2.0.55471

Resolved problem with SQL.bak files do not open.

Resolved problem with search in SQL Server files.

Resolved some problems with restoring sender's name.

Resolved some problems with exporting items into live Exchange Server.

Fixed issues / bugs NovaBACKUP Granular Restore v20.1.0.55264

Resolved problem with inability to process SQL Server database backup .bak files.

Fixed issues / bugs NovaBACKUP Granular Restore v20.1.0.55021

Resolved problems with previewing items in the product

Resolved problems in user interface

Resolved problem with incorrect highlighting during search

Resolved problem with search in name of attachments

Resolved problem with exporting properties of items

Resolved problems seen in cases with insufficient disk space

Known Issues NovaBACKUP

Creating boot CDs with the "simple" mode requires the presence of Windows installation files on the system. If these files are missing, use the "advanced" mode to create a boot CD.

Notes

All installations require an Administrator Account and cannot be installed under a Limited User Account. All installations require a TCP/IP network with active Internet connection is required for service, support, and software activation.

There have been no changes to the CMon (Central Monitoring Server) application since CMon version 18.1.705, so there is no need to upgrade to CMon v18.7.1417 unless you do not already have CMon v18.1 in place.

<top>

18.5.926

Release Date: 27SEP2016

New Features NovaBACKUP

Removed Express Wizard from NovaBACKUP version 18.0 and newer.

New Features NovaBACKUP Granular Restore v20.0.0.54178

Windows Server 2016 support

Exchange Server:

Exchange Server 2016 CU1 and Exchange Server 2016 CU2 support (open, search, export into PST, export into original/live server, open using transaction logs)

Greatly improved work with Exchange Server databases (increasing speeds of reading and searching processes)

Improved work with big-size databases

Added support searching with wildcards in the start of request

SQL Server:

SQL Server 2016 support (open, search, export into SQL scripts, export into live server)

Fixed issues / bugs

Enhance reporting in the backup server in cases where a connection to the client could not be established.

Fixed copy jobs if they're set to overwrite older files so that the logs do not indicate the files were skipped.

Fixed restoring Hyper-V virtual machines to their original location from the Virtual Dashboard.

Fixed daylight savings time issues with scheduled backup jobs.

Backup logs no longer display warnings if Open File Backup is enabled and only network shares are being backed up.

Fixed issue where partitions may not be available for selection when scheduling an image backup.

Fixed Image Backup's ability to distinguish between two or more removable devices with same name.

Fixed GUI issues when the backup client is running on systems with high resolution displays, larger fonts, and/or increased text size.

Fixed PDF Help in Image Backup

Implemented various bug fixes for VMware virtual machine backups.

Fixed memory leak after disconnecting from a VMware virtual machine.

Fixed issue where a VMware restore/replication fails if a virtual machine with the same name already exists.

Fixed possible DLL conflict when vmware.exe is deployed on the vCenter Server.

Virtual Dashboard message boxes can be positioned behind the main application's window.

Virtual Dashboard UI behaves unexpectedly when resized and maximized.

Fixed "Unable to initialize SDS kernel" errors due to corrupt or missing files which may prevent the backup client from running

Fixed help buttons and menu items within the backup client

Fixed issue when creating scheduled backup jobs where the password for the credentials were not being saved

Using the current time as the default time when editing a scheduled job (that doesn't already have a time) in the Virtual Dashboard

Replaced "Management Server" with "CMon Server" (Start Menu, Server Admin, Backup Client)

Known Issues

When right-clicking in the Open dialog, context menu is not displayed properly on Windows 10.

Notes

All installations require an Administrator Account and cannot be installed under a Limited User Account. All installations require a TCP/IP network with active Internet connection is required for service, support, and software activation.

Since nothing was changed in the CMon application since version 18.1.705 the version number stays at v18.1.705. CMon v18.1.705 is fully compatible with NovaBACKUP v18.5 backup client software.

<top>

18.1.705

Release Date: 05JUL2016

New Features NovaBACKUP

Replaced Kroll Ontrack Single Mailbox Restore for Exchange with NovaStor Granular Restore (NBGR) for granular restore of Microsoft Exchange single mailboxes and Microsoft SQL Server. Download the User Manual. For information on what versions of Exchange and SQL the NovaStor Granular Restore for Exchange and SQL application supports please read the section below "Known Issues". NBGR will only function with the Business Essentials edition of NovaBACKUP.

Removed Express Wizard from NovaBACKUP version 18.0 and newer.

Fixed issues / bugs

Fixed "Unable to initialize SDS kernel" errors due to corrupt or missing files which may prevent the backup client from running.

Fixed help buttons and menu items within the backup client.

Fixed issue when creating scheduled backup jobs where the password for the credentials were not being saved

Replaced "Management Server" with "CMon Server" (Start Menu, Server Admin, Backup Client).

Implemented various bug fixes for VMware virtual machine backups.

Fixed memory leak after disconnecting from a VMware virtual machine.

Fixed issue where a VMware restore/replication fails if a virtual machine with the same name already exists.

Fixed possible DLL conflict when vmware.exe is deployed on the vCenter Server.

Virtual Dashboard message boxes can be positioned behind the main application's window.

Virtual Dashboard UI behaves unexpectedly when resized and maximized.

Known issues

When right-clicking in the Open dialog, context menu is not displayed properly on Windows 10.

NovaStor Granular Restore Supported Applications

Microsoft Exchange mail store database versions

2007 RTM

2007 SP1

2007 SP2

2007 SP3

2010 RTM

2010 SP1

2010 SP2

2010 SP3

2013 RTM

2013 SP1

2016 RTM

Microsoft Outlook (PST/OST) version files

2007

2010

2013

Microsoft SQL Server database (MDF/BAK) versions

2008

2008 R2

2012

2014

Added virtual machine jobs to backup summary reports

Display the version number of CMon in the footer section on authenticated pages after logging in

NovaBACKUP Central Monitoring Console (CMon) Client

Client-Side Supported HTML5 Web Browsers (Desktop/Tablet/Mobile Phone)

Microsoft Internet Explorer 9 or higher

Microsoft Edge 25.10586 or higher

Google Chrome 51 or higher

Mozilla Firefox 47 or higher

Apple Safari 9.1 or higher

Apple Mobile Safari 6.0 or higher

Android Browser 5.0 or higher

Blackberry 10 browser or higher

Opera Mobile 10 or higher

Amazon Silk

Client-Side Browser Requirements

JavaScript must be enabled

Cookies must be enabled

Local storage must be enabled with a minimum size of 10KB

Internet Explorer specific requirements:

Active scripting must be enabled

Enhanced Security must be disabled

Protected Mode must be disabled

Compatibility mode must be disabled

Script debugging disabled

File downloads must be enabled for downloading reports

<top>

18.0.1819

Release Date: 21JUN2016

New Features NovaBACKUP

Added support for VMware SAN, SCSI HotAdd, and SSL virtual disk transport modes for virtual machine backups

Added support for VMware vSphere 6 when TLS is enforced

Added email notification options to the Virtual Dashboard

Removed Express Wizard from NovaBACKUP version 18.0 and newer.

And a very significant NEW product, the CMon Central Monitoring Console - available as a free download:

http://novabackup.novastor.com/data-backup-products/central-monitoring-console/ (This product Replaced by CMon)

System Requirement NovaBACKUP

NovaBACKUP requires GUID (GPT) partition style to be set for a destination storage device that is an external hard drive which is 2TB or larger in physical size. Please read our Knowledge Base article on this subject which contains instructions on how to verify if your drive is the older MBR partition style and how to set the drive to GUID (GPT). If you rotate/swap external hard drives, be sure to check each drive to verify that it is using GUID (GPT). If this requirement is not in place, and you are using a external hard drive that is 2TB or larger, but not set to GUID (GPT), then your backups will most likely randomly fail. We cannot support NovaBACKUP in your environment if this requirement is not met.

Added Support for Microsoft Windows Server 2016 (and Hyper-V 2016)

Added Support for Microsoft SQL 2016

Added Support for Microsoft Exchange 2016

Added native 64-bit backup client (automatically installed on 64-bit operating systems)

Removed Support for Windows Server 2003 and Windows XP.

You will not be able to install NovaBACKUP on Windows Server 2003 or Windows XP OS with NovaBACKUP v17.6, and newer.

Fixed issues / bugs

Implemented various bug fixes for VMware virtual machine backups.

Fixed memory leak after disconnecting from a VMware virtual machine.

Fixed issue where a VMware restore/replication fails if a virtual machine with the same name already exists.

Fixed possible DLL conflict when vmware.exe is deployed on the vCenter Server.

Virtual Dashboard message boxes can be positioned behind the main application's window.

Virtual Dashboard UI behaves unexpectedly when resized and maximized.

Known issues

Image backup may fail when the destination is a NAS that uses the SMB 2.0 protocol. (Example: Western Digital's MyCloud device)

When right-clicking in the Open dialog, context menu is not displayed properly on Windows 10

<top>

Unsupported NovaBACKUP Version / Changelog Archive

You can see the archived changelog here: Unsupported NovaBACKUP Version / Changelog Archive

<top>

Other Notes

Partner builds and xSP / OEM versions of NovaBACKUP will be one minor version higher than listed above but are the same technical versions (e.g. - Version 16.5.1216 is the partner version of NovaBACKUP 16.5.1215). For Partner-Specific downloads of NovaBACKUP, please be sure to sign up as a NovaStor ValueCreate! Partner and you can find the downloads at your Partner Portal.

Click here to jump to the Step-By-Step Instructions below

When submitting a ticket we would prefer to have your full log set to be attached to the ticket especially for a "problem" type of ticket, meaning anything other than just a general question. Tickets can have logs attached to them and these are the instructions to gather the full set of logs including some system diagnostics that we can use to see what the problem is.

A single ZIP file of the entire set of logs is generated by the simple tool that we provide which is linked below; you run this tool on the system that you are having the problem with that is running NovaBACKUP software.

Since this error could be related to so many different source issues as a first step to get a better understanding of the problem can you follow the steps below to get the log files. We have the NovaStor Log Collector application that can collect System Information and NovaBACKUP Logs to Help us Troubleshoot the issues with NovaBACKUP.

Download link for NovaStor Log Collector Application:

http://filestore.novastor.com/Support/tools/LogCollector.exe

Run the LogCollector.exe application and note that it can take up to 15 minutes to complete the operation.

Once completed, the NovaStor Log Collector tool will create a ZIP file on your desktop named:

NovaStor_LogCollector_TICKET_YEARMMONTHDATE.zip

You will then attach the .ZIP file via the NovaStor Support Ticket / Submit a ticket page. There is a file size limit of 20MB if using the Attachments function at the bottom of the submit a ticket page. If the file that you are attempting to attach to the ticket is larger than 20MB then use NovaStor LogCollector Uploads to upload the .ZIP file. You are required to reference your support ticket # to use the LogCollector Uploads system.

NovaStor LogCollector Uploads - Recommended

Step-by-step instructions:

NovaBACKUP 19.3 or older (or not working):

Download the LogCollector.exe utility

Use the link above or www.novabackup.com/logcollector

Locate the downloaded file, LogCollector.exe, double-click it

Normally in your downloads folder

Continue reading "ALL Versions of LogCollector" below

NovaBACKUP 19.4 or newer:

Open NovaBACKUP

(Server/Business Essentials) Domain Controller: Start NovaBACKUP using Right-click->Run as administrator

(Server/Business Essentials) If you do not do this, the software may crash

Click on "Help" (top right corner)

Choose "Run LogCollector" https://sendfiles.novastor.com/filedrop/SupportFile

Continue reading "ALL Versions of LogCollector" below

ALL Versions of LogCollector

Input your 6-digit ticket number 123456 and press enter

Press enter to confirm the default output location ("Desktop")

Wait for the numerous processes in the "DOS box" to complete

This can take up to 15 minutes

Look for the .ZIP file that was made on your desktop (or location you specified)

Navigate to novastor.com/uploads

Drag the log file .ZIP onto the page to upload it

Enter your email [email protected] and ticket number 123456

Click [Send]

A Note about Windows Defender updates in recent versions of Windows 10

If you are experiencing trouble with the LogCollector terminating after asking for your ticket ID:

Open Windows Security Dashboard

Right click on Windows Defender Task Tray bottom right and choose "View security dashboard"

In Windows Defender Security Center click on "Virus & threat protection"

Click on "Ransomware protection"

Switch off "Controlled folder access"

Run LogCollector.exe again.

Even if you add LogCollector to the whitelist ("Add an allowed app") Defender will block the LogCollector without changing this setting.

Alternatively here are direct download links to the previously mentioned utilities:

Log Collector:

http://filestore.novastor.com/Support/tools/LogCollector.exe

The LogCollector Uploads page:

Support Policy [U.S.]

NovaBACKUP NovaStor Technical Support

Mission Statement

NovaStor Technical Support is committed to provide a high level of professional support to our customers and partners, enabling their success with NovaStors software solutions and technologies. Our support teams in the U.S. and Germany consist of highly qualified support engineers who identify with our customers goals.

We aim to provide timely, accurate solutions to our customers by offering expertise and handing out appropriate sources of information and assistance. NovaStor maintains a high level of technical knowledge and competency in our support engineers and provides the team opportunities to exceed.

Our customers and partners success with our products is considered as our responsibility: we listen to your input in order to assist with the continued improvement of our services and products.

Overview

The purpose of this document is to provide you with an overview of NovaStors support service options and information on how to access NovaStor Technical Support resources.

The guidelines apply to support services for the following NovaStor products:

NovaBACKUP PC

NovaBACKUP Server

NovaBACKUP Business Essentials

NovaBACKUP for Buffalo

NovaBACKUP Network

NovaStor Storage Server (xSP)

NovaStor Remote Workforce (RWF)

NovaStor DataCenter

Contents

Support Services Overview

Online Support

Free Trial Support

NovaBACKUP for Buffalo Customers

NovaCare Support Plans

Restore Support

Complementary Support Services

Setup Assistance Support

Enterprise Solution Training

Partner Benefits

Not-For-Resale Licenses (NFR Licenses)

Support Request Processing

Submitting a Support Request Online

Support Request Ticketing

Support Request Closure

Customer Satisfaction Surveys

Supported Versions of NovaStor Software Products

We do not accept Support Requests for discontinued versions.

NovaBACKUP PC, Server, Business Essentials, for Buffalo, xSP and RWF

NovaStor DataCenter (and Network)

Update and Upgrade Policy

Product Update

Product Upgrade

Product Upgrade Protection Policy

1 Support Services Overview

NovaStor presents its customers with a range of support offerings that are designed to meet the support requirements of every customer who is in need of our assistance.

Online Support

NovaStor offers a range of informational material accessible to all our customers.

The NovaStor Knowledgebase is an online resource center that contains all publicly available information on NovaStors above listed products.

The Documentation section of NovaStors website offers product documentation and release notes for all major release versions, and currently released products when available.

Training videos and webinars are available in the webinar section of NovaStors website and offer introductions to selected products as well as training units on selected core tasks of data protection with NovaStor products.

Email Support is available for all supported NovaStor products by submitting a support request online at novastor.com/ticket.

Free Trial Support

For 15 consecutive calendar days starting with the date of either the registration of the evaluation software or the product registration, you may freely access the online support options, and submit your support requests online in order to receive an individual answer to your question from our support team within one business day.

NovaStor Storage Server (xSP), NovaStor Remote Workforce (RWF), NovaStor DataCenter Solutions have a 30 day free trial period.

Free Trial Support is available for all of the above listed NovaStor products.

NovaBACKUP for Buffalo Customers

NovaBACKUP for Buffalo products only include Email Support, as defined above.

To redeem a NovaBACKUP for Buffalo product please visit http://novabackup.com/buffalo/

In addition, NovaBACKUP for Buffalo Products do not include a NovaCare Support plan unless purchased separately. More information on how to purchase NovaCare for NovaBACKUP for Buffalo Products can be found at http://my.novastor.com/buffalo

NovaCare Support Plans

NovaCare plans add phone support and free updates / upgrades to ensure that you always have the latest product.

NovaCare support is designed to provide professional support for NovaStor products. NovaCare provides support to any employee using our software. We wish, however, to point out that online communication is most efficient and successful when IT professionals are involved at the customer site.

Each NovaCare support plan runs for a year starting with the date of purchase, unless otherwise specified.

Products purchased as part of a subscription include NovaCare support. As long as the subscription remains active, you are covered by NovaCare.

To check your NovaCare support status, enter your key on our NovaCare page.

Restore Support

Restore support is available at no additional change for customers with an active NovaCare plan.

Restore support can be requested by submitting a support request online or calling our NovaStor support number. Restore support is available for all of the above listed NovaStor products.

Please note: A successful data restore depends on the measures that customers have taken to protect their data. NovaStor can therefore not guarantee a successful restore, but support customers in an optimal manner during the process.

Top

2 Complementary Support Services

In addition to the standard support services described above, NovaStor offers a range of services upon individual arrangement.

Setup Assistance Support

Setup Assistance support is available at no charge to NovaBACKUP Server and Business Essentials customers. Upon purchase, customers will receive a link to schedule a Setup Assistance call with a NovaStor support engineer.

These customers are entitled to receive a phone call at the scheduled time and date and a remote assistance session from NovaStors support team to help them install and configure the software on their system. This is valid for a single installation within 30 days of purchase.

Enterprise Solution Training

NovaStor DataCenter, xSP and Remote Workforce customers are eligible to receive remote installation, training and setup assistance.

Top

3 Partner Benefits

Not-For-Resale Licenses (NFR Licenses)

NovaStor equips partners with NFR licenses that allow partners to evaluate one or more NovaStor product/s over a longer time than the standard evaluation period.

NFR Licenses are licenses for evaluation and demonstration purposes only and not for production use.

NFR Licenses are only available under the terms of NovaStors NFR Agreement. For further details please contact NovaStor at [email protected]

Top

4 Support Request Processing

Whether you contact us via email or the Support Request Form, we will promptly log your support request and quickly assign your issue to the appropriate support engineer. The following sections detail the life cycle of a support request and explains best practices, our processes and your options as the issue progresses. Here are general recommendations for contacting us by email or website.

Submitting a Support Request Online

If you have an active Support Plan, or are entitled to Complimentary Support, you can Submit a Support request from our website.

To Submit a support request, go to the Support Section of NovaStors website, and click "Submit a Ticket". You can also visit novastor.com/ticket to reach the same form.

Once there, fill out the necessary fields and provide a detailed problem description.

Please include your License Key (preferred), Cleverbridge Order reference number, or email used at the time of purchase when submitting the Support Request Form. This is necessary as our Support Request System will identify your support status from this information.

Support Request Ticketing

After you submitting your Support Request, our Ticket System assigns a unique ticket number (Ticket ID) to your request. These ticket numbers allow NovaStor Support to prioritize and track all requests through to resolution, and allow the customer to get a status update of their case via the Support section of our Website.

You will receive an email with the Ticket ID assigned to your request and the link to your support request in the support system. Always record your Ticket ID and please ensure that you have it readily available if you are calling our support team in reference to an existing case.

Please review the confirmation email is received as this is the same channel Technical Support will respond to any open ticket. Additional information may be requested after completing the ticket submission.

You can view the status of your support request and annotate your request any time via the NovaStor Support Website. Use the link you received in the response email to your ticket submission. You can also simply reply to the response email to update your support ticket.

You can close your support ticket if you found a solution to your problem. Tickets closed this way will no longer be visible to the support team.

Support Request Closure

Excluding cases described in the above section a Support Request is typically closed when you confirm that a resolution is reached or if we do not hear back from you after three attempts. We may also close Support Requests if we cannot resolve, or choose not to resolve certain issues.

You will be notified by e-mail when your support request will be closed; however, you can reopen your ticket by responding to the ticket again, if the ticket was closed more than 60 days ago, you will need to open a new ticket.

Please be sure before reopening a particular Ticket that your comment is not a new support issue, which requires a new ticket submission.

Customer Satisfaction Surveys

The current and future services we offer are based largely on feedback from you. Your satisfaction with our services is the only way we measure our success. Thereto we conduct customer satisfaction surveys that give you the opportunity to let us know how we are doing. These responses are for internal review for determining what we need to work on.

Top

5 Supported Versions of NovaStor Software Products

As a general policy, the current and previous major version of our products are supported by Technical Support. Our release cycle is typically annually for Major versions.

Documentation and related Knowledgebase articles for unsupported versions of NovaStor products may remain available on the NovaStor Website.

We do not accept Support Requests for discontinued versions.

NovaBACKUP PC, Server, Business Essentials, for Buffalo, xSP and RWF

Current Version:

19.x

Previous Version

18.x

Released:

June 2017

Released:

June 2016

NovaStor DataCenter (and Network)

Current Version:

7.x

Previous Version

6.x

Released:

November 2017

Released:

April 2016

Top

6 Update and Upgrade Policy

We provide software releases to fix problems uncovered in our current products. We use two mechanisms to provide bug fixes:

Product Update

Updates provide important fixes to NovaStor products that could affect you. By keeping your software updated, you ensure that you are running on the latest version with all of the latest fixes. Product Updates are released regularly.

To check your update and upgrade eligibility, visit our upgrade page.

The NovaStor email notification system allows you to remain up-to-date on current events, latest updates for your products, as well as new product releases. To subscribe please check the appropriate box in your registration form.

Being a registered user of one or more NovaStor products, you are entitled to free updates to this product until a new major release is launched that changes the version number of the product in front of the dot, e.g. from version 18.7 to 19.0, in accordance with the specific update policy.

Product Upgrade

An Upgrade refers to a new version of NovaStor products that contain major enhancements, new features or significantly improved functionality, thus we are committed to further development of our software. However, NovaStor does not assume any obligations concerning any dates of new version releases. Upgrades are signified by a major version number change. For example, a major upgrade from version 18.x would be 19.x.

If you have an active NovaCare plan you are entitled to free product upgrades. If you do not have active NovaCare, a full version will need to be purchased as upgrade purchases are no longer available for the NovaBACKUP product line. Occasionally discounts are made available to help customers get upgraded to the latest version.

When purchasing the product initially, it will include a full year of NovaCare, which entitles you to all new major releases and versions for as long as you maintain your NovaCare plan without interruption, as specified below.

NovaBACKUP subscription plans include NovaCare support. All active NovaBACKUP subscriptions are entitled to updates and upgrades.

If you purchased a NovaStor product that includes maintenance, it includes a full year of product updates and upgrades from the initial purchase date. As long as your maintenance remains active, you will continue to be entitled to product updates and upgrades.

To check your update and upgrade eligibility, visit our upgrade page.

Top

7 Product Upgrade Protection Policy

By purchasing a NovaStor product with NovaCare, a maintenance plan, or one of our subscription products, the customer ensures that their software is always kept up-to-date with the latest version of the software - without having to worry about any extra upgrade costs. NovaStors software continues to be developed and improved in response to customer needs and new technological advances, to ensure the best software is being provided. It is in the best interest of the customer to take advantage of these developments in the most cost-effective way.

During the term covered by NovaCare or maintenance plan, customers are entitled to receive all generally-released new versions of their NovaStor software title(s), including both updates and major releases, changes, service packs and patches for the product. In other words you can always download updates and upgrades for free, as long as your NovaCare, maintenance plan, or subscription remains active.

If you have any questions about our NovaCare protection plans, please contact us at [email protected]

Top

Disclaimer

This document has been created for your convenience. Nothing in this document conveys a contractual right to you, or a commitment from NovaStor. NovaStor reserves the right to make changes and amendments to this document and change any support policies referenced here at its discretion.

Top

NovaStor's Product Portfolio

NovaBACKUP PC

NovaBACKUP Server

NovaBACKUP Business Essentials

NovaStor DataCenter

Operating Systems

Windows for PCs and Laptops

Windows for Server

Linux

Solaris

Virtualization

VMware

Hyper-V

Databases and Applications

Microsoft SQL

Exchange

Granular Recovery (SQL/Exchange)

Exchange DAG

Sharepoint

Oracle

MySQL

Lotus Notes

SAP

Storage Devices

Local Disk

NAS

Single Tape

Disk Appliances (for

Deduplication, Replication, etc.)

Tape Library

Tape Autoloader

Central Management

Optional Monitoring

Optional Monitoring

Optional Monitoring

Support

Email

Phone

Optional

Please use the Compatibility guide to see what NovaStor DataCenter will work with.

Overview

NovaBACKUP Technical Support is able to provide assistance for the current and one previous Major Version of the software.

This article exists for customers who are interested in seeing all of the changes for older releases of the software that have been made available.

Current NovaBACKUP Version:

See www.novabackup.com/changelog for information about the currently supported versions of the software.

NOTE: Use the "Check for Updates" button in the Help menu of the software to find the latest version available. It can take about a week for you to be able to obtain the current version after it has been announced, using "Check for Updates" in the software.

Current version: Download NovaBACKUP PC/Server/Business Essentials Here

Changelog

Please see the following for an at-a-glance overview of what was added or removed from the software:

NovaBACKUP Major Version Highlights

Jump to a Release

Current NovaBACKUP Version / Changelog

Version 19.x

Version 18.x

Unsupported NovaBACKUP Version / Changelog Archive

Version 17.x

Version 16.x

Version 15.x

Other Notes

Version 17.x

17.6.415

Release Date: 29APR2016

Fixed issues / bugs

Image Backup Improvements

The user can now right-click on a scheduled Image Backup job and select an option to modify the job. Which parameters can be modified depends on whether the job has already run once or not.

As a simplification to creating Image Backup jobs, the user no longer has to specify a "job name" and a "backup name." They are now one and the same. In addition, the job name is automatically generated for incremental and differential Image Backup jobs.

The job name for Image Backup jobs is now displayed in the log file list. Previously, the job name was blank.

Image Backup will no longer display optical disk drives in the list of drives that can be backed up.

A bug was fixed that prevented the user from being able to backup individual partitions on some Windows systems if the partitions had drive letters assigned to them.

A bug was fixed that prevented the creation of Image Backup boot discs in simple mode on Windows 8.1 systems after the latest Windows updates were applied.

Fixed some errors in the German translations.

Fixed issue where LogViewer.exe may crash on systems without the .NET Framework 3.5 SP1.

Fixed issue where the backup client doesn't show any backup devices by preventing the "NovaBACKUP Devices" feature to be marked as "Feature will be installed when required" when performing a custom installation.

System Requirement NovaBACKUP

Removed Support for Windows Server 2003 and Windows XP.

You will not be able to install NovaBACKUP on Windows Server 2003 or Windows XP OS with NovaBACKUP v17.6, and newer.

<top>

17.5.1423

Release Date: 24FEB2016

New Features NovaBACKUP

Enhanced creation of Image Backup jobs such that incremental and differential jobs can be flexibly defined and scheduled before the first full backup job has run

Enhanced Image backups (a.k.a. disaster recovery) now conveniently assignable to NAS device destinations.

Backup client can use either .NET Frameworks versions 3.5 or 4.X, whichever is already installed, thus reducing the need for setup to install an alternate version.

Improved Error Handling: More information provided, and reduced false negatives create an improved user experience.

Fixed issues / bugs

Demote some error messages to informational, and remove several "false negatives" altogether. Specifically: DR retention jobs are not classified as failed if a log file cannot be removed, the cause of syslog.txt rename errors has been fixed, and snapcmd no longer logs an error caused by trying to access a non-existent message file.

Virtual Dashboard fixed to not allow the selection of Hyper-V VM's running on Windows 10 since this is not a supported configuration.

Clicking on an empty folder in the restore view throws an error.

GUI may crash if a large number of job logs are retained on the Logs tab.

When double-byte characters are entered into the Explanation portion of the scheduled setting for holidays and then saved, the texts come up garbled.

When attempting to backup/copy to a network path with double-byte characters in the path, the process fails.

Backup being ran on a Holiday when it should not be when a job is configured through the wizard.

Backup job failed if destination was a NAS drive and the user account used an empty password.

<top>

17.2.1112

Release Date: 18NOV2015

New Features NovaBACKUP

Enhanced "Last Run" column in schedule tab to display the date / time the job was executed if a user selected "Run Now"

Enhanced the default exclusion list to properly exclude the Windows 10 download folder

NovaBACKUP now reports with its License Key when querying the Application Update service for available updates

Fixed issues / bugs

Fixed crash that occurred while adding / using a NovaBACKUP script from a network share with read-only permissions

Fixed crash relating to log viewing if a restore was triggered using the 'Time Mode'

Fixed UI crash relating to inappropriate / unrecognized results being passed to commands unexpectedly

Resolved issue where NovaBACKUP did not recognize Microsoft Exchange on SBS 2008 / Exchange 2007 SP3

Resolved issues where backing up Exchange / SQL servers with similar names would produce duplicated backup data

Resolved multiple issues where SQL or Exchange were unable to be restored from Amazon S3

Resolved multiple issues with restoring backups from Amazon S3 which were encrypted

Resolved issue where NovaBACKUP Monthly Reports scheduled on certain days would begin emailing every day instead of monthly

Resolved issues on server operating systems using IE ESC receiving warnings

Resolved issue where OneDrive on Windows 10 was not showing up as a valid 'Device' in the destination selection

Resolved issue relating to tape backups and the error, "Function 'fopen' failed for file 'C:ProgramData\NovaStor\NovaStor NovaBACKUP\Data\Media.', error 13: Permission denied"

CMC Fixed bug relating to naming NovaBACKUP Backup Policies

System Requirement NovaBACKUP

Added Support for VMware 6.0

<top>

17.1.804

Release Date: 07AUG2015

Fixed issues / bugs

Fixed an issue relating to Disaster Recovery backups and removable media (RDX / USB) where users would be unable to eject their removable device after executing a DR backup.

Fixed an issue when backing up files to cloud storage destinations when the file system had 8.3 file names disabled

Fixed issues relating to incremental backup reporting within Daily / Weekly / Monthly summary reports that would display, 0, or unknown

Fixed an issue that would crash NovaBACKUP if a user attempted to change the default temporary folder from the Default Settings window

Known Issues

After creating a Disaster Recovery Boot Image using the Simple method, users are unable to write the DR Boot Image to a valid CD/DVD burner. Using the Advanced method or writing to USB work as expected.

The issue only relates to writing to a CD/DVD, the image that is created during the Simple method is a valid Disaster Recovery Boot Image

Users can choose to use either a USB thumb drive to write the DR Boot Image or use the DRBoot.iso file that is provided during the process as they so choose.

System Requirement NovaBACKUP

Added Windows 10 support

<top>

17.0.1615 (17.0 "R1")

Release Date: 22APR2015

New Features NovaBACKUP

NovaBACKUP Alerts SMTP service

Its now easier than ever to send an email alert with NovaBACKUP. Starting in NovaBACKUP 17, weve included the NovaBACKUP Alerts service. Simply provide your e-mail address and well do the rest no more messy SMTP settings (unless you want them!)

Daily, Weekly and Monthly Summary Reports

You are now able to configure and e-mail a summarized report of all activities performed by NovaBACKUP in the last day, week or month.

Updated Log Viewer

The log viewer has been given a facelift and matches the new Summary Reports. Its also cleaned up the information being presented to help you better understand what happened during your backup job.

The log viewer now also prints out logs that match whats on screen (HTML log)

Network Devices now in Disaster Recovery / Virtual Dashboard

Pre-configured Network Devices will now be available as an option within a manually executed Disaster Recovery job. Additionally, if you select a network destination for a backup job from the Virtual Dashboard, NovaBACKUP will automatically provide the credentials from the Network Device.

System Requirement NovaBACKUP

NovaBACKUP requires GUID (GPT) partition style to be set for a destination storage device that is an external hard drive which is 2TB or larger in physical size. Please read our Knowledge Base article on this subject which contains instructions on how to verify if your drive is the older MBR partition style and how to set the drive to GUID (GPT). If you rotate/swap external hard drives, be sure to check each drive to verify that it is using GUID (GPT). If this requirement is not in place, and you are using a external hard drive that is 2TB or larger, but not set to GUID (GPT), then your backups will most likely randomly fail. We cannot support NovaBACKUP in your environment if this requirement is not met.

Important note for First BACKUP & SiTaaS customers

We request at this time that you please DO NOT upgrade to NovaBACKUP 17 as there is a slight risk that it could affect your ability to perform offsite backups successfully to our service. This issue is not critical and your data is not and has never been at risk. If you remain on your current version, you will continue with no interruptions in your service.

Please check our support portal (http://support.novastor.com/hc) for any updated information regarding these issues and when the fix is made available.

Fixed issues / bugs

Fixed an issue relating to a Network Device during scheduled Disaster Recovery backups

CMC network file section error fixed users can no longer select the entire network during backup job creation

CMC manual file selection error fixed users can now browse subfolders during manual file selection

Fixed issues when backing up documents to an xSP device via CMC

Clients connected to a CMC can now add devices from their local NovaBACKUP installation

Resolved issues with certain clients where the CMC was incapable of starting a restore process

Removed built-in Antivirus support

Removed CD / DVD / Blu-Ray support (as backup/copy target)

NOTE: Media Spanning supported for Single Tape Drives, such as LTO

Resolved background crash if a users backup metadata was stored incorrectly

Modified files selected / files completed reporting within Log Viewer to more accurately portray whats happened.

<top>

Version 16.x

16.5.1215 (16.5 "R2")

Release Date: 18DEC2014

New Features NovaBACKUP and NovaBACKUP Central Management Console

Supports backing up to popular file sharing applications:

Dropbox

OneDrive

OneDrive for Business

SkyDrive

Google Drive

Sync

SafeSync

NovaBACKUP Support Tab Support portal included directly within the application for fast troubleshooting and notifications

Ability to set a Holiday Schedule (disable backups on a particular date)

Ability to recover NovaBACKUP Virtual Dashboard VMware or Hyper-V backups from an alternate NovaBACKUP installation (16.1+)

Restoring Legacy Hyper-V / VMware / SQL / Exchange files to an alternate location no longer requires a VDF extraction

Single Mailbox Restore trial now available for all Business Essentials users at time of installation.

Ability to delete individual backup logs from the NovaBACKUP Virtual Dashboard

Ability to encrypt disaster recovery backups from the Central Management Console

User interface now remembers internal window sizing

Double clicking a NovaBACKUP Backup File (.NBD) will now open the NovaBACKUP client to the restore tab or import tool

The Central Management Console's pie chart is now clickable to filter the recent job log history to a specific result type (Success / Warning / Errors / In Progress)

Ability to back up to international Amazon S3 buckets

Introduction of the NovaBACKUP Customer Experience Program

Fixed issues / bugs (R2)

Excessively verbose logging has been resolved

v16.5 warnings: Unable to reset archive flag for read-only or system/protected files resolved

Resolved issue relating to trusted sites on Server operating systems

sFTP functionality fully restored

Reduced excessive log retention when client is connected to a Central Management Console (agentsvc.log)

Resolved potential application issues relating to retention in NovaBACKUP

URLs in German client now direct to German pages as expected

Disaster Recovery fixes

NovaBACKUP will no longer prompt to close Disaster Recovery during uninstall / upgrade

NovaBACKUP will now install proper Disaster Recovery driver versions during upgrade / install

Resolved issue that required Windows Install discs in order to create basic boot media (Windows 8.1)

Resolved issue with converting Disaster Recovery images to VHD

Resolved issue with scheduled Disaster Recovery jobs and pre-configured NovaBACKUP Network Devices

<top>

16.5.1106 (16.5 "R1")

Release Date: 18NOV2014

Fixed issues / bugs (R1)

FTP, sFTP and FTP(s) now significantly more stable for large file transfers

NovaBACKUP no longer requires a reboot after installation

S3 backups now report their appropriate size within the restore tab

Installing the Central Management Console into a WSUS, OWA, or other 64-bit IIS configuration will no longer break the other application pools

Ability to restore Active Directory from 2012 / 2012 R2 installations

Ability to backup and restore Active Directory System Volume information from a non-default location

Removed legacy references to "Need to restore additional incrementals" from within the NovaBACKUP client and the Central Management Console

Now able to back up any length SQL or Exchange database

Now able to back up any length Hyper-V backups from the NovaBACKUP Virtual Dashboard

"Single Mailbox Restore" now immediately shows within the client after entering the appropriate license key

Corrupted values within NovaBACKUP XML logs will no longer cause the entire log to be unable to open

Deleting a Hyper-V Replication job no longer crashes NovaBACKUP Virtual Dashboard

Central Management Console environmental variables function again

Central Management Console is now able to restore to an alternative location again

NovaBACKUP Storage Server no longer retains unusable partially uploaded files

NovaBACKUP Virtual Dashboard now displays Hyper-V Virtual Machines in non-English Hyper-V installations

Fixed issues with SAS and USB tape drives on modern operating systems (Windows 8 and above)

Fixed / enhanced multiple issues relating to Microsoft Volume Shadow Copy service

Resolved multiple underlying NovaBACKUP Engine exceptions

<top>

16.1.908 - Initial Release

Release Date: 10SEP2014

Changes and Notes:

Fix for Disaster Recovery backups stop working after an upgrade to 16.1.720 or 16.1.731

The DR backups may stop working if a "System Reserved" partition existed on the disk which was being imaged and usually the stop would occur within the first 45 seconds of starting the DR backup.

NOTE: If you created a DR backup job in v16.1.720 or v16.1.731 and then upgrade to v16.1.908 you ARE REQUIRED to re-create your DR related job(s).

Fix for "Resource is currently in use" file backup related error

Selected file(s) as part of your backup set selection with invalid stored "Modified Date" property may result in a failed backup when the backup reaches that set of file(s)

Fix for "Buffer size 8192 is insufficient for requested data" related error

<top>

16.0.19 - Initial Release

Release Date: 13MAY2014

New:

New NovaBACKUP Virtual Dashboard for managing advanced virtual machine backups / replication

VMware and Hyper-V Backups with ability to restore individual files

VMware Host-to-Self and Host-to-Host Replication

Hyper-V Replication Management and Monitoring

Single Mailbox Restore

HTML5 Help documentation

Changes and Notes:

Install / Uninstall now require a reboot

The ability to mount and restore individual VMware files requires a special type of device driver which needs a reboot to function. Instructions on how to remove these features / disable reboot during an install are available on our FAQ for Silent installation of NovaBACKUP

Removed Mirror and Bi-Directional copy options

These options - while functional - caused more issues than they resolved. Both features have been shelved for review by our product team to make an overall better experience for our customers

Multiple VSS-related bug fixes

Known Issues:

Saving VMware / Hyper-V backups that result in a file path exceeding 255 characters will fail.

<top>

Version 15.x

15.0.14 - Service Pack 1

Release Date: 13JAN2014

Fixes to FTP backups and special characters (Japanese / Double-Byte characters, etc)

Fixes to Express Wizard "All Files" jobs (VSS errors for non-existent drive letters)

The Express Wizard "Splash Screen" no longer appears (still accessible through the main GUI)

Included a new German-language (Deutsch) EULA

<top>

15.0.10 - Initial Release

Release Date: 13NOV2013

Initial release of NovaBACKUP 15

Removed file-cache requirement for local Microsoft SQL, Microsoft Hyper-V, Microsoft SQL, and VMware backups (does not affect xSP, FTP, or S3 backups).

Added encryption options for Disaster Recovery backups

New XML-based logging and log-viewer

Added support "search" bar throughout application

Moved "Default Settings" to the NovaStor "N" logo (top left)

System Requirement NovaBACKUP

Added support for Windows 8.1 and Server 2012 R2

<top>

End.

Other Notes

Partner builds and xSP / OEM versions of NovaBACKUP will be one minor version higher than listed above but are the same technical versions (e.g. - Version 16.5.1216 is the partner version of NovaBACKUP 16.5.1215). For Partner-Specific downloads of NovaBACKUP, please be sure to sign up as a NovaStor ValueCreate! Partner and you can find the downloads at your Partner Portal.

Thank You for your interest in NovaBACKUP Cloud Storage.

NovaBACKUP can now include cloud storage space with new license key purchases.

If you are interested in NovaStor-hosted cloud storage, NovaStor Online Sales ( [email protected] +1.805.435.0067) handles email promotions, subscription changes, account changes and change of address, online purchasing, and returns. Additionally you can send an email to [email protected].

This article is designed to walk you through how to create and connect to your Cloud Storage from within the NovaBACKUP software. If you are connecting a machine to your existing Cloud Storage bucket associated with your license key, please see Getting Started: Connecting to an existing NovaBACKUP Cloud Storage account (multiple activation license keys).

Download and Install NovaBACKUP, then open it.

Select "Cloud Backup" on the Home tab.

[Guide] NovaBACKUP PC (Home User) Configuration Walkthrough

Create an Account by selecting [Register]

Create a new account

Provide a memorable username

We recommend using your email address here

Provide your email address

Provide and confirm a Password

Your Password must be between 6 and 64 characters

This Password will encrypt your data, as such YOU CANNOT RESET YOUR PASSWORD, and if you forget it, YOU WILL BE UNABLE TO ACCESS YOUR DATA

Confirm your License Key is correct

If you do not have a License Key with Cloud Storage included, you will need to contact NovaStor Online Sales ( [email protected] +1.805.435.0067)

Review and accept the Terms and Conditions

Click [Register] to complete the creation of your cloud storage account.

You will see this screen when the Cloud Device has been added to your configuration

Create, Save & Schedule your backup job like any other File Backup job in NovaBACKUP

Make sure to choose "Cloud Storage" as the [Backup to...] destination

Instructions on how to create and schedule a backup job can be found in these KB articles:

[Guide] Standard Backup Schedule with Retention

NOTES

You CANNOT perform an Image Backup to your Cloud Storage device

Always use the "FULL" backup mode when sending data to your Cloud Storage, only the information that has changed will be uploaded

Thank you again for your purchase of NovaBACKUP with cloud storage.

Thank You for your interest in NovaBACKUP Cloud Storage.

NovaBACKUP can now include cloud storage space with new license key purchases.

Multiple activation license keys are available for NovaBACKUP PC, allowing one license key to be used on 3 or 5 machines.

If you are interested in NovaStor-hosted cloud storage, NovaStor Online Sales ( [email protected] +1.805.435.0067) handles email promotions, subscription changes, account changes and change of address, online purchasing, and returns. Additionally you can send an email to [email protected].

This article is designed to walk you through how to connect to your Cloud Storage from within the NovaBACKUP software. If you have not yet created a Cloud Storage bucket associated with your license key, please see Getting Started: Connecting to Your NovaBACKUP Cloud Storage for the First Time.

Download and Install NovaBACKUP, then open it.

Select "Cloud Backup" on the Home tab.

[Guide] NovaBACKUP PC (Home User) Configuration Walkthrough

Login to your existing Cloud Storage account by selecting [Login]

Enter your User name and password

The next screen will show your Cloud Storage account(s) associated with your Username

The next screen will show the details of your License Key, Select [Connect] to associate this machine to your account

Confirm your License Key is correct

If you do not have a License Key with Cloud Storage included, you will need to contact NovaStor Online Sales ( [email protected] +1.805.435.0067)

If you need to change your license key on this machine, close the open dialog and select Help->Registration to change it

Enter your Cloud Storage Account Password again to create the "Cloud Storage" device on this machine

You will see this screen when the Cloud Device has been added to your configuration

Create, Save & Schedule your backup job like any other File Backup job in NovaBACKUP

Make sure to choose "Cloud Storage" as the [Backup to...] destination

Instructions on how to create and schedule a backup job can be found in these KB articles:

[Guide] Standard Backup Schedule with Retention

NOTES

You CANNOT perform an Image Backup to your Cloud Storage device

Always use the "FULL" backup mode when sending data to your Cloud Storage, only the information that has changed will be uploaded

Thank you again for your purchase of NovaBACKUP with cloud storage.

Problem

You attempt an Image Backup to a Network Location and receive the errors:

Operation Failed: Process completed with errors.Error e001001d: An internal error occurred. - Job processing failure

The message being generated in your Windows Event logs when an Image Backup is attempted to a network location is:

Error MM/DD/YY HH:MM:SS DRBACKUP 2... failure: Backup failed due to invalid credentials specified for the destination.

Resolution

When performing an Image Backup to a network share, you must always provide credentials to connect to that share.

The method of choice is to Create a NAS Device for NovaBACKUP

Or once you enter a Destination that is on the network, an [Access] button will appear:

For Scheduled Image Backups

For Manual (One-Time) Image Backups

If this still does not work:

Enter the IP address of the destination network share instead of the DNS Name.

ex: \\192.168.x.x\Technical Support\... instead of \\ag-fileserver\Technical Support\...

NovaBACKUP PC/Server/BE v19.x

Symptom:

If you open the "Restore" tab the lower part of the window with the details of the backup contents is not displayed and looks similar to Figure 1:

Figure 1: Lower window with backup details is missing

Solution:

Maximize NovaBACKUP window. Lower window area is visible (see yellow labeled area):

Figure 2: Maximized NovaBACKUP window shows missing area

Drag the horizontal line up (between red arrows in figure 2).Restore the NovaBACKUP window to the size you desire.AMo

How to Uninstall CMon

It is important to understand that for general issues with CMon, make sure that the installed CMon version is the same or newer than the NovaBACKUP client software that is connecting to it. NovaStor releases builds for the NovaBACKUP Client and CMon at the same time. There are various circumstances that can cause instability in the CMon database system, which would cause you to be unable to log into the web interface.If the issue is not resolved after restarting the Machine running CMon, then CMon will need to be completely uninstalled along with it's database.

Open Windows Services ("services.msc" command via Start Menu -> Run or Search entry box).

Navigate to these two services in the list "Management Server" and the one entry below that "Management Web Server" which are the Central Management Console.

Right click on each of those two services listed above and STOP those two services. Launch an admin command prompt:

sc delete "Management Server"

sc delete "Management Web Server"

Via Control Panel -> Programs & Features or Add/Remove Programs area: Uninstall "Management Server" from the list. This is the CMC that is currently installed.

Via Control Panel -> Programs & Features or Add/Remove Programs area: Uninstall "NovaBACKUP Central Management Console" from the list. This is just the desktop icon for CMon.

Delete the entire folder mentioned below to delete all of the CMon settings including the CMon database: "C:\Program Files (x86)\NovaStor\NovaBACKUP Central Management Console\". NOTE: If your operating system is 32-bit Windows then this folder may be named this: "C:\Program Files\NovaStor\NovaBACKUP Central Management Console\".

If you installed CMon using MS SQL you will need to remove this database manually using SQL Server Management Studio or similar.

Restart the computer that you uninstalled CMC on.

Re-install CMon after logging back on to restarted PC.

From each NovaBACKUP GUI client (the regular NovaBACKUP desktop shortcut for the client) (process name = NovaBackX.exe) software go to the Default Settings area and then "Management Server" tab. Make sure the information to contact your CMon machine is correct, then click the "Start Service" button to make the connection between the client and server machines.

NovaBACKUP PC/Server/BE v19.x and newer

If the retention rule does not work properly, the following reasons may apply:

1. NovaBACKUP no longer refers to the files on the hard disks

2.Log files for the backups were deleted

3.Missing access rights for the storage

4.Retention is not scheduled5. Incremental backups

-------------------------

1. NovaBACKUP no longer refers to the files on the hard disks

For all files backed up by NBK, entries for the backed up data must exist under "Restore" (= Media View). This is valid for file backups, NOT for image backups. For image backups the retention checks the logs!

If there is no entry for a file (extension .nbd) under "Restore" or all logs have been deleted, the retention rule will not delete anything on the storage. In this case, you must delete the corresponding data on the storage manually. Alternatively, backup files can also be imported, but this can be time-consuming depending on the amount of backed up data.

-------------------------

2. Log files for the backups were deleted

The retention rule also includes the log files belonging to the backups under "Logs" as a criterion. If there is no entry under "Logs" for a backup, the rule does not delete the relevant backup file.

-------------------------

3. Missing access rights for the storage

In order for the retention rule to delete, it requires full access rights to the target. As a rule, the rules for setting up a network device apply. In some configurations, however, this may not be sufficient. Then you have to make additional configurations. Proceed as described in the following articles: https://support.novastor.com/hc/en-us/articles/360006792073-Retention-job-cannot-delete-File-Backups-on-destination-network-storage-device-due-to-network-permissions

https://support.novastor.com/hc/en-us/articles/360010920734-Access-rights-for-shares

On page

https://support.novastor.com/hc/en-us/categories/360000516334-NovaBACKUP

you can find more share related articles by a search for the keyword "NAS" or "share" (without ").

Schedule the execution of the retention rule AFTER the backup jobs. Some NAS systems and external USB drives go into power save mode and take some time to wake up. The retention rule goes into a timeout quite quickly and then can't delete anything. If it is started AFTER a backup, the NAS is still online => rule can delete immediately.

In general, it is always advisable to switch off energy-saving modes of USB ports/drives and NAS systems.

-------------------------

4. Retention is not scheduled

After creating the retention rule, you may have forgotten to include it in your schedule. Proceed as described in this article:

https://support.novastor.com/hc/en-us/articles/360005569373--Guide-Create-a-weekly-full-backup-a-daily-differential-backup-and-a-monthly-image-backup-With-Retention-

---------------------------------

5. Incremental backupsThe retention will not delete any incremental backups! You have to execute a full backup first, and then followed by new incremental backups. If the oldest full/incr backups matches to the retention rule they will be deleted then at once. But you cannot delete only one incremental backup file out of the incremental chain.

---------------------------------

AMo

Here are links to some of our Knowledge Base articles on the subject of importing backups (.NBD) and Restoring files/folders from a backup that was imported into the Restore tab.

How to import file backups (.NBD) into the restore tab

This guide will provide a step-by-step instructions on how to import file backups (.NBD file) into the restore tab. You will need to do this if you have backups that you are bringing from another computer that had NovaBACKUP and you want to restore file from those backups.

Once your backup set is Imported you can then restore individual files and folders from the backup set (.NBD) via the Restore tab.

[Guide] Restoring Files in NovaBACKUP (Video).

Here is a screenshot of how to select files to restore:

How to perform a Direct Restore (Legacy) from the NovaBACKUP client

If something is damaged in the current restore "media index records", in place on your local hard drive, you may have to perform a clean of the media index records and then re-import the backup set again to be able to restore files from it.

Clean NovaBACKUP Restore Index/Media Index (used by file level backups)

If for other reasons your backup set (.NBD file) cannot be Imported, you can also attempt the Direct Restore method to restore all of the files and folders from the backup set (.NBD) to extract the contents of your backup set to a folder of your choice, this is an all or nothing restore and does not allow you to select individual files and folders to restore.

If the backup set is damaged it will stop extracting the files from the backup set at the point where the backup set (.NBD) is damaged.

NovaBACKUPPC / Server / Business Essentials

This guide will provide a step-by-step instructions on how to import file backups (.NBD) into the restore tab. You will need to do this if you have backups that you are bringing from another computer that had NovaBACKUP and you want to restore file from those backups.

1) First Go to the "Restore" tab.

Clean NovaBACKUP Restore Index/Media Index (used by file level backups)

2) Next click on the "Import" button

3) From here you will browse to where your backups are located.

NOTE: If you cannot see your backup file in this dialog, make sure the Windows File Explorer setting "File name extensions" is shown.

4) After you click "OK" you will be taken to the "Status" tab as the backup will start to be imported into the NovaBackup software.

5) Once you see that the import is completed you can go back to the restore tab to view your backup.

6) From here, you will have successfully imported your backups into the restore tab.

Useful links

[Guide] Restoring Files in NovaBACKUP (Video)

NovaBACKUP

A guide to create a image restore boot disc through Advanced Mode using:

USB orCD/DVD

This step by step guide will assist you in creating a Recovery Boot Disc for USB and CD/DVD using advance mode. Our current version of NovaBackup PC Supports USB flash drives from 1GB to 16GB in total space.

Your USB Flash drive will be erased during this process.

What is the difference between Simple Mode and Advanced Mode?

Simple mode would be for those running a Workstation operating system such as Windows 10, and Advanced mode would be for those running a Server operating system such as Windows Server 2012 R2. Regardless of OS type you are required to use Advanced mode if your computer has a RAID controlled internal hard drive. If your computer contains a RAID controller, the RAID controller driver is required to be added via Advanced mode Recovery Boot Disc creation, in order to support restoring to the RAID controlled hard drive. If this is not done then you will not see your RAID controlled hard drive when booting to the Recovery Boot Disc.

You want to use advanced mode if you have a special graphics driver, a special Network controller, or RAID/storage controller.

NOTE: If you are unable to create a boot disk using Simple Mode FOR ANY REASON, please try using Advanced Mode. simple Mode WILL NOT work on all systems

Not all systems have the Recovery Environment for Windows installed. Many OEMs will replace the default recovery environment with their own, and Windows updates may also change the included files in this system.

Contents:

Selecting the "Advanced Mode"

Downloading and Installing Windows ADK

NOTE: We Suggest to use Windows ADK for Windows10, version 1803

IMPORTANT: Make sure that you have Windows Preinstallation Environment (Windows PE) and Deployment tools checked.

ADK Installation Notes

Creating the Boot disc image

USB Method

Creating Image/DR Restore Boot media to USB flash drive alternate instructions

CD/DVD Method Using Windows Disc Image Burner

Helpful Tips

Selecting the "Advanced Mode"

Click on the Image Backup button

Creating Image/DR Restore Boot media to USB flash drive alternate instructions

Click on Launch Image Backup Tool for Backup/Restore/Boot CD Creation

Click on Boot Disc

Choose Advance and click next.

Downloading and Installing Windows ADK

If youdon'thave Windows ADK installer, adksetup.exe, download it from the Microsoft website. (You can skip this if you already have the Windows ADK installed)

[Go to Download Site] will download adksetup.exe to your default download location.

If the downloaded file is automatically renamed to prevent conflicts, such as to adksetup (1).exe, take note of the filename and location for the next step.

Select [Browse]

After locating the adksetup.exe file you just downloaded, choose [Open], followed by [Install]

[Yes] to continue

Select [Next] to continue.

Select [Install]

This step Will take time, as it needs to download the ADK files from the internet, extract and install them.

Once complete, [Close] the "Windows Assessment and Deployment Kit" installation window.

Select [Next] after closing the ADK Installation window.

NovaBACKUP will look for the installation automatically. If it is not found you will need to locate the installation folder for the Assessment and Deployment Kit. the default path would be:C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit

ADK Installation Notes

NOTE:

We Suggest to use Windows ADK for Windows10, version 1803:

https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install

This version will show as 10.1.17134.1 when installed

Direct Download Link for version 1803 adksetup.exe:

https://go.microsoft.com/fwlink/?linkid=873065

IMPORTANT:

If installing adksetup.exe manually, make sure that you haveWindows Preinstallation Environment (Windows PE) andDeployment tools selected to install.

Creating the Boot disc image

If you have additional drivers or applications you would like to add to boot disc, click on Show optional files list then click on [Browse] to add your drivers/applications.

Here is where you can add: Raid/storage controllers, special network drivers,etc.

If youdon'thave any special drivers or applications to add, you can click on create image to start the process of creating your bootable recovery environment image.

This dialog will likely display a (Not Responding) indicator while running,This is Normal Behavior, do not close the window.

Once The Image Creation is complete the message at the Bottom Left will change to: "Process completed successfully, click Next to continue."

Bootable USB Method

From here we are going to write the boot image onto your USB flash drive.

Some tips to remember:

The USB Flash drive must be 512Mb to 16Gb in total space on the drive. Your USB Flash drive will be erased during this process.

If no devices appear in this list (unlike in the images below), select "Just create ISO file, do not write to boot media" and choose [Finish]. You will need to use another utility to create a bootable flash drive, such as Rufus or PenDriveLinux.

Locate your USB drive and click Finish to start the writing process to the USB.

Once it says, process completed you are finished and have successfully created your bootable recovery USB drive.

CD/DVD Method Using Windows Disc Image Burner

From here we are going to write the boot image onto your CD/DVD using Windows Disc Image Burner.

If no devices appear in this list, select "Just create ISO file, do not write to boot media" and choose [Finish].

Copy the Source of where your bootable recovery image is and locate that directory in Windows Explorer. (You can copy the source destination and paste the directory into windows explorer or you can search for the folder)

Look for DRBoot.iso as this is your bootable image file. Right click on the file and open with Windows Disc Image Burner. (Note: If Windows Disc Image Burner does not show up first on your selections, then you may have a 3rd party burner software installed on your computer that you can use. If you don't have Windows Disc Image Burner or a 3rd party burner software installed on your computer then you would want to look for a 3rd party burning software online and use that to burn your image file.)

When the Windows burner program pops up, select the CD/DVD drive you want to burn the image to. Afterwards, click Burn. (You can check the Verify disc after burning to check the integrity of the disc.)

After the burning process is completed, you will have burned your bootable recovery image onto a CD/DVD.

Helpful Tips

Windows 10 ADK contains additional drivers to support newer chipset motherboards, newer video cards, and USB 3.0 in general.

The USB Flash drive must be 512Mb to 16Gb in total space on the drive. The Boot disk is normally around 400Mb.Your USB Flash drive will be erased during this process.

If you want to use a USB flash drive for the boot disc but have other files and folders on the USB flash drive; you can copy the files and folders to your computer, write the recovery image to your USB flash drive, then paste the files and folders back on the USB flash drive if needed.

NovaBACKUP PC/Server/BE 19.x and newer

You are using a share as a backup target. You want to restore files from this backup file, which is on a share, or you want to import this file again. The restore or import will run for a few seconds, but nothing will be restored or imported.

If you want to import a file or restore from a file, and this file is on a share, then NovaBACKUP (NBK) needs full access rights to this share.

Several approaches are possible:

1. Copy file to a local drive, e.g. USB drive

Simplest, but most storage intensive and time-consuming variant.NBK has direct access to local drives, usually no permission adjustments are necessary.

2. Map drive letters to UNC path

Right-click "Network" => "Connect network drive..." => Select UNC path to file and enter login data.In NovaBACKUP "Restore" tab select drive/path/file to import/restore.

3. Enter network credentials under "Restore"/"Import"

In the NovaBACKUP GUI under "Restore" by clicking on "Settings" => tab "Run under" enter a user who has full access rights to the share.

4. Change service "NovaStor NovaBACKUP Backup/Copy Engine" to another user

By default the service "NovaStor NovaBACKUP Backup/Copy Engine" runs under the local system account. With this the service has no direct access rights to shares! For the time of the recovery you may change this service to a user with full access rights to the share. After the recovery, return this service to the local system account.

On the NovaStor support website you can search for "NAS" to find more articles with a description of the permission settings. NovaBACKUP is not able to get extended access rights on its own and depends on appropriately configured access rights. Please also note that anti-virus software and/or other security settings may prevent NovaBACKUP from backing up files!

AMo

NovaBACKUP PC/Server/BE v19.x and newerIf you are unable to install any of the NovaBACKUP software and receive a message that the software installation ended prematurely there are a few potential causes and fixes.

If you experience a failed installation of NovaBACKUP v19.1.x or newer, where the installation or upgrade ends prematurely, you can attempt the fix that we have for this by reading the Knowledge Base article Fix for NovaBACKUP v19.x fails to install due to existing DR Drivers.

Please try the following before continuing:

Reboot your machine before trying again

Temporarily disable all Anti-virus, Anti-spyware, Anti-ransomware, Anti-malware and Firewall software

You should open Task Manager and make sure the following processes are not running (End Task if they are) before running the setup file:

drdiag.exe | nsCtrl.exe | NovaBackX.exe | nsService.exe | ManagementServer.Agent.Service.exe

Please make sure to open the downloaded setup file (usually in your Downloads folder) by utilizing Right-Click->Run as Administrator

If none of these help resolve the issue we recommend to submit a support ticket and include advanced logs

The following ADVANCED sections are included in this article:

Other Backup Software or Antivirus Software

Old NovaBACKUP Installations

Corrupted Internet Explorer Settings

Clear Temporary Directory on Windows

Try a Command Line installation (Advanced)

NOTE: Activation failures can occur when attempting to activate the software while connected to VPN or Proxy networks.

Other Backup Software or Antivirus Software

Verify that no other Backup Software is running and that all Antivirus Software is removed or disabled during installation. Once installed, How To Temporarily Disable Your Anti-Virus, Anti-Malware and Firewall Programs to install NovaBACKUP.

<top>

Old NovaBACKUP Installations

Older copies of NovaBACKUP could still be installed on your system. Try removing the NovaBACKUP software, rebooting your computer, and then reinstalling. NOTE: Make sure to clear the checkbox that asks: "Remove all logs and media indexes" in to keep your previous settings and history.

If you are updating from NovaBACKUP 19.0 to 19.1 and are experiencing difficulty:

Follow these instructions to download a .reg file to remove previous drivers from the Windows Registry:

First, make sure that you are logged in to Windows as a user with Administrator rights. If you are NOT logged in as a user with Administrator rights currently then these instructions will not work because there will not be enough rights to perform the actions necessary.

Using your web browser download the simple registry (.reg file) fix for this installation issue by clicking this link to download the fix, and be sure to take note of where the file is saved to: http://filestore.novastor.com/Downloads/NovaBACKUP/19.1/NBK_DRDrivers_Remove.zip

NOTE: If your anti-virus or anti-malware real-time protection software blocks .reg files from being saved then you may need to temporarily disable that software while you download and run this registry fix. You can re-enable the software after the fix is performed, and the software has installed.

Merge the .reg file into your registry (double-click the .reg file)

There will be two prompts minimum, choose Yes or OK for all prompts to continue.

Reboot the machine

Run the NovaBACKUP Setup.exe file again

<top>

Corrupted Internet Explorer Settings

Older or corrupted configurations of Internet Explorer can cause Windows Installers to fail in specific situations. Try resetting the Internet Explorer Default Settings.

<top>

Clear Temporary Directory on Windows

Open Windows File Explorer

In the address bar navigate to your temporary files directories

%TMP% [enter] and %TEMP% [enter] (both exist, but may be in different locations)

Once in each of these directories, remove any files found, these are all temporary files that were not cleaned up by other software.

Permissions issues with the Windows Temporary directory can also cause issues with temporary installation files.The instructions below allow you to change the default temporary files directory:

Right click on "This PC" and choose Properties.

Click on Advanced System Settings on the left navigation bar.

On the Advanced tab, and click on the button [Environment Variables]

Make a note of the current TEMP and TMP directories for use after the installation

Select the TEMP variable, and click [Edit]

Change the value to C:\TEMP and click [OK]

Select the TMP variable, and click [Edit]

Change the value to C:\TMP and click [OK]

Open This PC, go to your C:\ directory, and create new folders called TEMP and TMP

Reboot your computer.

Attempt to install NovaBACKUP again

<top>

Try a Command Line installation (Advanced)

NovaBACKUP client Installer fails on activation of either trial or licensed version; workaround install via command line

Start an Administrative Command Prompt.

Change to your own user's Downloads folder by entering:

cd \Users%USERNAME%\Downloads

After changing to the correct folder where the NovaBACKUP Setup-NB-*.exe is located, issue this command to start a silent installation:

Setup-NB-PC.exe /q /ComponentArgs "Backup Client":"/q /log c:\setuplog.txt"

The above command performs the following: calls the executable, tells it to run quietly (no visible prompts), tells the embedded msi installer to run quietly, tells the embedded msi installer to generate a log file at c:\setuplog.txt.

If the downloaded filename is different than Setup-NB-PC.exe you will need to use the filename of the downloaded setup file that is on your machine.

When that task runs you can see that it is running by looking at your Windows Task Manager and in the Processes or Details area look for Setup-NB-*.exe in the list of processes running and when it is done it will no longer list that processes as being active when it is done running.

Now look for the NovaBACKUP desktop shortcut to see if it was created after that install completed. If it is in fact listed then the software is installed.

If there is no desktop icon after 10 minutes, the installation did not succeed. Please attach the C:\setuplog.txt file to a Support Ticket

<top>

Welcome to the NovaStor Help Center.

The NovaStor Help Center is designed to provide a complete self-service support option for our NovaStor customers. The Help Center is made up of two parts: a knowledge base and a community. You can search for knowledge base articles to learn a task or create a ticket for NovaStor SMB or Enterprise software. If you cannot locate the answer in the knowledge base then you can submit a support request. You are able to manage your own tickets after logging in to the Help Center to be able to view the history on the tickets as well as respond directly to your ticket.

NovaBACKUP PC, Server, Business Essentials

The NovaBACKUP Quickstart Guide (Getting Started with NovaBACKUP 19) (PDF) is a simple step-by-step guide designed to get you started performing backups quickly and efficiently with NovaBACKUP v19 and above. The NovaBACKUP Quickstart Guide covers Performing File Backup, File Restore, Image Backup, and creating your Image Backup Boot Disc.

View the PDF guide here.

While the above guide is meant to be a simple introduction, more comprehensive guides exist for various configurations, see the following suggested how-to articles and how-to videos using the Support Knowledge Base links below.

New to NovaBACKUP? Start Here

[Guide] NovaBACKUP PC (Home User) Configuration Walkthrough

This walkthrough will describe how to create 2 alternating File backups, one Copy job for your photos, and a Disaster Recovery Image Backup, all on a Schedule. This is designed for Home Users that want to backup data, but don't need a daily backup schedule (see "[Guide] Standard Backup Schedule with Retention" for a full schedule).

Backup With Retention Walkthrough (Video)

This step-by-step how-to video will walk you through setting up a scheduled file backup job in NovaBACKUP while utilizing data retention so that you don't run out of space over time.

Getting Started: Connecting to Your NovaBACKUP Cloud Storage

This article will walk you through connecting to your NovaBACKUP-hosted Cloud Storage account. This is a service that is included on some license keys starting in Q4 2019.

Keep Multiple Copies of your Backups

Use more than one device for your backups, ideally alternating between devices regularly to avoid a single point of failure.

The 3-2-1 rule of backup: 3 copies, 2 types of media, 1 offsite

Plan your Storage Space Requirements

NovaStor has a Storage Calculator! Check it out at backupcalculator.com

Keep 15% Free Space available on your storage device

Mechanical Hard Drives encounter physical issues once they become 85% Full, the performance degrades fast.

Theresno specific number or percentage that fits every Windows PC. All Microsoft will tell you is that you need 20 GB of space before you install a 64-bit Windows 10 system on a modern PC. After that, youre on your own.

The rules of thumb can help. If you have a mechanical hard drive, leaving at least 15% of it empty can reduce fragmentation in newly created files and make it easier for Windows to properly defragment the drive, which is something modern versions of Windows do automatically in the background. If youdon'tleave enough empty space, Windowswon'tbe able to move files around to defragment them and the contents of the drive will become fragmented and slower to access over time. If you have an SSD, this doesnt apply.

If you have an SSD, leaving at least 25% of the SSD empty will ensure you have excellent performance. On modern SSDs with overprovisioning, this is probably much too conservative, and even 10% could be an okay number. It really depends on the SSD.

If you need to temporarily fill your drives up and only have 5% of disk space to spare, thats not a problem. Things will just slow down over time, so youll probably want to free up some space when you can.

For more detail, review How-To Geek | How Much Free Space Should You Leave on Your Windows PC?

If your drive runs out of space while a backup is being performed, the backup file that was in progress will be corrupted, and will not be able to be imported into the software to recover data from in the future.

Types of Backups

Image Backup (Disaster Recovery)

An image backup is different than a standard file backup. It is intended to backup theunderlying data structures of a computer including operating system and applicationsfor emergency restoration in the event of a disaster. In this case your destination maybe a completely different computer or set of hardware.

File Backup

A standard file backup is simply an archive of data that may be restored in the eventof data loss. This is archive is generally made from the files which you select as beingimportant (or an entire file system) and may be encrypted, or compressed.

Types of File Backup Jobs:

Full Backup

A backup of all (selected) files on the system. This does not include fileallocation tables, partition structure and boot sectors.

Differential Backup

A cumulative backup of all changes made since the last full backup.

Benefit: Only 2 files ever required to perform a restore (1 Full and 1 Differential).

Downside: Larger file sizes

Incremental Backup

A backup that only contains the files that have changed since the mostrecent backup (either full or incremental). Technical Support does not recommend using Incremental backups in most instances.

Benefit: Small file size with incremental backups.

Downside: May require many files to restore which can be time consuming. More prone to user error

Suggested Support Articles to read:

Backup Job Types and Modes

Backup Job Types and Modes This guide will walk you through the different backup job types and modes available in NovaBACKUP to help you understand the differences between them. Covered are File Backup, Image Backup, and Copy jobs along with their modes Full, Differential, Incremental, etc.

[Guide] NovaBACKUP PC (Home User) Configuration Walkthrough

[Guide] NovaBACKUP PC (Home User) Configuration Walkthrough This walkthrough will describe how to create 2 alternating File backups, one Copy job for your photos, and a Disaster Recovery Image Backup, all on a Schedule. This is designed for Home Users that want to backup data, but don't need a daily backup schedule (see "[Guide] Standard Backup Schedule with Retention" for a full schedule).

[Guide] Standard Backup Schedule with Retention

[Guide] Standard Backup Schedule with Retention This step-by-step guide will walk you through how to create, schedule, and implement a backup schedule. This includes a weekly Full file backup, daily Differential file backup, Retention, and a monthly Image Backup. This is the recommended way to backup all of your data while making sure that you don't run out of space over time.

What is the best practice for backing up and protecting my data

What is the best practice for backing up and protecting my data Our basic suggestions for best practices surrounding data backup and recovery with NovaBACKUP software. This includesusing more than one device for your backups, ideally alternating between devices regularly to avoid a single point of failure. (3-2-1 rule of backup: 3 copies, 2 types of media, 1 offsite).

Boot from recovery disc and restore an image backup for a disaster recovery

Boot from recovery disc and restore an image backup for a disaster recovery This step-by-step guide will walk you through booting your recovery disc from your PC and restoring an image backup for a disaster recovery.

Create an image backup

Create an image backup This guide will providestep-by-step instructions on how to create a one-time, manualimage backup. This process is only meant to createa one-timeimage backup and all of the steps haveto be donemanually. If you wish to have image backups run ona set schedule please follow this article regarding creating a scheduledimage backup job withretention policy to delete oldest image backups automatically.

Create a recovery boot disc in Simple Mode

Create a recovery boot disc in Simple Mode This step-by-step guide will assist you in creating a recovery boot disc for USB and CD/DVD using simple mode. NOTE: If you are unable to create a boot disk using Simple Mode FOR ANY REASON, please try using Advanced Mode. Simple Mode WILL NOT work on all systems as not all systems have the Recovery Environment for Windows installed.

Create a recovery boot disc in Advanced mode (with ADK instructions)

Create a recovery boot disc in Advanced mode (with ADK instructions) This step-by-step guide will assist you in creating a recovery boot disc for USB and CD/DVD using Advanced mode. It also has instructions for downloading and installing the Windows ADK.

How To Import & Restore .NBD Backup files

How To Import & Restore .NBD Backup files A collection of links to some of our Knowledge Base articles on the subject of importing backups (.NBD) and Restoring files/folders from a backup that was imported into the Restore tab.

Restore Image Backup using 19.2 or newer boot disk

Restore Image Backup using 19.2 or newer boot disk Version 19.2 introduced a new Disaster Recovery boot disk (DRBoot) for restoring an Image Backup of a System Partition.This article will show the steps required to perform a Restore from an Image Backup file (Full - .NDF, Differential - .NDD, or Incremental - .NDI)

Backup with to NAS with Retention Walkthrough

Backup with to NAS with Retention Walkthrough This step-by-step guide will walk you through setting up a scheduled file backup job in NovaBACKUP combined with configuring a data retention policy so that you don't run out of space over time. This guide does not cover creating a scheduled image backup job, for a guide that covers that click here.

Exclude NovaBACKUP Files and Directories from Active Anti-Virus and Anti-Spyware Scanning

Exclude NovaBACKUP Files and Directories from Active Anti-Virus and Anti-Spyware Scanning Occasionally, certain Anti-Virus software may incorrectly flag or interfere with your NovaBACKUP software from properly running. This can result in a failed backup job, unusually slow backup speed (transfer rate), failure for the application to start entirely, or the inability to see destinations to backup your files to. Please also confirm no files shown here have been quarantined by your Antivirus software if you cannot find the file in the listed location.

From the NovaBACKUP Blog

Differential and Incremental backups: Why should you care?

Differential and Incremental backups: Why should you care? An article describing Differential and Incremental backup methods as utilized in NovaBACKUP and how they work.

Suggested Support Videos to watch:

Complete Backup and Creating a Backup Schedule (Video)

Complete Backup and Creating a Backup Schedule (Video) This step-by-step how-to video shows one of NovaStor's customer support technicians setting up a complete backup plan for a customer.

Backup With Retention Walkthrough (Video)

Backup With Retention Walkthrough (Video) This step-by-step how-to video will walk you through setting up a scheduled file backup job in NovaBACKUP while utilizing data retention so that you don't run out of space over time.

Restoring Files in NovaBACKUP

Restoring Files in NovaBACKUP This step-by-step how-to video shows how to restore files from both file-based backups, and also how to extract files from system image based backups.

Restore Image Backup using 19.2 or newer boot disk

Restore Image Backup using 19.2 or newer boot disk This step-by-step how-to video shows how to restore Image-based backups.

Keep an eye on the NovaBACKUP Support Knowledge Base for additional suggested instructional guides.

NovaBACKUP BE v19.x and newer (2019-04-16)

If a particular VM cannot be backed up, but all other VMs can be backed up, the cause can usually be found within the VM. Often the Hyper-V VSS host cannot create a checkpoint (= shadow copy) for such a VM. You will then find a corresponding message in the Windows Event Viewer on the Hyper-V host and within the VM in the Event Viewer "Application" and/or "System". Please check the Event Viewer for such messages, determine the cause of the messages and correct it.

Here you can find the event viewer for the HyperV role on the Hyper-V host:

Open Windows Event Viewer.Goto "Application and Services Logs" => "Microsoft" => "Windows" => "Hyper-V-VMMS" => "Admin"For the backup of Hyper-V VMs NovaBACKUP BE requests a checkpoint from the Hyper-V host. If the Hyper-V host cannot create a checkpoint and make it available as a backup source, the backup terminates.

If you install the CMon the installer will ask you for the IP address of the CMon server.Three options (3rd is recommended) are possible:

Only internal clients connect to CMon:Configurethe local IP of the server. Clients from outside your LAN will not be able to access the CMon.

Only outside clients connect to CMon:Configure the external IP.Internal clients will not be able to connect to the CMon.

Outside AND inside clients (recommended method)Use an URL that is registered in your DNS, e.g. cmon.yourdomain.com. During the installation ofthe CMon enter this URL, do NOT enter an IP address. On the client enter this URL in the default settings => tab "CMon Server".

If you want to start the CMon GUI on the CMon server itself and you configured an URL (not IP), then you have to add the following line to your local hosts file "C:\Windows\System32\drivers\etc\hosts":

cmon.yourdomain.com<local IP address of CMon server>

NovaBACKUP Cloud Port / xSP / RWF all Versions

Where can I find the masterlog.txt?

The masterlog.txt is the central protocol file of the storage server. The storage server is the backup server and is technically identical in all editions (Cloud Port / xSP / RWF).Most of the messages in masterlog.txt can also be found in the Windows Event Viewer "Application". However, the masterlog.txt contains additional specific messages. Therefore the technical support of NovaStor asks for the transmission of the masterlog.txt for further analyses.

By default, the masterlog.txt is always stored in the installation directory of the storage server:

"C:\Program Files\NovaBACKUP Storage Server"

Depending on the setting, the masterlog.txt is regularly archived and recreated. Therefore, the directory contains the current active masterlog.txt and many archived files with the naming scheme

Masterlog Month Day, Year Time.txtExample:Masterlog Apr 15, 2019 04.00 PM-0.txt

You can also move the masterlog.txt to another directory. This prevents the C: drive from being filled with log files. To determine the location of the masterlog.txt and move the masterlog.txt if necessary:

On the storage server, open the Configuration Manager and click on the "Logging" tab:

Figure 1: Configuration Manager

The currently set storage location of the masterlog.txt can be found in the yellow area of the Configuration Manager (see Figure 1). In these settings you can also modify the storage location and adjust the maximum size of the masterlog.txt. If the masterlog.txt reaches the set size, it is archived and a new active masterlog.txt is created. Depending on the situation, it may be helpful for an analysis to also send the last archived masterlog file to support.

AMo

NovaBACKUP BE v19.x and newer

By default, a SBS creates 2 snapshots per day automatically. After a few days/weeks no temporary snapshot slot for NBK is available, depending on the configuration of the shadow copies. After deleting the Windows snapshots, NovaBACKUP can request snapshots again.

Deactivate the scheduled shadow copies of the SBS:

Image 1: Settings of scheduled shadow copies

Deactivating the shadow copies deletes the existing shadow copies. This can take some time, depending on the number and size of the existing shadow copies.

Alternatively, select individual shadow copies in the lower window and delete them. This creates space for new shadow copies. However, the planned executions will occupy this space again after some time.

Compare the specifications in the GUI (above) with the output of the command

vssadmin list shadows

and

vssadmin list shadowstorage

The size output in the command must match the specifications in the GUI. If there are differences, clean up the shadow copies.

Too many shadow copies can lead to increased latencies on hard disk accesses. This leads to timeouts and the NovaBACKUP backups remain in the shadow request status.

AMo

NOTE: This article explains how to remove all traces of NovaBACKUP from a computer, for a standard uninstallation of the software please see How To Completely Uninstall NovaBACKUP PC, Server, or Business Essentials

NOTE: Windows XP,Windows Server 2003, and Windows Vista are NOT supported by NovaBACKUP version 18 and newer. The software will not be able to install on those OS's.

There are times when only a CLEAN uninstall and removal of the NovaBACKUP software will be able to clear up various issues relating to possibly corrupt configuration data, etc. Even if you think that NovaBACKUP was removed, these clean uninstall steps often need to be utilized to remove all traces of the software.

This is the guide for performing a clean uninstall and reinstall of current NovaBACKUP software including Professional (PC), Server, and Business Essentials.

This guide is required to be used for if you are attempting to install NovaBACKUP current version, such as v19.0, on a computer that has an old version of NovaBACKUP installed that is more than a couple of major versions old. Versions older than v16.5 will not be able to upgrade to the current version of NovaBACKUP directly, and must perform all of the steps in order for the new version to work.

Clean Uninstall Instructions

1. Stop Running Tasks using Task Manager

Press [Ctrl], [Shift], and [Esc] keys simultaneously to open the Task Manager window.

Select Show Processes from all users at the bottom of screen

Verify drdiag.exe, ManagementServer.Agent.Service.exe, NovaBackX.exe, nsCtrl.exe, and nsService.exe processes are not active. Select each of them and select End Process / End Task if they are still active.

2. Use Windows Uninstall option

From Programs and Features (or Add/Remove Programs), select NovaBACKUP from the list and perform an Uninstall; make sure to enable the checkbox to "Remove jobs and data" so that it does not keep the old jobs and configuration data around. The backup files (.NBD or .NDF files) on your destination storage device will not be removed. If you will be using NovaBACKUP again, Make Sure to NOT CHECK this option.

3. Delete All traces of NovaBACKUP application files

If you will be using NovaBACKUP again, skip any mention of removing C:\ProgramData

On x64 (64-bit) Vista, Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2016:

C:\ProgramData\NovaStor\

C:\Program Files\NovaStor\

On x86 (32-bit) Vista, Windows 7, Windows 8, Windows 10, Windows Server 2008:

C:\ProgramData\NovaStor\

C:\Program Files (x86)\NovaStor\

On x86 (32-bit) Windows XP and Windows Server 2003:

C:\Documents and Settings\All Users\Application Data\NovaStor\ C:\Program Files\NovaStor\

4. Clean up Windows Registry entries that may still exist:

A. Simple Registry Method

Now using your web browser, download the simple registry (.reg file) fix for this installation issue by clicking this link to download the fix, and be sure to take note of where the file is saved to:

NBK_DRDrivers_Remove.reg

Alternatively, you can download the fix in .ZIP format. If you use this method, you may need to extract the .reg file out of the .zip file to continue to the next step:

NBK_DRDrivers_Remove.zip

NOTE: If your real-time protection software or browser blocks .reg files from being saved, you may need to temporarily disable that feature, or download the .zip version.

Now using Windows Explorer locate the NBK_DRDrivers_Remove.reg file and then simply double-click that file. If your user has the required administrator rights, answer Yes to the prompt(s). There may be one or two prompts depending on your system settings.

When successful there will be a confirmation screen that states The keys and

values contained in NBK_DRDrivers_Remove.reg have been successfully added to

the registry., you can click the OK button to complete the fix.

B. Advanced Registry Method

Using the Windows Registry Editor regedit.exe you can remove the root references to NovaBACKUP. If you have not used regedit.exe before, please do not attempt this process, as it can corrupt your Windows Installation. Once the Registry Editor program is loaded you will delete these particular registry keys:

'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Backup Client Agent Service'

'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NsService'

'HKEY_LOCAL_MACHINE\SOFTWARE\NovaStor'

'HKEY_CURRENT_USER\SOFTWARE\NovaStor'

5. Delete the NovaBACKUP license and activation files used by every version of NovaBACKUP that has been installed.

In order to see this hidden folder named C:\ProgramData you will have to enable " Show hidden files, folders, and drives " option (for a how-to read this guide ) in Windows Explorer or just paste directly in to Windows Explorer as the path C:\ProgramData

If the operating system is Windows Vista/ 7/ 8/ 10, Windows Server 2008/ 2008 R2/ 2012/ 2016/ 2019, navigate via Windows Explorer to:

C:\ProgramData\

Once inside the C:\ProgramData\ folder: Delete any NovaBACKUP related license files with the file extension *.lic. Next, delete nsActivation.act.

If your operating system is Windows XP or Windows Server 2003 then the instructions differ and the folder structure to navigate to via Windows Explorer will be:

C:\Documents and Settings\All Users\Application Data\

Once inside the C:\Documents and Settings\All Users\Application Data\ folder: Delete any NovaBACKUP related license files with the file extension *.lic. Next, delete nsActivation.act.

6. Uninstall Disaster Recovery Imaging via Windows Uninstall (if it exists)

Go to your Programs and Features (or Add/Remove Programs) area of Windows and then look or search for the item "Disaster Recovery Drivers", and right-click on that item and then click Uninstall. (This may or may not exist on all systems)

7. Run a Registry Cleaning utility after modifying the registry

In addition to deleting the old NovaBACKUP registry keys that is instructed in Step 4 you will also run the Registry Clean function of the freeware CCleaner software. CCleaner is a Windows Registry Cleaner and needs to have the Registry Clean function executed three times. Download the freeware program CCleaner at this direct link:

http://www.piriform.com/ccleaner/download/standard

This webpage will show you what you need to click on inside the free CCleaner software to perform the Registry Clean operation: http://www.piriform.com/docs/ccleaner/using-ccleaner/registry-cleaning and http://www.piriform.com/ccleaner/tour/registry-cleaner

8. Reboot your computer.

This part is very important, if you do not reboot it won't finish the registry clean.

9. Confirm these Windows services are uninstalled:

'Backup Client Agent Service'

'Disaster Recovery Imaging'

'NovaStor NovaBACKUP Backup/Copy Engine (nsService)'

'NovaStor NovaBACKUP Virtual Disk Mount Service (nsMountService)'

If one of these services is visible in services.msc, open an administrative command prompt (right mouse click on cmd icon and "run as administrator") and delete the service with command:

sc delete <name of service>

e.g.

sc delete "Backup Client Agent Service"

sc delete "Disaster Recovery Service"

sc delete nsMountService

sc delete nsService

Reboot your computer again in case you had to delete any services!

Re-Install Instructions

10. Stop Active Protection Software

Stop any running Anti-Virus software and stop any firewall process including Windows Firewall or the firewall component built in to your Anti-Virus software such as McAfee and Symantec.

11. Install NovaBACKUP latest version (linked below).

Here are the Direct Download Links to the Current NovaBACKUP version to match your product type (always available at novabackup.com/downloads ):

http://filestore.novastor.com/Downloads/NovaBACKUP/Current/Setup-NB-PC.exe

http://filestore.novastor.com/Downloads/NovaBACKUP/Current/Setup-NB-Server.exe

http://filestore.novastor.com/Downloads/NovaBACKUP/Current/Setup-NB-BE.exe

12. Run the downloaded Setup File

Install NovaBACKUP latest build mentioned above and after a successful installation, do the following:

13. Reboot the computer.

14. Launch NovaBACKUP

Log on to the computer and launch the NovaBACKUP software via the desktop shortcut and test out creating a manual backup job to see if the error still occurs.

15. Still having trouble? Submit a Support Ticket.

If the same installation or upgrade error occurs and you have a valid support contract, submit a ticket in our ticket system with the screenshot of the error or all of the logs. The NovaStor Logging Application to gather all of your logs is available for download here, including the instructions on how to utilize it.

16. For Advanced Users only:

NOTE: If you are uncomfortable making changes to the Windows Registry, please skip this step and see Step 17 below.

If you still cannot get NovaBACKUP software to install or upgrade, meaning you cannot proceed beyond Step 12, then you can perform the following Windows Registry searches to remove the leftover registry entries that CCleaner could not locate and remove for you in Step 7.

Run regedit.exe.

Once the Registry Editor loads, navigate to (highlight) the root level "Computer".

Open the "Find" dialog (CTRL+F). Make sure to "Look At" Keys, Values & Data and to "Match whole string only". (all check-boxes selected)

Search for, and remove, any Key with a reference to:

"NovaBACKUP"

AND "NovaStor"

(Helpful hint: F3 is Find Next) You should remove each Key (folder) associated with each value (file).

Close Registry Editor.

Reboot the machine to apply registry changes.

Log back in and attempt step 12 again to install NovaBACKUP.

17. Simple registry removal instructions, using a .reg file

This method is in case you are still stuck, or you are not experienced enough with the Windows Registry Editor to attempt Step 16:

Use NBK_NovaBACKUP_x64_Remove.reg to remove known registry entries.

As an alternative to Step 16, and for the less experienced users who are not familiar enough or afraid they may make a mistake utilizing the Windows Registry Editor application, you can try the easy registry removal method detailed here.

You will download and execute a file which will be able to remove all of the NovaBACKUP client related registry keys that are probably the reason at this point in the guide that NovaBACKUP will not install after performing all of the above steps.

This NovaBACKUP registry key removal method will only remove the NovaBACKUP client related items, including any DR Drivers (Disaster Recovery/Image Backup), and will not touch other NovaStor software such as NovaStor CMon (Central Monitoring Console), NovaStor Granular Restore tools, or NovaStor DataCenter.

Currently this fix method will only work on a Windows 64-bit operating system.

The simple registry removal instructions are as follows:

First, make sure that you are logged in to Windows as a user with Administrator rights. If you are NOT logged in as a user with Administrator rights currently then these instructions will not work because there will not be enough rights to perform the actions necessary.

A. Using your web browser download the simple registry (.reg file) fix for this installation issue by clicking this link to download the fix, and be sure to take note of where the file is saved to:

NBK_NovaBACKUP_x64_Remove.reg

Alternatively, you can download the fix in .ZIP format. If you use this method, you will need to extract the .reg file out of the .zip file to continue to the next step:

NBK_NovaBACKUP_x64_Remove.zip

NOTE: If your real-time protection software or browser blocks .reg files from being saved then you may need to temporarily disable that software while you download and run this registry fix. You can re-enable the software after the fix is performed.

B. Using Windows Explorer locate the NBK_NovaBACKUP_x64_Remove.reg file and simply double-click it to merge changes. If your user has the required administrator rights then answer Yes to the prompt(s), there may be one or two prompts.

When successful there will be a confirmation screen that states "The keys and values contained in NBK_NovaBACKUP_x64_Remove.reg have been successfully added to the registry.", you can click the OK button to complete the fix.

C. Reboot the machine to apply registry changes.

D. Log back in and attempt step 12 again to install NovaBACKUP.

18. Install still not working? Try a Command Line Install.

If the installation proceeds to the activation step and displays an error, please follow the instructions on how to perform a command line install found here.

Image Backup vs File Backup

The method that is used to create an Image differs from File-Based backups, as it does not look directly at the files and folders located on your machine. An Image Backup looks only at the data "blocks" that are stored on your Hard Drive.

If you have successfully performed an Image Backup in versions of NovaBACKUP previous to 19.1

There were updated Image Backup drivers utilized in NovaBACKUP version 19.1, and there may be remnants of the previous Image Backup drivers on your system that were not updated or removed.

Please read the following article on how to remove and repair these drivers: Repair the Image Backup Drivers

After performing this removal please re-install NovaBACKUP 19.1 or newer using the Setup-NB-xx.exe file you originally downloaded. When the setup starts:

Choose the "Maintenance" option and wait for the files to extract.

When the NovaBACKUP Setup dialog appears select "Next",

followed by "Repair".

When the repair finishes you can close the window that shows "Maintenance" (from the first step).

Some common problems:

Microsoft VSS

Image Backups utilize Microsoft VSS (Volume Shadow copy Service) to create a copy of the currently running environment (Open Files) for backup purposes.

Microsoft VSS Troubleshooting

Hardware Problems

Problems with hardware storage devices, such as disk errors or bad CD/DVDs left in the drives, will cause an Image Backup to fail.

Troubleshooting

As an Image backup can fail for numerous reasons, a few common things to look out for are:

Restart the Disaster Recovery Imaging service.

Open the services administrative tool by typing "services.msc" into a run dialog. Select "Disaster Recovery Imaging" from the list and choose "Restart the service". You can now try to run your Image Backup again.

Reboot the machine

Ensure you are not imaging a Microsoft System Reserved Partition with zero (0) size or any EFI partitions.

Verify there are no disk errors on the partition you are trying to image from by using the Event Viewer administrative tool.

Look at the Windows/System log and filter to show "Errors" and "Critical" and use the Event Source drop-down to choose "Disk" and "ntfs".

If disk errors are found, schedule a Check Disk for the next restart from administrative cmd prompt: "chkdsk /F /R"

Ensure the target drive is not full.

If you are backing up to an external drive that is 2TB or larger ensure it is GPT (GUID Partition Table)

Link: NovaBACKUP requires GPT for hard drives that are 2TB and larger

A 2TB or larger drive with partition style of MBR (Master Boot Record) will cause random Image Backup failures.

If you currently have or previously installed other programs that were able to perform an Image Backup, they can sometimes leave parts behind that will prevent an Image Backup from completing. Please refer to their documentation on how to clean-up after them.

If you are currently using any continuous backup programs you will need to disable them to complete an Image Backup.

Verify VSS is working correctly:

You can verify that VSS is "State: [1]: Stable" for all entries in an administrative cmd prompt: "vssadmin list writers"

Rebooting the machine will normally correct VSS Writer state issues

VSS may have some shadows saved, check for them in an administrative cmd prompt with: "vssadmin list shadows"

Remove any shadows that are found with: "vssadmin delete shadows /all"

Run a System File Check

Click the Start orb and then type cmd in the Search programs and files field.

In the results area, right-click cmd.exe, and then click Run as administrator. You will be prompted to type the password for an administrator account. Click Continue if you are the administrator or type the administrator password. Then, click Continue.

At the command prompt, type "sfc /scannow", and then press ENTER.

The scan may take some time, so be patient. Windows will repair any corrupted or missing files that it finds

For Network locations ensure you have added a Network Device on the Device tab of the main NovaBACKUP interface and selected it as the backup destination.

Link: Create a NAS Device for NovaBACKUP

If you are receiving the following error, please try resizing the partition the error is being reported on 100MB to 200MB smaller that it is currently using Windows Disk Management

C0000011

STATUS_END_OF_FILE

The end-of-file marker has been reached. There is no valid data in the file beyond this marker.

How-To Geek | How to Manage Partitions on Windows Without Downloading Any Other Software

These are common problems only and can usually be solved if you check them in order.

If these steps do not work, let us know by creating a support ticket at www.novabackup.com/ticket

Once your ticket is submitted, please generate advanced logs and reply to the confirmation email with the LogCollector ".zip" file as per the instructions found here:

http://novabackup.com/log

See Also:

How to repair the EFI bootloader on a GPT HDD for Windows 7, 8, 8.1 and 10

NovaBACKUP PC/Server/BE v19.x and newer (2019-04-03)

Executing a backup via script/batch

If you don't want to schedule a backup in the NovaBACKUP GUI and prefer the Windows Task Scheduler or want to control a backup by script/batch for other reasons, you can also run your backup jobs from the command line:

Open a command prompt with administrative rights. Use

cd C:\Program Files\NovaStor\NovaStor NovaBACKUP

or for NovaBACKUP older than v17.x

cd C:\Program Files (x86)\NovaStor\NovaStor NovaBACKUP

to jump to the NovaBACKUP installation directory (default setting during installation; if you have changed this, select the corresponding installation directory).Type it in:

nscmdornscmd -?

You will receive this help text:

Command Line Help:

-u user name-domain-password-s script file path-q allow queuing-h hide console-t ini file for scheduled job settingsExamples: Run a script specifying credentials and queuing-u John -d MyDomain -p 123 -q -s c:\temp\backup.nbk-s c:\backupplan\MyBackupScript.nbk -t c:\backupplan\XYZbackupschedule.ini

Create a backup job in the NovaBACKUP GUI and specify this backup with path and name in the command line. Example:

Script is in pathC:\ProgramData\NovaStor\NovaStor NovaBACKUP\UserScripts\Novastor\Backup\BackupAMO.nbkUser = NovaStorPassword = Password

Then the command line should look like this:

nscmd -u NovaStor -p Password -s "C:\ProgramData\NovaStor\NovaStor NovaBACKUP\UserScripts\Novastor\Backup\BackupAMO.nbk"

The -q option also allows you to specify multiple backup jobs on the command line.

You can also save this command line as a batch file and store it on the Windows Desktop. Double-click to start the backup. You can also add this script to the Windows Task Scheduler.AMo

Clean NovaBACKUP Restore Index/Media Index (used by file level backups)

There are times when the NovaBACKUP Restore Index / Media Index, used by file level backups, will become unusable or have some corruption which will cause a few different outcomes including newly completed file backup jobs do not index correctly.

I.E. they do not store a new index record when the backup has completed or

Importing a prior backup does not show the re-imported index record, or

Backup Retention does not seem to work because the Restore Index is not working correctly.

The root cause is unknown but could be related to using earlier editions of NovaBACKUP software and upgrading over time to newer versions and re-using previous media index records from older versions and something becomes corrupt.

NOTE: Image Backups will Never display on the Restore tab. You need to mount them to retrieve individual files instead: Mount (and Unmount) an image backup to Restore Files in Windows

If you are importing a backup file that already exists on the Restore tab, but was backed up to a different location originally, please Delete the entry on the Restore tab before performing the Import.

You can attempt to manually recover from this corruption by removing any 0-size files from the following directory with the software closed

C:\ProgramData\NovaStor\NovaStor NovaBACKUP\Data\Media

To rebuild the NovaBACKUP restore index used by file level backups, you can delete all index records using the following instructions:

After removing all records, you will have to Import all backups you wish to have in the Restore Index (which is also used by Retention jobs)

1. Close the NovaBACKUP software (NovaBackX.exe).

2. Via Windows File Explorer (not internet explorer), delete the contents of these two folders utilized by NovaBACKUP:

C:\ProgramData\NovaStor\NovaStor NovaBACKUP\Data\Media

C:\ProgramData\NovaStor\NovaStor NovaBACKUP\Index

NOTE: If your NovaBACKUP "Temporary Files directory" setting has been changed to a folder other than the default folder C:\ProgramData\NovaStor\NovaStor

NovaBACKUP you will also have to delete the Index records in two additional folders.

To locate this setting:

Click the large circle button at the top left of the program, that looks like a red and blue "NovaStor" logo, and choose Default Settings then go to the Advanced Settings tab.

Navigate to the "Temporary Files directory" on this tab using Windows File Explorer (not internet explorer), for example C:\NovaTEMP\

Once in this directory, browse to the C:\NovaTEMP\Data\Media\ folder and remove all contents (files and folders).

Then go into C:\NovaTEMP\Index\ and remove all contents from this folder (files and folders).

3. Start up NovaBACKUP software and go to the Restore tab and see if the index is empty and clean.

4. Re-try some new backup jobs to see if you can restore them without issue.

5. How to import file backups into the Restore tab

If that doesn't solve the restore index / media index related issue that you have, please perform a clean uninstall / reinstall of NovaBACKUP software and try again:

How To Uninstall NovaBACKUP PC, Server, or Business Essentials

NovaBACKUP PC/Server/BE v16.x and newer (2019-03-28)

NovaBACKUP offers the possibility to work with post- and pre-scripts, see also the manual on page 49:

http://go.novastor.com/hubfs/EUROPE/Documents/UM_NovaBACKUP_User_Manual_DACH_SMB.pdf

Please note the following:

A script (batch file or Powershell script) must always contain as last line

exit 0

Only with this last line NovaBACKUP (NBK) receives a signal when a script is finished. Without this line NBK waits forever for the a script termination and the backup job will not proceed.

Another condition:

The path to the batch file must not contain a blank.

AMo

This is a guide that will instruct an experienced user to remove backup paths from NovaBACKUP backup jobs which contain file paths that NO LONGER EXIST and which are producing various warnings relating to those file paths no longer existing.

This is a workaround for those users who do not want to have to re-create a new backup job to fix this issue.

If you are not comfortable with manually editing backup job scripts (.NBK files) using Notepad, you can simply create a new backup job on the "Backup tab" by selecting the "New Job" icon at the top left of the program. Be sure to only include files and paths which can be accessed when the job will run.

Cause:

A path existed when you created a backup/copy job, but no longer exists on your machine, such as files on a removable drive.

Your backup/copy job presents you with a warning for drives that are unreachable when the job runs:

Path: X:\*.*, error: The system cannot find the path specified.

Resolution:

Run the Notepad application. (notepad.exe)

Open the backup job (.NBK) in Notepad which is attempting to backup the path that no longer exists.

Your Backup job script files (.NBK file extension) will be stored in this location by default on your system:

C:\ProgramData\NovaStor\NovaStor NovaBACKUP\UserScripts%UserName%\Backup\

The area of the backup job which has the paths defined is near the top of the (.NBK) file, as seen below. The [select] section shows your files/folders to include in the job.

Remove the line for the path that no longer exists. all path.item.# values need to be sequential, starting at 0 for the last one, going up in value for each line sequentially above it.

In the following example, we will be removing the F: drive from the selections.

SAVE the modified file, replacing the existing .NBK file.

IMPORTANT: Make sure the saved file still ends in (.NBK) with the same name (i.e. My Backup.NBK not My Backup.nbk.txt)

The next time that job runs it will no longer attempt to backup the "F:" paths that you removed from the .NBK file.

Before

[select]path.item.7=+C:\MyFilespath.item.6=+F:\SomeOtherFilespath.item.5=-C:\ExcludedFilespath.item.4=+D:\ImportantFilespath.item.3=+F:\RemovableDrivepath.item.2=+D:\MyLargeFilespath.item.1=+C:\UserDatapath.item.0=+C:\Userspath.numberOfItems=8

After

[select]path.item.5=+C:\MyFilespath.item.4=-C:\ExcludedFilespath.item.3=+D:\ImportantFilespath.item.2=+D:\MyLargeFilespath.item.1=+C:\UserDatapath.item.0=+C:\Userspath.numberOfItems=6

The most straightforward method currently is to use SQL Server Management Studio and simply "Select Top 1000 Rows" of the "users" table in "BackupServer" database.The more advanced, filtered query used above is:

SELECT [UserName],[NumComputers],[Enabled],[AccountStatus],[LastBackupDate],[UsedDiskBytes]/1024/1024/1024 as TotalStorageInGB FROM [BackupServer].[dbo].[users] WHERE Enabled = 'YES'

After the results are shown, right-click in the bottom pane and choose "Save Results As..." to save as a .CSV file.In the future:There is already a feature in development for adding the ability to synchronize the xSP user list with a CMon instance, which would allow an export to be done through that interface.

Fix for NovaBACKUP v19.x fails to install due to existing DR Drivers

NovaBACKUP

In some cases when attempting to installNovaBACKUP v19.xtheclient installation may fail with an error"Installation has endedprematurely"; normally this will occur if you had a prior version of NovaBACKUP client installed. If that isthe case, toinstallNovaBACKUP v19.xit will be necessary to perform the fix detailed in this article to remove a driver (called the Disaster Recovery / Image Backup Driver)that was left over from a prior NovaBACKUPinstallation. This registry basedfix can be applied prior to attempting to install this new version or after attempting to install this new version, in either case there is no reboot required.The fix instructions are as follows:First, make sure that you are logged in to Windows as a user with Administrator rights. If you are NOT logged in as a user with Administratorrights currently then these instructions will not work because there will not be enough rights to perform the actions necessary.1. Using your web browser download the simpleregistry (.reg file)fix for this installation issue by clicking this link to download thefix, and be sure to take note of where the fileis saved to: http://filestore.novastor.com/Downloads/NovaBACKUP/19.1/NBK_DRDrivers_Remove.reg Alternatively,you can download the fix in.ZIPformat.If you use this method, you will needto extract the .reg file out of the .zip fileto continue to the next step: http://filestore.novastor.com/Downloads/NovaBACKUP/19.1/NBK_DRDrivers_Remove.zip NOTE: If your anti-virus or anti-malware real-time protection software blocks .reg files from being saved then you may need to temporarily disable that type of software while you download and run this registry fix. You can re-enable the software after the fix is performed.2. UsingWindows Explorer locate theNBK_DRDrivers_Remove.regfile and then simplydouble-clickthat file. If your user hasthe required administrator rightsthen depending on your version of Windows and User Account Control settings willmost likely ask you to allow the Registry Editor application to execute and toallow changes to be made to your system, answer Yes to the prompt, and after that you will be prompted again to allow the Registry Editor application to add/change/delete values in the registry, answer Yes to that prompt. When successful there will be a confirmation screen that states "The keys and values contained in NBK_DRDrivers_Remove.reg have been successfully added to the registry.", you canclick the OK button to complete the fix.3. You can now attempt to install NovaBACKUP v19.xby locating the Setup-NB-x.exe installer file for v19.1.xand then right-clickon that file and select "Run as administrator" (if you have any anti-virus,anti-malware real-time scanning software or firewall applications you would want to disable themtemporarily, as sometimes that software blocks some portions of the setup installer).If the installation issuccessfuland after loading NovaBACKUP and checking the Help -> About screen for theversion and it is displayed as'Version 19.1 Build x' then you can now delete the NBK_DRDrivers_Remove.regfile. You are now done.If after performing the fix successfully and then installingNovaBACKUP v19.xisNOTsuccessfulit is recommended to first attempt a reboot of your machine, and repeatStep 3 again, and then it is recommended for you to follow the Knowledge Base guidethat we have on the subject Installation ends prematurely on client install whichyou should attempt next.If after attempting all of the aboveyour installation still does not work and you are okay with removing all components of NovaBACKUP software, including all registry related items, you can read the Knowledge Base guide that we have named How To Uninstall NovaBACKUP.

Take notes of server hardware.

Drivers for iSCSI, HBA Adapters, Tape Devices.

Management Software (versions, installers).

Disk Layout (mapped drives and space usage).

Any Shares attached.

Take notes of devices in Device Manager.

Medium Changer devices.

Storage Controllers.

Driver Version/Date.

Network Adapters.

Take notes of server features.

Server Name

Firewall settings

NIC settings

Which is on public/private domain?

Programs installed

Via Start Menu

Via Programs and Features

Storage System software

Versions

Types

Create an image of the OS on the server.

Please refer to the Steps to build a successful BMR plan.

Once image is completed.

Prior shutting down the server.

Perform the Exporting of the Tape drives.

Log into the Command Server.

**Always export tapes (using the Library tab) prior removing them from the library.**

Using the Library tab, export the tapes by right-clicking on one or more tapes, and selecting one of the following options.

Offline Export Use this to logically export a tape from the tape in the library (no mail slot, ready for removal).

Mail Slot Export Use this to export a tape to the mail slot for removal.

Select the Off-site Location (Removed_From_Library in this example) for the export:

If Offline Export is chosen, the cartridge will remain in the physical library slot unless physically removed. The tape will be listed as Exported and will be located in the Offsite Location.

If Mail Slot Export is chosen, the cartridge will be placed into one of the Mail Slot as shown in the image below.

Shutdown the tape server.

Go to the Tape Changer / Loader and follow steps to remove the bay with the drives that were exported. **NOTE: Every changer and loader have different settings.**

Control > Management > Left or Right > Unlock

This will unlock the bay and issue a request to pull the bay from the changer.

Reboot the server.

Insert the Server OS to be freshly installed or upgraded.

Boot straight to the Media / USB or DVD.

Perform the steps for a fresh install.

<< OR >>

If performing an upgrade, the operating system needs to be loaded first from the original boot media.

Log in as Local Administrator.

Run the Setup.exe from the bootable media.

Follow the steps to perform an upgrade.

When at Get important updates

Select Not Right Now

Click next.

Enter the Product Key for the new OS.

Select the image to be installed, example is the OS + the Desktop Experience.

Select Keep personal files and apps.

What needs your attention

Follow any instructions there.

Click Install.

After the Upgrade has been performed.

Reboot the system to verify the upgrade completed.

Log in as local administrator.

Verify all the drivers are not showing warnings within the Device Manager.

When in Device Manager.

Go to Media Changer devices.

If it shows any Branded devices.

Update the driver.

Select Browse my computer for driver software

Use the Generic Device Driver

Select, Unknown Medium Changer

**Any OEM Drivers will NOT work.**

Steps to change the Drivers:

To install the correct driver, right-click on the Medium Changer and select "Properties", then select the "Driver" tab and click the "Update Driver" button:

In the "Update Driver Software" dialog box, select "Browse my computer for driver software":

Click on "Let me pick from a list of drivers on my computer":

Select "Unknown Medium Changer" and click "Next":

The system is now ready for the library to be configured in NovaStor.

Go to > C:\Program Files

Make a Zipped copy version of the NovaStor folder.

Uninstall NovaStor DataCenter from the server.

Reinstall the client onto the server that has been upgraded.

Open an explorer window

Go to the main commander server location

\\<cmdsrv>\c$

\Program Files\NovaStor\DataCenter\sw-depot

Choose the OS the client is to be installed

Windows x64 > Client

Copy the client executable to the server that was upgraded.

Run the client installer and follow the steps to install.

Be sure to enter the name of the command server within the steps to install.

Unzip the library files from the Zipped NovaStor Directory to the New Directory.

First go to services and STOP the current NBK DC services.

Select the new NovaStor directory and Zip it as as NovaStor_Old_Original.

Then take the previous zipped NovaStor Copy and unzip it to NovaStor.

Restart any NBK DC Service.

Upon reinstalling NovaStor DataCenter, if the services do not correctly install (rarely ever happens), you may need to manually install the services.

Launch an elevated command prompt (Administrator).

Go to > C:\Program Files\NovaStor\DataCenter\Hiback

Type the following command:

hijacc.exe -c C:\Program Files\NovaStor\DataCenter\Hiback\tape

Go to > C:\Program Files\NovaStor\DataCenter\Hiback

Type the following command:

hiserv.exe -c C:\Program Files\NovaStor\DataCenter\Hiback

Go to > C:\Program Files\NovaStor\DataCenter\Hiback\tape

mpx.exe -c C:\Program Files\NovaStor\DataCenter\Hiback\tape

Rename the services that were added to the services with NBK DC <>.

Open an elevated Command Prompt.

Type the following

sc config hijacc displayname= NBK DC Hijacc Service

sc config hiserv displayname= NBK DC Hiserv Service

***NOTE: Make sure you have a space between the = and the new name:

Ex: displayname= New Name, NOT displayname=New Name***

Once the server back online.

Login as Local Administrator or as Domain account with Admin privileges.

Go to Services.

Stop the NBK DC Services

Set NBK DC Backup Servicer & Remote Command Executor to logon as the local administrator or domain administrator that already exists.

Restart those services.

Log onto the Command Server.

Go to > Node Management

Select the Tape Server and Right Click to Sync the node.

Verify the Versions of the OS and components to make sure they match the new system that the DC was installed on to replace the original system.

Right click > Select Edit.

Verify Backup Server is selected: [X]

Click Service Account and click Edit.

Type in the information for Local Administrator.

Go to > Storage Management

Go to > Backup Servers

Verify the tape server is listed and all the devices are listed.

If the tapes are showing inaccessible.

**NOTE: To locate the current name ID of the, open an elevated command prompt.**

Go to > C:\Program Files\NovaStor\DataCenter\Hiback\tape

Type the following

hiscsi -scan

Type the following for the tapes within the changer / loader:

hiscsi -stat <Changer Name ID>

Command Server Database Backup / Restore Procedure:

In anticipation of a catastrophic failure, you should always protect your NovaStor DataCenter command server, as this contains the database required to browse and track your backups.

The following steps are critical in creating a backup job to protect your backup server:

Create a disk pool for the exclusive purpose of holding only the NovaStor DataCenter database, for ease of recovery. It is recommended to configure a 3-day retention of this database for data integrity.NOTE: ONLY use this pool for your NovaStor DataCenter Disaster Recovery Backup job! https://support.novastor.com/hc/en-us/articles/360005856213--Guide-DataCenter-Direct-Restore-from-SV-file

Configure some method of replication offsite or in the cloud of this storage pool so you can recover it in case of disaster.

Configure the backup job to use the pool that was created exclusively for this purpose with the Fileset containing the NovaStor folder in ProgramData and Program Files:C:\ProgramData\NovaStor\*C:\Program Files\NovaStor\*

Create a backup job to capture the NovaStor software installation locations:NOTE: Make sure to NOT configure Multiplexing and splits on this job, as it makes it almost impossible to restore later.

It is recommended that the backup be performed after all other critical data backups and Retention operations have completed:

Restore Procedure:

Retrieve the NSDR pool you have backed up with the software, it will contain some .sv files you will need to perform a direct restore of the data from.

Install the software onto the new machine just as before. No settings or special options needed just a Next, Next, Next, Wait......

Follow the procedure to perform a direct restore of the latest sv file in this pool.

You can also use the simple_restore.cmdscript to do this, simply copy the script into the folder that contains your .sv backup file

File copy/overlay (not using DataCenter .sv files)

This is the procedure to manually backup/restore the DataCenter/Network command server before/after a full system reinstall.

NOTE: This is also the same procedure you would use if you migrate from one machine to another, I.E. Physical machine to Virtual Machine.

The process to backup and restore to a new install is a very simple process.

**** Be sure you have the installer for the same version currently installed before starting the backups. ****

**** Installing any upgrade before backup would be a good idea to ensure the versions match. ****

Before doing the migration you will need check where your media pools are storing the backup data. This can be found on the Storage Management tab of the GUI. Each Media Pool will have a path to its storage location.

If these locations are on a NAS device or some other network location, I.E. \\device\storage\Backups, then there is no need to worry, as that path will be the same as it currently is.

If you are using a local storage location, i.e. D:\Backups, then you will need to make sure to copy all data in these folders to an external location, or all backup data will be lost.

You will also need to be sure to recreate the same local drive partition structure after refresh so the data can be copied back to the same path it is currently configured to look for in the Database (i.e. D:\Backups).

Procedure:

Stop all "NBK DC *" services (You can use the Stop.bat or Stop.ps1file attached or create your own, see below)

Copy the C:\ProgramData\NovaStor\DataCenterfolder into a zip file and copy externally.

Copy the C:\Program Files\NovaStor\DataCenterfolder into a zip and copy externally.**** At this point your database has been copied and is able to be restored to this point in time later. ****

Install the software onto the new machine just as before. No settings or special options needed just a Next, Next, Next, Wait......

Once install is complete: Stop all the services again. (You can use the Stop.ps1file attached or create your own, see below)

Copy the previously backed up folders to their original locations (Program Files and ProgramData) and overlay the current data. If you are concerned, rename the newly created folder and copy the old here.**** If needed, copy any moved backup data to their original path (i.e. local storage). Disregard if you store data on a network location. ****

Start NBK services and launch the GUI. (You can use the Start.bat or Start.ps1file attached or create your own, see below)

Batch Scripts to stop/start services

Stop.bat is a batch script to stop NBK DC services.

sc stop "nbksrv"

sc stop "DerbyDB"

sc stop "hijacc"

sc stop "hiserv"

sc stop "mpx"

sc stop "OpenEJBServer"

sc stop "rcmd-dispatcher@port:32335"

sc stop "rcmd-executor@port:32334"

sc stop "DCWebserver"

Start.bat is a batch script to start NBK DC services.

Start.ps1

sc start "nbksrv"

sc start "DerbyDB"

sc start "hijacc"

sc start "hiserv"

sc start "mpx"

sc start "OpenEJBServer"

sc start "rcmd-dispatcher@port:32335"

sc start "rcmd-executor@port:32334"

sc start "DCWebserver"

PowerShell Scripts to stop/start services

Stop.ps1 is a PowerShell script to stop NBK DC services.

"nbksrv", "DerbyDB", "hijacc", "hiserv", "mpx", "OpenEJBServer", "rcmd-dispatcher@port:32335", "rcmd-executor@port:32334", "DCWebserver" | %{ stop-service $_ }

Start.ps1 is a PowerShell script to start NBK DC services.

"nbksrv", "DerbyDB", "hijacc", "hiserv", "mpx", "OpenEJBServer", "rcmd-dispatcher@port:32335", "rcmd-executor@port:32334", "DCWebserver" | %{ start-service $_ }

Tips & Tricks from us to you

Try utilizing a Task Scheduler entry to run a RoboCopy script to create a spare copy of the C:\ProgramData\NovaStor & C:\Program Files\NovaStor folders and zip them with the current date (if you wish)

You can then have a Cloud sync program target these copies to have it offsite in case of failure (i.e. Google Drive, Dropbox, OneDrive, Amazon Drive, etc.)

Command Server Database Backup / Restore Procedure (for Linux):

In anticipation of a catastrophic failure, you should always protect your NovaStor DataCenter command server, as this contains the database required to browse and track your backups.

The below instructions are for Linux based Command Server installations, and it assumes the new server that you are intending to make as the new Command Server, that you are recovering to, is also a client of the original Command Server.

Ensure that you have the Linux installer for the Command Server portion of the software. Stop all the services on the new server that we are going to bring up as the new replacement Command Server.

On the new Command Server machine, run the installer for the Command Server portion of the software, keeping all of the defaults.

Stop all of the NovaStor DataCenter services on the new Command Server machine.

Either copy the /opt/NovaStor folder from the original Command Server or directly restore from a backup of the original Command Server (Example of how to do a GUI based direct restore on Windows is located at: https://support.novastor.com/hc/en-us/articles/360009111954-Restoring-an-unindexed-SV-file-from-a-network-location ) or command line direct restore at: https://dcmanual.novastor.com/help-html/dc/en/DirectRestore.html )

On the new Command Server machine, copy all of those files into the \opt\NovaStor folder and overwrite the files and folders except for the /opt/NovaStor/DataCenter/Hiback/disk folder. This folder contains the configuration for the disk pools, and we want to utilize the ones that are already there on the new / replacement server.

On the new Command Server you will be required to edit the 'hosts' file (in Linux this is normally /etc/hosts) to place the old / previous Command Server's hostname so that it can point to the local host. Various config files and database will still be referenced as the original Command Server's host name so that is why we need to do this. An example hosts file entry is here: '127.0.0.1 OldCommandServer.domain.local OldCommandServer'. Add a new entry to hosts to add an entry like so, of course change it to what your original / old Command Server's hostname was:

On the new Command Server machine you will need to be able to perform a ping to ping the old server's DNS name. For example: 'ping OldCommandServer.domain.local' and 'ping OldCommandServer' should both resolve to the localhost at 127.0.0.1 and show a valid ping result.

On the new Command Server, Start the NovaStor DataCenter services.

Login to the UI via IP address and port: x.x.x.x:32333

At that point you can restore files as normal that have been backed up.

If at this point you want clients to be able to back up to this new Command Server you need to add the IP address from the old Command Server server to the new / replacement Command Server server.

If that is not an option you can edit the central-server.properties file in /opt/NovaStor/DataCenter/conf folder on all of the agents to point to the new Linux Command Server.

NovaBACKUP xSP/RWF/Cloud Port

Network error: The virtual circuit was reset

NovaBACKUP xSP / Remote Workforce

Symptoms:

Agents backup jobs are failing when attempting to backup to Storage Server.

masterlog.txt is showing the following error: "Network error: The virtual circuit was reset by the remote side executing a hard or abortive close"

Cause:

This error is a result of network communications conflict between the storage server and the client. This can be caused by a poor network connection, or network monitoring software causing slow down of network traffic. Verify what is monitoring your environment by typing... netstat -an |find "308"on the storage server.

Solution:

Disable or remove the monitoring software pointing at the Storage Server (whether it be on the storage server itself or on another machine)

Settings that affect Storage Server space

NovaBACKUP xSP / Remote Workforce

The NovaBACKUP xSP and Remote Workforce Storage Server has a few settings that will allow you more granular control over how much data is stored for each user account.

Configuration Manager

In the Configuration Manager:

Open the Configuration Manager

Select a User

Click [Properties]

Restorable Window

This is a setting in the configuration manager that allows you to set the time period to keep versions of files. This does not mean that the storage server only keeps 1 week worth of data with your 1 week restorable window though. It keeps one week worth of versions.

Where we see the most issues with this is when the end user has something else backing up or doing some sort of dated file scenario. For instance SQL backups. Some customers do SQL backups to .bak files through the SQL management utility, and then backup those SQL backups.

So they have SQL backup files named SQL_09.20.2010.bak, SQL_09.19.2010.bak, SQL_09.18.2010.bak etc. Each on of these is a single version of a file. Since the Restorable Window is all about versions, all of these files would be retained on the server. And as the Restorable Window never deletes the latest version of a file, there will always be one version of the file available, no matter how old it is.

BackupServer.ini

In the BackupServer.ini:

[Storage]

# Allowed number of deleted storage streams before defragmentation is started.

# Dynamic

Defrag Limit = 7

# Enable saving corrupted storages.

# 0 or 1

SaveCorruptedStorages = 1

# Minimum number of versions to retain.

# Dynamic

MinNumberVersions = 1

DefragLimit

This is a setting in the backupserver.ini file that specifies the amount of outdated storages to keep before actually defragging the storage and getting rid of the old outdated storage. By default this is set to 7, which means there has to be 7 outdated versions of a file before the server rolls out the outdated storage. Decreasing this number makes the storage more true, but puts a higher load on the storage server.

SaveCorruptedStorages

This setting tells the server to save or discard any corrupted storage files that occur during the backup transport process. A file may become corrupt if there is a dropped connection or a stop is caused either on the client or server side.

MinNumberVersions

The MinNumberVersions control the absolute minimum versions of a file to retain regardless of the Restorable Window for the account.

This walkthrough will describe how to create 2 alternating File backups, one Copy job for your photos, and a Disaster Recovery Image Backup, all on a Schedule.

Contents

Storage Device

External Hard Drive(s)

Network Folder

Create a New Backup Job

Select Data to Backup

Your User Directory contains most of your saved data

Choose the Destination and output filename using [Backup to...]

Schedule My Backup A

Create and Schedule My Backup B

What about Photos?

If you have a large number of photos, use Copy.

Schedule the Copy Job

Disaster Recovery Image Backup

What is an Image Backup?

Storage Device

What will your destination storage device be?

External Hard Drive(s)

There is no preparation required other than to know the drive letter in Windows. You can make a specific folder here if you wish, this guide will do the same.

Network Folder

A brief overview:

Add a Network Device

Adjust your default settings

Select the Network Device as the destination.

A more comprehensive guide can be found in our [Guide] Backup to NAS with Retention Walkthrough

Create a New Backup Job

This guide will create 2 alternating File Backups, a Copy Job, and an Image Backup.

Select Start on the Home Tab to create a new file backup job.

Select Data to Backup

Your User Directory contains most of your saved data

Provide a Backup Name: My Backup A

Select your User Directory

Select your other Data files

Choose your [Backup to...] Destination

Save and Schedule the Backup Job

Exclude "Pictures" if you have many. See the "What about Photos?" section for more information on a better way to backup your "Pictures" directory for most users using a Copy Job.

Choose the Destination and output filename using [Backup to...]

Provide an output Media Name: My Media A

Navigate to your storage drive

If you created a folder to store your backups, select it

Confirm settings, click [OK]

Schedule My Backup A

Click [Schedule...] (5) in the screenshot earlier.

[Yes] to save changes

Confirm the Script File name My Backup A.nbk, choose [Save]

NOTE: The Machine must be on, and a user "logged In", for a scheduled job to run. Standby is not "On"

Change the "Type of Schedule" from One Time to Daily

Select the First Run... date and time

This is the Time the job will run based on the schedule options

Adjust your schedule frequency

Change "Repeat every..." x day(s) to two (2) to run every other occurrence

Choose the day of the week you wish the job to run on in "But only on these days..." Friday is selected here

This means "Every other Friday"

Provide a Windows username and password for "Run as specific user" if you logout of your machine. The machine must be on for a scheduled job to run.

Create and Schedule My Backup B

NOTE: The currently loaded job script can be found in the Title Bar of the software. In this case, the previously created job "My Backup A" is open.

Change the Backup Name: from My Backup A to My Backup B

Change the [Backup to...] options (below)

Save the backup job using Save My Backup A As from the menu

[Schedule...] the new backup named My Backup B

Adjust the output Media name: to My Media B

Re-select the destination drive and folder NOTE: after changing the media name, it will default to "C:\"

Confirm the [Backup to...] device options

After changing the Backup Name

After changing the [Backup to...] location and Media name

Open the main menu

Choose Save My Backup A As... to save the changes made to a new job

Confirm the File name: matches My Backup B.nbk

Select [Save]

(4) Schedule the saved My Backup B job, confirm the saved name matches My Backup B.nbk in the Job Name: area

Change the Type of Schedule to Daily

Select a First Run... Date to the next week from when My Backup A was scheduled

Choose a Time for the job to run at every other week

Repeat every...2 days onFriday

Provide Run as specific user credentials as needed (same as before)

Confirm the Schedule by selecting [OK]

What about Photos?

What's the difference between Backup and Copy?

A Backup will store all of your selected files into a single "container" file, with a .NBD file extension. You will have to access these files using NovaBACKUP

A Copy will maintain the folder structure of the selected files, keeping them visible to other programs and Windows. Also, if configured correctly, this job can update files instead of copying all of them every time, substantially decreasing the time it takes.

If you have a large number of photos, use Copy.

Make sure to remove these from your File Backups you just created if you wish to use this method.

Select your User Picturesdirectory

Select other locations your Pictures are saved in

Choose [Copy to...] destination. Make a folder to keep it separate.

Adjust [Settings]

Save and [Schedule...]

Select the Destination Drive

[Make New Folder] and/or select the Destination Folder

Choose [OK]

Schedule the Copy Job

(5) Select [Schedule...]

Confirm [Yes] to Save the Copy Job Script

Enter a File name for the Copy Job and Script (similar to Backup Name)

[Save] the Copy Job Script

If you are not prompted to Schedule the job at this point, select [Schedule] again.

Type of Schedule = Daily

First Run...Date & Time, Time is normally more important than Date here.

This job will run at the specified time each day.

If you want to restrict this job to certain days, you can choose the days to run on.

Confirm the Schedule Options with [OK]

Disaster Recovery Image Backup

What is an Image Backup?

An Image Backup is a block-level copy of all data on your drive. This process can be used to create a backup of your Windows Environment, as it does not look at individual files. This is also known as a Disaster Recovery Backup.

Open theHome Tab

SelectImage Backupto Start the Image Backup Wizard

SelectImage Backup Schedule

Click [Next]

Confirm the Backup Type is "Full", click [Next]

SelectDisk 0 (or whichever disk contains your "C:" partition)

Click [Next]

Specify aBackup Name"System Image"

Click [Backup to...]

Select thedestinationstorage device

Click [OK]

Click [Next]

SelectType of Schedule"Daily"

Adjust the First RunDate & Timeyou wish the backup to run

Repeat every4occurrences of the Day (chosen next)

Select the day of the week you wish the Image Backup to run (Fri)

Click [Finish] to schedule the job

This is caused by the way NovaBACKUP communicates with Amazon S3, and that the response is "paginated" but not processed by the NovaBACKUP client.

You can still backup more than 1000 items in a directory, but when attempting to restore data from the backup, via the NovaBACKUP client, you will only see the first 1000 items in any directory while in the Restore tab. Note: If your NovaBACKUP backup job to Amazon S3 has compression and encryption options disabled, at the job level, you would be able to utilize the Amazon AWS website to restore all of your data without requiring the NovaBACKUP client and you can still have Amazon S3's native encryption enabled on your backups if enabling encryption on the bucket itself via the AWS website ( https://console.aws.amazon.com/s3 ); thelimit does not affect in this case as you would be restoring the data via AWS website's own restore function and not via the backup client.

NovaStor Technical Support recommends performing your backups to S3 only after changing the following backup job [Settings], this will enable you to turn on versioning on the bucket if needed as well as be able to restore your data directly from S3 using any utility you want.

Compress backup files

i.e. Turn Compression OFF (the default option is ON)

Do Not enable Encryption

if you need this data encrypted, enable native encryption on the S3 Bucket instead inside the AWS website ( https://console.aws.amazon.com/s3 ).

What you need to do is add a sub-directory for any set of data, on S3, that has more than 1000 items, as NovaBACKUP CAN NOT Iterate past the first 1000 items the way it is programmed using the LEGACY API/SDK (this is what is limiting the bucket you can choose as well).

In the S3 Bucket

Using this path as reference:

\path\to\data\<more than 1000 items here>\<actual docs>.abc

Start here when browsing the S3 bucket using something besides NovaBACKUP:

\path\to\data\

At this level, you should be seeing the directory with <more than 1000 items here>.

Add a directory, move data using either method below

A) Move up to 1000 items into the new folder, creating a new folder for each set of data, then restore from the new location. OR B) Restore the first 1000 items you can see on the Restore tab, then move these to a new directory (such as \path\to\data\00_Restored), then repeat for the next 1000 items until all directories are restored. This method does not move any data from the original location it was backed up from until it has already been restored. In either case, you will need to perform a separate restore operation. To refresh the view on the Restore tab, open another backup from the list, then open the one you need and locate the data you need to restore.

Adjust Default Settings for NovaBACKUP

You can adjust the default settings for the restore job from the Main Menu ("N" logo at the top left) to specify the "Restore to" location, so you don't have to do it every time throughout this process. [Guide] Backup to NAS (with Retention) Walkthrough Please keep in mind that the folder structure is restored as well., starting from the location you provide. Windows Network paths must not exceed the MAX_PATH limits of 255 characters.

If this data was originally on a network share

You need to provide the Restore Job Network Credentials for it to be able to write data to the original location. You also can restore this data to an alternate location to make sure it is not overwriting anything on accident, plus it will move faster when restoring to a local device. To change the default Network Credentials if needed, follow these steps found in:

Setup your Network Device: In NovaBACKUP on the Home tab click on [Add Network Device] or open the Device tab and click on Add. In the drop down menu select Network Device, click "OK". Under Device Name give it a simple name, my example is NasBackup. Under Network Path type in the UNC path or browse for it. Domain Name, User name, and User Password are all optional depending on how your network device is configured on the network. NOTE: These credentials are those utilized to connect to the Network Share, for most devices you will use "admin" or "root" as the username. Click on "OK", if any of the above fields are incorrect, an error message will appear. If correct you will be taken to the Home tab, and see your device listed on the device tab.

Configure your Default Setting to run as an administrator, change the default backup location, and configure default backup notification emails. Click on the NovaBackup logo on the top left corner and choose "Default Settings". Click on Default settings, Click on the Run as Tab, put a dot on Run as specific user. Fill in your Domain Name, User Name, and User Password. (Most home users will not be in a domain.) Click Check Credentials to confirm you have entered all the correct information.

Change the default backup location to the previously added network device to ensure the network credentials are saved for Retention jobs.

[Guide] How To Perform P2V - Physical to Virtual Machine (Hyper-V) using NovaBACKUP Business Essentials 19 (Video)

This video demonstrates the new P2V (Physical to Virtual Machine) feature introduced in NovaBACKUP 19.1 (all editions). The video shows a NovaStor support technician performing a P2V - Physical to Virtual Machine Image Backup to Virtual Hard Disk (VHD), then creating a new Hyper-V Virtual Machine (using Microsoft Hyper-V Manager) and assigning the Virtual Hard Disk to the VM. It also covers converting the VHD to VHDX using Hyper-V Manager.

We recommend watching these videos in full screen / HD.

Watch on YouTube at: https://www.youtube.com/watch?v=dQVeEGkWJ8A

View all NovaBACKUP P2V related articles here.

How to Attach an Existing Virtual Hard Disk (VHD/X) in Hyper-V

NovaBACKUP

Last Updated: Apr 09, 2018 12:34PM PDT

How to Attach an Existing Virtual Hard Disk (VHD/X) in Hyper-V

NovaBACKUP 19.1 introduced P2V functionality to Image a Physical Machine directly to Microsoft Virtual Hard Disk (VHD) format for use as a Hyper-V Virtual Machine (VM). This guide covers how to take that produced Virtual Hard Disk (VHD) file and utilize it as a Virtual Machine in Hyper-V. NOTE: Currently, NovaBACKUP 19.1 only supports P2V to VHD format and not P2V to VHDX format, the later will be coming in a future release of NovaBACKUP. Please note that the VHD format only supports up to 2TB hard drive size and traditional BIOS (otherwise known as "Legacy") boot mode, meaning non-UEFI boot mode, on the physical machine that is being imaged to VHD. If the physical machine that you want to perform a P2V on contains UEFI boot mode and/or a 2TB or larger hard drive, then this function will not work at this time. Most serversprovide the option of usingthe traditional BIOS boot mode or UEFIboot mode, so you would need to confirm that before attempting NovaBACKUP 19.1's Image to Virtual Hard Disk (VHD) function.

1. Log on to your Windows Hyper-V Hypervisor (this would be a Windows Server 2012, 2012 R2, 2016, and Windows 8.x OS, that has the Hyper-V role installed). Launch the "Hyper-V Manager" application. Once in Hyper-V Manager click on "Action" in the toolbar, then click "New", and then on the click "Virtual Machine...", as the screenshot example shows. Proceed to the next step.

here

2. The 'Before You Begin' screen may nor not appear, in our example this screen does appear since we had never checked the box at the bottom that contains the option "Do not show this page again". If you do not see this screen it's fine and normal, then just skip to the next step to proceed. Click the "Next" button.

3. On the 'Specify Name and Location' screen you will assign a name to this new virtual machine that you are creating, the name would basically be what you would like to call that Physical Machine, so it could be the exact Windows Computer Name that was utilized by the Physical Machine or you can really do whatever you want here for the naming scheme as it is not as limiting as the Windows Computer Name restricts you to using (like the Microsoft DOS restrictions). Click the "Next" button.

4. You will now see the 'Specify Generation' screen which requires you to choose the generation of the virtual machine. Be very careful when choosing the Generation, you will very much have to understand the differences between the two available choices, Generation 1 and Generation 2.

NOTE:Choose your VM generation carefully. Starting with Windows 2012 R2 this Hyper-V has a new option: Generation 2 virtual machine. This is a second generation firmware for virtual machines with a revised set of virtual hardware and new opportunities for users, such as a boot from an SCSI device. There will be more to come on this topic in future releases. Among noticeable limitations of Generation 2 virtual machines, is that there is no support for a guest OS older than Windows 8.x, not to mention Unix-like. Practically speaking, choose this only for Windows 8/8.1 or Windows Server 2012/2012 R2 and only for 64-bit builds.

This explains why you should choose Virtual Machine Generation accordingly for your case and stick to Generation 1, unless youre 100% sure you need to use Generation 2.

For a further explanation on Generation choices read more about that topic in the next paragraphs.

As stated prior, you have to know that there are two Virtual Machine "Generation" types in Hyper-V currently, in Windows Server 2012 R2 and above Operating Systems. There are Generation 1 and Generation 2 types. On screen are the description of both Generation 1 and Generation 2 and why you may have to use one over the other. First of all you are using the function of NovaBACKUP 19.1 to Image a Physical Machine to Microsoft Virtual Drive (VHD). This function of NovaBACKUP 19.1 currently allows you to perform a Physical to Virtual Machine (P2V) operation, and that will image your Physical Machine to a Virtual Hard Disk (VHD). You have to know that there are limitations to VHD which affect how you will be able to utilize that P2V VHD file when creating a Virtual Machine from it. In general Physical Machines can utilize two types of boot to hard drive methods, the old standard is "BIOS" (otherwise known as "Legacy") and the newer standard is "UEFI". If your Physical Machine was using "BIOS" (Legacy) boot method, then you will always be able to utilize the Generation 1 for the Hyper-V Virtual Machine type.

NOTE: In a future release of NovaBACKUP we will support VHDX but currently NovaBACKUP 19.1 only supports VHD; this means that currently NovaBACKUP 19.1 can only perform a P2V of a physical machine, that contains up to a 2TB hard drive and uses non-UEFI firmware, to VHD format. For Physical Machines that utilize non-UEFI-firmware (UEFI type of BIOS) that you image to VHD or VHDX you can use the Generation 1 choice. For Physical Machines that utilize UEFI-firmware (UEFI type of BIOS) then you will for sure have to use the Generation 2 choice. For Physical Machines that contained 2TB or larger hard disk, and that hard disk is now part of the Virtual Hard Disk in the VHDX image, you will for sure have to utilize Generation 2 choice, no matter if the Physical Machine was using UEFI-firmware (UEFI BIOS) or not.

Make sure that select the correct Generation choice before continuing otherwise your VM will not be able to boot up as it will not be able to locate the hard disk that is part of the Virtual Hard Disk. This is an example of selecting the "Generation 1" choice, for further assistance on knowing which Generation to choose from see the next step.

Additionally, this is an example of selecting the "Generation 2" choice. You would 100% need to utilize Generation 2 if your Physical Machine was using UEFI-firmware (UEFI BIOS) for the boot mode. You would 100% need to utilize Generation 2 if your Physical Machine that you imaged to VHD contained a 2TB or larger hard drive. Additionally, you would 100% need to utilize Generation 2 if both of those mentioned items exist in your case on the Physical Machine that was Imaged to VHD. If your Physical Machine was using "BIOS" (Legacy) boot mode AND if your Physical Machine that you imaged to VHD contained a 2TB or larger hard drive, then you will have to first utilize Hyper-V Manager's built in Convert Image tool (which is only available in Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows 8.x) to convert your .VHD to a .VHDX. Additionally, If your Physical Machine was using UEFI-firmware (UEFI BIOS) for the boot mode AND if your Physical Machine that you imaged to VHD contained a 2TB or larger hard drive, then you will have to first utilize Hyper-V Manager's built in Convert Image tool to convert your .VHD to a .VHDX. The Conversion from .VHD to .VHDX format is something that is simple to do inside Hyper-V Manager for Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows 8.x, and we have a guide on how to do that here.

Make sure that select the correct Generation choice before continuing otherwise your VM will not be able to boot up as it will not be able to locate the hard disk that is part of the Virtual Hard Disk.

Click the "Next"button after making your Hyper-V Generation choice for this new virtual machine.

5. On the 'Assign Memory' screen you will be able to customize how much system memory to allocate to the new virtual machine. In our example we are using 1024MB (1GB) for the Startup memory value but we have in addition to that enabled the checkbox to "Use Dynamic Memory for this virtual machine", which is not a default enabled option but it is advisable to enable as this way Hyper-V's memory management system can allocate it the proper amount of memory as to what it thinks the VM should receive, based on usage and other performance factors. The Startup memory setting choices here are really up to you but it should be related to how much memory the Physical Machine may have required to operate properly based on the installed Operating System and how many applications and/or processes are used at one time. You will have to optimize it based on the installed system memory that is installed in the Windows Hyper-V Hypervisor machine itself and balance that with how many Virtual Machines you are utilizing. Click the "Next" button.

6. The 'Configure Networking' screen is where you will be able to assign a network adapter to the virtual machine, if needed. Normally it is necessary for the virtual machine to be able to contain a network adapter but just know by default that a network adapter is not selected for you by default in the Connection: drop down menu so you will have to choice that network adapter to assign to the VM. In our example we have selected the network adapter that is the Gigabit Network Connection on our Hyper-V Hypervisor server for the new virtual machine to utilize. Click the "Next" button.

7. The 'Connect Virtual Hard Disk' screen is where you will be assigning your VHD (or VHDX file if you used the Hyper-V Manager's VHD to VHDX Convert function as described previously) by selecting the option "Use an existing virtual hard disk" and then browse to the folder where you copied your VHD to, after using NovaBACKUP 19.1's Image backup to Microsoft Virtual Drive (VHD) function, and then copying that VHD file to your Hyper-V Hypervisor server hard drive. That is the Virtual Hard Disk file that you will be browsing for and assigning on this screen. NOTE: If you used the Hyper-V Manager's Convert function to convert your VHD to VHDX file, and that .VHDX file is now stored on the Hyper-V Hypervisor server's hard drive, then that .VHDX format file is the Virtual Hard Disk file that you will be assigning here. Special Note: The Hyper-V Generation 1 virtual machine type will support Connecting a Virtual Hard Disk that is either VHD or VHDX format, however the Hyper-V Generation 2 virtual machine type WILL ONLY SUPPORT Connecting a Virtual Hard Disk that is VHDX format.

The "Use an existing virtual hard disk" choice by default will have a file path selection path of "C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\". That path setting can certainly be changed but that is the default storage path for Virtual Hard Disk files (VHD or VHDX files). You will be required now to utilize the "Browse..." button inside the "Use an existing virtual hard disk" selection area here to browse and locate the actual .VHD or .VHDX file that you are intending to utilize for this new VM. Click the "Next"button to proceed.

8. After clicking on the "Browse..." button, you will be presented with a Windows Explorer screen to navigate to your saved VHD or VHDX file. NOTE: That Virtual Hard Disk file should be on a local storage device normally, keep that in mind. Select the file and then click the "Open" button to assign that Virtual Hard Disk file to the new virtual machine.

9. While still on the 'Connect Virtual Hard Disk' screen you will see the assigned Virtual Hard Disk file that you browsed to and selected in the step above. When ready click the "Next" button to proceed.

10. On the 'Completing the New Virtual Machine Wizard' screen that is displayed you will see a Description of the details of your new virtual machine that you are creating and when ready you can click the "Finish" button, otherwise you can go back in your choices to change something. Now click the "Finish" button.

11. If Hyper-V is successful in creating the new VM then the new virtual machine will be created with the name that you provided it in the first couple of steps, and the name of that VM will be displayed in Hyper-V Manager's Virtual Machines listing. In our example, the new VM shows up as "Windows Server 2016 x64" since that is what we provided in the name field. The new virtual name is in the powered off status. We can see next how to boot the virtual machine for the first time.

12. While still in Hyper-V Manager in the Virtual Machines listing area highlight the new virtual machine that was created and then right-click on it and then click "Connect..." and a screen will appear that is your virtual console to see the screen contents virtually. If you have not powered on the virtual machine then you will receive the message that "The virtual machine "x" is turned off" in the Virtual Machine Connection window, like our example shows:

13. Now let's attempt to boot this new virtual machine! Inside the Virtual Machine Connection window, click on "Action" in the toolbar and then click "Start" to start the VM. Alternatively you can click the icon that looks like a power button which is in the toolbar and is the second icon from the left. The VM should be starting up and the status will change to show that in the Virtual Machines listing.

The VM is now in the boot up process. You will need to know that the first time you start a new virtual machine it will take quite some time for the VM to boot up since the hardware configuration will be different since this is the first time you have booted in its' virtual form and the machine was a physical machine to begin with; now Windows has to figure out the differences. You may only see a black screen for 30 minutes at first and not realize anything is happening, and then eventually an animation may display that shows that Windows is "Getting devices ready" or something of that nature to tell you that it is working on figuring out hardware changes or it may even show the login screen. Our example showing the "Getting devices ready" message with on-screen animation:

Eventually you should see the login screen display for your operating system inside the connection window like in our example:

NOTE: You should find that after stopping the VM and then starting it again that the next time this virtual machine starts up it will be much faster to boot to the login screen. You are done, that's it!

The "If you have issues booting" troubleshooting section:

If you find that you cannot get the new virtual machine to boot up, there are some things to do, mainly you will need to go over the description of Step 4 entirely which describes why you may need to use Generation 2 instead of Generation 1 or vice-versa, depending on details of your Physical Machine. Hyper-V and the VHD format are very picky with boot firmware utilized on the original Physical Machine that you are now trying to make into a Virtual Machine.

If within 30 seconds after starting your virtual machine it shows a screen similar to the one in the screenshot example below, and detailed in our guide here, you will need to repair the boot configuration in this virtual machine, by reading the articles containing the subject " Repair unable to boot VM after a successful P2V with NovaBACKUP " which we have on this subject in order to continue and have the virtual machine be able to boot.

That's it, stay tuned for more, thank you.

Jon Ferraez / NovaStor

How to Convert VHD to VHDX with Hyper-V Manager (for P2V)

NovaBACKUP

How to Convert VHD to VHDX with Hyper-V Manager

NovaBACKUP 19.1 introduced the direct to Microsoft VHD (Virtual Hard Disk) feature which can be utilized for both on-demand and scheduled Physical to Virtual Hard Disk imaging. This direct to Microsoft VHD feature produces a VHD file for use with Hyper-V Manager, to take a physical machine and image it to make in to a Virtual Machine. The VHD format does contain some limitations, detailed in the paragraph below, and as luck has it the VHD format can be converted to VHDX easily via Hyper-V Manager's own 'Convert Virtual Hard Disk' function. VHDX is the newer and superior version of Virtual Hard Disk. There are reasons why you will have to convert a VHD produced with NovaBACKUP 19.1 to VHDX in order to use that Virtual Hard Disk image with Hyper-V. Windows Server 2012, Windows Server 2016, and Windows 8 introduced a new virtual hard disk file format, VHDX, which is an upgrade from the current VHD format and provides for superior performance, reliability and several enhancements including:

VHDX provides support for virtual hard disks larger than 2TB, and up to 64TB; whereas VHD has a limitation of 2TB for the physical machine's hard disk.

VHDX supports UEFI versus the BIOS boot method (meaning if the physical machine was using UEFI then you will need VHDX format to make the Virtual Machine be able to boot up in Hyper-V Manager). VHD only supports BIOS (also called "Legacy") boot method. Most modern computers utilize UEFI nowadays. If your physical machine that you are converting from Physical to Virtual (P2V) is using UEFI boot method, instead of BIOS "Legacy" boot method, then only VHDX will work for creating a Virtual Machine from a Virtual Hard Disk. VHD will probably fail to boot up if your physical machine that you are imaging to VHD was using UEFI as the boot method. Read more about UEFI vs BIOS boot mode here. Luckily there is a simple way to convert VHD to VHDX and that is built in to the Hyper-V Manager application.

Better performance of dynamic and difference files through new larger block sizes.

Improved alignment of the virtual hard disk on large sector disks.

Microsoft has a guide to read on this subject: Deciding On When To Use VHDX or VHD files with Hyper-V.

The Hyper-V Manager application in Windows Server 2012, Server 2016, and Windows 8, provides a very simple way to convert existing VHDs into VHDX. Here's how to do it:

Launch Hyper-V Manager and from the right-side Action pane and select Edit Disk.

The Edit Virtual Hard Disk Wizard starts; click Next to get past the initial screen.

here

Figure 1. Enter the name and location of the existing VHD file (see Fig. 1) and click Next.

Select Convert and click Next.

Select the VHDX file format and click Next (see Fig. 2).

Complete the wizard by selecting the settings you need.

Figure 2.Select VHDX file format and click Next.

This process makes an exact copy of your existing VHD file, except now it's in the new VHDX format. And should the need arise, you can always use the same process to convert from VHDX back to VHD. We have a video walk-through here on how to convert VHD to VHDX using Hyper-V Manager's Convert function; the link for this video is fast-forwarded (starting at the 2 minute 41 second mark) to the section of a larger complete how-to video to perform the Image Backup to VHD using NovaBACKUP, then take the completed VHD and convert it to VHDX (this section of the video ends at the 4 minute 51 second mark), and finally how to create a new Virtual Machine in Microsoft Hyper-V Manager on your Hyper-V Hypervisor Server, to then attach the VHD or VHDX virtual hard disk file to that new Hyper-V Virtual Machine.

Now you can take that converted VHDX file and Import it in to Hyper-V Manager to be able to utilize it. Next you will want to read the guide How to Attach an Existing Virtual Hard Disk (VHD/X) in Hyper-V. We also have a video walk-through guide available on YouTube here.

View all NovaBACKUP related P2V articles .

Thanks for reading and stay tuned for more,

Jon Ferraez / NovaStor

NovaBACKUP PC/Server/BE v19.x and newer

The system state backup fails with error message "Could not get drive letter" in Windows event log "Application" like

-----------------------------------------------------

Error 21.07.2019 23:12:12 nsService 2 NoneException 'Base:103'(dt_drv.cpp(330) unexpected failure)SystemStateBackupRestoreException : SystemStateBackupRestoreAdapter::Backup --> CHECKPOINTED AT dt_drv.cpp(105) --> THROWN FROM SystemStateBackupRestoreAdapter.cpp(303)CAUSED BY HResultException : Description: exception RegistryServiceException : RegistryService::Backup thrown from RegistryService.cpp (142)caused by exception MountManagerException : Could not get drive letter thrown from MountManager.cpp (161) checkpointed at MountManager.cpp (153) thrown from MountManager.cpp (147) checkpointed at MountManager.cpp (89) thrown from MountManager.cpp (144)Backup failed, error = 0x80004005, Unspecified error--> THROWN FROM SystemStateBackupRestoreAdapter.cpp(300)

-----------------------------------------------------

The error code "0x80004005" in the protocol may indicate missing access rights.The following solutions can help to solve this issue:

1. missing access rights

Create your own user that is used exclusively for backup purposes. You can find an article about this on the NovaStor support website by searching for the term "BackupAdmin" (without ").

For testing you can set the service "NovaStor NovaBACKUP Backup/Copy Engine" to this new user (if this is a LOCAL user on this system; otherwise use the lokal Admin). Usually it is not necessary to change this service if you use the "BackupAdmin" in all jobs and schedules. However, a test cannot do any harm here. After the test, set the service back to the local system account.

Anti-Virus Software (AVS) can also prevent access to components, directories and files to be backed up. You can search for "AVS" on the NovaStor support website for further information.

2. no access to hidden system partitions

This message may also occur if NovaBACKUP needs to access a hidden system partition without drive letters. Assign a drive letter to this partition once for testing purposes and make sure that this drive is also online. Run the backup again.

Click on "Start" or Windows icon in the bottom left corner of the taskbar.Type "Hard disk" and then click on the entry "Create and format hard disk partitions". orright click on the Windows icon and click on "Disk Management". In the disk management you assign a drive letter for the hidden system partition:

Image 1: Yellow labeled means "Change Drive Letter and Paths..."AMo

Overview

This article is to inform you about the methods needed to perform a successful and complete backup of dental software programs, or any software that utilizes an active database back-end that is not Microsoft SQL.

The best practice is to generate a backup using the software that created the data, and then capture that backup using your Backup application, in this case NovaBACKUP PC, Server, Business Essentials, or Cloud.

Additional information about NovaBACKUP can be found at https://novabackup.com/products

All information found in this article has been gathered from the respective software's resources.

After you have generated the backup using the 3rd party software, simply include the generated backup file in your file selection within NovaBACKUP.

Henry Schein Dentrix

https://www.dentrix.com/help/desktop/Routines/Backing_up_your_Dentrix_data_daily.htm

Backing up your Dentrix data daily

You should back up the Dentrix database every day. Generally, we recommend that you perform this backup at the end of the day after all patient data has been recorded in Dentrix for that day.

[...]

Important:With the release of Dentrix G5, the Dentrix database location has been moved to <Drive Letter>:\DENTRIX\Common. After installing Dentrix, you should configure your backup software to back up this new Common folder daily. (If you are upgrading from a previous version of Dentrix, your old backup configuration will no longer be valid.)

It is important to back up all of your important computer files; however, at a minimum, it is critical that you back up your important Dentrix database files in the Common folder. Remember that any data you choose to not back up cannot be restored in the event of data loss.

To perform the daily backup

1. Back up the \Common\DBCopyForBackup folder and all files and folders within it. You can update the files in the DBCopyForBackup folder by exporting a copy of your live database either manually or automatically. Use the Dentrix Server Administration Utility to manually export a copy of your database or to schedule recurring exports to happen automatically. [...]

2. Back up the \Common\DentrixSQL folder and all files and folders within it.

3. Back up the \Common\Doc folder and all files and folders within it.

For more information on backing up Dentrix, see Backing up the Dentrix database.

<top>

Patterson Eaglesoft

https://pattersonsupport.custhelp.com/app/answers/detail/a_id/19093/~/making-backups

https://pattersonsupport.custhelp.com/app/answers/detail/a_id/206/~/data-backup-recommendations

Eaglesoft and Patterson Imaging - What to consider when setting up a backup system for Patterson Dental software.

Applies to: Eaglesoft, Patterson Imaging, all versions; PattLock

Solution:

Backups

Making a backup is one of the most important things you can do for your office. Backups are a form of insurance against fire, power outages, theft and other misfortunes. If you lose your office data for any reason, a recent backup drive will save your office staff time and money. This section provides information on what to back up, how often to back up and where to store a backup.

Both single- and multi-user backup procedures involve backing up the same files and folders: theDatafolder containing -custom draw types, pattersonPM.db, pattersonPM.log, documents, audio, images, documents, indicators and metafiles.

The backup process for a multi-user involves a few more steps. Since the data on your multi-user system is located on your server machine, it is necessary to perform your daily data backups from your server machine. Remember: This process can only occur once you have completed the shutdown procedures.

Making Backups - Eaglesoft

The log file in the program directory is auto-archived when necessary. The archived file is renamed to reflect the date of archiving and appear in the data directory as such:

9-12-2002.log

It is important that ALL pertinent data is backed up including these archived files.If you are using Clinical along with Practice Management, there are six subdirectories that should be backed up along with the aforementioned files. Starting with Version 15, the files are located inC:\Eaglesoft\Data \<date>(seen in the example). Earlier installations are located in the following path:c:\EaglesoftorC:\Program Files\EaglesoftIf you are having problems making backups, verify that your path is set up correctly.The default paths are:

C:\Eaglesoft\Data\Audio

C:\Eaglesoft\Data\Images

C:\Eaglesoft\Data\Metafile

C:\Eaglesoft\Data\Customdraw types

C:\Eaglesoft\Data\Documents

C:\Eaglesoft\Data\Indicators

C:\Eaglesoft\Data\Data2* *NOTE: This path is for offices that have purchased the Dual Database module.

*IMPORTANT NOTE*

The Patterson database enginemustbe shut down before a successful backup can be performed. Failure to shut down the Patterson Software server will result in important database files not being backed up!

Making Backups - Patterson Imaging

There are subdirectories that should be backed up along with the aforementioned files. Starting with Version 15, the files are located in C:\PattersonImaging\Data\<date> (seen in the example). Earlier installations are located in the following path: C:\Program Files\Patterson Imaging If you are having problems making backups, verify that your path is set up correctly.The default paths are:

C:\PattersonImaging\Data\Image

C:\PattersonImaging\Data\Documents

*IMPORTANT NOTE*

The Patterson database enginemustbe shut down before a successful backup can be performed. Failure to shut down the Patterson Software server will result in important database files not being backed up!

When to Make Backups

It is the office's responsibility to make backups consistently. The more backups your office makes, the more your data is protected and insured against catastrophe.We recommend the following for backup frequency:

Daily backup - a separate disk or drive should be used for each day the office is open and rotated weekly.

Monthly backups.

Yearly backups.

Note: A separate drive or disk should be used for each type of backup.

Auto Backup

This feature enables Patterson software to automatically create local backups of the database at startup. This should be used as a fail-safe backup and not relied upon as your sole means of backing up data. This can be set up throughTechnical Reference. The backups will consist of a zip file containing the pattersonPM.db and pattersonPM.log files at the time of the execution.

SelectStart | Programs |Eaglesoft or Patterson Imaging (depending on the software)| Technical Reference. From here, select theDatabase Setupbutton. Select theAuto Backupbutton.

To use the Auto Backup, select the checkboxUse Auto Backup. Enter the number of days between Server startup that you wish to perform an automatic backup. Enter the highest number of backup files you wish to keep at any given time.

Use the button to browse to the auto backup folder if this hasn't been done before.

Note: This system should not be relied upon as the sole means for data backup. Patterson recommends using an additional process as your primary data backup.

*IMPORTANT*

This option will not replace your daily, monthly or annual backup.Auto Backupwillnot:

Protect your data from a hard drive failure

Protect your data from theft or damage from external forces

Copy or store any image, document or audio files

Auto Backupis a system tool and not a replacement for external backup media.

More Tips on Your Backups

Where to Store Backups

It is a good idea to store your backups in a safe, fire/waterproof location, such as a safe deposit box. More importantly, keep your backups at an off-site location.

Make Sure you are Making a Correct Backup

To verify that you are making the backup correctly, restore it at least once a month.

<top>

Opendental software

https://opendental.com/manual/backups.html

Backing up patient data is critical, as well as a requirement for HIPAA compliance. You should establish a regular backup and recovery plan. This will ensure that patient data is protected, even if there is accidental data loss, database corruption, hardware failures, theft, or other disasters (floods, fires, etc).

Backups should be frequent, stored securely, and tested regularly to ensure quality. We suggest backing up data to a high quality encrypted USB flash drive, using an online backup service, or both. Then verify the quality by restoring backups to your home computer or another location.

Note: It is recommended to run an Open Dental Backup only when other users are not working in Open Dental. Otherwise, users may experience aUE: Table 'procedurelog' is read onlyerror that will disappear when the backup is complete.

There are several backup options to consider when making a backup plan.

Backup Tool

Online Backups

Manual Backups

What to Back Up

\\SERVER\mysql\data\: The database that stores patient data.

\\SERVER\OpenDentImages\:The A to Z Folders that store files you scan or import. See Paths.

Other office documents unrelated to Open Dental.

Frequency

At minimum, backups should be made daily. If you at least have good daily backups, then the worst-case scenario is having to re-enter one day of data. Incremental backups throughout the day would be a little bit better, if you have that ability. Backing up while the database is in use is possible, but only with certain software, and it can get complicated.

Encryption

Backed-up data should be encrypted so that patient data remains secure, for example in cases of theft or loss. See Encryption of Data at Rest and in Transit.

Encrypted USB drives: We recommend purchasing a few and rotating them. An example is http://www.ironkey.com.

Hardware Encrypted Drives (Recommended), such as those offered by Apricorn (https://www.apricorn.com/). Data is encrypted by a dedicated processor located on the encrypted drive instead of using the computer's processor. Hardware encryption devices run independently of the operating system and any additional software. Data is protected from unauthorized access by pin numbers.

Software Encryption, such as BitLocker Encryption. This will entail encrypting the data first, then backing it up. Software encryption uses the computer's resources to encrypt data. Software must be updated, or reinstalled if you change operating systems.

RAID is not a backup solution and should not be relied on for backups or disaster recovery plans.

Archives

You also need to keep old copies of some of your backups. You can make separate monthly backups to a different flash drive. When it fills up, put it in storage, and get another one. If you are using imaging, then manually backup theC:\OpenDentImagesfolder to CDs, DVDs, or removable hard drives.

A good use of archiving would be to use a file versioning systems which allow you to go back to a specific date and time and restore files that might have been accidentally deleted or modified. These programs can typically backup to multiple locations safely and securely.

MySQL Service: Automated stopping and starting of the MySQL service is not important because backups can safely be done without stopping the MySQL service. You would never restore directly to the live database location, so the backup service is not involved with the actual final move of the restored data to the live location. All of the backup services are good at copying locked files. In the rare case that a locked file causes a failure, it should only affect that one file and should not be a major problem. When restoring a database using the data provided by your backup service, follow these general steps.

Restore to a new location (likeC:\restored files\or to another machine), not to your live database on your server.

Stop the MySQL Service.

Make a manual local backup of your current database (if there is one still there).

Delete the current database.

Place the restored database in the location where your live data was.

Turn back on the MySQL service

<top>

NovaBACKUP PC/Server/BE v19.x and newer

Question:

Is there a way to add the media to be backed up to a pool once or similarly, so that backups are made to any media in the pool?It must be possible to trace which medium was backed up on which day.

Answer:

No, this is not possible with the SMB products NovaBACKUP PC/Server/BE. If you have a backup job written to changing media, the media view under "Restore" always reflects the content of the last (most current) tape.If you want to recover from a previous (older) tape, you must first import it. Alternatively, you can create one full backup job per day (Mon, Tue, Wed etc.) and configure it to "Overwrite". Enter the appropriate names for the backup job, the media name and the schedule, e.g. for Monday:

Name of the backup: MoMedia name: MoScheduling name: Moetc.

You should then label the media accordingly.

If you find that you cannot Mount an Image Backup and receive a message in the Image Backup Tools area of NovaBACKUP saying "Unable to mount the image. You may need to reboot," but you know that you have restarted your PC since last installing or upgrading NovaBACKUP software, or if the NovaBACKUP Image Backup Wizard's "Launch Image Backup Tool .." or "Image BackupSchedule" function do not launch or appear to not go anywhere, you will probably need to fix the Disaster Recovery Drivers that are currently installed.

It is important to know that NovaStor makes changes to the Disaster Recovery Drivers (Image Backup Drivers) component in new versions of NovaBACKUP and in some cases the driver component often times does not get upgraded nor removed properly during an upgrade or even new install (if you ever had a prior version of NovaBACKUP installed it may leave leftover remnants of this driver in the Windows Registry) of NovaBACKUP. In some cases it is necessary to remove the driver altogether and that normally cannot successfully be done by removing the entry in Programs and Features, displayed as "Disaster Recovery Drivers" for whatever reason and so that requires the end user to remove Windows Registry Entries associated to the Disaster Recovery Drivers package. The instructions for how to do that are here.

Recommended solution:

If you recently updated to version 19, and are now unable to mount image backups please follow these steps

Please follow this procedure to update/repair the Image Backup Mount Drivers in NovaBACKUP 19.1 when updating from a previous version:

Locate the setup file you used to install the current version of NovaBACKUP on your machine

Run this setup file, when it starts select "Maintenance", "Next", followed by "Change"

Select the drop-down to the left of "NovaBACKUP Image Backup"

Select the arrow next to "Virtual Disk Driver"

Choose the option "Will be installed on local hard drive"

Submit a Ticket

Select "Next" until you "Finish", if prompted to reboot, choose "Yes"

Close the "NovaBACKUP Download Installer" dialog if it is open

You should now be able to mount an Image Backup

NOTE: You must reboot the machine to allow changes to the registry\drivers to be applied.

If you continue to have trouble, please follow these steps:

Follow these instructions to download a .reg file to remove previous drivers from the Windows Registry:

First, make sure that you are logged in to Windows as a user with Administrator rights. If you are NOT logged in as a user with Administrator rights currently then these instructions will not work because there will not be enough rights to perform the actions necessary.

Using your web browser download the simple registry (.reg file) fix for this installation issue by clicking this link to download the fix, and be sure to take note of where the file is saved to: http://filestore.novastor.com/Downloads/NovaBACKUP/19.1/NBK_DRDrivers_Remove.reg

Alternatively, you can download the fix in .ZIP format. If you use this method, you will need to extract the .reg file out of the .zip file to continue to the next step: http://filestore.novastor.com/Downloads/NovaBACKUP/19.1/NBK_DRDrivers_Remove.zip

NOTE: If your anti-virus or anti-malware real-time protection software blocks .reg files from being saved then you may need to temporarily disable that type of software while you download and run this registry fix. You can re-enable the software after the fix is performed.

Merge it (double-click)

Reboot the machine

Run the NovaBACKUP Setup.exe file

Select Maintenance -> Repair

Reboot the machine once the repair operation completes

Attempt to mount an Image Backup

If this still does not work, please follow these steps before scheduling a Support Booking through a Support Ticket:

First of all make sure that you are logged in to Windows as a user with Administrator rights, make sure the user is in the Administrators Group and that you log in with that user again to Windows if it did not have Admin rights in the first place. If you are NOT logged in as a user with Administrator rights currently then these instructions will not work.

Browse to this folder:

C:\ProgramData\NovaStor\NovaStor NovaBACKUP\Dr\

Delete all of the *.tmpfiles in the above folder. If no files exist go to the next step.

If you are uncomfortable performing registry changes yourself please follow the previous steps only.

The following steps are for advanced users.

Windows Registry editor contains important Operating System information, if you are unsure about what you are doing please be aware that changing or removing some entries can cause your system to become unstable.

Next, load Windows Registry Editor, by going to your Start Menu and then choose run or search, and type in "regedit.exe", without the quotes, to run that Registry Editor program. Now inside the Registry Editor application locatethe vertical scroll bar in the middle of the screen and scroll up to the top-left using the scroll bar and click once on the "Computer" object at the very top left of the program so that "Computer" is what is selected. Now click on Edit menu and then Find and do a find for this registry key and make sure that you enable the "Match whole string only" option check-box at the bottom of the Find screen:

273DCB41A0C230340A390A5933D13024

Once the above registry key is located, delete that entire root level registry key located on the left side of the window pane displayed in the "Registry Editor" program. The entry that you are actually going to delete is the named long key with text that contains "273DCB41A0C230340A390A5933D13024", without the quotes, in the name of that key. You may find up to 10 registry key results in total to delete, and here is an example of the first registry key that you will be deleting:

Computer\HKEY_CLASSES_ROOT\Installer\Features\273DCB41A0C230340A390A5933D13024

Now right-click on that registry key using the left-hand window pane for that search result it should already be highlighted for you in gray color and then click "Delete" to remove that entire key. It will prompt you to Confirm Key Delete, answer Yes to delete the registry key. That takes care of deleting the first matching registry key, but there are normally about nine more to be found. Next we will show you how to remove the remaining nine or so entries.

Next, inside the Registry Editor, click on the Edit menu and then click on "Find Next" (or press F3 on your keyboard to perform a Find Next) and continue your find search for the same text string "273DCB41A0C230340A390A5933D13024", without the quotes. Continue finding that registry key and perform a delete on each of the keys that match that string.

An example of all of the registry keys that you may typically find during a Find at this point are shown below in order from first result found to the last result found. Here we see the remaining nine registry keys that were found in order from first to last found entry. Each of these entries can be searched for using the Address Bar area of the Registry Editor to copy and paste in each of the registry keys text string to that Address Bar and press Enter to look for that entry one by one.

Computer\HKEY_CLASSES_ROOT\Installer\Products\273DCB41A0C230340A390A5933D13024Computer\HKEY_CLASSES_ROOT\Installer\UpgradeCodes\B63AE9372BAD7C24186A3B90B1FCC6B2Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Features\273DCB41A0C230340A390A5933D13024Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\273DCB41A0C230340A390A5933D13024Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\UpgradeCodes\B63AE9372BAD7C24186A3B90B1FCC6B2Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UpgradeCodes\B63AE9372BAD7C24186A3B90B1FCC6B2Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\22E815E899BFCC645ABF32BBE1CF57D7Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\D74123BA4797F0342951194F43C84BAAComputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\273DCB41A0C230340A390A5933D13024

For each result you find right-click on the registry key using the left-hand window pane for that search result it should already be highlighted for you in gray color and do a "Delete" command to remove that entire key. Make sure that from inside the Registry Editor, click on the Edit menu and then click on "Find Next" (or press F3 on your keyboard to perform a Find Next) and continue your find search for the same text screen mentioned above, "273DCB41A0C230340A390A5933D13024",without the quotes, to locate all of the results.

Alternatively you can delete each of the exact mentioned registry keys shown in the above list by using the "Address Bar" (check to make sure the "Address Bar" option is enabled in Registry Editor by clicking on the "View" menu in the toolbar and make sure that the checkbox is enabled for "Address Bar" in this menu) entry box area of the Registry Editor which is the entry box just below the "File - Edit - View - Favorites - Help" toolbar at the top of the Registry Editor application screen. If you go to the top-left of the Registry Editor and scroll up using the vertical scroll bar to the top of the screen you should see an object named "Computer", select that object and then just above where you selected "Computer" in gray color it will show the text "Computer" again in the address location area of Registry Editor. Inside that area you can paste in the entire text string for one of the 9 registry keys mentioned above in to that field to overwrite the contents of that address location field with the copied contents to locate that exact registry key and delete it via the left-side window pane in the result, the key will already be highlighted for you to delete on the left-side window pane, in gray color.

In total you may find about 9 entries to remove which match the"273DCB41A0C230340A390A5933D13024" registry key string.

Now, there may be additional Registry Keys that need to be deleted that do not contain the273DCB41A0C230340A390A5933D13024 text string. At this point while still inside the Windows Registry Editor, locate the vertical scroll bar in the middle of the screen and scroll up to the top-left using the scroll bar and click once on the "Computer" object at the very top left of the program so that "Computer" is what is selected. Now click on Edit menu and then Find and do a find for this registry key and make sure that you enable the "Match whole string only" option check-box at the bottom of the Find screen:

Disaster Recovery Drivers

If the Registry Editor does find a registry key which matches that text string, delete that entire root level key by right-clicking on the item highlighted on the LEFT side of the Registry Editor program screen.

Continue finding that registry key and perform a delete on each of the keys that match that string. Go to the Edit menu and click Find Next (or press F3 on your keyboard to perform a Find Next).

You may find additional entries which match the "Disaster Recovery Drivers" registry key strings.

Delete each of those registry keys if you find them by selecting the already highlighted key on the left window pane which is already going to be highlighted in gray for you to delete. Right-click and delete that entry. Continue finding that registry key and perform a delete on each of the keys that match that string. Go to the Edit menu and click Find Next (or press F3 on your keyboard to perform a Find Next).

Perform the Find command until the Registry Editor displays a pop-up window that says "Finished searching through the registry". Now you are done searching the Registry for these keys. You can go to the File menu and click Exit to exit out of the program. In total you should have find about 10 registry key items to delete.

Now Restart the computer. This step is 100% necessary or everything that you just did will not have any effect if you continue here without the computer reboot.

Test After Rebooting Your Computer

After restarting your computer load NovaBACKUP software and when the Home screen comes up click on "Image Backup- Start the Image Backup wizard" and then click on the "Launch Image Backup Tool for Backup/Restore/Boot CD Creation" item. You may need to click Yes here to continue.

To verify that the Disaster Recovery Drivers are installed properly, and able to be utilized, there are two things that you can do now to verify it:

First go to Device Manager in Windows to check to see if the "O&O DiskImage" driver itself is showing up in Device Manager.

This driver is 100% required to be in place and in working order in order to be able to Mount an Image Backup to restore individual files. Investigate the Device Manager for a item in the list of drivers shown as "O&O DiskImage". Expand that "O&O DiskImage" section to show the actual driver named "O&O DiskImage Virtual Devices". Make sure that this O&O DiskImage Virtual Devices" device itself does not have an exclamation mark on it to note that the driver is not working properly.

You can now attempt to Mount an Image Backup to restore individual files from the image backup using the "Mount backup image volume to a drive letter" function using the Image Backup Tool -> Tools area using KB article: Mount (and Unmount) an image backup to Restore Files in Windows, keep in mind the image backup file has to be on a locally connected device and not on a network device/path.

Still not working?

If you have valid NovaCare Support for your NovaBACKUP, check your NovaCare Status here, by entering your NovaBACKUP license key at the bottom of the web page, and you are hesitant to perform these steps yourself to correct the Disaster Recovery Drivers to be able to Mount an image backup to restore individual files, feel free to.

Tape Pool Maintenance fails

NovaBACKUP DataCenter

Please look in the GUI-> Dashboard-> SystemMessages for the entries for the maintenances of the Tape Mediapools.

Double-click to open the respective protocol.

Copy the contents of the latest maintenance logs into a mail to me.

Then I can see if the maintenance runs correctly or makes a mistake.

A common cause and the solution is described here: Tape mediapool maintenance fails

NovaBACKUP PC/Server v18.x and newer

For NovaBACKUP PC/Server you may need to activate the additional image backup options and deactivate some plugins that you do not need in NovaBACKUP PC/Server.

Disable Windows Defender and/or other anti virus application/settings.

Download NovaBACKUp installer and save it to your Desktop:

http://filestore.novastor.com/Downloads/NovaBACKUP/Current/Setup-NB-PC.exe

http://filestore.novastor.com/Downloads/NovaBACKUP/Current/Setup-NB-Server.exe Execute NovaBACKUP installer from Desktop with right mouse click and "run as admin".

Click on "Maintenance" => "Next" => "Change".

Enable all "NovaBACKUP Image Backup" options:

Image 1: NovaBACKUP Image Backup options

Please note:

A reboot is required to activate the new installed components.Image backup/restore will work without reboot, mounting an image will work only after reboot!

For NovaBACKUP PC and Server disable all "NovaBACKUP Plugins":

Image 2: Disable all NovaBACKUP plugins for NovaBACKUP PC and Server

For NovaBACKUP BE activate all needed server components (plugins).For Hyper-V backups you will need all VMware components. Activate all VMware plugins. Finish installer and reboot system.

If you do not use CMon (NovaBACKUP Monitoring Tool) you may disable "Agent Service":

Image 3: Disable Agent Service

Proceed with "Next" => "Change", then reboot.AMo