April 17, 2015 at 4:48 pm
I am newbie to mysql and want to clarify below on mysql backup and restore
What are the things needed to backup mysql and restore it like database name, username, password etc.
1)I have a database which need to be restored on different server so I used mysql dump command to backup the database by using username root and now during restoration on different server what is the username and password I need to use.
2)If I have created a new empty database on new server so can I restore old database on this new database.
April 18, 2015 at 5:26 pm
In case if your SQL database have been corrupted or you have lost stored SQL objects then you need to use third-party MySQL Restore Toolbox Software. It is effective software developed with latest techniques and strong algorithm with the help of which you can easily repair and restore the corrupt SQL database. The software is capable to repair .MDF files in Microsoft SQL Server 2000, 2005, 2008 and 2008 R2.
July 4, 2015 at 3:50 am
You have many options!!!
If you don't get to connect on database, you will have to restore it.
The basic restore command for restoring a full database from a disk backup image is
db2 RESTORE DATABASE dbname FROM directory TAKEN AT timestamp
To restore from TSM use:
db2 RESTORE DATABASE dbname USE TSM TAKEN AT timestamp
The timestamp represents the time the database
was backed up (it’s the timestamp you see when the backup completes and
it also exists in the recovery history file and for backups to disk you
can see it in the filename or path)
Assuming the backup was done online with log archiving enabled, there is one more thing to do. When you perform an online backup, the restore must apply any transactions that were going on when the backup occurred in order to make sure the database is consistent. So now you must roll forward the database or the tablespaces to a point of consistency. For database level restores, you can roll forward to any point between the end of the backup and the current time (i.e. end of logs).
To check if a backup image is corrupted, you can use the db2ckbkp command
db2ckbkp -h <backup_image>
To check the backups taken on your server you can perform the following command
db2 list history backup all for <dbname>
Output:
Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log Backup ID
-- --- ------------------ ---- --- ------------ ------------ --------------
B D 20080328013138001 N D S0000002.LOG S0000002.LOG
----------------------------------------------------------------------------
Contains 4 tablespace(s):
00001 SYSCATSPACE
00002 USERSPACE1
00003 SYSTOOLSPACE
00004 DMS_TS
----------------------------------------------------------------------------
Comment: DB2 BACKUP SAMPLE ONLINE
Start Time: 20080328013138
End Time: 20080328013213
Status: A
----------------------------------------------------------------------------
EID: 8 Location: c:\SAMPLE.0\DB2\NODE0000\CATN0000\20080328
The Start Time: 20080328013138 is the backup image timestamp.
To roll the database forward to the end of the logs and open the database for access
db2 ROLLFORWARD DATABASE dbname TO END OF LOGS AND STOP
To rollforward to a given point in time you can say
db2 ROLLFORWARD DATABASE dbname TO isotime USING LOCAL TIME AND STOP
If you able to connect on database, but some tablespaces are offline or are in the not normal state, you need to check and fix the problem.
Soon, a document will be post here with more details step by step to teach what you have to do when a database get crashed
If you want to ask, you can use MySQL Restore Toolbox to read articles:
July 4, 2015 at 8:09 am
You have better luck getting answers if you post your question on a mySQL forum.
This forum, is not about mySQL.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
July 7, 2015 at 11:18 pm
This was removed by the editor as SPAM
July 8, 2015 at 2:45 am
July 11, 2015 at 4:27 am
You have many options!!!
If you don't get to connect on database, you will have to restore it.
The basic restore command for restoring a full database from a disk backup image is
db2 RESTORE DATABASE dbname FROM directory TAKEN AT timestamp
To restore from TSM use:
db2 RESTORE DATABASE dbname USE TSM TAKEN AT timestamp
The timestamp represents the time the database
was backed up (it's the timestamp you see when the backup completes and
it also exists in the recovery history file and for backups to disk you
can see it in the filename or path)
Assuming the backup was done online with log archiving enabled, there is one more thing to do. When you perform an online backup, the restore must apply any transactions that were going on when the backup occurred in order to make sure the database is consistent. So now you must roll forward the database or the tablespaces to a point of consistency. For database level restores, you can roll forward to any point between the end of the backup and the current time (i.e. end of logs).
To check if a backup image is corrupted, you can use the db2ckbkp command
db2ckbkp -h <backup_image>
To check the backups taken on your server you can perform the following command
db2 list history backup all for <dbname>
Output:
Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log Backup ID
-- --- ------------------ ---- --- ------------ ------------ --------------
B D 20080328013138001 N D S0000002.LOG S0000002.LOG
Contains 4 tablespace(s):
00001 SYSCATSPACE
00002 USERSPACE1
00003 SYSTOOLSPACE
00004 DMS_TS
Comment: DB2 BACKUP SAMPLE ONLINE
Start Time: 20080328013138
End Time: 20080328013213
Status: A
EID: 8 Location: c:\SAMPLE.0\DB2\NODE0000\CATN0000\20080328
The Start Time: 20080328013138 is the backup image timestamp.
To roll the database forward to the end of the logs and open the database for access
db2 ROLLFORWARD DATABASE dbname TO END OF LOGS AND STOP
To rollforward to a given point in time you can say
db2 ROLLFORWARD DATABASE dbname TO isotime USING LOCAL TIME AND STOP
If you able to connect on database, but some tablespaces are offline or are in the not normal state, you need to check and fix the problem.
Soon, a document will be post here with more details step by step to teach what you have to do when a database get crashed
If you want to ask, you can use MySQL Restore Toolbox to read articles:
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply