Salta al contenuto principale

Issue "Non stop backup stopped" appear

Thread needs solution

NSB on just restarted system is worked fine for a while and issue "Non stop backup stopped" appear. Restarting NSB by pressing right mouse button on tray icon is trying to start service, but unsuccessfully....
Reinstalling the system has not solved the problem to.
----------------------------------------------------------------------------------------------------------​----------------​
Info:
Intel Core i7-6700K with 16Gb DDR4 (same issue appear on AMD FX4 3500Ghz and 16Gb DDR3)
Acronis True Image 2017 (same sympthoms on 2015 Acronis true image)
Windows 8.1
Seagate BlackArmor NAS 400 Series (3Tb free space for backups)
Router Asus RT-N66U
----------------------------------------------------------------------------------------------------------​----------------​​

My afcdpsrv.log says when I try to restart NSB by pressing right mouse button on taskbar icon of NSB:

28-12-2016 19:56:34: tid=0x00001104>Cancel restart sequence requested.
28-12-2016 19:56:34: tid=0x00001104>Base archive creation complete
28-12-2016 19:56:34: Session has started.
28-12-2016 19:56:34: Protection paths: D:\ C:\Users\
28-12-2016 19:56:34: Destination paths: \\kwa-nas-acronis-nonstop\Backups\KONSTANTIN-PC\Work NonStop\Time Explorer Storage\75FD8098-B271-4BCF-BE5F-92F3F5F2D848\image.data
28-12-2016 19:56:34: Excludes: *.tib.metadata *.~ %TMP% %TEMP% D:\Time Explorer Storage D:\pagefile.sys D:\hiberfil.sys D:\Recycler D:\System Volume Information C:\Time Explorer Storage C:\pagefile.sys C:\hiberfil.sys C:\Recycler C:\System Volume Information
28-12-2016 19:56:34: tid=0x00001104>Session start count: 26
28-12-2016 19:56:34: tid=0x00001104>Session start on user request is complete
28-12-2016 19:56:35: tid=0x00000F5C>Archive operation created
28-12-2016 19:56:35: [FileTracker] FileTrackerProxy()
28-12-2016 19:56:35: tid=0x00000F5C>
28-12-2016 19:56:35: tid=0x00000F5C>
28-12-2016 19:56:35: tid=0x00000F5C>KCdpDriverSession::MakeStringList(), multistring size 20, paths: *.tib.metadata
*.~

28-12-2016 19:56:35: tid=0x00000F5C>KCdpDriverSession::KCdpDriverSession(), excluded paths: *.tib.metadata
*.~

28-12-2016 19:56:35: [FileTracker] CreateSession: 
28-12-2016 19:56:36: [FileTracker] CreateSession, add included file masks: \??\Volume{67e95920-8962-4953-a789-23bf299df2ef}\Users\
28-12-2016 19:56:36: [FileTracker] CreateSession, create and finalize checkpoint: {6CF7160A-F5EC-4993-84A7-E07DCA0FDE2B}
28-12-2016 19:56:36: tid=0x00000F5C>KCdpDriverSession::KCdpDriverSession() status 0x0, session name {CA07C01A-AAEB-4EE0-A614-7DE36957CB75}, polling timeout 300000 ms
28-12-2016 19:56:36: [FileTracker] CreateCheckpoint, session name: {CA07C01A-AAEB-4EE0-A614-7DE36957CB75}, checkpoint name: {83AC8E8B-6009-4B9B-9F8C-FF55054EE56E}
28-12-2016 19:56:36: tid=0x00000F5C>KCdpDriverSession::Start(), status 0x0, session name {CA07C01A-AAEB-4EE0-A614-7DE36957CB75}
28-12-2016 19:56:36: tid=0x00000F5C>Session Started
28-12-2016 19:56:36: [FileTracker] FileTrackerProxy()
28-12-2016 19:56:36: tid=0x00000F5C>KCdpDriverSession::MakeStringList(), multistring size 3, paths: \

28-12-2016 19:56:36: tid=0x00000F5C>KCdpDriverSession::KCdpDriverSession(), included paths: \??\Volume{939d8ab8-c841-11e6-825b-1c1b0d606865}\*

28-12-2016 19:56:36: tid=0x00000F5C>KCdpDriverSession::MakeStringList(), multistring size 108, paths: \Time Explorer Storage
\pagefile.sys
\hiberfil.sys
\Recycler
\System Volume Information
*.tib.metadata
*.~

