commvault Alert: Index State Type: Custom Rules - Index State

   環境:

commvault

異常狀況:

突然每天都會收到這個警告信，但備份工作都正常，不知是哪邊有問題。

後來發現這個backupset底下的所有虛擬機備份，在這警告信出現前的備份都可以正常還原。

在開始發出警告信後的備份，還原時都會出現錯誤:Could not perform the operation as Log restore failed for Job 161471. Please check Index Server log for more details。

解決過程:

參考ai上的作法，在commvault主機上的C:\Program Files\Commvault\ContentStore\IndexCache，底下有CvIdxDB跟CvIdxLogs資料夾

在裡面找到跟上面DbName相同名稱的資料夾，把他們改名。

重新建立還原工作，系統就會重建裡面的內容，恢復正常~~但試過沒用。

後來重新啟動完整備份，還是一樣的錯誤。

最後解法就是，建一個新的backupset，在裡面對虛擬機建立新的備份工作，備份完測試，可正常還原。

Environment:

Commvault

Issue:

An alert email suddenly started appearing every day, although all backup jobs were completing successfully and no obvious issues were found.

Further investigation showed that:

• Backups of all virtual machines under this Backupset that were created before the alert emails started could be restored normally.

• Backups created after the alerts began failed during restore with the following error:

Error:
Could not perform the operation as Log restore failed for Job 161471. Please check Index Server log for more details.

Troubleshooting Process:

Based on suggestions found online, the following method was attempted:

1. On the Commvault server, navigate to:
   C:\Program Files\Commvault\ContentStore\IndexCache

2. Locate the folders under CvIdxDB and CvIdxLogs that have the same name as the DbName shown in the error.

3. Rename those folders.

4. Create a new restore job so the system can rebuild the index data.

However, this method did not resolve the issue.

A Full Backup was then executed again, but the restore error still occurred.

Final Resolution:

The issue was resolved by:

1. Creating a new Backupset.

2. Creating a new backup job for the virtual machines within that Backupset.

3. Running the backup again.

After the new backup completed, restore tests were performed and the restore worked normally.

安裝win11 抓不到pcie ssd硬碟。

 環境:

acer主機

Intel 13代 cpu

pcie ssd

異常狀況:

安裝win11，一直抓不到ssd硬碟。

上acer官網找到了irst的驅動，安裝時這個驅動也不支援，還是找不到硬碟。

上intel官網抓到最新一代的irst驅動，卻是exe檔，在win11安裝過程，也沒辦法安裝

解決過程:

intel官網抓到最新一代的irst驅動是exe檔，需在其他台電腦，用powershell指令，去解壓縮，裡面就會有driver這個資料夾。

安裝win11時就可以透過裡面的檔案，載入pcie ssd。

1. 在包含SetupRST.exe檔的目錄中打開終端，方法是右鍵按兩下目錄並在此處選擇「在終端中打開」或「打開 PowerShell」。您可能必須在目錄上按 SHIFT 鍵，才能看到要選擇的正確選項。
2. 透過執行命令 ./SetupRST.exe -extractdrivers SetupRST_extracted 來解壓縮預安裝驅動程式

Environment:

Acer desktop/laptop
Intel 13th Gen CPU
PCIe SSD

Issue:

During Windows 11 installation, the SSD drive is not detected.

The Intel Rapid Storage Technology (IRST) driver downloaded from the Acer support website was loaded during setup, but the SSD still could not be detected.

A newer IRST driver was found on Intel's website, but it was provided as an .exe installer, which cannot be installed directly during the Windows 11 installation process.

Resolution:

The latest Intel IRST package downloaded from Intel's website must first be extracted on another computer.

1. Download the latest SetupRST.exe from Intel.
2. Open a terminal (PowerShell or Command Prompt) in the folder containing SetupRST.exe.
3. Run the following command:

.\SetupRST.exe -extractdrivers SetupRST_extracted

This will extract the pre-installation drivers into a folder named SetupRST_extracted.

To open a terminal in the correct folder:

• Right-click within the folder and select "Open in Terminal" or "Open PowerShell window here".
• On some Windows versions, you may need to hold the SHIFT key while right-clicking to see the appropriate option.

4. Copy the extracted driver files to the Windows 11 installation USB drive.
5. During Windows 11 setup, select Load Driver when choosing the installation disk.
6. Browse to the extracted driver folder and load the IRST driver.

After loading the extracted driver, the PCIe SSD will be detected and Windows 11 installation can proceed normally.

MS SQL 維護計劃 備份到NAS共用資料夾

環境:

AD

NAS

MS SQL

異常狀況:

MS SQL 維護計劃 在設定DB備份的路徑，不能指定到NAS上的共用資料夾。

解決過程:

維護計劃在備份時，執行的身份通常是預設的一個系統服務帳號，可以到"服務"去查。

因為沒辦法在NAS上的共用資料夾上指派存取權限給這個帳號。

所以要換個方法

1.先在AD建立一個群組，然後把MS SQL這台主機的電腦帳號，加到這個群組。

2.接著在NAS上的共用資料夾，指派AD群組有修改權限。

這樣就完成了，備份時，這台主機就直接有權限讀寫，不會被SQL服務執行的身份給影響。

Environment:

Active Directory (AD)

NAS

Microsoft SQL Server

Issue:

When configuring a database backup destination in an MS SQL Server Maintenance Plan, the backup cannot be written directly to a shared folder on a NAS.

Resolution:

When a Maintenance Plan runs, it typically executes under the security context of a SQL Server service account (which can be identified in Services).

Since it is often not possible to assign permissions on the NAS shared folder directly to this service account, the following approach can be used:

1. Create a new Active Directory security group.
2. Add the computer account of the SQL Server to this AD group.
3. On the NAS shared folder, grant the AD group Modify permissions.

With this configuration, the SQL Server host can access the shared folder using its computer account permissions, allowing the Maintenance Plan to read from and write to the NAS share without being affected by the specific SQL Server service account being used.