The easiest way to do this is to use a separate instance of MySQL, in a virtual machine or otherwise. Copy your files to the ‘dev’ host that you will be using. Doing so will create the database. Then you’ll be able to do mysqldump of the database, and restore it to your original DB.
- Tar up the MySQL backup files (optional)
tar -czvf mydatabase /var/lib/mysql/mydatabase
- Copy to the ‘dev’ host via scp, rsync, or whatever tool you’d like to use
rsync mydatabase server2:/var/lib/mysql/mydatabase
- Extract the MySQL backup files (if they are archived)
tar -xzvf mydatabase
- Dump the new database using ‘mysqldump’
mysqldump -u dbuser -p mydatabase > mydatabase.sql
- Copy the dump back to your original host (or wherever you’re restoring to)
rsync mydatabase.sql server1:/root/
- Restore from your .sql dump
mysql -u dbuser -p mydatabase < mydatabase.sql
I ran into a couple snags configuring tape backups using NTBackup on A Windows Server 2003 Standard machine. For starters, I didn’t look at media pools to confirm that I was using the correct removable media. I was using a Sony 8mm AIT, which can be designated as ‘8mm AIT’ or ‘8mm AIT1’ (both of which show up in NTBackup). According to rm.com, “…older media tapes such as the SDX1-35C, SDX2-50C and SDX3-100C will be in the 8mm AIT1 media pool. New media such as the TAIT-140C and TAIT-280C will be in the 8mm AIT media pool.”
To be sure, take a look at your media pools. You can do so by going to
Administrative Tools > Computer Management
and expanding ‘Storage’ and ‘Removable Media’ in the tree at left, as shown below.
As you can see, the media showed up as ‘8mm AIT’ in the Free Media pool.
With the price of hard drives dropping (and the speed and replacement advantages), tape backups are not nearly as common as they used to be. However, there are still plenty of them around. Here are some magnetic tape backup acronyms and meanings.
AIT is 8mm across and uses helical scanning technique and the MIC (Memory In Cassette) technology to provide increased access. It also supports high data transfer rate up to 78 MB/sec and maximum storage capacity of 500GB compressed using ALDC (adaptive lossless data compression) technologies.
DAT is 4mm across and offers over 40GB of storage at a data transfer speed of about 5 Mb per second and is optimized for high volume backups.
DDS is a format that evolved from DAT technology. Tapes conforming to the initial DDS format can be read by either DAT or DDS tape machines. However, most DDS tape drives cannot retrieve the audio stored on a DAT cartridge.
DLT uses a technique to write data onto the tape in 128 or 208 linear tracks. DLT cartridges can contain around 70GB of data with compression. SuperDLT, a new DLT variant supports tape capacity up to 300GB(SDLT 600) and transfer data at speeds up to 36MB/sec.
LTO uses an open-format technology that provides compatibility to various storage media products. It supports a capacity up to 6.4 Terabytes and transfer rate of 540MB/s.
Packet Tape, available from VXA (tape manufacturer), has a capacity of 33GB native and 66GB compressed. It is an 8mm format and one that is commonly used by home-based business owners.
Tape library – a storage device which contains tape drives, slots to hold tape cartridges, a barcode reader to identify tape cartridges and an automated method for physically moving tapes within the device. These devices can store immense amounts of data.
The DAT roadmap
Thanks to adrc.com, supermediastore.com and Wikipedia
Useful in so many ways… Share/sync files between work and home or between friends, backup documents…
- All data is transferred over SSL and encrypted with AES-256 before storage
- Block-level sync makes working with large files easier
- Sync between Linux, Mac, PC
- Changelog for files that shows who edited it when
- View or restore any previous versions of a given file
- Web interface allows you to get to your files from anywhere
- Create shared folder that other users can access
Use this referral link for extra free space!
Its obviously been way to long since I’ve played with MySQL, because i ran into trouble trying to restore a db from a .sql mysqldump I created. Here are all the steps:
Create a .sql file from a MySQL Database in your current directory:
mysqldump dbname > filename.sql
A database must exist for the .sql file to be restored to, if you don’t have one already then:
create database newdbname;
grant all on newdbname.* to dbusername@localhost identified by ‘dbpassword‘;
Restore the .sql to the newdb database:
mysql newdbname < filename.sql