All that LR backs up is the catalogue. It does some optimizations and integrity checks and then creates a straight copy of the catalogue to your backup directory. You are responsible for backing up your images through some other mechanism.
If you were to look in your backup folder (as designated in your backup preferences) you would see that it only backs up the database or catalog (*.lrcat), which simply contains all of the adjustments you have made in Lightroom. It does NOT backup your images! Your other backup routine should be doing that.
Thank you both
Thats cool. A backup of all the picture data (on servers) are taken care of. I have a mechanism that work good and without too much work and hassle.
I'm installing, testing and evaluating LR and haven't got around to the LR back routine before now.
Shifting to LR on this large amount of pictures takes a bunch of tests. Right now I'm replicating a couple of TB's data and is testing the setup. But before letting LR runs its backup routine I would just make sure that LR didn't try to wrestle to picture data on the server.
Once again, thanks for your quick answer.
If a supplementary question is allowed.
Do any of you have some experience to rather big amount of picture data and LR.
As described I have approx 16-17 TB growing each year.
Does this amount of data handled by LR - lead to performance problems, stability problem etc?
I know of one person with over half a million images in a single catalogue, running fine. Backups do start to take a while with that size of catalogue, I hear.
Yes, I can imagine that this takes a while.
My backup takes a while as well.
OK, a third question.
Can you configure where LR put its backup of the database?
Have looked in the catalog config, but nothing much to change here?
Thanks a bunch for your help