Problems after migration.

[AlicanAskin]

Hi,

I did a migration from Plesk 9.5.4 to Plesk 11.5.30 and i have some problems:

There were 450 domains to migrate and 200+ domains are in "Domains", but the other 200+ domains are in "Subscriptions"(what is the difference between "Domains" and "Subscriptions"
Why aren't all the domains imported in "Domains" but also in "Subscriptions" ?? Can i leave it like this or would this give me problems? Can i move the domains from subscriptions to domains??



And i also had alot of these warnings after the migration in the log:

Warning:
Failed deployment of domain enquetesysteem.dvcicta.nl
Warning:
Execution of /opt/psa/admin/plib/api-cli/domain.php --create enquetesysteem.dvcicta.nl -owner admin -do-not-apply-skeleton -notify false -guid 43fcd351-fb4d-49f8-b889-bb10dc6245fe -vendor admin -creation-date 2012-06-11 -ip 10.113.10.6 -ignore-nonexistent-options failed with return code 1.
Stderr is
An error occurred during domain creation: unable to set domain name: Unable to create the domain enquetesysteem.dvcicta.nl because a DNS record pointing to the host enquetesysteem.dvcicta.nl already exists.

What must i do to solve this problem?

I started a migration before but i had to do another one so i deleted all the domains from the first migration, could that be the problem??



Can someone please help me with these problems?

Thanks!

 

[Faris Raouf]

It is very important that you understand the difference between a Domain and a Subscription in order to get to grips with Plesk 11.x (and 10.x).
It can be difficult to grasp at first, but it really is very easy indeed once you "get it"

It boils down to this:
In earlier versions of Plesk, you had Clients, who had one or more Domains in their account.
Domains could have certain limits set -- disk space, transfer limits, number of mailboxes, size of mailboxes.
Although it was not often used, Clients could also have limits set -- number of domains, amount of disk space in total and suchlike.

In 10.x and later, you have Customers, Subscriptions, Domains (and Service plans).

Customers can't have any limits set on them. They are simply customer records with contact details.
Each Customer can have one or more Subscription.
Subscriptions can have all sorts of limits set on them -- disk space, mailboxes, php settings, transfer limits
AND Subscriptions can also have one really important other limit: number of domains.
This is because an individual Subscription can have more than one Domain associated with it.
A Subscription with a limit of one domain and having only one domain in it is exactly the same as a Domain was in older plesk versions.
But having the flexibility of allowing more than one domain per Subscription means that you can sell a customer an account with "unlimited domains" but limit it to, say 1Gb of disk space and 20 mailboxes. These resources are shared between all the domains the customer may add to the Subscription. This may sound like a crazy thing to do, but 1and1, for example, sell a lot of accounts on this sort of basis.

Now...in the Plesk GUI: under Domains, you should see ALL your domains. Every single one. It is basically a list of every individual domain.

in the Subscriptions list, if every subscription only had one domain in it then you'd see exactly the same list as you would see if you clicked on Domains.
But if you had more than one domain in a Subscription then you'd see fewer Subscriptions.

KEY POINT: Subscriptions are shown sorted by their "primary" domain. Essentially this is the first or if you like the "main" domain in the Subscription.

When you migrated from 9.x to 11.5, I *think* you would normally have been given an option as to what to do with Clients who had more than one domain - put them all in one Subscription, put each in a Separate Subscription, or do something else again. If you said put them all in one Subscription, then you'll see multiple domains per Subscription.

Check carefully in the Domains list: What's actually missing? Is it possible that you did not select all domains to be migrated? Can you identify a domain that has not been migrated? Or have they all been migrated and you aren't quite seeing that this has happened due to the Subscription/Domain confusion?

Now, as to that error you are getting, it is quite simple and easy to deal with.

In Plesk 10.x and 11.x, when you create a subdomain (like the one giving the error), a complete set of DNS records are produced for the subdomain, just like they would for an ordinary domain.

If you already have an A record in domain.com for subdomain.domain.com, when subdomain.domain.com is migrated, Plesk will notice that it already has an A record and will generate an error because you cannot have duplicate DNS records. If Plesk didn't complain, you'd end up with an A record in domain.com's DNS and another on in subdomain.domain.com, both identical (e.g. subdomain.domain.com > A > [some ip address] ).

The solution is simply to delete the A record for subdomain.domain.com from domain.com's DNS records and try the migration of subdomain.domain.com again.

Whew! Long post. Sorry. I hope it makes some sense at least!

 

[AlicanAskin]

It is very important that you understand the difference between a Domain and a Subscription in order to get to grips with Plesk 11.x (and 10.x).
It can be difficult to grasp at first, but it really is very easy indeed once you "get it"

It boils down to this:
In earlier versions of Plesk, you had Clients, who had one or more Domains in their account.
Domains could have certain limits set -- disk space, transfer limits, number of mailboxes, size of mailboxes.
Although it was not often used, Clients could also have limits set -- number of domains, amount of disk space in total and suchlike.

In 10.x and later, you have Customers, Subscriptions, Domains (and Service plans).

Customers can't have any limits set on them. They are simply customer records with contact details.
Each Customer can have one or more Subscription.
Subscriptions can have all sorts of limits set on them -- disk space, mailboxes, php settings, transfer limits
AND Subscriptions can also have one really important other limit: number of domains.
This is because an individual Subscription can have more than one Domain associated with it.
A Subscription with a limit of one domain and having only one domain in it is exactly the same as a Domain was in older plesk versions.
But having the flexibility of allowing more than one domain per Subscription means that you can sell a customer an account with "unlimited domains" but limit it to, say 1Gb of disk space and 20 mailboxes. These resources are shared between all the domains the customer may add to the Subscription. This may sound like a crazy thing to do, but 1and1, for example, sell a lot of accounts on this sort of basis.

Now...in the Plesk GUI: under Domains, you should see ALL your domains. Every single one. It is basically a list of every individual domain.

in the Subscriptions list, if every subscription only had one domain in it then you'd see exactly the same list as you would see if you clicked on Domains.
But if you had more than one domain in a Subscription then you'd see fewer Subscriptions.

KEY POINT: Subscriptions are shown sorted by their "primary" domain. Essentially this is the first or if you like the "main" domain in the Subscription.

When you migrated from 9.x to 11.5, I *think* you would normally have been given an option as to what to do with Clients who had more than one domain - put them all in one Subscription, put each in a Separate Subscription, or do something else again. If you said put them all in one Subscription, then you'll see multiple domains per Subscription.

Check carefully in the Domains list: What's actually missing? Is it possible that you did not select all domains to be migrated? Can you identify a domain that has not been migrated? Or have they all been migrated and you aren't quite seeing that this has happened due to the Subscription/Domain confusion?

Now, as to that error you are getting, it is quite simple and easy to deal with.

In Plesk 10.x and 11.x, when you create a subdomain (like the one giving the error), a complete set of DNS records are produced for the subdomain, just like they would for an ordinary domain.

If you already have an A record in domain.com for subdomain.domain.com, when subdomain.domain.com is migrated, Plesk will notice that it already has an A record and will generate an error because you cannot have duplicate DNS records. If Plesk didn't complain, you'd end up with an A record in domain.com's DNS and another on in subdomain.domain.com, both identical (e.g. subdomain.domain.com > A > [some ip address] ).

The solution is simply to delete the A record for subdomain.domain.com from domain.com's DNS records and try the migration of subdomain.domain.com again.

Whew! Long post. Sorry. I hope it makes some sense at least!

So if the domains from the old plesk are migrated to "Subscriptions" there will be no problems with the old domains??


And if i just delete everything on the panel and start the migration again there will be no more problems with the domains?

 

[Faris Raouf]

So if the domains from the old plesk are migrated to "Subscriptions" there will be no problems with the old domains??


And if i just delete everything on the panel and start the migration again there will be no more problems with the domains?

Putting each domain (old plesk) in its own Subscription (new plesk) is certainly how I would do it, yes. So if a Client (now called "Customer") had more than one domain on old plesk, they will now just have more than one Subscription (each Subscription having one domain).

In theory, if you delete all Customers in new Plesk (along with their Subscriptions and the domains they contain), you should end up with no domains, no Subscriptions and no Customers. This will allow you to try the Migration again. I must admit I've had some problems with this in the past, however, with Plesk saying it can't migrate such and such a domain because it already existed even though it had been deleted (but that was with 10.4.4 and a long time ago).

If you remove the A record for subdomain.domain.tld from the DNS records for domain.tld in the old Plesk before migration, you should not get the same error with the subdomain. However, if you do this, subdomain.domain.tld will stop working in old Plesk because there is now no A record for it.

What I suggest is that you migrate domain.tld without the subdomain.domain.tld, remove the A record in new Plesk, then migrate subdomain.domain.tld. I'm not absolutely sure you can do this due to the way old plesk worked though. Hmmm....errr....umm.....maybe some experimentation is in order here?

Important: The magic of Subscriptions is being able to associate a Service Plan to the Subscription. When you change the Service Plan (which defines all the limits), ALL domains associated with that same Service Plan all have their limits changed at the same time. This is really useful. For example you could say you are putting your prices up but all customers with a Gold Service Plan will get 20Mb extra storage in their mailboxes. And you could do this with a few clicks instead of going through each domain one by one.

Any manual adjustments you make to a Subscription's limits will "lock" the Subscription, preventing any such global changes affecting that Subscription.

When you Migrate domains from old to new, all Subscriptions will have "custom" settings (limits) associated with them, which will have limits that are identical to what they had in old Plesk. You can then select one or many or all of your Subscriptions at once and then associate a Service Plan (which you will create and configure as you want it) to them. So if you have Bronze, Silver and Gold hosting accounts, you can create Bronze, Silver and Gold Service Plans, then select all domains that are Bronze hosting accounts and associate them with the Bronze Service Plan. Similarly for Silver and Gold.

It is all good fun. It takes a little while, but once it is done you won't have to worry about it.

 

[AlicanAskin]

I will try to delete everything and retry the migration, i will post when it works!

Btw, plesk indicated this "hard disk quota is not supported due to configuration of server file system" when i wanted to migrate before.
It said that 89 domains will be affected, but will the affected 89 domains get migrated to the new plesk and will the domains work?
Or do i need to solve it before i can use the migration, and how can i do that?

I found this information:https://kb.mediatemple.net/question...etween+domain+disk+space+and+hard+disk+quota?


There it shows how to change a hard disk quota, so maybe i can use that on the affected domains after the migration?


Sorry for this many qeustions and i am very happy that you are helping sir!


Thanks again!

Putting each domain (old plesk) in its own Subscription (new plesk) is certainly how I would do it, yes. So if a Client (now called "Customer") had more than one domain on old plesk, they will now just have more than one Subscription (each Subscription having one domain).

In theory, if you delete all Customers in new Plesk (along with their Subscriptions and the domains they contain), you should end up with no domains, no Subscriptions and no Customers. This will allow you to try the Migration again. I must admit I've had some problems with this in the past, however, with Plesk saying it can't migrate such and such a domain because it already existed even though it had been deleted (but that was with 10.4.4 and a long time ago).

If you remove the A record for subdomain.domain.tld from the DNS records for domain.tld in the old Plesk before migration, you should not get the same error with the subdomain. However, if you do this, subdomain.domain.tld will stop working in old Plesk because there is now no A record for it.

What I suggest is that you migrate domain.tld without the subdomain.domain.tld, remove the A record in new Plesk, then migrate subdomain.domain.tld. I'm not absolutely sure you can do this due to the way old plesk worked though. Hmmm....errr....umm.....maybe some experimentation is in order here?

Important: The magic of Subscriptions is being able to associate a Service Plan to the Subscription. When you change the Service Plan (which defines all the limits), ALL domains associated with that same Service Plan all have their limits changed at the same time. This is really useful. For example you could say you are putting your prices up but all customers with a Gold Service Plan will get 20Mb extra storage in their mailboxes. And you could do this with a few clicks instead of going through each domain one by one.

Any manual adjustments you make to a Subscription's limits will "lock" the Subscription, preventing any such global changes affecting that Subscription.

When you Migrate domains from old to new, all Subscriptions will have "custom" settings (limits) associated with them, which will have limits that are identical to what they had in old Plesk. You can then select one or many or all of your Subscriptions at once and then associate a Service Plan (which you will create and configure as you want it) to them. So if you have Bronze, Silver and Gold hosting accounts, you can create Bronze, Silver and Gold Service Plans, then select all domains that are Bronze hosting accounts and associate them with the Bronze Service Plan. Similarly for Silver and Gold.

It is all good fun. It takes a little while, but once it is done you won't have to worry about it.

 

[Faris Raouf]

The quota thing isn't a show-stopper. It just means Plesk won't be able to limit the total amount of disk space the user can write to. You can safely migrate then worry about enabling quotas in one way or another. I don't know if the quota value will be stored anywhere or whether it will be set to unlimited following the migration though.

Is it a real physical server or a VPS?
If it is a physical server, take a look at http://kb.parallels.com/en/768

If it is a VPS, contact your provider. I've actually had this issue on Virtuozzo VPSes we provide to our customers, and it is easy to resolve. Essentially all that's required is to set quotaugidlimit to a non-zero (but sensibly high) setting.

This explains what the quota is: http://kb.parallels.com/146
I am reasonably certain that you can set a quota within a Service Plan. This means that as long as you assign Service Plans to all your Subscriptions you will be able to set a quota without going through each Subscription individually (once you fix the quota issue).

Personally I'd look into fixing the quota issue before Migrating, however, as it will be one less loose end to worry about.