我公司使用FTP服務(wù)器為客戶上傳數(shù)據(jù)，理論上可以使用任何FTP客戶端下載。您僅需幾步即可下載您的文件。

注意數(shù)據(jù)請在一周內(nèi)下載完成，超時自動刪除數(shù)據(jù)。

注意數(shù)據(jù)請在一周內(nèi)下載完成，超時自動刪除數(shù)據(jù)。

注意數(shù)據(jù)請在一周內(nèi)下載完成，超時自動刪除數(shù)據(jù)。

下面以Windows平臺為例：

第1步 下載ftp客戶端軟件

點擊下載：FlashFXP單文件版

第2步 打開ftp客戶端軟件下載您的文件

下面以macOS平臺為例：

服務(wù)器地址：ftp://cloud.data-sos.cc:2100

轉(zhuǎn)載請注明：成都千喜數(shù)據(jù)恢復中心 » FTP下載方法說明

在監(jiān)控技術(shù)廣泛應(yīng)用的當下，?？低暎℉IKVISON）晧視通嵌入式硬盤錄像機所存儲的監(jiān)控視頻數(shù)據(jù)，其安全性與完整性備受關(guān)注。成都千喜數(shù)據(jù)恢復中心精心打造的 Data-SOS?？低?HIKVISON)晧視通監(jiān)控視頻數(shù)據(jù)恢復軟件，應(yīng)運而生，為監(jiān)控視頻數(shù)據(jù)恢復提供了專業(yè)且可靠的解決方案。

這款 Data-SOS?？低?HIKVISON)晧視通監(jiān)控視頻數(shù)據(jù)恢復軟件是成都千喜數(shù)據(jù)恢復中心智慧與技術(shù)的結(jié)晶，其研發(fā)聚焦于海康威視晧視通監(jiān)控視頻文件的恢復難題。無論是錄像機初始化操作不慎抹去的視頻數(shù)據(jù)，還是誤刪除且尚未被新數(shù)據(jù)覆蓋的視頻文件，Data-SOS?？低?HIKVISON)晧視通監(jiān)控視頻數(shù)據(jù)恢復軟件都展現(xiàn)出強大的恢復能力。其核心的碎片處理技術(shù)堪稱亮點，最大程度地確保監(jiān)控錄像文件得以成功恢復，為用戶找回珍貴的監(jiān)控影像資料。

然而需留意，因技術(shù)特性，軟件可能遭部分殺毒軟件誤報病毒，此為正?，F(xiàn)象。使用時可關(guān)閉殺毒軟件或設(shè)為信任運行。

此外，Data-SOS?？低?HIKVISON)晧視通監(jiān)控視頻數(shù)據(jù)恢復軟件還具備高度的靈活性與定制化服務(wù)能力。如果您對軟件的定制服務(wù)感興趣，歡迎隨時通過 QQ 與我們?nèi)〉寐?lián)系。我們的專業(yè)團隊將竭誠為您服務(wù)，協(xié)助您定制專屬的監(jiān)控視頻數(shù)據(jù)恢復方案，讓Data-SOS?？低?HIKVISON)晧視通監(jiān)控視頻數(shù)據(jù)恢復軟件成為您在數(shù)據(jù)恢復領(lǐng)域的得力助手，守護您的監(jiān)控視頻數(shù)據(jù)資產(chǎn)。

購買軟件請聯(lián)系QQ：1429567802 價格:200元/單次 600元/永久

軟件下載

晧視通版? ?全功能版

軟件截圖

轉(zhuǎn)載請注明：成都千喜數(shù)據(jù)恢復中心 » Data-SOS?？低?HIKVISON)晧視通監(jiān)控視頻數(shù)據(jù)恢復軟件

客戶描述使用的是使用的是索尼SONY_ILCE-7SM3 微單拍攝的視頻，在拍攝過程中由于拍攝設(shè)備死機造成C7503.MP4和C7504.MP4損壞不能正常播放。

