• Hyper-V - 建議的網路配置 (Recommended network configuration for Hyper-V)

    Your server have two physical NICs and below is a description of your original networking configuration:
    1. Disable one of the physical interface
    2. Bind the second physical interface to Hyper-V, so that the interface is now actually only a virtual switch (a vitual interface is created as a result of this binding)
    3. Configured the host to use virtual interface for external connection (this design will force host to use the same virtual switch that every other VM uses for external connections)

    SYMPTOM
    ==================
    - VM's synthetic network adaptor is configured with static IP
    - Saved the VM
    - Backup the VM using WSB
    - Restored the VM
    - Started VM after restoration, VM's synthetic network adaptor was in DHCP state
    - The problem symptom persisted even if we tried to rebooted the VM and disabled/enabled the problbematic network adaptor.

    We use the following method to workaround the issue:
    - Re-configured NIC to use previous assigned static IP
    - We will get a warning message saying that this IP is already being assigned to a NIC. Do you want to want to use a different IP?
    - Click No and close the TCP/IP properties
    - NIC's connection will suddenly resume and all previous TCP/IP configuration returned to previous static state

    RECOMMENDATION
    ==================
    The following design is rather recommended:
    1. Configure the first physical interface for host's external connection
    2. Bind the second physical interface with Hyper-V, so that the interface is now actually a virtual switch
    3. Disable the virtual adaptor that was generated as a result of step 2 (this design separates the host traffic from all other VMs, allowing complete traffic isolation between the parent/child partition)

    After making the above configuration changes, the problem symptom no longer happens.

  • FRS Replication JRNL_WRAP_ERROR

    事件類型:    錯誤
    事件來源:    NtFrs
    事件類別目錄:    無
    事件識別碼:    13568
    日期:        2008/4/28
    時間:        下午 07:03:06
    使用者:        N/A
    電腦:    DRM
    描述:
    檔案複寫服務偵測出複本組 "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" 在 JRNL_WRAP_ERROR 狀態。
    複本組名稱是:   "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
    複本根路徑是:   "c:\windows\sysvol\domain"
    複本根磁碟區是: "\\.\C:"
    複本組發生 JRNL_WRAP_ERROR,因為它嘗試讀取 NTFS USN 日誌,但找不到這個日誌。 這可能是因為下列原因所導致。
    [1] 磁碟區 "\\.\C:" 已經被格式化。
    [2] 在磁碟區 "\\.\C:" 的 NTFS USN 日誌已被刪除。
    [3] 在磁碟區 "\\.\C:" 的 NTFS USN 日誌已被截斷。如果 Chkdsk 在日誌 結尾發現損毀的項目,就有可能會截斷日誌。
    [4] 檔案複寫服務已經有很長一段時間並未在這台電腦上執行。
    [5] 檔案複寫服務跟不上 "\\.\C:" 磁碟 IO 活動的速度。
    設定 "Enable Journal Wrap Automatic Restore" 登錄參數為 1 將造成 下列修復步驟自動修復錯誤狀態。
    [1] 在 5 分鐘內會執行第一次輪詢,並從複本組上刪除這台電腦。 如果您不想等候 5 分鐘,可以先執行 "net stop ntfrs",再執行  "net start ntfrs",以重新啟動檔案複寫服務。
    [2] 刪除這台電腦之後,後續的輪詢會將它重新加入複本組。 重新加入的動作會觸發整個複本組樹狀目錄的同步處理。
    警告: 在修復過程中,複本樹狀目錄中的資料可能無法使用。如果這 個錯誤繼續發生,您應該將上述的登錄參數重設為 0,以避免自動修復 意外地將資料變成無法使用。
    如果要變更這個登錄參數,請執行 regedit。
    請按 [開始] 功能表、[執行],然後輸入 regedit。
    展開 HKEY_LOCAL_MACHINE。
    請按機碼路徑:
       "System\CurrentControlSet\Services\NtFrs\Parameters"
    請在下列值名稱上按兩下:
       "Enable Journal Wrap Automatic Restore"
    並更新值。
    如果值名稱不存在,您可以使用 [編輯] 功能表 New->DWORD 值的功能來新增它。 請輸入如上所顯示的正確值名稱。
    請在 http://go.microsoft.com/fwlink/events.asp 查看說明及支援中心,以取得其他資訊。
    解決方法

    建議您根據以下完成非授權還原連線

    1. Stop FRS.

    2. Start Registry Editor (Regedt32.exe).

    3. Locate and click the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore/Process at Startup

    4. On the Edit menu, click Add Value , and then add the following registry value: Value name: BurFlags Data type: REG_DWORD Radix: Hexadecimal Value data: D2

    5. Quit Registry Editor.

    6. Restart FRS.

    參考資料

    Troubleshooting FRS Event 13568

    http://technet.microsoft.com/en-us/library/bb727056.aspx#EFAA

    Troubleshooting journal_wrap errors on Sysvol and DFS replica sets

    http://support.microsoft.com/kb/292438/en-us

  • Hyper-V - 如何使用 WSB 備份 VM? (How to use WSB to backup Hyper-V VM files)

    REGISTER HYPER-V WITH WSB VSS

    ===================================

    Hyper-V does not automatically register its VSS writer for use with WSB. You must manually add the registry key and value.

    Please run the following two commands in DOS prompt to register Hyper-V VSS writer for use with WSB

    reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WindowsServerBackup\Application Support\{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}"

    reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WindowsServerBackup\Application Support\{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}" /v "Application Identifier" /t REG_SZ /d Hyper-V

    BACKUP STEPS

    ===================================

    1. Go to Start | Administrative Tools | Windows Server Backup.

    2. If backing up a remote host, choose Connect to Another Computer and type in the Hyper-V host.

    3. Choose either Backup Once or Backup Schedule.

    4. Select Backup configuration - Full server or Custom.

    5. Choose the location to store the backup.

    6. Choose either VSS Full or Copy Backup. For host-based backups where no other backups are occurring with the VMs, choose VSS full backup.

    7. Once you have confirmed the details, select Backup.

    Note:

    - You must back up all volumes related to a VM, including Virtual Hard Disks (VHDs), VM configuration files, and snapshots.

    - If you are creating a Backup Schedule, you must use a dedicated local volume that will be formatted and used exclusively by WSB. In contrast, if you are performing a Backup Once job, you can store the backup on a non-dedicated local volume, a removable device, or a network share.

    - If the Integration Components are not installed within the VM being backed up, WSB will save the state of the running VM in order to ensure backup data consistency.

    - Once completed, the backup set is portable and can be used with any Hyper-V host.

    RESTORE STEPS

    ===================================

    WSB does not use VSS when restore individual files, therefore you need to restore the entire volume(s) for running VMs.

    1. Go to Start | Administrative Tools | Windows Server Backup

    2. In the Actions Pane, select Recover.

    3. Choose the server from which to recover data (the one where the WSB backup data is located)

    4. Choose the date from which to restore the data.

    5. Now you can select the recovery type.

    A. Restore Entire Volume(s)

    If you need the entire VM, including its configuration, snapshots, and virtual disks (in the event of a complete host failure, for example), select Application Restore and then Hyper-V

    In this case, you do not have the option to restore individual files. You will have to restore everything included in that backup set. Note that this will not overwrite existing Hyper-V and VM configuration data that has changed since the backup.

    B. Restore Individual Files

    If you need only the VHD itself and the configuration data and snapshots for the VM are healthy, you can select Files and folders and pick the individual VHD file you need.

    Note that this process does not use the VSS writer; the VM should have been backed up with with its state saved first.

    C. Restore Hyper-V Host

    If you've suffered total system and data loss and need to recover the Hyper-V host itself, including the Windows Server 2008 operating system and all the VMs running therein, you must boot to the Windows Recovery Environment and perform your restore from there. This can be done from the Windows Server 2008 setup disk or a pre-configured disk partition.

    NOTE

    ===================================

    1. Virtual machines that contain dynamic disks in the guest operating system cannot be backed up using VSS. Only offline backups are supported. The other alternative is to backup the virtual machine using backup software inside the guest operating system as you would with a physical machine.

    2. Virtual machines that do not have support for VSS Backups, such as Windows 2000, Windows XP, or virtual machines without Integration Services installed, will enter a saved state while the snapshot is taken and restore once the snapshot is complete.  You will also experience the same behavior if the backup component from Hyper-V Integration Services is disabled.

    3. When performing a recovery from backup, the entire volume(s) must be restored for running VMs.  Individual (running) VM restores are not supported with Windows Server Backup.

    參考知識文件:

    How to enable Windows Server Backup support for the Hyper-V VSS Writer http://blogs.technet.com/askcore/archive/2008/08/20/how-to-enable-windows-server-backup-support-for-the-hyper-v-vss-writer.aspx

    Backup and Disaster Recovery for Server Virtualization http://technet.microsoft.com/en-us/magazine/cc895627.aspx

  • Network Connections missing

    Verify the Registry entry for the service is intact for Network Connection Service

    (HKLM\SYSTEM\CCS\SERVICES\NETMAN)
    clip_image002

    If the Key is missing, export the full key from another machine merge it with problem machine

    In command prompt Type the following "regsvr32 netman.dll"

    Reboot the machine

  • SCOM 2007 RMS server having critical health state due to SQL Broker

    CAUSE:
    ======

    SQL Broker was not enabled on the Operations Manager database

    Resolution:
    ==========

    The SQL Server Broker Service can be checked with the following query.

    ========================================================

    Open SQL Management Studio the select New Query

    Type: SELECT is_broker_enabled FROM sys.databases WHERE name ='OperationsManager'

    Execute the query.

    If the results return a 0 then the Broker Service is disabled.

    To enable the service execute the following:

    1. Stop all of the Ops Manager services on the RMS and other management servers.

    ***Note**** if you don't stop the services before you run the query it executes forever (hangs).

    2. Re-enable the broker

    ALTER DATABASE OperationsManager SET ENABLE_BROKER

    3. Restart the Ops Manager services.

    Now run the original query again and you should see a 1 telling you the service is enabled.