[SOLVED] Windows Server 2012 R2 (FileSystem Corruption/Backup Issues)

H

hogpenny1

Member
Joined
Dec 19, 2018
Posts
8
Hello,

We have a backup scheduled each day to perform and when it gets executed via the automatic task scheduler it will return an error "More data is available".
The backup is configured with an iSCSI connection via VPN in a Datacenter to connect the server and the backup location.

There are numerous things i have tried in order to fix this and without any result :

1) Checked the server for updates and applied them
2) Checked the space from both shadow copies allocated space, the initial drive and the backup location (there is enough space)
3) Created a new backup machines on the same host, made a new schedule and it failed the same way
4) Have tried to change the user that the task schedule for backup runs from System to Administrator account
5) Modified the time when the backup is made
6) Modified the backed up partitions and removed the drive C: and just left the files from the clients to get backed up..
7) Modified the registry and gave certain zones read/write permission
8) Ran a SFC /scannow and could not repair the file system.


All these 1 month work on this topic leads me to believe there is a problem to the fact that the filesystem is corrupt and once this is fix i believe the backup should be ok.
I attached the cbs.log in a .zip file on this topic and if someone can help me read it and point out what i could try or what the problem is as to why the filesystem fails to repair, i could try and go ahead to approach it differently.

Reinstalling the OS is not an option.

Thanks !
 

Attachments

Hello and welcome!

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.



  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.





SFC Scan



  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

softwaremaniac said:
Hello and welcome!

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.



  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.





SFC Scan



  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
Click to expand...

I have applied what you have instructed me, now it looks like no more errors, attached logs also
 

Attachments

Yes, all clean:

Please open CMD as Admin and enter the following:

Code: 
reg query HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide /v PublisherPolicyChangeTime

Let me know what it says.
 
softwaremaniac said:
Yes, all clean:

Please open CMD as Admin and enter the following:

Code: 
reg query HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide /v PublisherPolicyChangeTime

Let me know what it says.
Click to expand...


reg query HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide /v PublisherPolicyChangeTime


HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\SideBySide
PublisherPolicyChangeTime REG_QWORD 0x1d4986347308efc
 
But when i request to backup via schedule still the same error .. More data is available

I am currently making a full backup on a newly created LUN and i will attempt to format de whole disk of the old backups as a last resort and after will attempt to set the schedule again.. saw it helped a few before, so i guess it's worth a try
 
softwaremaniac said:
Have you tried resizing the shadow storage?
Click to expand...

Hello, yes i have tried to do that also before, furthermore i even created a new disk on which to place the backup on... still it failed, same error "More data is available".
I can see now after the new year passed that the backup started being successful, what i did last time was i change the disk backup and set the backup schedule from folder specific to FULL.

At this time i recreated the backup schedule, set it on the iSCSI target disk, formated and erased all the previous backups, and started it again fresh (task is running, will monitor for 2 days and get back here).
 
but it is still weird that it worked, as this style i have did before also and it failed ... i'm confused myself also
 
Hello,

I am coming in with an update, backup failed again.

1) If i schedule the task to backup certain folders i am interested (folders of user contents) it will fail, this is over iSCSI through VPN to another datacenter.
2) If i schedule the task to backup the whole server it will not fail, this is over iSCSI through VPN to another datacenter.

I have left the whole server to be backed up to the iSCSI target, but i would like to change it to folder specific.

I pulled out a list of files that have a file path longer than 255 and sent it to the client in order to rename them under this limit, i would give it a go with a folder specific backup after they have done so..

Can a folder specific backup fail, but a full backup succeed, and be caused by long file paths ?... i am out of ideas at this point..

Can i make the backup task ignore the file path length ?
 
i confirm it has a problem completing backups when selecting the standlone(4 folders), but it works when doing a full server backup
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top