Just upgrade my laptop to Windows 7 and my BenQ scanner no longer works. Since BenQ no longer provides drivers update to the scanner, I am stuck. Try to install the XP drivers in XP mode but it still fails to detect the scanner. Search Google for a couple of hours and finally find this link with the drivers that work.
http://www.eightforums.com/drivers-hardware/16245-old-acer-benq-scanner-drivers-x84-x64.html
Download the driver. Just use driver update from device manager and it works. However, I prefer the XP scan GUI.
Saturday, September 28, 2013
Thursday, September 12, 2013
Turn off time sync in virtual machine
Recently, I got a request to recover the gst database of NetWorker to retreive some historical backup stats because retention for stats was set too short. To avoid interfering the production environment, I close the gstd saveset out with FTD as clone device. Build a Windows 2003 VM on my laptop with same version of NetWorker. Because retention for stats was too short. As soon as I recovered the gstd database and started gst service, those expired records would be purged. Only option is to change the system time of VM to an earlier date within the retention period. To achieve that, I follow VMware kb1189 to disable the time sync with host.
Since I am using VMware Workstation, I choose to edit the vmx file. For vSphere, you can add parameters following the kb1189.
Add configuration options in the virtual machine's .vmx file:
Open the virtual machine's configuration file (
Since I am using VMware Workstation, I choose to edit the vmx file. For vSphere, you can add parameters following the kb1189.
Add configuration options in the virtual machine's .vmx file:
Open the virtual machine's configuration file (
/vmfs/volumes/datastore_name/vm_name/vm_name.vmx) using a text editor.- Set these options to zero. If the entries do not exist, add them.
Note: 0 = disabled, 1 = enabled.tools.syncTime = "0"
time.synchronize.continue = "0"
time.synchronize.restore = "0"
time.synchronize.resume.disk = "0"
time.synchronize.shrink = "0"
time.synchronize.tools.startup = "0"
time.synchronize.tools.enable = "0"
time.synchronize.resume.host = "0"
Note: In GSX, VMware Fusion, and VMware Workstation, you must use"FALSE"instead of"0". For example:tools.syncTime = "FALSE"
time.synchronize.continue = "FALSE"
time.synchronize.restore = "FALSE"
time.synchronize.resume.disk = "FALSE"
time.synchronize.shrink = "FALSE"
time.synchronize.tools.startup = "FALSE"
time.synchronize.tools.enable = "FALSE"
time.synchronize.resume.host = "FALSE"
Sunday, August 25, 2013
Add new shelf on DD880
Just add the last ES30 shelf with 2TB disks. You can simplily find the instructions on DataDomain Document ID 72323. The DD880 was setup with 5 ES20 shelves of 2TB disks. So, we can only add one more ES30 shelf of 2TB. Because you cannot mix ES30 with ES20 on the same loop, I arrange downtime to power down the DD880 before moving the ES20 to free up one loop. That free loop is for the newly purchase ES30.
For DDOS 5.1, you do need a shelf license and a Expanded Storage license. Make sure you get your topology first before adding. I will email a copy of autosupport to myself first. On ES20, you do see the word host on the host port. On ES30, they use diamond to represent ext port and circle represent host port.
For DDOS 5.1, you do need a shelf license and a Expanded Storage license. Make sure you get your topology first before adding. I will email a copy of autosupport to myself first. On ES20, you do see the word host on the host port. On ES30, they use diamond to represent ext port and circle represent host port.
Saturday, August 24, 2013
EVA4400 Array Based Management Module
Recently, I was working on a move of EVA4400. It is similar to the EVA4000 I worked before. However, it comes with a management module. Read through the manual, and it is an option to save money to have a management server to manage EVA4400. Keep in mind though. If you need to use EVAperf to collect performance stats, you still need to set up a management server with FC connection to EVA4400. EVAperf is not installed with management module.
Here is the instructions to collect logs using the Array Based Management Module. You can find the full detail instructions from HP website.
1) logon to the Array Management Module through web browser (https://ip:2732 to access CommandView).
2) Click the Cell name under Storage Systems on the left.
3) Click Server Options.
4) Click Capture system information.
5) The minimum for EVA4400 diagnosis of operational issues is as follows:
Controller Termination Events, Controller Events, Controller Configuration Dump
6) If you have a more complex issue involving Command View objects and the use or interaction of the ABM Command View to the EVA4400, you may be requested to collect all entries.
7) Click Capture selected information .
8) Click the Save button, then the OK button to return to management of Command View.
To change ip of Array Based Management Module (You can find the steps in EVA4400 User Guide)
1) browse to https://ip:2373 and login using account with administrator rights
2) Select Administrator Options > Configure Network Options.
3) Enter an IP address and other network settings that apply.
NOTE: The management module firmware reserves IP addresses for internal communications.
If you are using HP Command View EVA 9.2 or earlier, the reserved IP addresses are 10.0.0.1
through 10.0.0.3. Later versions of the management module firmware will also use these
addresses if the array has older controller firmware loaded. The latest versions of controller
and management module firmware, however, use the reserved IP address range from
10.253.251.230 through 10.253.251.249. The management module cannot be configured
to use these addresses, nor can it communicate with external systems that fall within the reserved
address range (for example, web client, router, DNS server, and so on).
4) Click Save Changes.
To test email notification
1) Login to https://ip:2372 and click Server Options.
2) Open Email Notification Server Options and confirm email notification is setup with smtp info entered.
3) Expand Disk Group from the left and click on your Disk Group (I have only one disk group setup)
4) Change the warning and critical level to lower % say 5% and click "Save Change" (learn this from HP forum)
5) Wait for a few minute and you should receive the notification email.
Here is the instructions to collect logs using the Array Based Management Module. You can find the full detail instructions from HP website.
1) logon to the Array Management Module through web browser (https://ip:2732 to access CommandView).
2) Click the Cell name under Storage Systems on the left.
3) Click Server Options.
4) Click Capture system information.
5) The minimum for EVA4400 diagnosis of operational issues is as follows:
Controller Termination Events, Controller Events, Controller Configuration Dump
6) If you have a more complex issue involving Command View objects and the use or interaction of the ABM Command View to the EVA4400, you may be requested to collect all entries.
7) Click Capture selected information .
8) Click the Save button, then the OK button to return to management of Command View.
To change ip of Array Based Management Module (You can find the steps in EVA4400 User Guide)
1) browse to https://ip:2373 and login using account with administrator rights
2) Select Administrator Options > Configure Network Options.
3) Enter an IP address and other network settings that apply.
NOTE: The management module firmware reserves IP addresses for internal communications.
If you are using HP Command View EVA 9.2 or earlier, the reserved IP addresses are 10.0.0.1
through 10.0.0.3. Later versions of the management module firmware will also use these
addresses if the array has older controller firmware loaded. The latest versions of controller
and management module firmware, however, use the reserved IP address range from
10.253.251.230 through 10.253.251.249. The management module cannot be configured
to use these addresses, nor can it communicate with external systems that fall within the reserved
address range (for example, web client, router, DNS server, and so on).
4) Click Save Changes.
To test email notification
1) Login to https://ip:2372 and click Server Options.
2) Open Email Notification Server Options and confirm email notification is setup with smtp info entered.
3) Expand Disk Group from the left and click on your Disk Group (I have only one disk group setup)
4) Change the warning and critical level to lower % say 5% and click "Save Change" (learn this from HP forum)
5) Wait for a few minute and you should receive the notification email.
Sunday, August 11, 2013
Do not start NetWorker automatically after successful installation
For some reason, if you don't want NetWorker start automatically after successful installation, you can run the command below with setup.exe.
setup /vSTARTSVC=0
There should be a kb in powerlink if you are interested.
PS: Please refer to installation guide for more option used with the command line installation. (7/13/14)
setup /vSTARTSVC=0
There should be a kb in powerlink if you are interested.
PS: Please refer to installation guide for more option used with the command line installation. (7/13/14)
Sunday, May 12, 2013
Scrubbing Your NetApp Disk
I was asked about how to scrub NetApp disk. Find the following video in the internet.
Scrubbing Your NetApp Disk
Scrubbing Your NetApp Disk
Saturday, May 11, 2013
Apply Microsoft fix 2748349 on all Windows backup clients
Other than applying Microsoft patch 940349 on all Windows 2003 server, there is a new patch now for all VSS backup on Windows client - 2748349. This is required on all VSS backup. Here are the symption and the prerequisites described in the Microsoft kb 2748349 (please review Microsoft kb for all the details). Basically, this applies to all backup application using VSS.
Assume that you have a computer that is running Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2. You use a backup application that uses the Windows Volume Shadow Copy feature to create snapshots and read files from the snapshots. In this situation, one or more corrupted files are found in the snapshots.
Notes
Assume that you have a computer that is running Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2. You use a backup application that uses the Windows Volume Shadow Copy feature to create snapshots and read files from the snapshots. In this situation, one or more corrupted files are found in the snapshots.
Notes
- The corrupted files can be backed up by using the backup application. The corrupted files can only be noticed during a restore process.
- The backup data of any third-party back up application can be affected. For example, NTBackup, Windows Server Backup, System Center Data Protection Manager (DPM) can be affected. Please contact your third-party backup solution manufacturer to determine whether they use the Windows Volume Shadow Copy feature to create backups.
Prerequisites
To apply this update, you must be running one of the following operation systems:- Windows Server 2003 Service Pack 2 (SP2)
- Windows Vista Service Pack 2 (SP2)
- Windows Server 2008 Service Pack 2 (SP2)
- Windows 7
- Windows Server 2008 R2
Sunday, December 2, 2012
VSS snapshot is not cleaned up by NetWorker NMM
I have an issue on one of the Windows 2008 client running Sharepoint 2010. I have to manually stop the backup from NMC. However, I find out nsrsnap_vss_save is still running on the client. So I manually stop all Networker service on the client. However, the VSS snapshot is still there. I have tried vssadmin to delete shadow but I receive an error the snapshot will not be deleted. If you run vssadmin list shadows, you can still see the snapshots (borrow output from esg110691)
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Contents of shadow copy set ID: {5bce2dd1-b18c-49d1-bb1a-51f656d07794}
Contained 5 shadow copies at creation time: 12/20/2009 11:01:01 PM
Shadow Copy ID: {a8019c4f-7dc1-4717-ac1f-affe759a1ea4}
Original Volume: (C:)\\?\Volume{264f5213-8311-11dc-82da-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Originating Machine: w2k3.acme.com
Service Machine: w2k3.acme.com
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ApplicationRollback
Attributes: Persistent, No auto release, Differential, Exposed locally
Shadow Copy ID: {4d5c74fe-7683-4ad8-8cba-cbeaff1adb92}
Original Volume: (D:)\\?\Volume{4efae4e1-834a-11dc-99fe-001a64242e28}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy17
Originating Machine: w2k3.acme.com
Service Machine: w2k3.acme.com
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ApplicationRollback
Attributes: Persistent, No auto release, Differential, Exposed locally
So I contact EMC support and they recommend to try the following three method.
Method 1:
a, if nsrsnap_vss_save.exe is still running in the client while no scheduled backups are running from NetWorker Server, kill that process and it should kill all the subsequent processes.
b, After that please start another NMM scheduled backup, it is supposed to clean up the mess it left behind last time. (This does not happen successfully a number of times).
If method 1 does not work, please kindly try method 2.
Method2：
you can use the following two commands to delete the shadows and the mount points.
vssadmin list shadows
mountvol
These two commands should help you find out what shadows copies are left behind on the system and how these are mounted. Try to unmounts them first using mountvol /D.
/D Removes the volume mount point from the specified directory.
And then use:
vssadmin delete shadows all
That should clean up the rest of the mess manually.
If method 2 does not work, please kindly try method 3.
Method3：
please kindly download VSS SDK from Microsoft:
http://www.microsoft.com/en-us/download/details.aspx?id=23490. and use that instead to get rid of the existing snapshots.
Obviously, I have tried first one. For the 2nd method, I carefully examined the vssadmin list shadows output and made sure I choose the correct one to umount. If you pick a data volume by mistake, you can umount a volume in use and cause data unavailable. However, it still failed.
I didn't go any further since I needed approval from server owner to install the the VSS SDK mentioned in method 3. I decide to go for google and find out the command to remove snapshot in Windows 2008 is different (my mistake not to tell support the OS version). I find the instructions from Doug's blog.
I just ran diskshadow then "delete shadows all". Now, the stuck snapshots are removed. After that, restarted the backup from NMC and go back to sleep.
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Contents of shadow copy set ID: {5bce2dd1-b18c-49d1-bb1a-51f656d07794}
Contained 5 shadow copies at creation time: 12/20/2009 11:01:01 PM
Shadow Copy ID: {a8019c4f-7dc1-4717-ac1f-affe759a1ea4}
Original Volume: (C:)\\?\Volume{264f5213-8311-11dc-82da-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Originating Machine: w2k3.acme.com
Service Machine: w2k3.acme.com
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ApplicationRollback
Attributes: Persistent, No auto release, Differential, Exposed locally
Shadow Copy ID: {4d5c74fe-7683-4ad8-8cba-cbeaff1adb92}
Original Volume: (D:)\\?\Volume{4efae4e1-834a-11dc-99fe-001a64242e28}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy17
Originating Machine: w2k3.acme.com
Service Machine: w2k3.acme.com
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ApplicationRollback
Attributes: Persistent, No auto release, Differential, Exposed locally
So I contact EMC support and they recommend to try the following three method.
Method 1:
a, if nsrsnap_vss_save.exe is still running in the client while no scheduled backups are running from NetWorker Server, kill that process and it should kill all the subsequent processes.
b, After that please start another NMM scheduled backup, it is supposed to clean up the mess it left behind last time. (This does not happen successfully a number of times).
If method 1 does not work, please kindly try method 2.
Method2：
you can use the following two commands to delete the shadows and the mount points.
vssadmin list shadows
mountvol
These two commands should help you find out what shadows copies are left behind on the system and how these are mounted. Try to unmounts them first using mountvol /D.
/D Removes the volume mount point from the specified directory.
And then use:
vssadmin delete shadows all
That should clean up the rest of the mess manually.
If method 2 does not work, please kindly try method 3.
Method3：
please kindly download VSS SDK from Microsoft:
http://www.microsoft.com/en-us/download/details.aspx?id=23490. and use that instead to get rid of the existing snapshots.
Obviously, I have tried first one. For the 2nd method, I carefully examined the vssadmin list shadows output and made sure I choose the correct one to umount. If you pick a data volume by mistake, you can umount a volume in use and cause data unavailable. However, it still failed.
I didn't go any further since I needed approval from server owner to install the the VSS SDK mentioned in method 3. I decide to go for google and find out the command to remove snapshot in Windows 2008 is different (my mistake not to tell support the OS version). I find the instructions from Doug's blog.
I just ran diskshadow then "delete shadows all". Now, the stuck snapshots are removed. After that, restarted the backup from NMC and go back to sleep.
Saturday, November 17, 2012
Manually uninstall NetWorker in Windows
I try to upgrade NetWorker on one of the Windows client and find out NetWorker is no longer in Add / Remove Program. If I try to upgrade, it will complain an existing version exist. Do a bit google search and find the following article in EMC community on how to uninstall NetWorker manually in Windows.
Remove the Upgrade Code from the following registry keys:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Upgrade Codes
HKCR\Installer\UpgradeCodes
Windows Installer uses a GUID (Global Unique Identifier) to uniquely identify products being installed. They call it an Upgrade Code. This is used to identify that NetWorker is installed on this machine.
NetWorker has three upgrade codes (the first for NW 6.0, the second for all other NW versions (except X64), the third for the X64 package):
3EB2C626C9BC4D118811000972CCA7DF
2827A1B508153D114831000A9C877BD1
1D09C7743451200439D99949BD5A9F1E
It may also be necessary to remove the NetWorker services from the registry. They are located in:
-HKLM\SYSTEM\CurrentControlSet\Services
-Delete the following keys: nsrd, nsrexecd, nsrpm, hagentd, lgtolmd
-For NMC, the key to look for is: gstd
-After removing the services, reboot the machine.
Also run the below commands on the command prompt before you reboot the machine
sc delete nsrexecd
sc delete nsrd
All installed products have an entry in the following registry key:
-HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
-Control Panel Add/Remove programs gets its information from this key.
-If an entry under this key is deleted, it will not be displayed in Add/Remove Programs.
The above steps work for me. The version of NetWorker on my box is 7.6.1. You may need to delete the following key.
HKLM\Software\Legato\NetWorker
To manually remove the old binary. Be very careful if it is a NetWorker server.
If it is a NetWorker server running on Windows, NEVER delete res and mm folders (that's where the NetWorker config and media database located). I normally keep the logs folder too. I believe the dedupe folder contain the cache info for Avamar.
Again, backup your registry keys before making changes to your registry.
Remove the Upgrade Code from the following registry keys:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Upgrade Codes
HKCR\Installer\UpgradeCodes
Windows Installer uses a GUID (Global Unique Identifier) to uniquely identify products being installed. They call it an Upgrade Code. This is used to identify that NetWorker is installed on this machine.
NetWorker has three upgrade codes (the first for NW 6.0, the second for all other NW versions (except X64), the third for the X64 package):
3EB2C626C9BC4D118811000972CCA7DF
2827A1B508153D114831000A9C877BD1
1D09C7743451200439D99949BD5A9F1E
It may also be necessary to remove the NetWorker services from the registry. They are located in:
-HKLM\SYSTEM\CurrentControlSet\Services
-Delete the following keys: nsrd, nsrexecd, nsrpm, hagentd, lgtolmd
-For NMC, the key to look for is: gstd
-After removing the services, reboot the machine.
Also run the below commands on the command prompt before you reboot the machine
sc delete nsrexecd
sc delete nsrd
All installed products have an entry in the following registry key:
-HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
-Control Panel Add/Remove programs gets its information from this key.
-If an entry under this key is deleted, it will not be displayed in Add/Remove Programs.
The above steps work for me. The version of NetWorker on my box is 7.6.1. You may need to delete the following key.
HKLM\Software\Legato\NetWorker
To manually remove the old binary. Be very careful if it is a NetWorker server.
If it is a NetWorker server running on Windows, NEVER delete res and mm folders (that's where the NetWorker config and media database located). I normally keep the logs folder too. I believe the dedupe folder contain the cache info for Avamar.
Again, backup your registry keys before making changes to your registry.
Wednesday, November 7, 2012
HP Advisory on 10G NC522SFP with connectivity issue
Recently, one of the servers with 10G NIC starts to show the following error message.
DEVICE: HP NC522SFP Dual Port 10GbE Server Adapter #2
PROBLEM: Tx path is hung. The device is being reset.
ACTION: Adapter recovers from this error automatically.
Search from the web and see this HP advisory. When I attempt to upgrade the firmware, I get the following error.
"Dependencies Failed -- Driver and firmware set are not allowed for update. Please install driver version 4.3.11.407 prior to performing firmware upgrade on devices with firmware version 4.0.550 or earlier installed. See nxflash.log for further details"
Upgrade to the latest driver and update the firmware. Failed!
Upgrade to driver version 4.3.11.407 and then update the firmware. Failed again!
Call support and they have me redo the same thing again. Testing different firmware version and going nowhere. After 3 hrs of troubleshooting, HP tells me it is a bad NIC. I refuse to get a replacement NIC since the NIC is functioning fine. So, I arrange another downtime and use my a spare 10G NIC. I still have the same issue. Eventually, we put the driver back to 4.3.11.407. After that, they escalate to next level. Suggestion is to use Local Admin account but it is still going nowhere (it is true that even domain admin account will return the same error. You need to login as local admin to complete the firmware upgrade).
Check back on HP site and see firmware version 1.3.9.7 is available. Run the installation and it passes the dependencies check. So, I know it must be dependencies issue on firmware not driver.
The solution is to stay at driver 4.3.11.407 and update firmware to 1.3.9.0. Reboot. Then update firwmare to 1.3.9.6. Reboot. Run the driver update and issue is now resolved. If your NC522SFP firmware is too old, upgrade to firmware 1.3.9.0 first.
DEVICE: HP NC522SFP Dual Port 10GbE Server Adapter #2
PROBLEM: Tx path is hung. The device is being reset.
ACTION: Adapter recovers from this error automatically.
Search from the web and see this HP advisory. When I attempt to upgrade the firmware, I get the following error.
"Dependencies Failed -- Driver and firmware set are not allowed for update. Please install driver version 4.3.11.407 prior to performing firmware upgrade on devices with firmware version 4.0.550 or earlier installed. See nxflash.log for further details"
Upgrade to the latest driver and update the firmware. Failed!
Upgrade to driver version 4.3.11.407 and then update the firmware. Failed again!
Call support and they have me redo the same thing again. Testing different firmware version and going nowhere. After 3 hrs of troubleshooting, HP tells me it is a bad NIC. I refuse to get a replacement NIC since the NIC is functioning fine. So, I arrange another downtime and use my a spare 10G NIC. I still have the same issue. Eventually, we put the driver back to 4.3.11.407. After that, they escalate to next level. Suggestion is to use Local Admin account but it is still going nowhere (it is true that even domain admin account will return the same error. You need to login as local admin to complete the firmware upgrade).
Check back on HP site and see firmware version 1.3.9.7 is available. Run the installation and it passes the dependencies check. So, I know it must be dependencies issue on firmware not driver.
The solution is to stay at driver 4.3.11.407 and update firmware to 1.3.9.0. Reboot. Then update firwmare to 1.3.9.6. Reboot. Run the driver update and issue is now resolved. If your NC522SFP firmware is too old, upgrade to firmware 1.3.9.0 first.
Subscribe to:
Posts (Atom)