Commvault 備份虛擬機 突然變的很慢

環境:

Commvault 備份虛擬機

異常狀況:

對新的虛擬機做第一次備份，可能容量比較大，過程中又有其他的備份，造成效能問題，最後就停住多個小時後，手動取消。

但後來要重新備份時，傳輸速度變超級慢，速度大概只剩之前的1/7~8，重開機也一樣。

解決過程:

後來發現之前備份失敗後，虛擬機上有一份snapshot沒被移除，先在esxi上，把那份snapshot刪除後，重新備份，就正常了。

Environment:

Commvault (VM Backup)

Issue:

When performing the first backup of a new virtual machine, the data size was relatively large. During the process, other backup jobs were also running, causing performance issues. Eventually, the job became unresponsive and was manually canceled after several hours.

After that, when attempting to run the backup again, the transfer speed became extremely slow, dropping to about 1/7–1/8 of the original speed. Restarting the system did not resolve the issue.

Resolution:

It was later discovered that after the failed backup, a snapshot remained on the virtual machine and was not removed.

By logging into ESXi and deleting the leftover snapshot, then running the backup again, the performance returned to normal.

ESXI 無法開啟虛擬機器 xxx的電源。開啟模組 monitorloop 的電源失敗

  環境:

ESXI  

Synology active backup business

異常狀況:

用Synology active backup business備份的虛擬機，還原到其他esxi後，開機出現錯誤。

解決過程:

原機配置了較高的CPU與RAM，還原後，目的esxi上資源不足，無法開機，把虛擬機的CPU與RAM調低後，就可以正常開機

Environment:

ESXi
Synology Active Backup for Business

Issue:

After restoring a virtual machine using Synology Active Backup for Business to another ESXi host, the VM fails to power on and shows an error.

Resolution:

The original VM was configured with relatively high CPU and RAM.
After restoration, the target ESXi host did not have sufficient resources to support that configuration.

By reducing the VM’s CPU and RAM allocation, the virtual machine was able to power on normally.

ESXI VMFS 增加容量失敗-無法變更主機組態。

 環境:

ESXI 6.7

異常狀況:

底層硬碟RAID擴充完一顆新硬碟後，要在ESXI上也對儲存區進行擴充。

在web console上操作，對著要擴充的datastore ，選擇"增加容量"。

再來選擇"擴充現有..........."。

第三步，要先在分割之前的圖，點選vmfs區塊，然後就會出現一個調整新增容量的設定，選擇要把新增的硬碟，擴充多少容量到vmfs中。

按下完成後，就會出現錯誤，試了很多次，擴充不同的容量，都一樣錯誤:

說明:延伸 VMFS 資料存放區範圍的容量

狀態:失敗 - 無法變更主機組態。

解決過程:

用指令的方式擴充，就成功了。

Environment:

ESXi 6.7

Issue:

After expanding the underlying RAID by adding a new disk, the datastore also needs to be extended in ESXi.

When performing the operation via the web console:

1. Select the datastore and choose “Increase capacity”
2. Then select “Expand existing…”
3. In the partition layout screen, select the VMFS partition, and adjust how much of the newly added space should be allocated to VMFS

However, after clicking Finish, the following error occurs regardless of the size selected:

• Description: Extend VMFS datastore capacity
• Status: Failed – Unable to change the host configuration

Resolution:

Expanding the datastore using the command line (CLI) was successful.

DHCP 設定匯出匯入

DHCP config export command

netsh dhcp server export d:\backup.txt all

DHCP config import command

 netsh dhcp server import d:\backup.txt all

SQL management tool連線時出現錯誤:此憑證鏈結是由不受信任的授權單位發出的

 

環境:

MS SQL2022

異常狀況:

SQL management tool連線時出現錯誤:此憑證鏈結是由不受信任的授權單位發出的

解決過程:

錯誤訊息「此憑證鏈結是由不受信任的授權單位發出的」是因為 SQL Server 2022 預設強制執行加密連線。

勾選下面的「信任伺服器憑證」選項，即可正常登入。

Environment:

MS SQL Server 2022

Issue:

When connecting using the SQL management tool, the following error appears:

“The certificate chain was issued by an authority that is not trusted.”

Resolution:

This error occurs because SQL Server 2022 enforces encrypted connections by default.

