You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by kotipalli venkatesh <ve...@gmail.com> on 2017/02/04 05:04:41 UTC
unable to take the Database dump
Hi All,
Cloudstack Version : 4.3.1
XenServer :6.2
ExportDatabase :
[root@cs4 ~]# mysqldump -u root -p --all-databases --master-data >dbdump.sql
Enter password:
-- Warning: Skipping the data of table mysql.event. Specify the --events
option explicitly.
Import Database error:
mysql -u root -p < dbdump.sql
Enter password:
ERROR 1449 (HY000) at line 10533: The user specified as a definer
('cloud'@'localhost')
does not exist
please suggest how to take the dump and import the dump.
Before taking dump we ned to follow any precautions (management or sql )
services are stop ?
Regards,
Venkatesh.k
Re: unable to take the Database dump
Posted by kotipalli venkatesh <ve...@gmail.com>.
Hi Dag,
yes, I understand.Thanks for the confirmation.
Regards,
Venkatesh.k
On Mon, Feb 6, 2017 at 6:18 PM, Dag Sonstebo <Da...@shapeblue.com>
wrote:
> Hi Kotipalli,
>
> You would always point your MySQL slaves to the same master server – you
> don’t want your second slave to receive “second hand news”. Also – if you
> pointed slave 2 to slave 1 and the synchronization to slave 1 died for some
> reason (not uncommon) then you would end up with two slaves out of date.
>
> Hope this makes sense.
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
>
> Dag.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
> On 06/02/2017, 12:44, "kotipalli venkatesh" <ve...@gmail.com>
> wrote:
>
> Hi Sergey,
>
> As suggested, we created a cloud database and then imported the dump
> without any warning/error message.
>
> Thanks for sharing knowledge.
>
>
> Hi All,
>
> I have another doubt, currently environment having HA of Database
> servers
> (Master+Slave) both the servers working fine.
>
> a. we deployed 3rd DB server and point to the 1st DB Master server as a
> slave server is a good method ?
>
> or
>
> b. 3DB server pointed to 2 DB Slave server so in this scenario 2DB
> server
> again master of 3 DB server.
>
> Can anyone please suggest me best method.
>
> Regards,
> Venkatesh.k
>
>
>
> On Sat, Feb 4, 2017 at 12:04 PM, Sergey Levitskiy <
> Sergey.Levitskiy@autodesk.com> wrote:
>
> > You pretty much OK with the mysqldump options you use. ACS doesn't
> use
> > MySQL events or triggers so you should be good with all-databases
> flag.
>
>
>
Re: unable to take the Database dump
Posted by Dag Sonstebo <Da...@shapeblue.com>.
Hi Kotipalli,
You would always point your MySQL slaves to the same master server – you don’t want your second slave to receive “second hand news”. Also – if you pointed slave 2 to slave 1 and the synchronization to slave 1 died for some reason (not uncommon) then you would end up with two slaves out of date.
Hope this makes sense.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
On 06/02/2017, 12:44, "kotipalli venkatesh" <ve...@gmail.com> wrote:
Hi Sergey,
As suggested, we created a cloud database and then imported the dump
without any warning/error message.
Thanks for sharing knowledge.
Hi All,
I have another doubt, currently environment having HA of Database servers
(Master+Slave) both the servers working fine.
a. we deployed 3rd DB server and point to the 1st DB Master server as a
slave server is a good method ?
or
b. 3DB server pointed to 2 DB Slave server so in this scenario 2DB server
again master of 3 DB server.
Can anyone please suggest me best method.
Regards,
Venkatesh.k
On Sat, Feb 4, 2017 at 12:04 PM, Sergey Levitskiy <
Sergey.Levitskiy@autodesk.com> wrote:
> You pretty much OK with the mysqldump options you use. ACS doesn't use
> MySQL events or triggers so you should be good with all-databases flag.
Re: unable to take the Database dump
Posted by kotipalli venkatesh <ve...@gmail.com>.
Hi Sergey,
As suggested, we created a cloud database and then imported the dump
without any warning/error message.
Thanks for sharing knowledge.
Hi All,
I have another doubt, currently environment having HA of Database servers
(Master+Slave) both the servers working fine.
a. we deployed 3rd DB server and point to the 1st DB Master server as a
slave server is a good method ?
or
b. 3DB server pointed to 2 DB Slave server so in this scenario 2DB server
again master of 3 DB server.
Can anyone please suggest me best method.
Regards,
Venkatesh.k
On Sat, Feb 4, 2017 at 12:04 PM, Sergey Levitskiy <
Sergey.Levitskiy@autodesk.com> wrote:
> You pretty much OK with the mysqldump options you use. ACS doesn't use
> MySQL events or triggers so you should be good with all-databases flag.
Re: unable to take the Database dump
Posted by Sergey Levitskiy <Se...@autodesk.com>.
You pretty much OK with the mysqldump options you use. ACS doesn't use MySQL events or triggers so you should be good with all-databases flag.
Re: unable to take the Database dump
Posted by kotipalli venkatesh <ve...@gmail.com>.
Hi Sergey,
Thanks for the quick response.
Destination side clear now.
Coming to Source side what is the command to take the backup of all
database and tables. please paste the command here.
And also before taking dump need to take any precautions.
Regards,
Venkatesh.k
On Sat, Feb 4, 2017 at 10:42 AM, Sergey Levitskiy <
Sergey.Levitskiy@autodesk.com> wrote:
> Easiest way to first create cloud user at the destination server and then
> import the backup
>
> GRANT ALL ON cloud.* to cloud@`localhost` identified by 'complex_password
> ';
> GRANT ALL ON cloud.* to cloud@`%` identified by 'complex_password';
> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
> GRANT ALL ON cloud_usage.* to cloud@`%`;
> GRANT process ON *.* TO cloud@`localhost`;
> GRANT process ON *.* TO cloud@`%`;
> FLUSH PRIVILEGES;
>
>
>
>
>
Re: unable to take the Database dump
Posted by Sergey Levitskiy <Se...@autodesk.com>.
Easiest way to first create cloud user at the destination server and then import the backup
GRANT ALL ON cloud.* to cloud@`localhost` identified by 'complex_password ';
GRANT ALL ON cloud.* to cloud@`%` identified by 'complex_password';
GRANT ALL ON cloud_usage.* to cloud@`localhost`;
GRANT ALL ON cloud_usage.* to cloud@`%`;
GRANT process ON *.* TO cloud@`localhost`;
GRANT process ON *.* TO cloud@`%`;
FLUSH PRIVILEGES;