Backups are regularly being deleted on my NAS!

I have never had this happen when backing up to my Synology NAS. It appears that you are using a mapped drive for the backup. Not sure if that is important or not - I do not use a mapped drive. There is a recent post in one of the other forums indicating that in the latest insider build of Windows 10 they have changed the way networking works, which may play a role here.

Please confirm the OS being used and the build, also the Acronis product being used and the build (I am assuming you are using ATI 2019 rather than Backup 12.5).

Ian 

Thanks Ian,

I'm running ATI 2019 build 17750 and Windows 10 1809 build 17763.437.

I suspect it has nothing to do with mapped drives, as it works perfectly OK for weeks doing incremental daily backups.  3 times now over the last 2 or 3 months, all files in my backup folder are deleted on my Synology NAS, and I get the message posted in #1.

My other backups to the NAS - via CCC on MacOS - work without a hitch, and any other operations on the NAS are problem free as well.  Additionally, my daily backup using ATI 2019 to local HDD also works without a problem.

Iain, one factor that can come into play with this type of scenario is if you have had any other backup tasks using the same name "Win10 Scan Backup" perhaps going to a different location than the NAS?  If so, then this can confuse the Acronis Database and give rise to some strange to fathom issues like this!

The recommendation here would be to use the 'Clone settings' option for this task, rename the cloned task to have an unique name that has never been used before, then set it going to start a fresh backup chain.  Once you have started the new task and made a backup, then you can disable any schedule on the old task, keep it if desired or delete it and its associated files, if any.

Thanks Steve, no other task called that, and it's the 'Iain Folders Backup' task that is the issue.  There have been tasks called that, but all going to the same NAS. The original attachment is confusing as it is highlighting the wrong backup. The 'Win 10 Scan backup' always runs ok. It is highlighted as it was trying to run on schedule, but couldn't due to the 'Folders' backup issue.

Why would any of this cause ATI to delete all backups from that location?

Just to show that the backup completed ok yesterday from scratch.

it's the 'Iain Folders Backup' task that is the issue.  There have been tasks called that, but all going to the same NAS.

Iain, sorry but cannot tell you why ATI does this delete of files but have learnt that using unique task names helps me avoid such issues.

The only other suggestion would involve forcing a rebuild of the Acronis Database so that there are no references to any previous backups with the same or any other names.

See KB 60915: Acronis True Image: repairing program settings - for details of the process that would be needed.

Thanks again, Steve.

I've rebuilt the database, and let's see what happens.  However, if this 'deleting all backups thing' happens again, I'm really going to have to contact Acronis as this is a very serious problem!

I really can't see how it can delete 100s of GBs of data from my NAS..

Iain, did you check the backup logs for the tasks that were active around the time that the backups were deleted from your NAS - I would expect there to be messages in the logs for each deleted file?

This is what is has:

