On a specific environment, a backup is performed using SQL Server regular commands. So, this is from the built in functionality as it is not using an external tool such as Red Gate or Barracuda.

As opposed to before, when that procedure was executed on a previous environment, in the new environment, on pretty much every time it is running, in the first few minutes, it seems that it takes all CPU and/or memory resources and pretty much nothing can be done against the SQL Server during that time, nor the server as it is so tied down that RDP is completely cut off. Before, when doing such, I recall we were allowed to continue regular functionalities, at about 80% of capacity I would say. But, now, we are talking about a total lock for a random amount of time ranging from 30 to 120 seconds. There is much more memory than before, more CPU, and everything up to date. I never had to restrict resources down to a certain percentage, if that would be possible, up until now. Could this be something required on Windows Server 2012 with SQL Server 2014?

Otherwise, if this is known to cause problems or not performing as pretty much transparent as other tools, would it be recommended to use specialized tools for doing such procedure?