@jpm@aus.social @da_667@infosec.exchange So Bacula - have not tracked it for many years. But there's a company that produces a more enterprisey solution with all the appropriate support. Noting in the thread the reference to port 443 being commonly used - my experience overall is that most enterprise backup solutions tend to use their own custom ports .Where things get messy these days, I'll acknowledge, is control path comms given so much of it is done over REST API these days. But good software will always allow segregation of data traffic, and most for data still communicate over custom ports (or at least well defined, different ports, if they don't allow full port customisation). In terms of whether or not you need network segregation for backup traffic -- often these days that's going to be influenced by two key factors: whether you're using deduplication storage that supports client (agent) deduplication to reduce traffic, and what your restore speed requirements look like. Source-side integration into deduplication will (unless you're protecting large volumes of heavily encrypted & pre-compressed data) will make the network requirements for backup mostly a negligible impact after the first backup is complete. But, it's the restore to make sure you can accomplish.