18/04/2019 03:00:00: +01:00 8788 I00000000: -----
18/04/2019 03:00:00: +01:00 8788 I00000000: ATI Demon started. Version: 23.5.1.17750.
18/04/2019 03:00:00: +01:00 8788 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
18/04/2019 03:00:00: +01:00 8788 I00640002: Operation Iain Folders Backup started by schedule.
18/04/2019 03:00:02: +01:00 8788 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
18/04/2019 03:00:02: +01:00 8788 I013C0000: Operation: Backup
18/04/2019 03:00:02: +01:00 8788 I0064000B: Priority changed to Low.
18/04/2019 03:00:11: +01:00 8788 I000B03F0: Create Backup Archive From: C:\Users\Iain\
C:\Program Files (x86)\Steam\userdata\
D:\Iain User Folders\Downloads\
D:\Iain User Folders\Music\
D:\Iain User Folders\Pictures\
D:\Iain User Folders\Videos\
To file: Iain Folders Backup_inc_b1_s2_v1.tib Compression: Normal Exclude: System files, Files matching mask Match criterion: hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\Iain\AppData\Local\Temp, C:\Users\OVRLibraryService\AppData\Local\Temp, C:\Users\OVRLibraryService\AppData\Local\Microsoft\Windows\INetCache, C:\Users\Iain\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\Iain\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\Iain\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\Iain\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\Iain\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\OVRLibraryService\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\OVRLibraryService\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\OVRLibraryService\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\OVRLibraryService\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\OVRLibraryService\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\WINDOWS\CSC
18/04/2019 03:00:33: +01:00 8440 I00640000: Writing incremental version to file: Iain Folders Backup_inc_b1_s2_v1.tib
18/04/2019 03:01:34: +01:00 8788 I00640000: The following backups have been successfully created: \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s2_v1.tib
18/04/2019 03:01:37: +01:00 8788 I000B0000: Consolidate Backup Archive Location: \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s2_v1.tib Destination: \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s2_v1_C05D62EF-8D67-4E09-A02B-8D026BA657F5.tib
18/04/2019 03:01:37: +01:00 8788 E000B03E9: Error 0xb03e9: Failed to open data stream. Try to remove the backup from the list, add it again by clicking 'Add existing backup' and recreate the backup settings.
| trace level: error
| line: 0x6d5b4dcc0ba14815
| file: c:\bs_hudson\workspace\790\products\imager\archive\impl\operations\archive_operation_clone.cpp:2583
| function: TrueImage::Archive::CloneArchiveOperationImpl::SwitchToArchive
| line: 0x6d5b4dcc0ba14815, c:\bs_hudson\workspace\790\products\imager\archive\impl\operations\archive_operation_clone.cpp:2583, TrueImage::Archive::CloneArchiveOperationImpl::SwitchToArchive
| $module: ti_demon_vs_17750
|
| error 0x1e50006: The specified file does not exist.
| line: 0x6d5b4dcc0ba1465f
| file: c:\bs_hudson\workspace\790\products\imager\archive\impl\operations\archive_operation_clone.cpp:2145
| function: TrueImage::Archive::CloneArchiveOperationImpl::PrepareReadStream
| line: 0x6d5b4dcc0ba1465f, c:\bs_hudson\workspace\790\products\imager\archive\impl\operations\archive_operation_clone.cpp:2145, TrueImage::Archive::CloneArchiveOperationImpl::PrepareReadStream
| $module: ti_demon_vs_17750
|
| error 0x40011: The specified file does not exist.
| line: 0x132134cb418e750a
| file: c:\bs_hudson\workspace\790\products\imager\archive\impl\archive_data_stream_impl.cpp:1309
| function: TrueImage::Archive::GetArchiveVolumeInformation
| line: 0x132134cb418e750a, c:\bs_hudson\workspace\790\products\imager\archive\impl\archive_data_stream_impl.cpp:1309, TrueImage::Archive::GetArchiveVolumeInformation
| $module: ti_demon_vs_17750
18/04/2019 03:01:37: +01:00 8788 I000B0000: Deleting backup file with path \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s10_v1.tib.
18/04/2019 03:01:37: +01:00 8788 I000B0000: Deleting backup file with path \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s9_v1.tib.
18/04/2019 03:01:37: +01:00 8788 I000B0000: Deleting backup file with path \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s8_v1.tib.
18/04/2019 03:01:37: +01:00 8788 I000B0000: Deleting backup file with path \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s7_v1.tib.
18/04/2019 03:01:37: +01:00 8788 I000B0000: Deleting backup file with path \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s6_v1.tib.
18/04/2019 03:01:37: +01:00 8788 I000B0000: Deleting backup file with path \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s5_v1.tib.
18/04/2019 03:01:37: +01:00 8788 I000B0000: Deleting backup file with path \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s4_v1.tib.
18/04/2019 03:01:37: +01:00 8788 I000B0000: Deleting backup file with path \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s3_v1.tib.
18/04/2019 03:01:37: +01:00 8788 I000B0000: Deleting backup file with path \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s2_v1.tib.
18/04/2019 03:01:37: +01:00 8788 I000B0000: Deleting backup file with path \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_full_b1_s1_v1.tib.
18/04/2019 03:01:37: +01:00 8788 I013C0006: Operation has succeeded.

