I'm not sure about your error, but for converting. It will convert just about any file format to DVD, and burns it, all in one program. Plus it's really easy to use. I'll look into the error you're getting with Nero; I also use Nero6 all the time, and never really have any trouble with it either, but I'll see if I can help You must log in or sign up to reply here. Show Ignored Content. Make sure that data connection and power cables are connected properly.

Open Computer Management and, in Device Manager , verify that the library is displayed. Remove the tape from the library autoloader.

Consult the documentation for your hardware for instructions on troubleshooting tape errors. When the tape is repaired, run the library job again. In the Management task area, on the Libraries tab, select the library, and then, in the Actions pane, select Rescan. Change the cleaning tape, and in the Management task area, on the Libraries tab, in the Actions pane, select the drive, and then select Clean.

Contact product support for your hardware to have the drive serviced. You should also review all protection groups to identify if the absence of this drive requires changes to drive allocations. In the Management task area, select the Libraries tab, and then, in the Actions pane, select Inventory library to run an inventory. Operation cannot be performed because DPM Administrator Console is not synchronized with the actual state of the library.

Close and then reopen DPM Administrator Console to synchronize it with the actual state of the library. Use the front panel of your library to move the tape from its current location to the slot specified above. In the Management task area, select the Libraries tab, and then, in the Actions pane, select Inventory library. Make sure that there are no pending alerts for the library. Remove the tapes from the library. Clear duplicate barcode information from DPM. Replace the barcodes on the tapes and then insert them back into the library.

Inventory the library. In the Management task area, on the Libraries tab, select Inventory library , and then select the option to perform a detailed inventory. It is likely that your data spans multiple tapes and the catalog information is present on another tape.

Insert all tapes associated with the backup, and then retry the operation. Check for any Free tape threshold reached alerts generated by the libraries. If such alerts are present, proceed to step 3. In the DPM Administrator Console, select Management on the navigation bar, select the Libraries tab, and then do the following: Expand all library slots and check for any free or expired tapes.

If there is none, proceed to step 3. Check for any suspect tapes in the library. If suspect tapes are present, see Managing Suspect Tapes. Insert new tapes into the library, and then run a Fast inventory action followed by an Identify unknown tapes action.

In DPM Administrator Console, select Management on the navigation bar, select the Libraries tab, and make sure that the new tapes appear as free. Then, select Monitoring on the navigation bar, select the Alerts tab, and restart the failed jobs.

DPM could not reserve the drive resource because one of required drive resources is not online or it needs cleaning or servicing.

View and resolve all alerts for the library and its drive s. After resolving the alerts, retry the operation. In the Management task area, select the Libraries tab, and then, in the Actions pane, select Rescan. After the rescan operation has completed successfully, retry the operation. View and resolve all alerts for the library and drive, or wait for the other operations to complete.

Retry the operation after resolving the alerts. Either there is no drive online or all the drives need cleaning or servicing. In the Monitoring task area, on the Alerts tab, resolve all alerts for this library and its drive. After resolving the alerts, retry this operation. If you have drives that are functioning correctly but that are currently being used, wait for the other operations to complete, and then retry this operation.

If this library is associated with an active protection group, modify the protection group to associate it with another library to prevent tape-related jobs from failing. If you want to use this library for your tape-related jobs, in the Management task area, on the Libraries tab, select this library, and then, in the Actions pane, select Enable library. Retry the failed tape backup job by using the alert in the Monitoring task area. If your copy failed because the tape backup job did not run at all, in the Protection task area, select Create recovery point - tape to create a short-term tape backup.

After successfully running the tape backup, retry the failed copy job by using the alert in the Monitoring task area. All encrypted backup jobs will fail after this time. If this certificate contains a private key, move this certificate to the DPM recovery certificates collection for recovering data in the future, and replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups. If this certificate does not contain a private key, replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups.

To resolve this error, do the following: If this certificate contains a private key, move this certificate to the DPM recovery certificates collection for recovering data in future, and replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups.

See also Deploy protection groups. Check to see if there are any active alerts indicating suspect tapes. If such an alert exists, take the appropriate recommended action, and then retry this job. Use this tape on a DPM server that is authorized to read this tape. Add certificates to the DPM backup certificates collection. This is because DPM is not synchronized with the current state of the library.

In the Management task area, on the Libraries tab, select the library, and then select Inventory library. If enabled, select the Fast inventory option; otherwise, select the Detailed inventory option.