28-12-2016 19:56:36: tid=0x00000F5C>KCdpDriverSession::KCdpDriverSession(), excluded paths: \??\Volume{939d8ab8-c841-11e6-825b-1c1b0d606865}\Time Explorer Storage
\??\Volume{939d8ab8-c841-11e6-825b-1c1b0d606865}\pagefile.sys
\??\Volume{939d8ab8-c841-11e6-825b-1c1b0d606865}\hiberfil.sys
\??\Volume{939d8ab8-c841-11e6-825b-1c1b0d606865}\Recycler
\??\Volume{939d8ab8-c841-11e6-825b-1c1b0d606865}\System Volume Information
*.tib.metadata
*.~

28-12-2016 19:56:36: [FileTracker] CreateSession: 
28-12-2016 19:56:37: [FileTracker] CreateSession, add included file masks: \??\Volume{939d8ab8-c841-11e6-825b-1c1b0d606865}\*

28-12-2016 19:56:37: [FileTracker] CreateSession, create and finalize checkpoint: {4C4A10B8-2060-4FDB-826D-90892B601956}
28-12-2016 19:56:37: tid=0x00000F5C>KCdpDriverSession::KCdpDriverSession() status 0x0, session name {78EF00FA-48C9-4693-98BB-2571E3616DBC}, polling timeout 300000 ms
28-12-2016 19:56:37: [FileTracker] CreateCheckpoint, session name: {78EF00FA-48C9-4693-98BB-2571E3616DBC}, checkpoint name: {2CFB54FB-E44F-46E8-B68C-24FC2F6CB475}
28-12-2016 19:56:37: tid=0x00000F5C>KCdpDriverSession::Start(), status 0x0, session name {78EF00FA-48C9-4693-98BB-2571E3616DBC}
28-12-2016 19:56:37: tid=0x00000F5C>Session Started
28-12-2016 19:56:37: tid=0x00000F5C>Driver started
28-12-2016 19:56:37: tid=0x00000F5C>Archive existence checked before consolidation with result: false
28-12-2016 19:56:37: tid=0x00000F5C>Error opening archive stream
28-12-2016 19:56:37:  Code: 0x52 tag: 0xC59423F28FF7EF6A  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x1703EC tag: 0x38A9B4027C0FFC11  message: Read error. KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x40007 tag: 0xF35F747B3B21F90A  message: Error occurred while opening the file. KSTATUS: -2147023766   function: OpenFileW    path: \\?\UNC\kwa-nas-acronis-nonstop\backups\konstantin-pc\work nonstop\time explorer storage\75fd8098-b271-4bcf-be5f-92f3f5f2d848\cdp.data    $module: afcdpsrv_vs_4310   Code: 0xFFF0 tag: 0xBD28FDBD64EDB8F1  message:  KSTATUS: -2147023766   code: 2147943530    $module: afcdpsrv_vs_4310  
28-12-2016 19:56:37: Consolidation has failed.
28-12-2016 19:56:37:  Code: 0x1720001 tag: 0x6F3D13FF1B3C09AC  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x1720001 tag: 0x6F3D13FF1B3C06CF  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x52 tag: 0xC59423F28FF7EC2A  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x52 tag: 0xC59423F28FF7EF6A  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x1703EC tag: 0x38A9B4027C0FFC11  message: Read error. KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x40007 tag: 0xF35F747B3B21F90A  message: Error occurred while opening the file. KSTATUS: -2147023766   function: OpenFileW    path: \\?\UNC\kwa-nas-acronis-nonstop\backups\konstantin-pc\work nonstop\time explorer storage\75fd8098-b271-4bcf-be5f-92f3f5f2d848\cdp.data    $module: afcdpsrv_vs_4310   Code: 0xFFF0 tag: 0xBD28FDBD64EDB8F1  message:  KSTATUS: -2147023766   code: 2147943530    $module: afcdpsrv_vs_4310  
28-12-2016 19:56:37: tid=0x00000F5C>Archive existence checked after consolidation with result: false
28-12-2016 19:56:37: tid=0x00000F5C>globalOperationMutex Unlock()
28-12-2016 19:56:37: tid=0x00000F5C>ERROR: KCdpArchiveCreator::OnRun():
28-12-2016 19:56:37:  Code: 0x1720001 tag: 0x6F3D13FF1B3C05EE  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x1720001 tag: 0x6F3D13FF1B3C09AC  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x1720001 tag: 0x6F3D13FF1B3C06CF  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x52 tag: 0xC59423F28FF7EC2A  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x52 tag: 0xC59423F28FF7EF6A  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x1703EC tag: 0x38A9B4027C0FFC11  message: Read error. KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x40007 tag: 0xF35F747B3B21F90A  message: Error occurred while opening the file. KSTATUS: -2147023766   function: OpenFileW    path: \\?\UNC\kwa-nas-acronis-nonstop\backups\konstantin-pc\work nonstop\time explorer storage\75fd8098-b271-4bcf-be5f-92f3f5f2d848\cdp.data    $module: afcdpsrv_vs_4310   Code: 0xFFF0 tag: 0xBD28FDBD64EDB8F1  message:  KSTATUS: -2147023766   code: 2147943530    $module: afcdpsrv_vs_4310  
28-12-2016 19:56:37:  Code: 0x1720001 tag: 0x6F3D13FF1B3C05EE  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x1720001 tag: 0x6F3D13FF1B3C09AC  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x1720001 tag: 0x6F3D13FF1B3C06CF  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x52 tag: 0xC59423F28FF7EC2A  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x52 tag: 0xC59423F28FF7EF6A  KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x1703EC tag: 0x38A9B4027C0FFC11  message: Read error. KSTATUS: -2147023766   $module: afcdpsrv_vs_4310   Code: 0x40007 tag: 0xF35F747B3B21F90A  message: Error occurred while opening the file. KSTATUS: -2147023766   function: OpenFileW    path: \\?\UNC\kwa-nas-acronis-nonstop\backups\konstantin-pc\work nonstop\time explorer storage\75fd8098-b271-4bcf-be5f-92f3f5f2d848\cdp.data    $module: afcdpsrv_vs_4310   Code: 0xFFF0 tag: 0xBD28FDBD64EDB8F1  message:  KSTATUS: -2147023766   code: 2147943530    $module: afcdpsrv_vs_4310  
28-12-2016 19:56:37: tid=0x00000F5C>Stop minifilter and all worker threads
28-12-2016 19:56:37: tid=0x00000F5C>KCdpDriverSession::Stop(), set shutdown event
28-12-2016 19:56:37: tid=0x00000F5C>Driver session C: stopped with status 0x0
28-12-2016 19:56:37: tid=0x00000F5C>KCdpDriverSession::Stop(), set shutdown event
28-12-2016 19:56:37: tid=0x00000F5C>Driver session D: stopped with status 0x0
28-12-2016 19:56:37: [FileTracker] DeleteSession: {CA07C01A-AAEB-4EE0-A614-7DE36957CB75}
28-12-2016 19:56:37: BufferedStreamImpl: connection lost
28-12-2016 19:56:37: BufferedStreamReadOnlyImpl: connection lost
28-12-2016 19:56:37: tid=0x00000A74>KCdpArchiveImpl: connection lost
28-12-2016 19:56:37: tid=0x00000F5C>KCdpDriverSession::Delete(), status 0x0, session name {CA07C01A-AAEB-4EE0-A614-7DE36957CB75}
28-12-2016 19:56:37: tid=0x00000F5C>KCdpDriverSession::~KCdpDriverSession()
28-12-2016 19:56:37: [FileTracker] ~FileTrackerProxy()
28-12-2016 19:56:37: [FileTracker] DeleteSession: {78EF00FA-48C9-4693-98BB-2571E3616DBC}
28-12-2016 19:56:37: tid=0x00000F5C>KCdpDriverSession::Delete(), status 0x0, session name {78EF00FA-48C9-4693-98BB-2571E3616DBC}
28-12-2016 19:56:37: tid=0x00000F5C>KCdpDriverSession::~KCdpDriverSession()
28-12-2016 19:56:37: [FileTracker] ~FileTrackerProxy()
28-12-2016 19:56:37: tid=0x00000F5C>CdpSession::OnCdpArchiveCreated() with result:
28-12-2016 19:56:37:  Code: 0x1720001 tag: 0x6F3D13FF1B3C05EE   $module: afcdpsrv_vs_4310  
28-12-2016 19:56:37: tid=0x00000F5C>Session fail stop count: 13
28-12-2016 19:56:37: Nonstop backup has been created successfully.
28-12-2016 19:56:41: tid=0x00001D44>ERROR: Demon has exited with code 1
28-12-2016 19:56:41: Initial full backup version has been created successfully.
28-12-2016 19:56:41:  Code: 0x1720001 tag: 0xE3C4D53C6BFE495A  KSTATUS: -536870907   $module: afcdpsrv_vs_4310   winerror: 0xE0000005  winerror: 0xE0000005  KSTATUS: -536870907   code: 3758096389    $module: afcdpsrv_vs_4310  

