Unless a sound sample is provided, it's hard to say for sure what you mean by “clicking”. Even a healthy drive can make “click” sounds sometimes.
If the data is important to you, and you have the means, by all means, bring the drive to a data recovery expert in your area (or in the USA, might be easier to find a reputable one with cheaper prices, I don't know, maybe someone here can give you a few specific names).
If the data is definitely not worth to you the typically hefty price of a professional recovery, and/or you simply don't have the money, since the drive seems to be still recognized with its correct size (2TB, right ?), you
may have a shot at imaging it with ddrescue or HDDSuperClone on a Linux live system (others might disagree on this, and they might be right, I'm still far from the “DR pro” level, take what I say with a whole bag of salt).
But it might not work at all if the drive is indeed having a mechanical failure, and you may damage it further with each attempt ; even if it does work there's the risk that it could fail for good (or “for bad” rather) in the process, and the total recovery ratio may end up far worse than what a professional could have obtained (even if you do bring the drive to a data recovery laboratory at that point, because more damage has been done).
But if you're very lucky you may get a high percentage of your files for free.
But if you've never done anything like this before and never even heard of anything I just wrote, it's going to be very tricky anyway, and it's easy to screw it up beyond repair if you type the wrong command (typically if you reverse the input and output drive names).
If you're aware of the risks, and are still willing to try something by yourself, the first thing to do would be to setup a system with a live Linux USB drive or memory card (
the one designed by the author of HDDSuperClone is ideal for that purpose, as it's lightweight, based on Lubuntu, can run on an older machine, you only need a 1GB device to store it, and it includes both ddrescue and HDDSuperClone), then install GSmartControl, then plug an empty drive with at least the same size as the faulty one (if it does work you want to be ready to “make it talk” as those may be its last words ever), but do
not plug your faulty drive yet ; ideally, you should plug
another known working drive to run tests (if it does work you want to know what you're doing in order to do it right and right away), a smaller one preferably. List the drives (“lsblk” command in the terminal), note which is which, make a wish to the witch, try to image the test drive with ddrescue, with HDDSuperClone, see which one feels the most comfortable (HDDSuperClone is supposedly better optimized for some particular kinds of failures but I find the GUI interface a bit confusing, haven't tested it in CLI mode), play with the commands, read a bunch of guides about those tools, go back to testing...
Once you feel approximately confident, after about three sleepless nights and a couple tubes of paracetamol, take a nap, then a deep breath, make a prayer (it doesn't serve any actual purpose but it calms you down !
), then, and only then, plug the damn faulty drive... List the drives again : if the faulty drive appears in the list, you can proceed ; if not, unplug it right away, nothing more you can do, you're only going to damage it if you insist and not recover one bit.
Now check what GSmartControl has to say about it... if you're lucky, the drive is recognized with its correct name and size, but has bad blocks, maybe a few hundreds, that would be enough to make it misbehave quite badly (check the “reallocated sector count” and “pending sector count” in particular, although other fields might be relevant in assessing the kind of failure) ; if it's more than 1000 you're in for a lotta trouble but it might still be doable... Then note the name of the empty drive, and the name of the faulty drive (which you should have done each time before running a test), double check, triple check, then if it's not done already mount a partition on the empty drive (for example /media/sdb1), and then run the cloning or imaging command. If you're lucky, it will do its trick until the end, although it might be a long process ; but there might be issues along the way, the drive could disconnect itself, in which case you would have to restart it manually, so stay around, better do that on a weekend or vacation...
If you make it that far, the hardest and riskiest part is done – pat yourself on the back with one hand, while slapping your face with the other for not having made a proper backup !
Then scan the clone or image with a good data recovery software, compared to what is described above that part should be easy...
Again, if the data is valuable, and if you have no idea of how to perform each step, better seek the help of someone with the required knowledge and skills and equipment.