If you enter the command, perl -V (with a capital “V”), you will see, among many other things, the complete library path search-list that Perl is using.   This is the initial content of @INC.

There are several places where this variable is populated.   The base list is compiled directly into the interpreter when it is built.   The list is ordinarily added-to from the PERL5LIB environment-variable, which could be set in a number of ways ... a globally-available system script, the hidden .bashrc file, or, in Windows, a completely-different strategy which uses the system registry.

The first problem here, given that the system has been “restored,” is to determine whether what you’ve got right now is complete.   Was there, at some time in the past, another copy of this module, which would have superseded the one you’ve found now?   Are you now running the correct version of the Perl interpreter?   And so forth ... what was the “correct” state, before the excrement hit the air-movement device prompting a restore?   When you restored whatever-you-did, how exactly does present-state differ from that?   (Do you, for example, have another server at your disposal, which didn’t take a hit, which could be used for reference?)   Simply “re-installing” will only repair the core installation ... but you also must consider the correct operation of (and, a complete inventory of!) CPAN modules that might have separately been added thereafter.   You’ll need to thoroughly map-out what the correct final-state consists of.