[Darryl Ramm]

How you do it is one thing.

You also need to think about practice recovering sessions... ideally test on a different computer so that things like content files not included in the session folder are detected.

There are many options, you can drag and drop folders, or write a script that zips them up, adds a date to the zip file name, etc. simple scripts can be great... as long as you test periodically. And what happens when the target drive is full? Or the same name file exists on the drive, or there is some error.. same for commercial backup software... know where the error log is and check it periodically.

And then just backing up to one HDD may not be enough, how many separate HDD copies? where are they kept? How many off-site? What about copies to cloud storage as well.

And that's Pro Tools sessions? What happens when the boot drive fails or is corrupted? How do you recover the boot drive?

Also how do you save finished projects, the exported/bounced files or stems, make sure they are backed up as well.

The right approach is not always to just make new backups over old, you may need to roll back in time, in which case things like zipped folders with a date in the name are handy.