h data recovery master

Server RAID 5 Data recovery caseThis shared case is a RAID disk array in a server, with 12 disks in the disk array, a single-disk capacity 500g,ext3 file system, and a Linux platform for the system platform. Raid in 2nd and 6th, two hard disks reported yellow lights, management personnel after the check on the 6th plate has been forced on-line operation, forced on-line found that most of the directory can n

. (yes, you need to do this and need absolutely moisture proof)4. Place the double-pack hard drive in one of the coldest panes of your refrigerator.5. Freeze the hard drive for more than 12 hours.6. Immediately install the frozen hard drive back to the computer and start retrieving the data.7. At some point, the hard drive is still unreadable. If necessary, freeze it again.8. You may need to repeat multiple times until the hard drive stops working or

ORA-16139: media recovery required error encountered during physical DG Master/Slave database switchover SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY; ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY * ERROR at line 1: ORA-16139: media recovery required Solution: -- If the ORA-16139: media recovery required

First, let's talk about SQL Server recovery master database method, as follows The first step: copy model.mdf, Mastlog.ldf, Model.mdf, Modellog.ldf, msdbdata.mdf, msdblog.ldf files.From X:\Program Files\Microsoft SQL Server\mssql10. Mssqlserver\mssql\binn\templatesTo X:\Program Files\Microsoft SQL Server\mssql10. Mssqlserver\mssql\dataNote: the above "X:\Program Files\Microsoft SQL Server" is the installat

.txt#查找1048964 to determine the position;Operation on Slave:Mysqlbinlog slave-relay-bin.000008 > 0008.txtVim 0008.txt#查找1048964, found 1048964 of the location at the very bottom of the file recordThe two TXT generated above can also be compared to the content, the two 1,048,964 positions near the content is consistent, so determine 1048964 this position is slave before the collapse of the main position of synchronizationContinue from the top action:MysqlSlave stop; #显示OKChange

Tags: PNG image rebuild Instance mssql tar font FFFFFF ShadowSQL SERVERDatabaseMasterDatabase RecoveryFirst, the experimental steps probably1 , first create a database and a table to be used for post-recovery validation. 2 , the Master The database is backed up well in advance. 3 , Simulation Master database Delete, shut down in service SQL Server service can the

Tags: mysql master-slave monitoring fault alarm and recovery#!/bin/sh#check_mysql_slave statusIp=eth1 #网卡名称Mysql_binfile=/usr/local/mysql/bin/mysqlMysql_user=root #MySQL数据库账号mysql_pass=123456 #密码Mysql_sockfile=/tmp/mysql.sockDatetime= ' date + '%y-%m-%d/%h:%m:%s ' #获取当前时间Mysql_slave_logfile=/opt/slave.log #日志文件路径 must be created in advance.slave_ip= ' ifconfig $ip |grep "inet addr" | awk-f[: ""]+ ' {print $

A recent project requires a high-availability master-slave synchronization of mysql + keepalived, which is of course easy to configure. However, it is easy to think about how to restore data as quickly as possible after the master database is suspended and taken over from the slave database, and let the master database

HP Server is one of the most popular low-end servers. Some server failures, such as the server hard disk is not the line, the server does not go to the system can not boot and so on is also a common server failure, and for these different failures occur data loss problem, HP Server can be data recovery? If so, what's the way?The reasons for the failure of HP serv

the partition. The disk character disappears. partition table destruction. u disk can't open. The disk character double click prompts to format. The partition error says that the root directory is corrupted and unreadable. Ghost System. A key ghost into 4 partitions. The memory card of the cell phone is restored. The Recycle Bin was emptied after the anti-virus software scan. Disk self-test and missing files. The root directory is empty but the disk space is still occupied and so on.

Backup: mongodump has the best speed and compression ratio, with 28% MB of data per second and a compression ratio of up to. Restore: mongoimport is faster, but it does not guarantee complete data import to m. Backup: mongodump has the best speed and compression ratio, with 28% MB of data per second and a compression ratio of up to. Restore: mongoimport is faster

Master and slave failed to first view from the database show slave status\gRemember Bin-log Pos and Binlog files (typically select the last point of the nearest POS to recover) or view MySQL's error diary at a point in time,Convert Mysql-binlog to TXT to see every operation of the databaseMysqlbinlog/Path/mysql-bin.000xxx >txt1.txtUseChange master to master_host= ' xxxx ', master_user= 'Mysync' , master_pas

MySQL master-Slave synchronization common exception and recovery method 1. General exception only need to skip one step to recover >slave stop; >set GLOBAL sql_slave_skip_counter = 1; >slave start; 2. The last Bin-log log of the main library is restored when the power failure causes the master/slave to be unable to synchronize On the main library server, Mysqlb

. Recovery is easier. Backup policy: Considerations 1. Select the backup mode and the method based on the needs of our production environment; 2. It is reasonable to select the minimum access time for backup; 3. recovery costs: Recovery duration; 4. Backup Cost: Considering the lock time, backup duration, and backup load; Backup object: What do we need to back up

Official API: http://www.mongodb.org/pages/viewpage.action? PageId = 6750283 Master-slave synchronization: 1. Create a database directory Mkdir/Mongodb/masterdbMkdir/Mongodb/Slavedb_1Mkdir/Mongodb/Slavedb2.2. Start the Master/Slave servers respectively.Start the master server to listen to port 10000./Bin/mongod-Dbpath/Mongodb/masterdb/-- Port 10000 -- masterYou c

Mysql data backup and recovery, mysql backup and recoveryBackup/recovery policies:1. Regular mysql backup and recovery time that the system can afford should be taken into consideration.2. Make sure that mysql opens log-bin. With binarylog, mysql can perform full recovery, t

optimize the architecture and try to get the DDL of the main library to execute quickly. There is the main library is written, the data security is high, such as sync_binlog=1 (, Innodb_flush_log_at_trx_commit = 1, and so on, and slave does not need such a high data security, can speak sync_ Binlog is set to 0 or off Binlog,innodb_flushlog can also be set to zero to increase the efficiency of SQL execution

is not right 1. Stop MSSQLServer service net stop MSSQLServer 2. Modify Master's MDF name CD C:\Program Files\Microsoft SQL Server\mssql.1\mssql\data ren master.mdf master01.mdf 3.net start MSSQLServer 4. View Error file C:\Program Files\Microsoft SQL Server\mssql.1\mssql\log: 2010-02-08 12:02:00.88 Server error:17113, Severity:16, State:1. 2010-02-08 12:02:00.88 Server Error 2 (the system cannot find the specified file.) ) occurred while o