我們使用WINHEX打開C7503.MP4，根據(jù)MP4文件結(jié)構(gòu)定義，本MP4文件由ftyp BOX開始大小為0x1C，在文件開始偏移跳轉(zhuǎn)0x1C為uuid BOX的大小為0x94，繼續(xù)跳轉(zhuǎn)0x94為mdat Box 大小為0xF8FFFF50，此Box包含MP4文件的媒體數(shù)據(jù)，繼續(xù)跳轉(zhuǎn)0xF8FFFF50發(fā)現(xiàn)已到達文件尾，可以發(fā)現(xiàn)此MP4文件缺少moov Box，該box包含了文件媒體的metadata信息，例如視頻和聲音每一幀的開始偏移，每一幀的大小等等非常重要的信息必須要有這些信息播放器才能根據(jù)這些信息播放視頻，要粗略了解MP4&MOV的文件結(jié)構(gòu)可以查看MP4文件結(jié)構(gòu)分析一文。

現(xiàn)在這種情況要想修復C7503.MP4和C7504.MP4文件需要參照同一機型同一參照拍攝的視頻，C7666.MP4為客戶發(fā)來的參照視頻，分析C7666.MP4的moov Box及下級子Box得到參照數(shù)據(jù)用于修復損壞的視頻。視頻修復成功能測試播放，一切正常。

轉(zhuǎn)載請注明：成都千喜數(shù)據(jù)恢復中心 » 修復相機斷電或其它原因損壞的MP4&MOV視頻文件

（本文為機器翻譯）現(xiàn)代希捷硬盤數(shù)據(jù)恢復非常復雜，其硬件變得越來越敏感。如果磁頭出現(xiàn)問題，它們可能會在內(nèi)部固件過程中損壞服務(wù)區(qū)中的一些關(guān)鍵物體。這可能是數(shù)據(jù)恢復時間增加的一個原因：我們必須花費更多的時間和金錢來尋找新的磁頭并修復不良的系統(tǒng)文件。是否有可能避免這種情況并阻止服務(wù)區(qū)的寫入？讓我們同成都數(shù)據(jù)恢復一起來學習一下。

我們有一個Rosewood 家族的ST1000LM035驅(qū)動器，我們需要停用服務(wù)區(qū)中的寫入功能。首先，我們應(yīng)該使用固件的DiskFW部分。事實上，DiskFW 實際上是一個替換 ROM 擴展——它被加載并替換了 ROM 的完整接口代碼（內(nèi)存中只有 ROM 中的伺服碼和自適應(yīng)代碼）。

使用 PC-3000，我們可以在 vol.0x00 文件 ID 0x020D中找到 DiskFW。我們可以通過終端或ATA手動讀取和保存它：

在下一步中，我們必須打開工具->實用程序擴展->使用閃存ROM映像文件并選擇以前保存的20D：

將DiskFW添加到ROM編輯器的另一種方法是直接讀取它：

一旦我們讀取20D，我們將看到一條錯誤消息，這是由于實用程序沒有看到有效的ROM段而出現(xiàn)的，因為我們使用的不是ROM，而是DiskFW：

要停用保護，請在同一菜單中選擇“寫保護”，停用選項。

正如我們之前提到的，所有更改都已應(yīng)用于 HDD RAM，因此我們只需重新啟動驅(qū)動器即可停用寫入保護，并允許磁頭再次在服務(wù)區(qū)中進行更改。軟復位和硬復位不會停用保護，只有電源重啟才會將其關(guān)閉。

轉(zhuǎn)載請注明：成都千喜數(shù)據(jù)恢復中心 » 使用PC-3000如何阻止寫入希捷硬盤固件區(qū)

讀取模塊到配置文件夾
文件夾: E:\!Profiles\SgF3\Rosewood_8C\SDM1-WES07P6X\Data\SABackup\ModDir\