Start: 18/04/2019 03:00:00
Stop: 18/04/2019 03:01:37
Total Time: 00:01:37

Iain, the first message of interest in the log says:

The following backups have been successfully created: \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s2_v1.tib

After this, we have Consolidation aka Automatic Cleanup being actioned, but now there is an issue because the files being consolidated / cleaned appear to be using the same backup chain as the file just created!

Deleting backup file with path \\DS216j\iain\Acronis Iain Folder PC Backup\Iain Folders Backup_inc_b1_s10_v1.tib.  >> s9, s8, s7, s6, s5, s4, s3, s2 and finally the full_b1_s1 file.

This would suggest that there has been either a restore where information about the earlier chain was lost from the Database, or else the information in the database has been confused by having more than one backup task using the same name.

So, does that mean that clearing the database should resolve this?

I really feel that it should be made clear by the software that backups should not have the same name as a historical one. Easy for it to check, I would that thought. 

I would hope that clearing the database will resolve this particular issue Iain.

If all backup tasks and files are always deleted using the ATI GUI or by automatic cleanup rules or using the new Cleanup versions option with ATI 2019, then this problem should never arise, but this also depends on users maintaining some separation between their backup tasks.

For example: ATI will let users create multiple backup tasks using the same name, and if these are all directed to be stored in the same destination location, rather than each having a different destination, then I would expect issues to arise!!

Thanks Steve, I think what I am saying is that it shouldn’t allow users to use the same backup name if it causes problems. 

Iain, agreed but not sure how much extra coding they would need to police this etc.  You could submit Feedback about this using the tool in the GUI as you feel strongly about it.

Thanks again, Steve. I would have thought that if the software is aware of entries in the database, and that causes issues for it, that it should be fairly straightforward for it to check for the existence of a previous, similarly named backup. 

I’ll submit feedback, as this seems fairly fundamental. 

Steve,

So, today, I have a new issue. See attachment.  ATI is saying it couldn't find the backup file for my other backup, i.e. 'Win 10 Scan backup'. The file is located correctly, and hasn't moved. I pointed ATI to the file via browse and it is backing up OK. This error message also stopped the 'Iain Folders Backup' going ahead as scheduled.

I really don't know what is going on here, but I am concerned about the number of issues I am having with this software. Not just the ones in this thread,  but others over the last year as well.

So, now I have a similar situation with the 'Iain Folder Backup'. See attached which shows the files in File Explorer as well.

I 'browse' to the 'missing' file in ATI, and then get the error shown in 2nd attachment.

However, the file in question loads perfectly OK when I try to recover data from it.

Iain, I would expect some pop-up messages to show after rebuilding the database as doing so has removed references to files that were previously created.  Doing a Validation for the tasks should resolve such issues as should running a new backup.

For the second issue, you seem to be mixing how you are addressing the backup destination on your NAS?

The top snippet shows using \\DS216j\iain\ etc, whereas the lower one is using a mapped drive Z: to get to the same destination.

I also have a Synology DS215j NAS and the one thing I have never done is to map drive letters to my backup folder locations on the NAS, and have never hit this type of problem.

Thanks Steve,

I am only addressing the NAS through the browser once in selecting the destination, it is ATI that seems to reference in 2 different ways. However, I don't think that is the issue, as I have been using that method for years now without this problem.

Since I last posted, the backup in question ran OK, but did a full backup rather than incremental!

I really just don't get what is going on.  Would I be best to completely remove everything to do with ATI and start afresh?  What is the best way of purging ATI and its databases from my computer?

Iain, if your backup has now run successfully, albeit making a new Full backup, then you shouldn't need to do a clean install of ATI at this point.

