backup

When committing a running container with docker commit , is this creating a consistent snapshot of the filesystem? I'm considering this approach for backing up containers. You would just have to docker commit <container> <container>:<date> and push it to a local registry. The backup would be incremental, as the commit would just create a new layer. Also would the big amount of layers hurt io performance of the container drastically? Is there a way to remove intermediate layers at a later point in time? Edit By consistent I mean that every application that is designed to survive a power-loss

I have a huge tree of files and dirs for cache in my document directory. As recommended, I'm going to use NSURLIsExcludedFromBackupKey for preventing iTunes from saving this data with the app. Can I use it once on my root directory URL, as [rootDirectoryURL setResourceValue:[NSNumber numberWithBool:YES] forKey:@"NSURLIsExcludedFromBackupKey" error:&error]; Or will I have to call it for each file? Yup, you can pass it a NSURL of the directory you want excluded. - (BOOL)addSkipBackupAttributeToItemAtURL:(NSURL *)URL { assert([[NSFileManager defaultManager] fileExistsAtPath: [URL path]]); NSError

Possible Duplicate: What is the best way to do Incremental backups in Mysql? Is there a way to do differential incremental backup in MySQL ? I dont know if there is a PHP script or shell script able to do this. I believe each tables states must be saved and their differences must be exported in the backup. Any way to accomplish this? I know there are other types of backup but I like the way smallers backup are generated at time in differential incremental backups. Edit: I forgot to specify that my DB engine is InnoDB Yes, is called incremental backup instead of differential backup (correct me

Is it necessary to do backups of gae's datastore? Does anyone have any experience, suggestions, tricks for doing so? You can now use the managed export and import feature, which can be accessed through gcloud or the Datastore Admin API: Exporting and Importing Entities Scheduling an Export Backups are always necessary to protect against human error. Since App Engine encourages you to build mutiple revisions of your code that run against the same dataset, it's important to be able to go back. A simple dump/restore tool is explained in the Bulkloader documentation . Something else I've done in

I wrote a basic content-management system for my website, including an administration panel. I understand basic file IO as well as copying via PHP, but my attempts at a backup script callable from the script have failed. I tried doing this: //... authentication, other functions for(scandir($homedir) as $buffer){ if(is_dir($buffer)){ //Add $buffer to an array } else{ //Back up the file } } for($founddirectories as $dir){ for(scandir($dir) as $b){ //Backup as above, adding to $founddirectories } } But it did not seem to work. I know that I can do this using FTP, but I want a completely server

Is there a way to back up MySQL database automatically at certain times of the day for designated servers or send an email with an attachment.. Which ever do you think is the best and safest way to achieve this? I would use Windows Task Scehduler/cron (depending on your system) and mysqldump . Scroll down in the link, it includes some insights how to achieve what you want. Tarun Gupta Best way to do this would be mysqldump.exe --user=YourUserName --password=YourPassword --host=localhost --port=3306 --result-file="Path\dump.sql" --databases "DatabaseName1" "Database2" mysqldump.exe --user=root

How to backup a mysql database from a java code such that: It's saving path is dynamically allocated. Spaces in Path do not create problems. Path is generated using the executing jar file. DBname,DBusername or DBpass are dynamically allotted. Creating a specialized folder to save the backup file. Note: The codes given below are one way of solving the problem and probably not the best method. Everything is changeable inside the code. If you do not have mysql in environment variables, add the path before mysqldump and mysql (e.g. For XAMPP, C:\xampp\mysql\bin\mysqldump) (Hope, this will solve