將跳過 : 000C, 000E, 000F, 0022, 0023, 002C, 0044, 0045, 0046, 0047, 0048, 0049, 004A, 004F, 0052

模塊 0000, Reserved Defect Table (SA defect table)…………………. : Ok
模塊 0001, Drive Information File (DIF)…………………………… : Ok
模塊 0002, Performance Parameter File (PPF)……………………….. : Ok
模塊 0003, Primary Defect File (P-List)…………………………… : Ok
模塊 0005, Manufacturing Information File (MIF)……………………. : Ok
模塊 0008……………………………………………………… : Ok
模塊 000B……………………………………………………… : Ok
模塊 000D……………………………………………………… : Ok
模塊 0013, Disc Registry File (settings, security, etc)…………….. : Ok
模塊 0015, BGMS File (Directed Offline Scan)………………………. : Ok
模塊 0016……………………………………………………… : Ok
模塊 0017……………………………………………………… : Ok
模塊 0019, Log File…………………………………………….. : Ok
模塊 001A, Log File…………………………………………….. : Ok
模塊 001B, Log File…………………………………………….. : Ok
模塊 001C……………………………………………………… : Ok
模塊 001D, Physical Overlay File 0……………………………….. : Ok
模塊 001E, Physical Overlay File 1……………………………….. : Ok
模塊 0020, Physical Overlay File 3……………………………….. : Ok
模塊 0021, Physical Overlay File 4……………………………….. : Ok
模塊 002A, Saved Mode Pages (HDD settings)………………………… : Ok
模塊 002B, R/W Operating Parameters (translator, etc)………………. : Error
錯誤 : Rq Rd Sys File part ID 2B, Offs 0x0 err!技術(shù)狀態(tài) 0x72, 0x04440000
模塊 0033……………………………………………………… : Ok
模塊 0034, Packed CONGEN XML definition…………………………… : Ok
模塊 003A……………………………………………………… : Ok
模塊 003D, Disc firmware container 1……………………………… : Ok
模塊 003E, Disc firmware container 2……………………………… : Ok
模塊 003F, SED parameters……………………………………….. : Ok
模塊 0040, SED parameters……………………………………….. : Ok
模塊 0041, SED parameters……………………………………….. : Ok
模塊 0042, ST Ovl………………………………………………. : Ok
模塊 0043, Defect list report file……………………………….. : Ok
模塊 004B……………………………………………………… : Ok
模塊 0050, MCMT………………………………………………… : Ok
模塊 0058……………………………………………………… : Ok
模塊 005C……………………………………………………… : Ok
讀取模塊完成

讀取System Files到配置文件夾
文件夾: E:\!Profiles\SgF3\Rosewood_8C\SDM1-WES07P6X\Data\SABackup\SysFiles\
拷貝 : 0 1