This may be because the data on this tape is corrupt. If you have another copy of this tape, use that to retry the recovery. If you do not have another copy of this tape, in the Recovery task area, select all required individual recoverable items, and then perform the recovery.

Hardware snapshots of the DPM replica and recovery point volumes are not mounted on the protected computer for SAN recovery. Use your SAN software to take hardware snapshots of the DPM replica and recovery point volumes, and to mount them on the protected computer. To resolve this error, do the following to erase the contents of the tape: In DPM Administrator Console, in the Management task area, select the Libraries tab, select the tape, and then click Erase tape.

After erasing the tape, DPM can use it for backups. In the Management task area, on the Libraries tab, select the library, and then, in the Actions pane, select Inventory library. Make sure that drives of this library are zoned properly. Make sure that all drive-related alerts for this library are resolved.

Make sure that the network connection to the computer hosting the global DPMDB database is properly configured. However, this tape is not marked as a cleaning tape. In the Management task area, on the Libraries tab, select this tape, and then select Mark as cleaning tape. The cleaning operation may have failed. If supported, check the front panel of your library to verify that this cleaning operation completed successfully. If the cleaning operation failed, try changing the cleaning tape, and then run the cleaning job again.

DPM is not synchronized with the current state of your library. In the Management task area, on the Libraries tab, select Inventory library. If available, select the Fast Inventory option, otherwise, select the Detailed Inventory option. In the Management task area, on the Libraries tab, select Inventory library to run inventory. If enabled, select the Fast inventory option. Otherwise, select the Detailed inventory option. This will update the library state as seen by DPM. Retry the operation after DPM has completed the inventory successfully.

This is possibly due to a hardware issue. If available, select the option to perform a fast inventory, otherwise, perform a detailed inventory. Check the SCSI and bus mappings of the drive to make sure that the drive is mapped correctly.

If you change any of the mappings, in the Management task area, on the Libraries tab, and then select Rescan. Check for loose connections of data or power channels. Make sure that the library appears in Device Manager. Make sure that the door on the library is closed. Refer to your hardware manual for other troubleshooting steps. If the drive is being serviced, you can ignore this alert. Make sure that the drive is powered on.

Make sure that the drive is connected properly. In Device Manager, if the drive is not enabled or is not visible, refer to your hardware manual for other troubleshooting steps.

If it is, in the Management task area, select the Libraries tab, select this tape, and then, in the Actions pane, select Mark as cleaning tape.

Examine the front panel of your library to see if any errors are being reported by your library. This could be a problem with your drive or tape. Select this tape and select Identify unknown tape. If this operation fails, it indicates a potential problem with your tape. Load the tape in the other library, select this tape, and select Identify unknown tape.

On the Libraries tab in the Management task area, select Rescan in the Actions pane. Check for loose data or power channel connections.

Make sure the library is visible in Device Manager. The drive will not be used for further operations until it has been cleaned. If you are seeing this error frequently, service the drive. Tape might not be properly inserted in the stand-alone drive or the stand-alone drive is not ready. Check to see if the tape has been inserted correctly into the drive. Check to see that the drive is ready and operational. Rescan failed because the tape drive or library hardware does not seem to have been set up correctly.

In Device Manager, check to see that the drivers for the tape drive or library hardware are installed correctly. Determine if any other process on the DPM server is currently using the library. If this is the case, stop the process. Check to see that your library is powered up and functional. The information in this file is not formatted correctly.

To update the library state, perform an inventory, and then retry the operation. Verify that the tape and the drive type are compatible and that the drive is supported. Also find out if you need to upgrade the drive firmware. This may be because the tape data is corrupt. If you have another copy of this tape, use that instead for the recatalog operation.

If this is the only copy of the tape and you want to recover as much data as is possible: 1. On the Libraries tab in the Management task area, select the tape. Select View contents. Copy the contents of this tape to disk. If it fails consistently, remove the protected data from the protection group and reprotect it again. Increase the disk allocation space for the recovery point volume, or delete old recovery points by using the Remove-RecoveryPoint cmdlet.

In these cases follow these steps: 1. In the Modify disk allocation dialog, identify the volume that corresponds to the recovery point volume for the data source. Select Disk Management , then right-click the custom volume. Select Extend Volume. To validate exclusion or inclusion filters for the data source, select Modify Protection Group.

After you modify the protection group, select the link below it to run a synchronization job with a consistency check. If the problem persists, the recovery point may be corrupt. Retry recovery from another recovery point.

