What you describe is essential a geographically distributed RAID and a RAID was never a backup.
Online sync usually means everything you do on the primary storage gets immediately replicated to the backup system, including operations like the deletion of (all) snapshots and/or volumes by an attacker or simply an admin error.
For production use, the best approach is to have a testing environment where you can test any changes before applying them into production. Having this as a VM of course helps with snapshots and rollbacks.
Another approach is the use of modern file systems like ZFS that also allow to do snapshots or even LVM.
Depending on what backup solution you are using the terms are fairly Synonyms
Can also be a full backup with system state.
Incremental or Differential.
Depending on preference and space you can use either.
Incremental backup all changes from last Incremental backup
Differential backup add changes from last Full backup
For a DR situation you ...
I know this is quite an old question, but googling took me there. On ubuntu 14.04 I have a following line in /etc/sources.list.d/mongo.list to have the 3.2 version there:
deb http://repo.mongodb.org/apt/ubuntu trusty/mongodb-org/3.2 multiverse
The source contains few packages. According to the MongoDB Manual it's like this:
mongodb-org - A metapackage ...
The 30-day rollback is a great capability, but what if "critically-important-file-xyz" became corrupt/damaged and this was not detected until 31+ days later? This situation is the difference between back-up and archival schedules, but in your description the latter is not mentioned. Archival systems are usually stored on very low cost tape.
Also no ...
Having geographically separated machines both having the data is good.
What happens when you have multiple failures involving both or all your sites?
A fire at one, theft of the servers at the other?
Or there is a problem with the line between them, then the primary location's server goes out, and the HD controller goes ape and writes junk?
Or some insider ...
You can't export data directly from Glacier to a disk.
S3 Glacier Storage Class
If your data was in S3, moved to the Glacier storage class, you initiate a retrieval request from Glacier to S3. You then use Import/Export or Snowball to export on a drive.
Once it's in S3 you can use any of the S3 tools available to download the files. If you have a 100Mbps ...
This is best done with in a virtual machine such as VMware or VirtualBox, rather than on physical hardware. Take a snapshot of your virtual machine prior to making any changes, then it's a trivial matter of reverting to your snapshot should you need to revert to your previous state.
Unless otherwise specified The tar utility will extract files into the original tree within the current directory so for example in you are in /home/antonio/recovery and you issues the command
tar xvpfz backup.tgz
the files would be recovered into /home/antonio/recovery...
If you use the -C option this tells tar to change directory and to extract the ...
First of all, if you restored a database using a full database backup, but specified a new name for the new database, the drop down menu in the Restore Database dialog in SSMS will show the name from the original backup, not the new name you specified
Another situation when a database is not shown in the drop down menu in the Restore Database dialog is ...
For those installing on Amazon Ubuntu on EC2 using the 10gen yum repository for MongoDB, I had to sudo yum install mongo-10gen.x86_64 to get mongo, mongodump, mongorestore and mongos.
Don't forget you can always sudo yum search mongo...
I just had to handle this.
Finding the backup
In my case, mysql lives in /usr/local/mysql/ (where the last part is actually a symlink to the current installed version of mysql). It actually does correctly back up the files, and the whole structure exists on the backup.
But for some reason, even if you navigate to the correct local path in finder, if you ...
It turns out that the solutions is as simple as specifying a larger timeout. It does matter which timeout though (there are several timeout switches for SqlPackage.exe and it's neither the connection timeout specifiable in a connection string), it's CommandTimeout. The below modified command won't fail even with a bacpac containing a large number of tables (...
The question here seems to be about just how disconnected and geographically distinct a replicated copy of your data needs to be before it's a backup and not high availability/redundancy infrastructure. My gut is that you're close, but still need a backup.
To bring together (cherry-pick) some thoughts in the other answers and comments, you can go really far ...
You test your backups primarily to test your restore procedures so that when you're in crisis situation you'll know exactly what to do and when everybody will be panicking you'll be competent, confident, calm and will know exactly what to do and roughly how long the restore will take etc. etc. because by then restoring backups is a routine event.
The second ...
If you made a snapshot of your instance, you can create new volume from that snapshot, detach the current volume from your instance and attached the one restored from a snapshot.
There are also plenty of backup tools, which could serve the purpose.
It is a good practice to backup your instances, data etc etc, if you haven't done so, you will not be able ...
I believe you're looking for the -b switch of tar:
-b, --blocking-factor BLOCKS
BLOCKS x 512 bytes per record
Now your command will look like this:
tar xfv mybigbigtar.tar --blocking-factor=<whatever you desire>
Chkdsk utility must help in order to restore the NTFS partition -> chkdsk X: (drive letter) /f /r
If the diskpart already identify partition as RAW, you can use EaseUS to restore the partition and the NTFS should be available.
This is one of those "zfs just works" kinds of answers...
The pool metadata is actually stored in the pool, not on the local OS. So, for example, if a system crashes and isn't shut down clean, the metadata within the pool knows that the pool was not "exported" cleanly. If you were to try and import this pool into a new system, you would ...
You have 2 options here:
Leverage the Rackspace Cloud Backup solution
Write a multi part custom backup script (mysqldump to disk, zip up files plus backup files, rsync/ftp/sftp the file to another location).
For the Rackspace Cloud Backup option, I'd suggest checking out the following documentation:
Ignite software will gather all system configuration information, not only the specified files. This information includes LVM configuration, VG's and physical disks, so during recovery, it will try to restore the system configuration as much as it can. If the disks remain in the system, the original VG will be created.
I suppose you know the exact syntax:
For now at least, they are basically equivalent, assuming the mongod is not doing anything else significant. To explain, in versions 2.6 and below, the mongorestore utility effectively contains the mongod binary which allows it to act as a mongod and insert to data files without a mongod running already. The advantage a solo mongorestore usually has is ...
The ReadyNAS uses a debian based Linux OS if I recall correctly. It also has a built-in A/V scanner for write operations to CIFS shares:
That said, anything is possible. I was about to expound on the unlikeliness of this happening, but I've learned that new threats come along all the time, ...
As pointed by this great community:
/dev /proc /sys /tmp /run /media /lost+found /boot ( /boot is optional see other comments)
For reference my final rsync command (under Arch with external media mounted in '/run/media/fred/INTENSO/' and backing up to a folder named 'fred') is:
$ sudo rsync -Pazhmxv --exclude /run/media --exclude /dev --exclude /lost+...
A system state backup will back up AD. You can do this for free with the Windows Server Backup software that comes with your server.
The command line for that is:
wbadmin start systemstatebackup -backupTarget:<VolumeName>
The only "gotcha" is that the backup disk has to be something that the install DVD can see while booting, so I use things like ...