What I noticed with R6 is that when creating a replica of a db it automatically with medium encryption.
This can be unchecked by unchecking “Encrypt the replica using” checkbox which is found when creating a new replica of the database dialog box, under replica settings. When doing this all databases that you create new replicas for will automatically have the encryption unchecked.
Now, I have a new HD as the old one crashed, and my backup mail database can’t be accessed. Local access protection is enabled on the database due to the encryption.
This is NOT how it worked for R5, why would such a big impacting change be made for R6 ?
Is there -any- way around this ?
Thanks
Subject: Replica R6 v R5 - aka How to lose databases
Why not replicating again from the server??? databases on the server are not encrypted.
Subject: RE: Replica R6 v R5 - aka How to lose databases
New server install…
Subject: Replica R6 v R5 - aka How to lose databases
Subject: Replica R6 v R5 - aka How to lose databases
Assuming you have a copy of your ID file, then it shouldn’t be an issue at all. And if you don’t have a copy of your ID file, then you’re just asking for trouble…
Stephen Lister
Subject: RE: Replica R6 v R5 - aka How to lose databases
Well no, the only backup i managed to get was the mail database, hence no copy of ID file.
Surely there has to be a way ?
Subject: RE: Replica R6 v R5 - aka How to lose databases
Not as far as I know - the encryption is based on the private key, which is stored in the ID file (somebody please correct me if I’m wrong here…)
I have mutliple backups of all of my critical files, of which my ID is only one, for exactly this reason.
Stephen Lister
Subject: RE: Replica R6 v R5 - aka How to lose databases
Yes, it’s based on the private key.
Hmmm. I sure hope someone knows a way around this. sigh
Subject: Of course there’s no way around.
If there was, encrypting anything would be useless.
Subject: RE: Of course there’s no way around.
So isn’t it dangerous for Lotus to make it a default setting in R6 when it wasn’t in R5 ??
Subject: RE: Of course there’s no way around.
So isn’t it dangerous for Lotus to make it a default setting in R6 when it wasn’t in R5 ??
Not really, given that almost everyone has a backup of their ID file which would make the problem disappear. I have backups of every single ID file I’ve ever had, all stored with the same password (one known only to me and used only for ID backup) so that I can recover any file I might need to - both for myself and my clients. I owe that level of professionalism to them. You can’t blame Lotus for your failure to take proper disaster recovery procedures.
Even if you didn’t do it, your Domino Administrator should have - it’s one of the first, most basic lessons in any form of network administration, not just Domino. Always back up your critical files. In the case of Domino, specifically all your ID files, names.nsf, admin4.nsf and certlog.nsf. (There are others, but those are the absolute minimum.)
The fact that the default has changed the way it has between R5 and ND6 shows that Lotus are serious about the security of their users’ data. If those users aren’t as serious about it then that’s not Lotus’ problem.
It sounds to me like you just plain stuffed up and you’re desperately casting around looking for anyone other than yourself to blame. Sorry if that sounds harsh (it probably is), but that’s the view from here.
Stephen Lister
Subject: RE: Of course there’s no way around.
Yeah i know.
It’s my home system, and i guess i should have been more careful, but i’ve never backed ID files at home and have done copy database to new system often before R6.
Oh well