I hope you can help me

0 Users found this helpful

I am no expert but it looks to me like the non stop backup failed to make connection to the NAS device which I assume is where your non stop backup file is located.  Fix your connection issue should fix the non stop backup problem.

Connection lost only on non-stop backup shedule. Secondary shedule on normal backup is worked fine.

I personally think the NSB backup scheme is too intensive for non-local disks.  Most NAS devices go to sleep or power saving mode.  NSB is designed to run 24\7 and then there's the I/O of constantly being active, plus the network connection as well.  

I'll be blunt, I'm not a fan of NSB.  The idea is great, but I just don't think that Windows is designed for 24/7 scanning and backup.  Plus, NSB's main purpose is to give you constant backups - OK cool.  However, each day, the entire' days worth of backups are consolidated into the last backup of the day, leaving you only one backup for the day again - not really NSB.  This behavior repeats again on a weekly basis after you have 30 days of backups so your daily's become a single backup each week during the weekly consolidation. 

Personally, I can't think of many scenarios where NSB would even be needed.  Turn on Windows System Protection for file changes and run more frequent incrementals - maybe 4 a day if need be or perhaps more.  However, if you are making lots of incrementals, make sure to follow up with a full every now and then so that your incremental chain doesn't get too crazy since incrementals depend on every incremental that came before it... the longer you wait or the more you have between fulls, the more chance of one of them causing you problems that might require you go much farther back to get a working backup (if corruption should occur).

