Sql-server – Backups fail to copy over the network

You dont need to have them use COPY_ONLY. Only An intermediate LOG BACKUPS will break the LSN. What you can do is explicitly DENY BACKUP LOG to [user|group] privilege to developers or developer group. Alternatively, just create a ROLE and deny backup log to that role. So all the users in that role will inherit the permissions.

e.g.

USE test_kin
GO
CREATE ROLE [deny_log_backups]
GO
USE [test_kin]
GO
CREATE USER [Kin] FOR LOGIN [Kin]
GO
ALTER USER [Kin] WITH DEFAULT_SCHEMA=[dbo]
GO
use test_kin
GO
DENY BACKUP LOG TO [deny_log_backups]
GO
USE test_kin
GO
EXEC sp_addrolemember N'deny_log_backups', N'kin'
GO

Now test it :

backup database [test_kin]
to disk = 'C:\crap_test\kin_test_full.bak'
with compression, stats =10, init

---- ### success for FULL BACKUP 

backup log [test_kin]
to disk = 'C:\crap_test\kin_test_log.log'

 --- $$$ ERROR MESSAGE 

Msg 262, Level 14, State 1, Line 3
BACKUP LOG permission denied in database 'test_kin'.
Msg 3013, Level 16, State 1, Line 3
BACKUP LOG is terminating abnormally.

In short - yes, there are standard operating procedures for doing all of this with Oracle. You should start by looking into RMAN (Recovery MANager). I have put together a high level overview of RMAN as well as an introduction to Oracle backups for SQL Server DBAs. I suggest watching both of those and then heading over to the Oracle Database Backup and Recovery User's Guide to learn more about the options available to you.

Basically, though - RMAN can perform all of these tasks for you. If you need additional tooling, RMAN + Oracle Enterprise Manager can provide you with automation, cloning, and other reporting capabilities. Oracle Enterprise Manager Database Control (dbcontrol) will also be very helpful, it will give you additional web-based GUI tools.

To get to a point where you can get to restoring from a bare bones Windows server and cold backup file is going to take significant training. You need to work with the business to define effective RPO/RTO plans, budget training for the future, and then do what you can right now to mitigate the risks before you're stuck with an empty server.

Improving the original answer slightly...

1. You should start using Oracle Recovery Manager (RMAN) to back up your databases. Depending on how you configure RMAN, you may be sending this to NFS or to a set of disks on a different SAN. The way you configure this has a lot to do with your RPO/RTO policies. If you need to send this to a cool standby server, you should look into Oracle Data Guard. Depending on the configuration, this may take the place of either log shipping or an AlwaysOn Availability Group.
2. You can clone a database using RMAN, just make sure you have everything in place and you practice it.