Sys File FC00C000(0), Reserved Defect Table (SA defect table)……… : Ok
Sys File FC00C000(1), Reserved Defect Table (SA defect table)……… : Ok
Sys File FC00F203(0)………………………………………….. : Ok
Sys File FC00F203(1)………………………………………….. : Ok
Sys File FC01020D(0), Disc firmware container 1………………….. : Ok
Sys File FC01020D(1), Disc firmware container 1………………….. : Ok
Sys File FC01120E(0), Disc firmware container 2………………….. : Ok
Sys File FC01120E(1), Disc firmware container 2………………….. : Ok
Sys File FC012226(0)………………………………………….. : Ok
Sys File FC012226(1)………………………………………….. : Ok
Sys File FC00D330(0), Packed CONGEN XML definition……………….. : Ok
Sys File FC00D330(1), Packed CONGEN XML definition……………….. : Ok
Sys File FC00E331(0)………………………………………….. : Ok
Sys File FC00E331(1)………………………………………….. : Ok
Sys File FC35701B(0), Primary Defect File (P-List)……………….. : Ok
Sys File FC35701B(1), Primary Defect File (P-List)……………….. : Ok
Sys File FC35E028(0), R/W Operating Parameters (translator, etc)…… : Error
錯誤 : Rd SysF 3:28:0 (0/8000) err = 0x0000000E
Sys File FC35E028(1), R/W Operating Parameters (translator, etc)…… : Error
錯誤 : Rd SysF 3:28:1 (0/8000) err = 0x0000000E
Sys File FC360035(0), Non Resident G-List……………………….. : Ok
Sys File FC360035(1), Non Resident G-List……………………….. : Ok
Sys File FC361036(0)………………………………………….. : Ok
Sys File FC361036(1)………………………………………….. : Ok
Sys File FC365100(0), Physical Overlay File 0……………………. : Ok
Sys File FC365100(1), Physical Overlay File 0……………………. : Ok
Sys File FC366101(0), Physical Overlay File 1……………………. : Ok
Sys File FC366101(1), Physical Overlay File 1……………………. : Ok
Sys File FC367102(0)………………………………………….. : Ok
Sys File FC367102(1)………………………………………….. : Ok
Sys File FC368103(0), Physical Overlay File 3……………………. : Ok
Sys File FC368103(1), Physical Overlay File 3……………………. : Ok
Sys File FC369104(0), Physical Overlay File 4……………………. : Ok
Sys File FC369104(1), Physical Overlay File 4……………………. : Ok
Sys File FC36A105(0)………………………………………….. : Ok
Sys File FC36A105(1)………………………………………….. : Ok
Sys File FC36B106(0)………………………………………….. : Ok
Sys File FC36B106(1)………………………………………….. : Ok
Sys File FC36C107(0)………………………………………….. : Ok
Sys File FC36C107(1)………………………………………….. : Ok
Sys File FC36D108(0)………………………………………….. : Ok
Sys File FC36D108(1)………………………………………….. : Ok
Sys File FC36E109(0)………………………………………….. : Ok
Sys File FC36E109(1)………………………………………….. : Ok
Sys File FC36F10A(0)………………………………………….. : Ok
Sys File FC36F10A(1)………………………………………….. : Ok
Sys File FC37010B(0)………………………………………….. : Ok
Sys File FC37010B(1)………………………………………….. : Ok
Sys File FC37110C(0)………………………………………….. : Ok
Sys File FC37110C(1)………………………………………….. : Ok
Sys File FC37210D(0)………………………………………….. : Ok
Sys File FC37210D(1)………………………………………….. : Ok
Sys File FC373110(0)………………………………………….. : Ok
Sys File FC373110(1)………………………………………….. : Ok
Sys File FC3961D1(0), SED parameters……………………………. : Ok
Sys File FC3961D1(1), SED parameters……………………………. : Ok
Sys File FC3991D2(0), SED parameters……………………………. : Ok
Sys File FC3991D2(1), SED parameters……………………………. : Ok
Sys File FC38430A(0), Disc Registry File (settings, security, etc)…. : Ok
Sys File FC38430A(1), Disc Registry File (settings, security, etc)…. : Ok
Sys File FC34F346(0)………………………………………….. : Ok
Sys File FC34F346(1)………………………………………….. : Ok
Sys File FC3B1348(0), MCMT…………………………………….. : Ok
Sys File FC3B1348(1), MCMT…………………………………….. : Ok
讀取 System Files 完成
服務(wù)區(qū)信息完成備份

可以從日志中看到只有“模塊 002B”和“Sys File FC35E028(0)”損壞其它固件正常；

解決方法

首先備份非常駐缺陷表，【缺陷表】-【編輯非常駐缺陷表G-LIST(G)】-【保存(S)】保存缺陷表表

重新斷電上電此時能識別硬盤容量，嘗試訪問硬盤的0扇區(qū)和最后一個扇區(qū)均正常

