I think you should publish this question in the other branch - https://www.sqlservercentral.com/Forums/SQL-Server-2017/SQL-Server-2017-Administration

Is it a tape backup device or something else?

Alternative options you can use are database audit or temporal tables.
https://docs.microsoft.com/en-us/sql/relational-databases/security/auditing/sql-server-audit-database-engine
https://docs.microsoft.com/en-us/sql/relational-databases/tables/temporal-tables

There are nothing against that. But in general I wouldn't recommend such configuration. Why don't you migrate 2014 databases on 2016?

SQL Server 2017 on Linux does not have a listener.

Hi,

There is another option - use AOAG on top of VMWare boxes.

You can use NTILE to split rows between batches, more details here - https://docs.microsoft.com/en-us/sql/t-sql/functions/ntile-transact-sql

Check that this backup file is valid:
RESTORE VERIFYONLY FROM DISK = N'\\1.2.3.4\BackUp\Backup\Test.bak'
If it is not when backup your database in another file or use FORMAT option...

Hi,

That is only option in this case. You can use msforeachdb in order to make it simple. Or you can write your own script.

Unfortunately that is not officially supported by Microsoft - https://technet.microsoft.com/en-us/library/ms187348(v=sql.110).aspx
<update_stats_stream_option>

Have you tried this method? https://blog.sqlauthority.com/2011/01/05/sql-server-copy-statistics-from-one-server-to-another-server/

Check that you can connect from the user/application pc using an odbc connection. If that is possible trace the SQL Server instance and make sure that Access is actually trying...

I think that is easier on the application side. Also you may consider using encryption for sensitive data instead of RLS. https://docs.microsoft.com/en-us/sql/t-sql/functions/decryptbykey-transact-sql