You have already purged the database and I doubt that there is a real issue with the ATI application, so if you wanted to do anything, then consider creating a whole new backup task in the GUI, ensuring that the new task has a truly unique name, then test that the task runs correctly.

Thanks for your continued patience on this Steve.

I think there is a problem with the ATI app, as the issue (as can be seen in my previous attachments) is not unique to the backup going to the NAS.  The same issues occur with the one going to the local internal HDD (Win 10 Scan Backup).

I would still suggest creating a completely new backup task and testing that before going for a total clean start Iain.

Thanks, Steve.

I've deleted the old 2 backups and started 2 new ones with names not used before, so we'll see what happens.

Steve Smith wrote:

 

For the second issue, you seem to be mixing how you are addressing the backup destination on your NAS?

The top snippet shows using \\DS216j\iain\ etc, whereas the lower one is using a mapped drive Z: to get to the same destination.

I also have a Synology DS215j NAS and the one thing I have never done is to map drive letters to my backup folder locations on the NAS, and have never hit this type of problem.

 

In the case of the supposed deleted backup files in Steve's observation above you clearly have two destination locations for this backup task thus is the root of your problem.  I do not have a Synology NAS but do have a TerraMaster NAS plus a custom built FreeNAS server that I use Primarily as an NAS device.  In the case of the TerraMaster, it can be managed via a WEB browser interface and has a file explorer so it is easy to locate files and file locations.

You definitely have two locations for files as the path is different to each.  My question for you is how did you map the drive letter Z: to the NAS share?  Did you do this using Windows File Explorer or did you create it using the management interface of the NAS device itself?

In File Explorer if you click on Network do you see your Synology device listed and if so does it show as a Computer, Media Device, Infrastructure, or Other device? 

While in Explorer view with Network selected in the address bar type \\DS216j\iain\Acronis Iain Folder PC Backups\ then press Enter.  You might see a progress bar which shows inside the address bar while Explorer attempts to locate your destination.  You might get a credentials pop up in which case enter the username and password for user iain on your NAS.  What is the result?  Do you see your lost backups?