As a recomendation, you might do 1 full system backup with a single full and 3 weekly differentials (1 month) and keep 2 version chains.  Then do a second backup with 1 full and perhaps  8 incrementals that are spread out every 4 hours.  Then keep something like 6 version chains of that data if it isn't large.   It's really up to you to determine how often to backup and storage space and retention will have to be factored in of course, but I think you'll be better of with incremntals since those backups are for that moment in time and not consolidated into a single daily backup that removes all of your previuos NSB backup for the day. 

I would agree with Bobbo here.  You NAS power configuration is what is causing the issue.  If possible to defeat the power saving features you might try that to get around the issue.

Bobbo_3C0X1 wrote:

I personally think the NSB backup scheme is too intensive for non-local disks.  Most NAS devices go to sleep or power saving mode.  NSB is designed to run 24\7 and then there's the I/O of constantly being active, plus the network connection as well.  

I'll be blunt, I'm not a fan of NSB.  The idea is great, but I just don't think that Windows is designed for 24/7 scanning and backup.  Plus, NSB's main purpose is to give you constant backups - OK cool.  However, each day, the entire' days worth of backups are consolidated into the last backup of the day, leaving you only one backup for the day again - not really NSB.  This behavior repeats again on a weekly basis after you have 30 days of backups so your daily's become a single backup each week during the weekly consolidation. 

Personally, I can't think of many scenarios where NSB would even be needed.  Turn on Windows System Protection for file changes and run more frequent incrementals - maybe 4 a day if need be or perhaps more.  However, if you are making lots of incrementals, make sure to follow up with a full every now and then so that your incremental chain doesn't get too crazy since incrementals depend on every incremental that came before it... the longer you wait or the more you have between fulls, the more chance of one of them causing you problems that might require you go much farther back to get a working backup (if corruption should occur).

As a recomendation, you might do 1 full system backup with a single full and 3 weekly differentials (1 month) and keep 2 version chains.  Then do a second backup with 1 full and perhaps  8 incrementals that are spread out every 4 hours.  Then keep something like 6 version chains of that data if it isn't large.   It's really up to you to determine how often to backup and storage space and retention will have to be factored in of course, but I think you'll be better of with incremntals since those backups are for that moment in time and not consolidated into a single daily backup that removes all of your previuos NSB backup for the day. 

I am a programmer with a variety of projects where data is changed very fast and all the day. I really need the NSB mode. It is very convenient for me.

Enchantech wrote:

I would agree with Bobbo here.  You NAS power configuration is what is causing the issue.  If possible to defeat the power saving features you might try that to get around the issue.

 

NAS power is have no issues because normal backup shedule and direct access to the NAS is worked fine at this time.

I suggest that you open a support case with Acronis.  Let them investigate your issue.

Enchantech wrote:

I suggest that you open a support case with Acronis.  Let them investigate your issue.

I did it yesterday. Thanks...