轉(zhuǎn)載請注明：成都千喜數(shù)據(jù)恢復中心 » 恢復希捷硬盤002B模塊(FC35E028系統(tǒng)文件)損壞的解決辦法導致硬盤容量為0 MB數(shù)據(jù)的方法

如果硬盤上電后狀態(tài)燈進入就緒狀態(tài)，【工具欄】-【程序自動檢測】-【啟動程序】程序會自動識別硬盤的家族，否則需要手動選擇【硬盤廠商】-【實用程序】-【家族】，如果不清楚該硬盤屬于何家族任意選一個即可

方法一

點擊【啟動實用程序】

【工具】-【擴展實用程序】-【操作 Flash ROM 映像文件】

如果硬盤能正常就緒而且該ROM沒有固件鎖，可選擇【通過ATA讀取】讀取硬盤ROM，否則需要選擇【通過引導代碼讀取】讀取硬盤ROM,【COM端口傳輸速率】需要根據(jù)經(jīng)驗選擇，或從大到小嘗試；

讀取成功后可以手動保存ROM文件

方法二

啟動【Seagate F3 Architecture】-【Boot Code Start】

選擇合適的【COM端口傳輸速率】-【讀取ROM】

讀取成功后【啟動實用程序】

解鎖ROM

如果ROM有固件鎖需要解鎖ROM

點擊【準備技術(shù)模式解鎖】

解鎖ROM后重新寫入硬盤即可

轉(zhuǎn)載請注明：成都千喜數(shù)據(jù)恢復中心 » 如何使用PC-3000備份希捷硬盤ROM和解鎖ROM

轉(zhuǎn)載請注明：成都千喜數(shù)據(jù)恢復中心 » 西部數(shù)據(jù)2060-810033-000 USB電路板改SATA板接線圖

轉(zhuǎn)載請注明：成都千喜數(shù)據(jù)恢復中心 » 西部數(shù)據(jù)2060-810067-000 USB電路板改SATA板接線圖

還原包含數(shù)據(jù)庫 Restoring a Contained Database：
當我了解到包含性數(shù)據(jù)庫，我第一個擔心的問題是，作為一個dba如何阻止那些沒有專業(yè)知識的人來訪問數(shù)據(jù)庫呢？還好，已經(jīng)有三個保護層面了。

One of the first concerns I had when I learned about contained database was how am I as a DBA protected against giving someone access to a database without my knowledge. Well, there are several layers of protection starting with the fact that it is up to the administrator to enable containment before it even comes in to play.

第一層保護 First Layer of Protection：
在還原一個包含數(shù)據(jù)庫或創(chuàng)建一個包含數(shù)據(jù)庫之前，或者之前已經(jīng)存在一個包含數(shù)據(jù)庫，那么在服務(wù)器級別的包含選項必須要啟動。如果服務(wù)器級別不啟動包含選項，那么是完全的保護。你可以通過sp_configure或者通過服務(wù)器屬性，它在高級選項里，不過他不是一個真的高級選項，所以在你修改或查看服務(wù)器級別包含選項時不需要開啟Show advanced options選項。

Containment has to be enabled at the server level before a contained database can be restored or created or before an existing database can have containment enabled. As long as you do not enable this setting at the server level, you’re completely protected. You can enable it via sp_configure or via the Server Properties dialog (Advanced tab). Despite the fact that it is listed on the Advanced tab, it is not an advanced option. You do not have to enable?Show advanced options?before changing or checking this setting. I see a lot of blog posts stating that it is an advanced option and showing that the Show advanced options has to be set, but it is not and does not.

如果要查看是否開啟了服務(wù)器級別的包含選項，也可以查詢sys.configurations這個系統(tǒng)表，用它的好處就是可以自動化腳本，如果要修改，還是需要用sp_configure。

In addition to sp_configure and the Server Properties dialog, you can check the current setting by querying the sys.configurations table. this is my preferred method for querying for configuration settings because it is a lot easier to use in automation scripts. However, if my intent to change it if it needs it, I generally use sp_configure.