If you change the address that you typed adding the drive letter Z: (\\DS216j\Z:\Acronis Iain Folder PC Backups\ and press Enter do you see the same backup files or only those shown in your screenshot?

Thanks for that.  However, I have to disagree that the ‘2 destinations’ is the issue here.  Additionally, there is no ‘supposed’ about the deleted backups.  As you can see from the log I posted earlier in this thread, ATI is actually deleting all the backups on previous occasions.

I am not defining 2 different locations, it is ATI interpreting it that way.

To select the destination for the backup, I go to ‘This PC\iain(||DS216j)(Z:)\Acronis Iain Folder PC Backup’ within the ATI Destination dialogue box.  It then shows up as ‘Z:\Acronis Iain Folder PC Backup’ on the screen. However, if there is an error or an entry in the log file it shows up differently.

An example from the last backup today is:

To file: Iain User Files_full_b1_s1_v1.tib Compression: Normal Exclude: System files

25/04/2019 18:20:17: +01:00 6760 I00640000: Writing full version to file: Iain User Files_full_b1_s1_v1.tib

25/04/2019 18:57:52: +01:00 2828 I00640000: The following backups have been successfully created: \\DS216j\iain\Acronis Iain Folder PC Backup\Iain User Files_full_b1_s1_v1.tib

25/04/2019 18:57:59: +01:00 2828 I013C0006: Operation has succeeded.

The backups always work perfectly well with this, except for 2 occasions recently when I have had the errors posted above several times.

As I have already said in previous posts here in this thread, it is not restricted to the NAS drive. There have been similar errors on the backup to my local HDD.

In answer to your questions,

1. If I click on Network, the Synology shows under ‘Other’
2. Doing what you suggest does not show the lost backups, because they have been deleted by ATI! (see log in earlier post above)
3. If I change the address adding Z: then I see the same files.  I see the same files no matter how I navigate to the NAS folder.

As I say, I do not believe the issue has anything to do with the ‘2 destinations’ as the backup works 99% of the time correctly.

I have followed Steve’s advice and created new backups with no naming conflict with previous ones, and all have completed successfully so far. However, it’s too early to tell if this has worked, as it usually takes a few days for the issue to appear.

Iain wrote:

To select the destination for the backup, I go to ‘This PC\iain(||DS216j)(Z:)\Acronis Iain Folder PC Backup’ within the ATI Destination dialogue box.  It then shows up as ‘Z:\Acronis Iain Folder PC Backup’ on the screen.

If you are using Browse >> This PC when selecting the destination, then you are picking a mapped drive to your NAS (Z:) - which is not the way I use with my own Synology NAS - see below:

Going back to Iain's posting at 9:21 today, note that the file name ends in v11.tib, not v1.tib. This looks like the old problem we were dealing with last year. I know there was a lot of discussion on it and we never go a good resolution as I recall.

https://forum.acronis.com/forum/acronis-true-image-2018-forum/mysterious-v11tib-file-access-error

I recall I had a suspicion at the time and I want to bring it up now. For some reason, I was experiencing issues more when I had spaces in the file names. It might have been my imagination, but the I see lots of spaces in the files that are problematic here. Just saying...

Steve, my Synology doesn’t show in NAS, just ‘This PC’.

BrunoC, I think your on to something there. Just noticed the extra ‘1’ in the file name myself. 

I am totally convinced for reasons I’ve explained before that it’s nothing to do with the path to the NAS. I think that’s a red herring. 

BrunoC, Iain,

Great catch Bruno, I had missed the v11.tib totally.  I do remember the thread you provided link to.  I still suspect that the error there can be caused by a variety of issues including the path to the file(s) being open when the backup task needs to run. 

So a failed task or an open path are the commons to generating the error, question is, why does it occur?

imacken wrote:

Steve, my Synology doesn’t show in NAS, just ‘This PC’.

Iian, my recollection is that it depends on the protocols that are enabled on the NAS.  If you do not see it under "NAS" try under "Network", if does not appear used the address of the NAS, the default bieng //DISKSTATION/

Ian

IanL-S - yes, that works, but it gives the same path as if I choose from 'This PC', i.e. \\DS216j\iain\Acronis Iain Folder PC Backup\

Guys, I just want to report that both backups worked perfectly - as expected - last night.

From the NAS one:

To file: Iain User Files_inc_b1_s2_v1.tib Compression: Normal Exclude: System files
26/04/2019 03:00:38: +01:00 7732 I00640000: Writing incremental version to file: Iain User Files_inc_b1_s2_v1.tib
26/04/2019 03:01:32: +01:00 8380 I00640000: The following backups have been successfully created: \\DS216j\iain\Acronis Iain Folder PC Backup\Iain User Files_inc_b1_s2_v1.tib
26/04/2019 03:01:35: +01:00 8380 I013C0006: Operation has succeeded.
 

Iain, glad that the new tasks are running fine.

For the Synology NAS to show in ATI under the NAS section, I believe you need to have the Apple Bonjour (network discovery) service active, plus enable the same on the NAS side too.

Thanks Steve, I'm afraid that made no difference to me. Still doesn't show under NAS in ATI.

Your NAS will NOT show up under NAS unless you have SMB 1.0 enabled on your computer unless that NAS is a Windows based machine which most consumer NAS devices are not.  The mainstream consumer NAS devices on the market today use a trimmed down Linux/UNIX OS.  These systems use SAMBA to communicate and function with the SMB Protocol.  SAMBA at present only broadcasts machine presence over a network via NetBIOS Device Discovery.

Win 10 1703 and later have removed SMB 1.0, NetBIOS, WINS, and HomeGroup thus breaking the device discovery of SAMBA broadcasts of machine presence.  The next version release of SAMBA is suppose to include support for WSD device discovery which should return the discovery functionality of SAMBA to the Windows SMB Protocol.

Edit:  In addition the option of SSDP discovery in the Synology WEB Interface allows the device to show up as "Other" network location in Explorer.

Enchantech wrote:

Your NAS will NOT show up under NAS unless you have SMB 1.0 enabled on your computer unless that NAS is a Windows based machine which most consumer NAS devices are not.

Bob, I definitely do not have SMB 1.0 enabled as shown below:

PS E:\powershell> Get-SmbServerConfiguration

AnnounceComment                 :
AnnounceServer                  : False
AsynchronousCredits             : 64
AuditSmb1Access                 : False
AutoDisconnectTimeout           : 15
AutoShareServer                 : True
AutoShareWorkstation            : True
CachedOpenLimit                 : 10
DurableHandleV2TimeoutInSeconds : 180
EnableAuthenticateUserSharing   : False
EnableDownlevelTimewarp         : False
EnableForcedLogoff              : True
EnableLeasing                   : True
EnableMultiChannel              : True
EnableOplocks                   : True
EnableSecuritySignature         : False
EnableSMB1Protocol              : False
EnableSMB2Protocol              : True
EnableStrictNameChecking        : True
EncryptData                     : False
IrpStackSize                    : 15
KeepAliveTime                   : 2
MaxChannelPerSession            : 32
MaxMpxCount                     : 50
MaxSessionPerConnection         : 16384
MaxThreadsPerQueue              : 20
MaxWorkItems                    : 1
NullSessionPipes                :
NullSessionShares               :
OplockBreakWait                 : 35
PendingClientTimeoutInSeconds   : 120
RejectUnencryptedAccess         : True
RequireSecuritySignature        : False
ServerHidden                    : True
Smb2CreditsMax                  : 2048
Smb2CreditsMin                  : 128
SmbServerNameHardeningLevel     : 0
TreatHostAsStableStorage        : False
ValidateAliasNotCircular        : True
ValidateShareScope              : True
ValidateShareScopeNotAliased    : True
ValidateTargetName              : True

And SMB 1.0 is also disabled on my Synology DS215j NAS to force use of SMB 2.0 or higher.

Steve,

Please use Admin PowerShell to detect the state of SMB1 Protocol on your system using this command:

Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

The output will show State Disabled or Enabled.  I would be very surprised if it shows as Disabled.

If you find it enabled you can disable it by running this:

Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

Let me know your results please.

PS E:\powershell> Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

FeatureName      : SMB1Protocol
DisplayName      : SMB 1.0/CIFS File Sharing Support
Description      : Support for the SMB 1.0/CIFS file sharing protocol, and the Computer Browser protocol.
RestartRequired  : Possible
State            : Disabled
CustomProperties :
                   ServerComponent\Description : Support for the SMB 1.0/CIFS file sharing protocol, and the Computer Browser protocol.
                   ServerComponent\DisplayName : SMB 1.0/CIFS File Sharing Support
                   ServerComponent\Id : 487
                   ServerComponent\Type : Feature
                   ServerComponent\UniqueName : FS-SMB1
                   ServerComponent\Deploys\Update\Name : SMB1Protocol

Same result as Steve with me.

Ok, I'm convinced you both have SMB1 disabled.  Do both of you have the same version of firmware on your Synologe devices?

Another possibility is having FTP enabled.  Do either of you have FTP enabled on your Synology?

I have a Synology DS213j. It's configured just as Steve describes, Bonjour is active and SMB 1.0 is disabled.

Under the ATI UI, I am required to type in nas://<NASname> in order to get it to appear in the tree. It will not find it automatically, either under the NAS section or the Network section.

Enchantec, I don't have FTP enabled, and the DSM version is 6.2.1-23824 Update 6.

(BTW, how do I get quoting messages to work here?  I click on the quote symbol, but I can't see how to enter my message outside of the quote.)

Thanks for the information.  To get quotes to work once you click the quote symbol position your cursor over the quoted text.  Look to the bottom right corner and you should see a Return arrow.  Clicking on that should move the cursor outside the quote area and allow you to type.  Sometimes you have to click the Return arrow twice.  :)

Bob, I do have FTP enabled for when testing scenarios involving that protocol.
DISM version is DSM 6.2.1-23824 Update 6 same as Iain.

Iain, probably the easiest way of using quotes is to first add a couple of new lines to your post, then position your cursor on the first of these and click on the quotes icon.  Otherwise, move the mouse over the bottom right of the quote box and you should see an arrow appear that you can click.

Enchantech wrote:

Thanks for the information.  To get quotes to work once you click the quote symbol position your cursor over the quoted text.  Look to the bottom right corner and you should see a Return arrow.  Clicking on that should move the cursor outside the quote area and allow you to type.  Sometimes you have to click the Return arrow twice.  :)