To delete the change journal, at a command prompt run: fsutil usn deletejournal For more information, see the command usage. On the Exchange server, set the Overwrite database flag and retry the operation. The volume for one of the specified database file locations does not exist. Check to see that the volumes for all file locations specified are available on the destination SQL server.

Future backups will also fail until this issue is fixed. If your recovery point volume is offline, bring it online and then run consistency check for the affected data sources. If your recovery point volume is not available to bring online, remove the affected members from protection and reprotect them. When stopping protection for the affected members, select the option to delete the replica on disk.

Protection for this data source will fail to prevent existing recovery points from being deleted before their expiration. Verify that there are no pending recovery point volume threshold alerts active for this data source and rerun the job.

Future backups are also likely to fail until this issue is fixed. Rerun the consistency check and see if it resolves this issue. Check to see if your disks are connected properly to the DPM server. If there are any disk cabling issues, correct them and then run a consistency check.

If you are certain that you do not have any disk cabling issues, clear the VSS fault. If running a consistency check does not resolve this issue, increase the page file size on the DPM server and then run the consistency check job. Check the volsnap events in the Windows Event Log. Check the Event Viewer entries to determine the cause. After you correct the issue, retry the operation.

If the problem persists, contact your network administrator to diagnose possible network issues. All future backups will fail until this is resolved. Use a different DPM server to protect this datasource.

Download and install the latest driver and firmware updates from the tape drive vendor. Many tape drive vendors also offer utilities that you can use to diagnose hardware problems. Clean and service the tape drive. Update the library state by performing an inventory, and then retry the operation. On the Libraries tab in the Management task area, select Inventory library.

Check that the tape and the drive type are compatible, and the drive is supported. Also check if the drive firmware needs an upgrade. Share this folder out as a share called temp. Use another copy of the tape and retry the operation.

You can view the contents of the tape to confirm that it contains the expected data. DPM failed to recatalog the contents of the tape because it encountered a critical error while attempting to read catalog information from this tape.

If this is the only copy of the tape and you want to recover as much data as possible, then select this tape on the Libraries tab in the Management task area, click View contents , and copy the contents of this tape to disk.

DPM has encountered a critical internal error. Either it was already in a bad state or it entered a bad state during the current operation. Make sure that the required licenses are installed on the server, and then retry the backup.

This can also occur if you are attempting to back up a virtual machine and the VHD file is located in the root of a CSV. To work around this issue, create a folder and move the VHD inside the folder.

Depending on which situation you were in when you encountered this error, the following sections describe how to resolve this error. Volume Shadow Copy Service VSS error on a virtual machine To resolve this error in this situation, take one or more of the following actions: Make sure that the version of the Integration Components package on the virtual machine is up to date.

On the host for the virtual machine, open Server Manager , expand Roles , select Hyper-V , and then in the Events list in the Summary area, look for a warning that the Integration Components package must be updated. Make sure that all the writers on the virtual machine are in a stable state.

On the virtual machine, open an elevated Command Prompt window, type vssadmin list writers , and then press Enter. Make sure that there are no unresolved VSS errors on the virtual machine. Resolve any VSS errors that you find. Expand Diagnostics , expand Windows Logs , and then review the Application and System events for resolution steps. Expand Roles , select Hyper-V , and then, in the Summary area, review the Events list for resolution steps.

Creating a recovery point by using incremental backup for a computer that's running Exchange Server Circular logging might be enabled on this data source. DPM does not support incremental backups for a computer that's running Exchange Server on which Circular Logging is enabled.

To resolve this error in this situation, clear the Circular Logging check box, and then try to create the recovery point again. The next incremental backup fails when an incremental backup is performed after you run ntbackup on the storage group.

Create a DPM full recovery point before performing an incremental backup. This may have happened because the volume name is no longer valid. Increase the space allocated for the VSS diff area of volumes involved in protection on this server. If the problem persists, you can increase the change journal size or configure the current protection group to synchronize more often. To change the change journal size 1. Select Modify disk allocation , then select the Protected Server tab.

Select Modify and change the space allocated. To change the synchronization schedule: 1. Select the protection group in the Protection task area. In the Actions pane, select Modify protection group. To configure change journal size, select the Modify Disk Allocation link that appears below the alert window. On the Disk Allocation page, select Protected Server and select Modify , then change the space allocated.

Verify that there is at least MB of free space on the volume being protected. The change journal ID may have changed since the last synchronization. DPM is unable to track changes on this computer. File copy failed. Make sure that the source and destination locations exist and have Full Control permissions for the local system account.

Wait for the earlier backup job to finish, and then retry the backup. Or, you can cancel the current job, and then retry the backup job. DPM could not find a valid recovery point on disk. On the Jobs tab in the Monitoring task area, check for failures of synchronization jobs and resolve those. Next, create a valid recovery point and then run the backup to tape job again. To create a valid recovery point: 1.

For application data, in the Protection task area, select Create recovery point , and then select Express full backup on disk. For file data, in the Protection task area, select Create recovery point and then select Create a recovery point after synchronizing. The incremental backup job was cancelled because the associated full backup for the data source is not available or there is a newer version of the backup on which this job depends. This is a non-fatal error.

Another backup has been created at approximately the same time as this backup. Use the other backup for recovery. If you are backing up to tape, perform a full backup. If you are backing up to disk, perform an express full backup. On the Libraries tab in the Management task area, select the tape and then in the Actions pane, select View Contents. Verify that you do not have more than protectable data sources on a single volume.

If this is the case, check to see if you can split your data source across more volumes. Protection cannot continue. Check to see if you are protecting a clustered resource which has undergone a dirty failover. In this case, DPM requires a synchronization with consistency check before it can continue protection. To validate exclusion and inclusion filters for the data source, in the Protection task area, select Modify Protection Group.

If modifying the protection group does not start a consistency check, run a synchronization with consistency check. Synchronization will fail until the replica cleanup succeeds. This may happen if the replica volume is being accessed from outside of DPM. See the detailed error, resolve the issue with respect to the replica volume path, and retry the job.

Otherwise, DPM will synchronize with the changes during the next scheduled synchronization job. DPM has detected changes in file locations or volume configurations of protected objects since the data source was configured for protection. DPM detected that some protected objects are missing since it was configured for protection. In the Protection task area, select Modify Protection Group to update the configuration information for the data source on the DPM server and to increase the replica volume size if necessary.

DPM detected new protectable objects for the data source since it was configured for protection. DPM detected changes in existing protected objects and detected new protectable objects for the data source since it was configured for protection. A synchronization job with consistency check will be automatically triggered after 30 minutes. DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job.

All incremental backup jobs will fail until an express full backup runs. For backup failures If you see this failure as part of a backup job, in the Protection task area, select the SQL Server database, select Create recovery point , and then run an express full backup.

Alternately, you can wait for the next scheduled express full backup to run. For recovery failures If this failure occurs as part of a recovery job, then try to recover from another point in time. Make sure that this database is not already protected by another backup application.

After stopping the service, DPM was unable to successfully start the service. Check that the SQL Server service on the protected computer can be sent the start command successfully. After you ensure that the service can be successfully started, retry the recovery. If this error occurs again, try to recover the master database from another recovery point.

DPM was unable to successfully stop the service. Check that the SQL Server service on the protected computer can be sent the stop command successfully. After you ensure that the service can be successfully stopped, retry the recovery. Contact the Exchange Server admin. Verify the cause of failure from event logs entries on the Exchange server.

If you recently upgraded your Exchange server, copy them from that server to the DPM server. Contact your Exchange Server administrator, and then verify the issue. You can recover the last known good backup to address the corrupted state. Contact the Exchange Server administrator. Event logs on the Exchange server may help resolve the issue. Verify that the volumes are online and that the file system is in a consistent state.

If the volume is locked, unlock the volume and retry the operation. The alias of the user to which DPM has to connect the recovered mail box is online and connected to an Exchange server. If the replica has been marked inconsistent, run a consistency check on this data source.

Delete the change journal on the protected computer by using the FsUtil. Next, run a consistency check on the data source. This can cause backup or recovery jobs to fail. To fix this issue: 1. Change the location of the database log file so that its physical path is as short as possible. Run a consistency check job for this database. To troubleshoot this issue, verify the following: 1.

The database is online. The database is not in a restoring state. The database has not been deleted. The database is accessible. If the database was part of a mirroring session, either re-establish mirroring between the partner SQL Server databases or remove the database from protection and recreate the protection group for this database.

Protection jobs will fail until the recovery point volume is brought online. In the Protection task area, select Create recovery point-disk and select Create a recovery point by using express full backup. The data source is online. The data source is not in a restoring state. The application VSS writer is running. The data source is accessible. The data source is not missing.