Enable the “Trust Server Certificate” option in the connection settings, and then you will be able to log in normally.

SQL 2022安裝時卡住不動

環境:

MS SQL2022

Kaspersky endpoint security

異常狀況:

MS SQL2022安裝到一半停住很久，cpu跟ram的使用資源都不會動。

解決過程:

將Kaspersky endpoint security防護暫停後，就會繼續安裝過程，完成剛裝

Environment:

MS SQL Server 2022
Kaspersky Endpoint Security

Issue:

During the installation of MS SQL Server 2022, the setup process gets stuck for a long time.
CPU and RAM usage remain unchanged and the installation does not continue.

Resolution:

After temporarily disabling Kaspersky Endpoint Security protection, the installation process resumes and completes successfully.

Synology 取消 "此裝置以後不需要驗證"

 環境:

Synology  NAS啟用 2FA的"此裝置以後不需要驗證"，需要取消

解決過程:

管理者登入後，到使用者設定中，在該帳號底下，選擇"登出所有裝置"，就會跳出說明，提醒這樣也會取消信任裝置。

之後同設備要登入時，就要輸入2FA的驗證碼。

Environment:

On a Synology NAS, 2FA is enabled and the option “Trust this device / Do not require verification on this device in the future” needs to be revoked.

Resolution / Steps:

1. Log in as an administrator.

2. Go to User settings.

3. Under the target user account, select “Sign out of all devices”.

4. A prompt will appear explaining that this action will also revoke trusted devices.

After this, when the same device logs in again, it will be required to enter the 2FA verification code.

Backup exec 的資料庫備份

  環境:

Backup exec 2014

異常狀況:

想要透過Backup exec 本身的工具beutility.exe，把Backup exec 自己的設定db檔匯出到其他存放。

但執行beutility.exe指令時，都會先跳出一個警告視窗，因為無法設定用batch自動執行。

解決過程:

Backup exec 的主程式裡就有可以設定db檔定期匯出到預設資料夾的功能了，不需要額外用beutility.exe來執行。

在"組態與設定"->"Backup Exec設定"，裡面有一個"資料庫維護"，就可以設定排程來做這件事。

Environment:

Backup Exec 2014

Issue:

Attempting to use Backup Exec’s built-in tool beutility.exe to export the Backup Exec configuration database to another storage location.
However, when running beutility.exe, a warning dialog always appears, making it impossible to automate the process using a batch script.

Resolution / Workaround:

Backup Exec already provides a built-in feature to periodically export the database to a default folder, so there is no need to use beutility.exe.

In Configuration and Settings → Backup Exec Settings, there is a Database Maintenance option where you can configure a scheduled task to perform this database export automatically.

python抓取元大rtd裡的欄位即時資料範例

 import xlwings as xw

import time

# 連接當前開啟的 Excel 檔案

wb = xw.Book('txf.xlsm')

sheet = wb.sheets['價格記錄']

while True:

    # 假設元大 RTD 資料在 A1 儲存格

    price = sheet.range('A2').value

    print(f"當前即時價格: {price}")

    # 根據需求設定取樣頻率 (例如每秒 1 秒)

    time.sleep(1)

Windows 資料夾透過FASTCOPY同步到NAS共用資料夾 權限並沒有同步

 環境:

Windows 資料夾透過FASTCOPY，同步到NAS共用資料夾

異常狀況:

資料夾開始建立進行同步時，發現權限並沒有同步過去

解決過程:

研究了很久，發現測試的資料夾正常，正式要同步的資料夾會有問題。

原來是資料夾第一次在同步時，還沒全部完成前去查看資料夾權限時，不會是最後的結果，所以要等同步完再檢查，就會發現資料夾的ACL權限有全部同步過去了。

Environment:

Windows folders synchronized to a NAS shared folder using FastCopy.

Issue:

When the folder creation and synchronization start, the folder permissions (ACLs) do not appear to be synchronized to the NAS.

Resolution / Findings:

After extensive investigation, it was found that test folders behaved normally, while the production folders showed this issue.

The root cause is that during the initial synchronization, if you check the folder permissions before the sync process has fully completed, the permissions shown are not the final result.
Once the synchronization finishes completely and you recheck the folder permissions, you will see that the ACL permissions have been fully and correctly synchronized.