![Foto](http://delphiaccess.com/foros/uploads/profile/photo-thumb-12359.jpg?_r=1534943372)
Respaldos
#1
Escrito 17 abril 2009 - 08:34
ayer tuve un problema con una de las bases de datos de produccion aqui en la empresa.
resulta que los respaldos generalmente lo hacia con navicat
un sql dump
de repente hacia uno cada mes con Gui tools de mysql
pero ayer que tuve el problema descubri que el respaldo
solamente era parcial
ninguno de los respaldos estava completo
asi que les pido me iluminen de como es que hacen ustedes sus respaldos de Mysql
#2
Escrito 17 abril 2009 - 08:42
Saludos.
#3
Escrito 17 abril 2009 - 08:53
#4
Escrito 27 abril 2009 - 08:31
para poder programarlos y que se realicen por la noche
por que lo que note es que por ejemplo
si hago el dump como la base de datos se queda abierta pueden seguir trabajando en el archivo y la literatura dice que podria llegar a generar errores
ademas que para programarlos seria una rutina algo mas compleja y tendria que ser local, a menos que se incluya en la rutina el procedimiento para montar y desmontar una unidad de red, etc etc etc .
GRACIAS A TODOS
#5
Escrito 27 abril 2009 - 08:54
de hecho ya estuve viendo opciones y lo que estoy haciendo es los respaldos en Mysql gui
para poder programarlos y que se realicen por la noche
por que lo que note es que por ejemplo
si hago el dump como la base de datos se queda abierta pueden seguir trabajando en el archivo y la literatura dice que podria llegar a generar errores
ademas que para programarlos seria una rutina algo mas compleja y tendria que ser local, a menos que se incluya en la rutina el procedimiento para montar y desmontar una unidad de red, etc etc etc .
GRACIAS A TODOS
Hola
Aprovecho para publicar esto que me llegó por correo de IBExpert.
Database recovery for Interbase and Firebird
Backing up your Interbase or Firebird Server is standard practice, but without a proven recovery process, the backup might be useless.
Use this checklist to get started:
* Never copy a database file on file system level if the server has write access to the database file. This might result in physical database file errors in the copied file and also in the original database file
* Always use gbak to create a serverbased backup file of your database. The result file can be copied wherever you need it
* Firebird allows to use nbackup to improve the speed for large databases, but since it sometimes needs more space than required, it should only be used with large database files with few changes, for example larger than 50GB
* Depending on the speed of the server and the used IB/FB version, the backup process takes only a few minutes per gigabyte, so in most cases a full backup using gbak is recommended
* A backup file should always be tested in the restore process, since there are different possible database errors, that are not shown while the backup process is running, but it prevents a successful restore
* To minimize lost data in case of a failure, a database backup can also be made several times per day. The multigenerational architecture of IB/FB allows to run a backup while all users are connected
* If the backup takes for example just 5 minutes, you can schedule an hourly backup to be sure that only data might be lost within the last hour before the crash
* We recommend to restore your database right after the backup on a seperate server, which can be used from all clients in case of a failure of the main server immediatly
* Be prepared for the case that your server has an unrecoverable error and no experienced admin is available to restore the environment on a replacement server. You can set up a backup database server with two network interface cards, where the second disconnected interface card uses the same IP as you regular server. When the main server operates without problems, it is not connected to the network, so there is no conflict and the backup/restore process uses the first network interface card. When the main server crashes, you just have to switch the network cable from the main server to the backup server and all clients can use the backupserver using the same IP based connection string
* Do not rely only on the RAID technology, we have received several databases from customers, that were the result of a RAID system failure, for example two disks crashed at the same time. Sometimes a simple harddisk is more reliable
* Always check if the backup was done successfully, for example by sending the log file per e-mail in case of an error
* The use of a database shadow on an external usb drive is another way to improve the recovery time
Salud OS
#6
Escrito 21 mayo 2009 - 02:15
#7
Escrito 05 junio 2017 - 07:55
Prueba con esto ...
var DirCompleto : string; const MysqlExe = 'C:\Program Files\MariaDB 10.0\bin\mysqldump.exe'; DirCompleto:='C:\respaldo.sql'; BDORG:='mybd'; ShellExecute(self.Handle, PCHAR('open'),PCHAR(MysqlExe), PCHAR('-u'+USUARIO+' -p'+CLAVE+' -h'+SRV+' -R -r "'+DirCompleto+'" '+BDORG), PCHAR('C:\Program Files\MariaDB 10.0\bin'), SW_SHOW);
Saludos !!