如果在沒有啟用包含選項的服務(wù)器實例上還原一個包含數(shù)據(jù)庫，將會失敗并返回下面的信息：

The error message you will receive is:

Msg 12824, Level 16, State 1, Line 1
The sp_configure value 'contained database authentication' must be set to 1 in order to restore a contained database.  You may need to use RECONFIGURE to set the value_in_use.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.

這個信息告訴你需要先啟用服務(wù)器級別包含選項才能還原，對于DBA來說，這是一個警告，是否啟用這個包含選項由你自己決定，并不是看到這樣的信息就一定要去啟用，因為可能會影響服務(wù)器或數(shù)據(jù)庫的安全。

If you have not enabled containment at the server level at you attempt to restore a database that has containment enabled, the restore will fail with an error telling you that containment has to be enabled first. This is a warning to the DBA that the database is contained. It is up to you to decide whether enabling containment is the proper thing to do or not. Please don’t just enable it because the error message said to. This affects the security of your server and databases.

開啟或禁用包含數(shù)據(jù)為選項命令為，注意，這里是Reconfigure，不是Reconfigure WITH OVERRIDE，這里有一個重要的原因，后面對提到。

The option that you are enabling or disabling is?contained database authentication?and the command to enable/disable containment at the server level is as follows:

-- Enable "contained database authentication"
Exec sp_configure 'contained', 1;
Reconfigure;

-- Disable "contained database authentication"
Exec sp_configure 'contained', 0;
Reconfigure;

通過圖形界面：

第二層保護 Second Layer of Protection：
如果你啟用了包含數(shù)據(jù)庫選項，那么當還原一個包含數(shù)據(jù)庫時，不會有任何警告或是提示。只能由你自己來確定還原的數(shù)據(jù)庫是不是包含數(shù)據(jù)庫，幸運的是，有一個內(nèi)置的結(jié)構(gòu)可以知道這點，在SQL Server 2012，當你執(zhí)行RESTORE HEADERONLY時有一個新的列被增加，它就是Containment ，當它為1時，表明是包含數(shù)據(jù)庫，反之則不是，如下圖我對一個包含數(shù)據(jù)庫做的檢查：

You will notice that I used RECONFIGURE in that code and not RECONFIGURE WITH OVERRIDE. I did so for a very important reason. I will get to that later, but first, let’s take a look at the next layer of protection. Let’s move a step further and see how you are protected after you have enabled containment at the server level. Once the option is enabled, you will get no warnings whatsoever when you restore a contained database. It’s up to you to make sure you know whether or not the backup you are going to restore is contained or not. Fortunately, there is a built-in mechanism for discovering that.

If you are presented with a backup of a new database, you can check for containment yourself. You don’t have to rely on being told about it. A new column (Containment) has been added to the output of the RESTORE HEADERONLY command. You can use this command to inspect the header information for the backup before restoring it. If Containment = 1, containment is enabled in the database. If Containment = 0, it is not enabled.

In this example, I am checking the header information of a backup named c:\bakCDTest.bak:

Restore HeaderOnly From Disk = 'c:\bakCDTest.bak';

It’s very easy to check and there is no reason not to perform this check before restoring a database if the server has containment enabled.

最后一層保護 Final Layer of Protection：
假設(shè)有這樣一個災(zāi)難恢復場景，你需要盡快的恢復一個數(shù)據(jù)庫上線，但是當你把它還原到一臺替代服務(wù)器上時，你發(fā)現(xiàn)它是一個包含數(shù)據(jù)庫?，F(xiàn)在讓我們假設(shè)你還沒有意識到已經(jīng)啟用了這個設(shè)置，而且就你的能力和可以查閱的文檔，你會認為這個數(shù)據(jù)庫沒有使用包含用戶，再者，假設(shè)可能有一些法規(guī)或者安全策略，在沒有確切有效文檔支持情況下，不能有包含用戶，但是你可能暫時沒有時間去找到相關(guān)人去解釋為什么存在包含用戶，現(xiàn)在你又需要盡快的恢復數(shù)據(jù)庫又要遵守安全策略。

