database-backups

First, I would like to mention that I have done some research and found the following questions about the same error: MySQL error 2006: mysql server has gone away (2006) MySQL server has gone away 2006: MySQL server has gone away MAMP - #2006 - MySQL server has gone away None of these questions — and the corresponding answers — actually fit my situation. I am trying to move my WordPress site, currently hosted at OVH, from a VPS to a shared hosting solution, still with OVH. Unfortunately, I cannot simply change my hosting plan, but need to backup my files through FTP (done) and export my

I found a PHP function to dump a mySQL database that someone else had written, and then cleaned it up and formatted it a bit. I wanted to know if I could get a critique of it. I have ran it, tested it on a Wordpress blog and the DB completely restores, but wanted to get some other eyes on the code. Specifically I am looking for feedback on: Anything that could corrupt the data - not properly escaping etc Violating any best practice / principles Security issues Anything else you may see as an issue NOTE: I am NOT looking to use mysqldump, I want to completely generate this sql backup from code.

I'm implementing a backup/restore system in my android app. An automatic backup occures every couple of minutes. I'm trying to restore my db backup file from my sd card, after my app was uninstalled and then installed again. Backup works, but here's the problem: Whenever the user installs my app again, there's a file not found exception, but, if the user closes the app, and then opens it again, the restore is just fine. Somehow, the restoring faces problem when the app is first launched. The restore must happen on first time launch. Note: the backupExists function returns true. @Override

I created a new user on the server that will access certain databases. But when I go to backup or restore the database I get the error: C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Backup Cannot access the specified path or file on the server. Verify that you have the necessary security privileges and that the path or file exists..................... The error shows for any other path in my system. Even those where the user and the Service Account has full control permissions. BUT, if I type the full path and click ok, it complains that it can't show, BUT it does backup or

I need to create a backup of my application which would include creating a backup of 2 databases and also the shared preferences using Google drive API. I was able to get the authentication done for the app and also create a new folder in Drive using the following code: public class MainActivity2 extends BaseDemoActivity { DriveId folderId; @Override public void onConnected(Bundle connectionHint) { super.onConnected(connectionHint); MetadataChangeSet changeSet = new MetadataChangeSet.Builder().setTitle("New folder").build(); Drive.DriveApi.getRootFolder(getGoogleApiClient()) .createFolder

I have dumped a clean, no owner backup for Postgres Database with the command pg_dump sample_database -O -c -U Later, when I restore the database with psql -d sample_database -U app_name However, I encountered several errors which prevents me from restoring the data: ERROR: must be owner of extension plpgsql ERROR: must be owner of schema public ERROR: schema "public" already exists ERROR: must be owner of schema public CREATE EXTENSION ERROR: must be owner of extension plpgsql I digged into the plain-text SQL pg_dump generates and I found it contains SQL CREATE SCHEMA public; COMMENT ON

How to export a Postgresql db into SQL that can be executed into other pgAdmin ? Exporting as backup file, doesn't work when there's a difference in version Exporting as SQL file, does not execute when tried to run on a different pgAdmin I tried exporting a DB with pgAdmin III but when I tried to execute the SQL in other pgAdmin it throws error in the SQL, when I tried to "restore" a Backup file, it says there's a difference in version that it can't do the import/restore. So is there a "safe" way to export a DB into standard SQL that can be executed plainly in pgAdmin SQL editor, regardless of