If the data source is a member of a SharePoint farm, verify that it still exists in the SharePoint farm configuration. For more information on this error, go to Hyper-V Protection Issues. The recovery to the latest point in time failed. This tail log restore failed. You can do the following to fix the issue: 1.

Recovery to the latest point in time is not possible immediately after another recovery has been performed on the same database. Allow a synchronization job to run before you attempt a recovery to the latest point in time. Choose an alternate point in time to recover to, if you run into this problem repeatedly. The recovery to the latest point in time has failed.

This transaction log backup has failed. If the SQL Server log chain is broken, you will have to run a full backup to reinitialize the log chain 2. If the DPM replica for database is invalid, you will have to run a consistency check operation for this database.

Choose an alternate point in time to recover to, if transaction log backups cannot be successfully run against database. For more information, look at the SQL Server error logs. On the Exchange Administrator Console, set the Overwrite database flags for the databases being recovered and retry the operation. Check to see that no application running on this computer is malfunctioning to cause this high file system activity.

If you consistently run into this error, in the Protection task area, select Modify disk allocation. To increase the change journal size on the protected computer, on the Protected Computers tab, select Modify. File may be in use by some other application. In the Monitoring task area, resolve the Unable to configure protection alert for this data source, and then select the link that follows to retry the job. In the Recovery task area, select the recovery point prior to the latest recovery point.

In the Management task area of the DPM Administrator Console, on the Agents tab, enable the protection agent on the protected computer. Some data from this recovery point may contain partially synchronized data. Make sure that the pre-backup script finishes execution within the time specified, or increase the timeout period. Make sure that the post-backup script finishes execution within the time specified, or increase the timeout period.

Make sure that the pre-backup script or post-backup script configuration XML file does not have any errors and that the XML is well formed. Make sure that there are no pending recovery point volume threshold alerts that are active for this data source, and then rerun the job. Retry the operation and specify a storage group that is not a recovery storage group, or select the Recover to Recovery Storage Group option. In the Protection task area, create a recovery point for this database.

Scheduled consistency check will not be run on consistent replica. Provide an alternate name for the database to be recovered. Ensure that no database with the name you have specified already exists on the SQL server.

You will be unable to perform granular level recoveries from this recovery point. No action is required because the next scheduled full backup will synchronize the list of recoverable objects. Alternately, in the Protection task area, select the required protected object, click Create recovery point , and select the option to create a recovery point using a full backup.

If the error has been reported for your Exchange server, it indicates that the Exchange server backup files may be corrupt.

Follow these steps to resolve the issue: 1. Consult the Exchange server administrator to verify if the databases and logs on the Exchange server are in a good state. If the database and logs on the Exchange server are not corrupt, you need to run a synchronization with consistency check for this data source. In case the database and logs on the Exchange server are corrupt, you can choose to recover the Exchange data from the last known good backup.

Check to see that the post-snapshot step does not have any errors and can complete successfully. DPM failed to create the backup. If you are backing up only System State, verify if there is enough free space on the protected computer to store the System State backup.

On protected computers that are running Windows Server , verify that Windows Server Backup WSB is installed and that it is not performing any other backup or recovery task. You can see the errors reported by WSB in the event log on the protected computer. For resolution actions and more information on these errors, go to Backup Operations.

To resolve this error, do the following: If you use Windows Server Backup to back up a volume, do this only by using the Backup Once Wizard. If you use the Backup Schedule Wizard to perform scheduled backups, make sure that the volumes that are being protected by DPM do not contain application data such as Exchange Server mailbox stores or SQL Server databases. Reconfigure Windows Server Backup. Then, in DPM Administrator Console, in the Protection task area, select the volume, select Create recovery point , and then, in the Actions pane, select Express full backup.

This may cause the consistency check to fail. The bit version of eseutil. You can also choose not to run Eseutil consistency check for this protection group, by deselecting the Run Eseutil Consistency check option. This is not recommended because it will not ensure that the protected Exchange data can be recovered.

For more information on this error, see Hyper-V Protection Issues. Where are you located? There's an app called OpenSignal that is quite revealing for tower coverage. The unlock request can take up to two business days to process for devices not currently under a BoostUP! During that time, the following steps can help ensure the request processes properly:.

Tap UICC unlock for a settings refresh. And I've done a full factory reset now. My condolences. What a nuisance for you. I wish Boist was handling this network switchover more smartly.

If that doesn't work out, may be time to move on. They're cheaper, not sure they're smarter tech and customer support though. Still struggling with this issue.