Bug in DA

Aspegic

Aspegic

Verified User
Joined
Aug 4, 2005
Messages
282
I think I found a small bug in DA.

To reproduce the problem:

I have 2 DA servers "A" and "B".
"A" has the "multi-server setup" option turned on (A -> B).

If I now restore a userbackup on server "A" which has a username that already exists on "B" then that user is partially restored!
DNS and other stuf is not restored, but the user account itself is created. Also a ticket is created stating that the userfiles were restored correctly.

I believe in this situation it is correct that the restore should fail (because the user already exists on "B"), but the ticket message should state that and the useraccount should not be created.

Not a biggy though, just ran into this one and thought I'd post it here.

(Tested with DA 1.28.1)
 
Last edited:
Hello,

For the first time user creation, form checking is top priority, make sure it's right at the start.
For backup restore, the priority is getting as much of the data we have restored, as we can.

If ever you do a restore onto a server where you might have duplicates mirrored on B.. it's recommend you shut of the "domain check" part of the multi server setup.. so that server B doesn't get in the way with "domain already exists".

An error message wouldn't be a bad idea to explain what's goning on though.

John
 
I solved the problem by turning off multi-server, restoring the user, copying the files I needed from "A" to "B", deleting the user on "A" and turning multi-server back on. I realise now I could have just disabled the 'domain check' option temporarily, like you suggested.

Normally I would have expected a question like "The user already exists, restore may fail, do you want to continue anyway?" or maybe "The user already exists, do you want to restore using a different account name?". But since a restore job is scheduled no questions can be asked and the job must decide for itself what action to take.
I guess a partial restore is ok, as long as the ticket message explains exactly what happened and what got restored and what didn't.



"For the first time user creation, form checking is top priority, make sure it's right at the start."
I don't think I understand that sentence :(
 
Last edited:
For the first time user creation, form checking is top priority, make sure it's right at the start.
Click to expand...
When creating a user through the interface (not with backups, but with "Create User"), DA does all the domain/username checks as it needs to make sure all the provided form data is valid before doing anything at all.

John
 
You must log in or register to reply here.
Back
Top