Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
My Windows Server backup keeps failing

Answered My Windows Server backup keeps failing

  • Friday, May 04, 2012 11:43 PM
     
     
    Sign In to Vote
    0

    Windows Server backup keeps failing before ever getting started with the following error:

    "One of the backup files could not be created. Detailed error: The parameter is incorrect."

    Backing up up to external 3 TB drive with 2.33 TB free space. Server I need to backup is 775.95 GB (so no space issues).

    Folder has been shared to everyone with Modify permissions.

    Need help to get this going!

     

All Replies

  • Saturday, May 05, 2012 2:35 AM
     
     
    Sign In to Vote
    0

    Read the following technet article to troubleshoot your problem:

    http://blogs.technet.com/b/askcore/archive/2010/06/18/reasons-why-the-error-enumeration-of-the-files-failed-may-occur-during-system-state-backup.aspx

    Another resources for troubleshooting:

    http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/0be3d3b4-2561-4c4c-90ec-0f6ec939fd54

    http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/73bb349f-0acb-4360-8b74-c2b51d556de5

    Also, as the backup target is a 3 TB External drive, I suggest you to read the following thread:

    http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/889b01be-d333-4fc7-b005-e12b7b236ad7

    Please feel free to let us know if you have any question or concern.

    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


     
  • Monday, May 07, 2012 2:25 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hi,

      

    it looks like your backup target is either full(most probably) or the WindowsServerBackup folder inside the backuptarget has not access to the user you are trying backup with.

     

    If the target has very less space left, you can free up space by deleting some of the data from the target Or by deleting old backups.

     

    Deleting old backups:

    If you want to delete the system state backup, you may use "wbadmin delete systemstatebackup" in command line.

     

    Windows Server 2008 R2 does not support to restrict the number of versions on a backup target. We are considering this for the next release.

     

    Windows Server Backup does not support backup deletion of other kinds. However, there is a work around if you really need to delete backups on a target. You can delete the shadow copies where the backup exists. You can get the shadow copy Id for a backup using the command "wbadmin get versions -backuptarget:<TargetDrive>". This command will list all the backups on the given target with their shadow copy IDs.  If you delete all consecutive shadow copies starting from the oldest shadow copy, you can get some space.

    I would suggest you to go through this link to make your decision.

    http://blogs.technet.com/b/filecab/archive/2009/06/22/backup-version-and-space-management-in-windows-server-backup.aspx

     

    If the User does not have access to the WindowsServerBackup server folder, give him access and then try backup.

     

    Additionally, as R.Alikhani mentioned, it may be caused by the reason in the following thread.

    http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/889b01be-d333-4fc7-b005-e12b7b236ad7

    Jeff Ren TechNet Community Support beneficial to other community members reading the thread.

     
  • Monday, May 07, 2012 8:19 PM
     
     Answered
    Sign In to Vote
    0

    I had a similar issue that happened to me. It backed up fine a couple of times then failed.

    I decided to delete the directory with the VHD file in it and re-run the backup. It worked fine after that.

    Sometimes this is related to drive space but not in your case.

    Try recreating your backup as well.