there is normally absolutely no need for a rescan when restoring a wallet backup.
Really?
Odd. I thought a rescan was often necessary after restoring a backup. I'll have to search through threads and see if I can find evidence of that.
EDIT:
Ok, I suspect that the reason I thought a -rescan might be necessary was because I had previously read some of these posts (and others like them):
- snip -
Place the November 7th backup in place and try the rescan.
just replace the wallet.dat file in the bitcoin folder with the backed up version, then use -rescan
Yes, a rescan has solved the problem.
- snip -
just copy back and spend
might be good idea to start the bitcoin client with the -rescan switch
- snip -
Do a rescan.
Start it from the command line with the -rescan option.
Also, make sure you have your most recent wallet.dat on the data folder.
- snip -
Restoring of a wallet backup is supported since 0.3.20 with -rescan
- snip -
You can simply rename the wallet.dat on your current Bitcoin installation, and temporarily put a copy of this old backup wallet.dat there. When you launch bitcoin with the -rescan option, it will update the wallet to show the correct balance.
- snip -
- snip -
the client can become confused when you start switching keyrings back and forth is not a problem - just run -rescan.
- snip -
Whenever you copied your wallet from backup place, you should start bitcoin-qt with rescan option:
- snip -
- snip -
So assuming that you using the backup of the encrypted wallet and that no errors are occurring you might need to run bitcoin with the -rescan option.
- snip -
So the old backup could still have some or all of the coins yet.
Of course, the encrypted wallet should not be missing anything, so like CIYAM suggested, -rescan
- snip -