Let’s say you are in a disaster recovery scenario and you need to get the database back online as quickly as possible, but when you attempt to restore the database on a replacement server, you discover that it has containment enabled. Now let’s assume that you had not been aware that this setting was enabled and to the extent of your knowledge and available documentation, the database does not use contained users. Furthermore, let’s assume that there may be some compliancy regulations or security policies that say that you can’t have undocumented contained users. You may not have time to hunt down someone that can explain why there are contained users. You need to get the database restored and also respect your security restrictions.

在這種情況下，你可以做的就是先啟用包含數(shù)據(jù)庫選項，再恢復數(shù)據(jù)庫，然后再禁用掉。

One option you can do is to enable containment at the server level, restore the database, and then disable containment at the server level. If you try to disable containment at the server level using sp_configure and RECONFIGURE, you will get an error message stating that you can not disable containment because there are contained databases. You can force disabling of containment at the server level by using RECONFIGURE WITH OVERRIDE. This is why I was sure to use just RECONFIGURE in the earlier example. I want to ensure that I don’t accidentally disable the setting if there are contained databases without realizing it.

在禁用時，會報錯，需要我們使用WITH OVERRIDE，這其實就是最后一個保護，這就是之前用Reconfigure而不用Reconfigure WITH OVERRIDE的原因。

Here is what happens when you try to disable containment at the server level when a contained database already exists:

-- Disable "contained database authentication"
Exec sp_configure 'contained', 0;
Reconfigure;

Configuration option 'contained database authentication' changed from 1 to 0. Run the RECONFIGURE statement to install.
Msg 12818, Level 16, State 1, Line 3
RECONFIGURE failed. Attempting to change the 'contained database authentication' value to 0 while there are existing contained databases requires a RECONFIGURE WITH OVERRIDE.

-- Force disabling of "contained database authentication"
Reconfigure With Override;

Command(s) completed successfully.

總結(jié) Summary：
三層保護按我個人理解應(yīng)該就是：服務(wù)器級別的contained啟用、RESTORE HEADERONLY可以確認是否為包含數(shù)據(jù)庫、禁用時如果用Reconfigure，那么存在包含庫就會有警告。作為DBA來講，有責任理清這些，DBA是應(yīng)該是第一道防護，其次才依靠這三個防護。

There are built-in protections and mechanisms for protecting yourself from restoring a contained database, but there is also a responsibility on us as administrators to make sure we understand our actions and don’t get blind-sided by a contained database. These built-in features should be your second line of defense, and good practices and being diligent about being aware of what we are doing and the implications our actions should be our first line of defense. It’s on us to secure our databases and servers and the built-in functionality is just a fail-safe.

轉(zhuǎn)載請注明：成都千喜數(shù)據(jù)恢復中心 » SQL Server 災(zāi)難恢復之二：包含數(shù)據(jù)庫備份在還原時的保護

下面我們同千喜成都數(shù)據(jù)恢復中心的工程師一起來解決這個問題；手上有一塊?TOSHIBA MQ04UBB400 4T的硬盤，PCB電路板型號為：G4311A，現(xiàn)在的故障磁頭0有輕微磨損，懷疑0號盤面劃傷，下面我們通過虛擬磁頭的方式的讀取硬盤其它盤片的數(shù)據(jù)。

8.硬盤能正常識別，并能讀取固件；

9.新建Data Extractor任務(wù)，發(fā)現(xiàn)除0頭外的其它磁頭均能正常讀?。?/p>

轉(zhuǎn)載請注明：成都千喜數(shù)據(jù)恢復中心 » 東芝硬盤如何虛擬磁頭，東芝硬盤虛擬磁頭的方法？