Backup Assist Support
Last updated Created Further assistance 09th Dec 2015 20th Aug 2007 BackupAssist Support page All Files Volume Shadow Copy Error 0x80042319 - writer not responding Error code Product Applies to BA920 Backup to local cache only Dated Added: 07th Jan 2010 Disk I/O error. Known Cause 4 - Destination drives not formatted in NTFS If your destination drive is not formatted in NTFS, this can cause a conflict with the snapshot process which causes this Dated Added: 15th Dec 2008 Iomega REV system software is installed - should not be installed on Vista / Server 2008 or later Dated Added: 11th Jan 2009 Could not create
Backup may not be completed Dated Added: 15th Mar 2011 Warning: This backup appears to be configured as a full system backup- but not all critical volumes were backed up. Dated Added: 19th May 2010 Backup media will not be made bootable - an existing partition needs to be shrunk to make space for a new bootable partition Dated Added: 28th Each error is given a code corresponding to the relevant help document to make them easier to access. Each article outlines the current known causes of the error message you have encountered, together with ways to fix the problem and avoid a recurrence in the future.
Backup Assist Support
Known Cause 2 - Shadow storage on the source drives is not configured or not large enough. Dated Added: 17th Jun 2009 Mailbox backup cannot proceed as one or more dependencies are missing Dated Added: 17th Jun 2009 Unspecified ZipEngine exception. Known Cause 6 - Advanced format drives used as backup destination VSS snapshots have been known to fail because an advanced format drive is connected to the machine. Dated Added: 21st Oct 2013 BackupAssist v5 Beta Known Issues Dated Added: 17th Mar 2008 Error while copying or deleting compressed backup file.
- If you are backing up to a local destination Check that the backup drive is showing as Online and active within Disk Management.
- Dated Added: 03rd Jul 2007 A selected Exchange Server does not exist or is not currently available Dated Added: 03rd Jul 2007 Out of space when performing the backup Dated Added:
- If you are backing up to a network destination Check all network cabling (physically) to make sure it is not faulty.
- To give yourself fast access later, remember to save the link to "Favorites" in your browser menu.
- Error 7 - Incorrect Function This error typically occurs if there is an issue with the backup destination configured (most commonly network shares, but it can occur on local destinations as
- Dated Added: 05th Sep 2011 Duplicate file entries found in a backup catalogue.
- Dated Added: 15th Dec 2008 The destination does not support 'single instance store' Dated Added: 15th Dec 2008 Could not copy directory attributes Dated Added: 15th Dec 2008 Invalid handle Dated
- Known Cause 5 - The Sqlvdi.dll file unregistered on the system This error is generated if there is an issue with the file Sqlvdi.dll on the system.
- Please send technical support a copy of the BackupAssist diagnostics file using the steps provided in the Resolution section below.
Dated Added: 18th Dec 2007 An error occurred while disconnecting a network resource Dated Added: 21st Feb 2008 An unknown error occurred trying to start the backup job Dated Added: 21st Dated Added: 22nd Aug 2010 Selected VSS Writer has no components Dated Added: 22nd Aug 2010 Local cache device was not detected. Dated Added: 27th Apr 2011 BitLocker USB media not found Dated Added: 11th Nov 2014 BitLocker key folder not found Dated Added: 11th Nov 2014 BitLocker key not found Dated Added: Dated Added: 20th Mar 2013 Multiple selections of the same SQL Server are not allowed.
To resolve this, remove the network drive from the backup and then re-run the backup job. Ba2513 Unable To Backup Volume More information on the defragmentation process is located at Microsoft-au/windows/improve-performance-defragmenting-hard-disk#1TC=windows-7 Error 4 - The device is not connected This error usually indicates that the backup destination was connected during the backup Dated Added: 16th Mar 2007 Exmerge must be installed for the mailbox export to work. https://www.backupassist.com/support/en/knowledgebase/BA30-An-unknown-error-occurred-trying-to-start-the-backup-job.html?cshid=BA30 Please review the following video on how to check Event Viewer for these specific event logs: https://www.youtube.com/watch?v=76u-MML-h9w.
To resolve this, it is recommended that you re-schedule your backup for a time where there is less disk usage.It is also recommended that you perform consistency checks (such as chkdsk) One of the drives should report an error which once addressed will resolve the issue. Unfortunately, this is on the hardware level and a format of the drive will not change this. Dated Added: 03rd Jul 2007 The backup job has failed to run because BackupAssist does not have an active license.
Ba2513 Unable To Backup Volume
You must have Windows XP or later. https://www.backupassist.com/support/en/knowledgebase/BA952-Volume-Shadow-Copy-Error-0x800423f2-writer-error-timeout.html?cshid=BA952 Resolution The error's known causes and resolutions are described below. Backup Assist Support Please review the following document from Microsoft on the use of chkdsk: https://technet.microsoft.com/en-us/magazinhttps://kb.backupassist.com/errormap.php?BA266e/ee872425.aspx It is also recommended that a defragmentation is performed on your destination drives. Unable To Create Vss Snapshot Backupassist If the sector size is anything larger than 512 (typically 4096 will be the result) the drive is an advanced format drive.
Check the Last Error and State output specifically. Dated Added: 05th Dec 2013 This File Archiving backup job uses a trial Zip to Tape Add-on license that is due to expire. At the Knowledgebase Home Page, you'll also find links to our technical support forum where you can ask a question or search for previous discussions regarding the difficulty you are encountering, Click on the Help menu at the top of the console.
Please look for any writers that are displayed with errors as this will indicate what part of the snapshot caused the error. Dated Added: 05th Dec 2013 This File Protection backup job uses a trial Rsync Add-on license that is due to expire. Dated Added: 16th Mar 2007 CDOEXM must be installed for the mailbox export to work. All Files Volume Shadow Copy Error 0x80042306 - provider veto Error code Product Applies to BA904 BackupAssist BackupAssist v4 and later Description This error occurs when the Volume Shadow Copy Service
This will take you directly to the entries available for the error message you have received. You should also run a registry cleaner after the other backup solutions have been uninstalled: https://www.backupassist.com/blog/support/how-to-resolve-a-ba910-volume-shadow-copy-error-0x80004230/. You will specifically want to look at the Application and System logs in this instance.
Last updated Created Further assistance 19th Nov 2015 20th Aug 2007 BackupAssist Support page All Files Volume Shadow Copy Error 0x800423f4 - writer error: non retryable Error code Product Applies to
Microsoft outline how to resolve this for SBS 2011 and Windows Server 2008 in their KB: https://support.microsoft.com/en-us/kb/2615182 Last updated Created Further assistance 14th Sept 2016 20th Aug 2007 BackupAssist Support page Summary: The Technical Support Knowledgebase is a fast and easy way to troubleshoot errors that appear in your BackupAssist report files. The steps to configure shadow copies varies between operating systems, so it's advised to check Microsoft's knowledgebase for the steps specific for your OS. Articles are listed by category.
It is best practice to only have one backup solution installed at any one time. Dated Added: 03rd Jul 2007 The backup job has failed because there is no active Open Files Add-on licence. Known Cause 3 - Scheduling Conflict Having two backup jobs running at the same time within BackupAssist can cause this error to occur if both backup jobs are trying to run If the issue persists, it could indicate a larger issue occurring with the system.
If this does not resolve the issue, check that all Windows Updates have been applied to the server.