Welcome to WebmasterWorld Guest from 220.127.116.11
Forum Moderators: phranque
I'm working with a small business in south florida to revamp their website and transfer them to a dedicated server. The owners have a very large and complicated set of databases for customer information and invoices, and we'd like to save time and money by having the migration from their old server to the new one automated by the new host. Unfortunately, their friend who's been administering their site for years will not release the required username and password which would allow the new host to migrate the data for us. His argument is that he currently hosts 12 different websites on that server, so giving us that username and password would compromise those sites' security. But when I tried to check his claim by entering my client's domain into a reverse IP-domain checking tool, my client's site is the only which resolved to that IP.
Is this man a liar, or is there a legitimate reason for him to resolve multiple IPs on the same webserver?
Thanks for your help.
Personally, I wouldnt want to release the admin password either, I would try find another solution to tranfering the data.
There are a number of methods for him to allow you access to your data without giving you the admin password.
He could give you read only FTP access to the data for example.
Also, I checked the site which Seb7 recommended (onsamehost.com). It still shows no additional sites hosted at that IP, but quite a few on nearby IP addresses. I take it from the summary returned that the definition of nearby is that the first two octets match (126.126.#*$!.#*$!) , but not the second two. I'm not sure of the significance.
Note also: reverse lookup results (PTR records) *should* only return one result however many sites are hosted. Convention suggests only ever having one PTR record per address.
It may be *convenient* for your new host to have admin access, but it's almost certainly not necessary (dump files as bill says), and if your new company is telling you porkies like this *and* accusing the old admin of lies and bad faith then I think I'd abort the move to the new hosters ASAP and go elsewhere as they would appear to be incompetent and, at the very least, unbusinesslike and rude (can you say lawsuit?).
If it's MySQL data why not just create a dump file and transfer the data out?
We were worried that he might export the data in a form unacceptable to the new host's installation. Perhaps this is an unfounded worry, but we are not DBAs.
Thanks for your comment.