New answers tagged backup-restoration
Use the "Restore Files and Folders Wizard" as mentioned in the vendor's documentation here. You may also find this document useful; "Restore a full system from an existing client computer backup"
To export: bcp "[MyDatabase].dbo.Customer" out "Customer.bcp" -N -S ServerName -T -E -U"xxxxxx" -P"xxxxxxx" To import: bcp "[MyDatabase].dbo.Customer" in "Customer.bcp" -N -S ServerName -T -E -b 10000 -U"xxxxxx" -P"xxxxxxx"
It cost me much time to find out the answer. If you read the innobackup.backup.log from the donor node and observe the data being created in the adding node, you will get some idea why this happen. I have exactly the same problem. And for my case, comment out the customized innodb_data_home_dir and innodb_log_group_home_dir value will fix the problem. ...
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 ...
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: ...
Top 50 recent answers are included