Kat1949 wrote:
my NIS was in my online backup. at least when i did it i told it to back up all files and c drive.
the IS i have now will NOT take my password i used with the other one. i'm thinking i need to gt rid of this one and find my other on (where ever it is) on y puter.
also, can u please tell me what the heck these LOC extensions are?? from what i've read they have something to do with GPS (??)
.
Hello,
If I understand you correctly, you're saying that you had a Norton Identity Safe database stored locally, and had your Norton Online Backup set to recursively backup C:\ (meaning that it would backup the root of the drive as well as any files in any sub-folders).
If that is the case, your ID Safe may not have been backed up since one must specify which file-types should be backed up with NOBU. You would need to export your IDSafe data to a back-up-able file, and make sure that that file's extension was in the list of extensions to back up in NOBU.
Unfortunately I can't say for certain if this is the case or not, since the settings were lost along with everything else in the crash.
If I am correct about the above information, then you can check in your backup set for the specific files which store the encrypted identity safe data. Those files are named IDDStore.dat (and the backup: "IDDStore_bak.dat"). If those files do not exist and you don't recall exporting your IDSafe data or moving it to the cloud, then it is unlikely that your IDSafe data was backed up.
It is an unfortunate and inconvenient situation that you're in, but fortunately we do have a solution to ensure that this does not happen again: IDSafe in the cloud. When you create a new IDSafe profile, you do have the option to set up IDSafe "in the cloud", meaning that it is stored in an encrypted store on our servers rather than on your computer. In this way, not only can you ensure that if your hard drive is lost or damaged you won't lose your logins, but you also get the added bonus of being able to use those same logins from anywhere using only your Norton Account login as the "master key".
To respond to the second part of your question, the LOC extension is used by various programs for different reasons, but Norton uses it in two ways:
1. There is a ".loc" file which is a user interface component (but this is not likely what you're referring to)
2. There is an "arestore.loc" file which must be included along with "arestore.exe" to do a manual restore of a backup set. If arestore.loc is not present, you'll get the error "Unable to load resources" when running the restore operation.
Note: If you were able to run a restore without getting that error, you don't have to worry about the arestore.loc file.
I apologize for the inconvenience of possibly having to re-create your IDSafe profile, but hopefully the solutions provided in this reply will help to make sure that an issue like this cannot occur in the future.
If you have any other questions or concerns, please reply below.
Thanks for your time and for using the Norton Community Forums.
EDIT: Peterweb beat me to this post! His reply is also correct. :-)