Got it! Thanks 

Steve, Iain,

I believe that FTP being enabled is the difference in how Steve's device shows as an NAS whereas Iain's does not.  FTP being an insecure protocol broadcasts its presence on port 21.  SMB has for some time, since NT 4.0 I believe used port 445 which it does without using a transport layer of TCP.

So in Steve's case having FTP enabled, the Synology NAS will broadcast its presence on the network via port 21 and the Bonjour Service picks that up and displays the device as an NAS.  

Iain, I have given your problem with file deletion some thought and I ask if it is possible that cleanup rules set in the Task Backup scheme are behind these deletions?  The default setting for that is 183 days.  You may have changed that to a lesser time frame and it may be enforcing that rule on you?

Edit:  Steve, I just noticed in your screenshot that you have SMB port 137 enabled.  That setting might be enforcing Samba to use NetBIOS over TCP/IP and would result in your device showing under NAS as well.  It is best if you disable port 137 and opt for using port 445 without the transport layer as NetBIOS introduces a security risk of your network being accessible over TCP/IP from any network connection including the internet.

Just checked the settings on my Synology NAS and I did not have FTP enabled - enabled secure FTP and made no difference; Steve have you "activated" the secured or unsecured FTP or both. Just noticed you have them both active. I am running DSM 6.2.1-23824 on my DS414.

Ian

Enchantech wrote:

Iain, I have given your problem with file deletion some thought and I ask if it is possible that cleanup rules set in the Task Backup scheme are behind these deletions?  The default setting for that is 183 days.  You may have changed that to a lesser time frame and it may be enforcing that rule on you?

No, that's not it.  I use 'Create only incremental versions...' option, and there is no CleanUp rules option. I wasn't even aware that there was a CleanUp rules option in other methods until your mention made me look it up! 

Iain, if you are not using Automatic Cleanup for your backup tasks, then how are you managing the number of backup files being created for when you need to make space for more?

Steve, I wasn't even aware that such an option existed!

I use Incremental backups, which as far as I can see, doesn't offer that option. Please enlighten me as to how I can set this up.

Iain, if you choose the option for 'Incrementals only' after making the first full backup, then automatic cleanup is not an available option, but this, in my opinion, is a higher risk backup scheme as any damage, corruption or loss of any incremental file will break the whole chain at that point.

See the ATI 2019 User Guide section on Custom Schemes which has a good write up on how to use Automatic Cleanup with other backup schemes.

The combination of backup scheme and automatic cleanup rules that I default to using is:

Incremental backup set to create a new full backup after 5-7 incremental backups - this will keep the size of any version chain to just 1 full plus the 5,6 or 7 incremental files depending on the number I choose.  At that point a new full is created for a new version chain.

For automatic cleanup, I normally use 'Store no more than 2 recent version chains' which means I will have 2 such chains to recover from if needed, but it also means that I need to have enough free space to store those 2 chains (2 x Full plus 10-14 Incrementals) along with 1 further Full - this is because ATI does not delete anything until after the next new chain has been started with a successful Full backup file.