Wednesday, September 18, 2019

Install IE and flash in Windows server 2016

Find the link below on how to reinstall IE in Windows 2012 server.

To install only IE in Windows Server 2016, just run the command below and reboot.  

dism /online /enable-feature:"Internet-Explorer-Optional-amd64"

If you need to enable flash for IE, you can run the command below.  

dism /online /add-package /packagepath:"C:\Windows\servicing\Packages\Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum"

Monday, September 9, 2019

iDRAC version 8 virtual console only works with IE

I have no trouble accessing iDRAC v8 GUI using IE 11, Chrome and Firefox.  It is a R630 server.  However, I found out I can only access Virtual Console using IE 11.  Chrome v76 and Firefox v67 won't work for Virtual Console.

I guess try to use other browser if you cannot access Virtual Console.


Sunday, September 8, 2019

AppSync with VMAX 40k

AppSync 3.5 was installed couple years ago to protect our SQL application.  Basically, AppSync agent was installed in SQL cluster.  The SQL clusters were running as VMs and the databases were residing in RDM.

Kept getting VSS error that it takes more than 10s to create VSS.  That was what MS supported for VSS.  If it took more than 10s, the VSS creation step would fail.

Installed latest Solution Enabler 8.4.x.x available at the time and no change.  Since the array was VMAX 40k, DNS was not a factor.  Eventually, version Version 3.5.0.1_URM00111091_PRELIM_R2  fix the bug VSS 10s delay bug with VMAX 40k.

Couple things I don't like about the AppSync.
1)  Mounting and Dismounting SQL VMFS takes long time and does not work well.
2)  Need to reserve an extra copy of luns in the pool   
3)  If info is not sync, AppSync does not know what to do.  So, manually dismount copy from mount host will cause problem because AppSync does not know the luns are dismount.  Eventually, contacting support to clean up is required.

------------------------------------------------------------------------------------------------------------

Now, 3 yrs later, AppSync 3.9 was setup for proof of concept few months ago.  This time, we have SQL running in VMFS.  We encounter same issue as before.  Mounting copy to mount host is very slow and timeout.  Eventually, we keep our design for SQL as before in RDM.  Things are working smoothly with RDM as expected.   

We are still using the AppSync 3.5 now until we migrate to AppSync 3.9 next yr.  Recently, SQL team change the DB structures and instead of a few larger database, we have a lot of smaller database to be protected.  The AppSync host plugin service has memory leak problem.  So, we have to setup a process to bounce the service once every 3 days.  Hopefully, this won't happen in version 3.9.

Thursday, August 29, 2019

DCNM version 11.1(1) and bug ID CSCvf99665

Recently build a new DCNM 11.1(1) box in Windows 2016 to replace the existing 7.2(3) because the old one is running Windows 2008 R2.  Major difference is HTML5 and the webclient is a lot faster and most of the work even port channel can be completed in the GUI (I have not tried that yet).  If you don't like to use the new webclient to complete your zoning, you can still use the old FM. 

Besides, I use the Oracle Express for the db of DCNM since very 7.2.  The performance is better than the POSTGRESQL.  

You can follow the Oracle link below to have some basic knowledge of Oracle Express.

If you use SolarWind as your TFTP server, make sure .NetFramework 3.5 is required.  See link below on how to enable it in Windows 2016 server.

After new DCNM server is in production, I plan for the firmware update on all the FC switches in the fabric.  However, I find out both of the MDS9710 are affected by Cisco bug ID CSCvf99665

It show an invalid IPV6 IP address in the mgmt/0 interface and has a zero length subnet mask.

Example:
::148.237.143.255/0

Suggestion from support
(1)Open a case and get Cisco TAC to send you a DPLUG file that will be downloaded and run on the switch.  We would run the DPLUG, do a 'copy r s' to save the configuration, then do a 'system switchover' and run 'copy r s' again.

(2)Upgrade to 8.1(1a).  After the upgrade has completed, do a 'copy r s',  do a 'system switchover' and after both supervisors are back up, then do another 'copy r s'.

On the safe side, we choose the 1st option and have support apply the DPLUG file.  Everything is fine.  Then, we update the firmware to 8.1(1a).  

Sunday, July 24, 2016

Backup Unix raw device with NetWorker

To backup Unix Raw Device in NetWorker, pls follow esg59701 or video in EMC community


Here is the kb article from EMC website.


How can NetWorker be configured to backup a rawdevice?
How to backup a RAW device?
 
Fact
NetWorker for UNIX/Linux 7.x.x
 
Resolution
Create a directive using rawasm. Rawasm used to backup /dev entries (block andcharacter-special files) and their associated raw disk partitiondata. On some systems, /dev entries are actually symboliclinks to device specific names. Unlike other ASMs, this ASM followssymlinks, allowing the shorter /dev name to be configured.
  1. Open NMC.
  2. Go to the Configuration > Directives.
  3. Right Click > new.
  4. In the Name field enter Raw.
  5. In the directives field enter the directive in the following format:
    <
>
+rawasm: partition1
+rawasm: partition2
Click on Apply.
  • Close this window and go to the Clients menu and select Client Setup. 
  • Select the client with the raw devices. 
  • In the Saveset field specify:
    /dev/partition1
    /dev/partition2 
  • In the Directive field select Raw. 
  • Click on Apply.

  • Note:
     
    Precautions when using rawasm to back up UNIX raw partitions:
    One can specify the rawasm directive to back up raw disk partitions on UNIX.
    However, if the raw partition contains data managed by an active database management system (DBMS), ensure that the partition is offline and the database manager is shutdown. For greater flexibility when backing up partitions that contain data managed by a DBMS, use a NetWorker Module application.
    Similarly, if rawasm is used to save a partition containing a UNIX file system, the file system must be unmounted or mounted read-only to obtain a consistent backup.
     
    Note: Do not specify the rawasm directive to backup or recover raw partitions on Windows. See    Backing up raw partitions on Windows on page 88 provides more information.

    Using rawasm to recover a UNIX raw partition
    When recovering data, rawasm requires that the file system node for the raw device exist prior to the recovery. This protects against the recovery of a /dev entry and the overwriting of data on a reconfigured disk. You can create the /dev entry, having it refer to a different raw partition, and enforce overwrite if needed. If you create the /dev entry as a symbolic link, the data is recovered to the target of the symbolic link.
     
    Recovery of a raw partition must occur on a system configured with the same disk environment and same size partitions as the system that performed the backup:
    • If the new partition is smaller than the original partition, the recovery will not complete successfully
    • If the new partition is larger than the original partition the estimated size reported upon recovery is not accurate
    Note: Only level FULL is supported with rawasm, this is because the original NetWorker traditional backup codes are designed for Filesystem level Backup, and not Block Level backup. 



    ESX host does not discover new path after migrating to new fabric

    Once, I work on fabric migration.  They want to migrate to new equipment and choose not to link the existing and new switch together (no ISL) to have a clean config in new fabric.  The servers connect to different fabric A and B.  On each migration, we need to re-connect storage controller on one fabric and the servers that are connecting the controller to new fabric at the same time.  Only one fabric and one controller will be worked on each time.  Since they are all ESX hosts and no AIX, it is much easier. We complete the job in the weekend during low I/O period.  What happens is after connecting to the new switch, it does not see the new path even VI team rescan.  I did confirm zoning had been completed correctly on the new fabric.  They suggest me to follow VM article Configuring fibre switch so that ESX Server doesn't require a reboot after a zone set change


    However, I know RSCN is enabled in the Cisco switch.  Eventually, VI agree to vMotion the VMs in the host, and reboot the ESX host, one by one.  After that, they are discovered correctly. 


    One thing we learn, stay away from boot from SAN for ESX host, it takes 30 min for each host to come up after reboot even there are not a lot of luns in the ESX clusters.  It is proven much faster to boot ESX from local disk. 


    Also, minimize the number of RDMs!!!  I work in another messy environment with lots of RDM.  Even rescan cannot happen during business hours. 
     

    Sunday, April 19, 2015

    Installing Bodhi Linux on Lenovo T400

    Used to run Centos on my T400.  Just want to rebuild the laptop with Bodhi Linux.  Try to install Bodhi Linux 2.3, 2.4 and 2.5 but the CD only boots to command line for some reason.  Suspect it is the ATI card.  Some people have success with 32 bits.  However, I am only interest in 64 bits.  So, I try the new 3.0 and it works fine.  Boot up the machine with the Live CD first and start the Bodhi Linux Installation.

    Hardware
    This is a 5 yrs old laptop without SD card reader, webcam and bluetooth.  Only have builtin WiFi.  All hardware are detected correctly.  Wireless work fine however, I don't see a list of access point.  To correct that, I found this link.  It works after I complete step 3.

    1. turn on wireless switch
    2. in a terminal windows execute the below command sudo rfkill unblock wifi
    3. reboot
    VMware Workstation 9 installation
    After the installation, I add the following packages before installing VMware Workstation 9.
    sudo apt-get install build-essential linux-headers-`uname -r`

    Download VMware Workstation 9 and copy to my home folder.  Then, follows steps below to complete the installation.

    chmod +x VMware-Workstation-Full-9.0.4-1945795.x86_64.bundle
    sudo ./VMware-Workstation-Full-9.0.4-1945795.x86_64.bundle

    Now, goto /usr/bin and start vmware with "vmware &"

    However, you will see vmware failed to build the vmnet.  Search google and see it happens with VMware 10 on Ubuntu.

    Download the patch in VMware Community (see post  https://communities.vmware.com/message/2327060.  I download the patch upload by WoodyZ).

    cd /usr/lib/vmware/modules/source
    tar -xvf vmnet.tar
    patch vmnet-only/filter.c < ~/ws1001.vmnet.filter.c.313.patch
    tar -uvf vmnet.tar vmnet-only
    rm -r vmnet-only
    /usr/bin/vmware&

    Installation completes successfully.

    Java Installation
    All the hardware are detected and work fine.  Run the speaker-test to confirm sound card is working fine.  I plan to try the lightweight browser Midori.

    To install Java, I run the following command.
    sudo apt-get install default-jre  (java 1.7 is installed)
    sudo apt-get install icedtea-plugin  (version 1.5 is installed as of today.  From Midori FAQicedtea6 version 1.8 and above has been known to crash midori)

    Flash Installation
    sudo apt-get install flashplugin-installer

    Gdebi installation
    sudo apt-get install gdebi

    Foxit Reader installation
    Foxit Reader is used to open Adobe document.  Download a copy and use Gdebi to install it.
    sudo gdebi FoxitReader.deb

    Office suite installation
    Go to AppCenter and select the office you want to install.

    VideoLAN installation
    The last version I know that will work with rm file is 1.05.  After that, playing rm file with videolan will crash intermittently.  Not sure if it is fixed in version 2.  Find a 1.0.5 deb package but fail to install with dependency issue.  Eventually, install what's available in appcenter.

    Disable auto-login
    To disable auto-login, open up /etc/lightdm/lightdm.conf with epad and comment out the line
    #autologin-user=username

    DIA installation
    sudo apt-get install dia
     

    Friday, April 3, 2015

    Moving quorum to another node for Windows 2008 and 2012

    Work on a SAN migration and need to move the quorum to the other node.  For Windows 2008, I find the post Windows Cluster: Moving Quorum Disk to Another Node 

    To move it other node we have run below command.

    cluster group "Cluster Group" /move 

    In you have more nodes in your cluster and to move the 'cluster group' to a specific group use the below command.

    cluster group "Cluster Group" /moveto:node5

    For Windows 2012, actually, for some reason, the above command does not work.  Instead, I open to Failover Cluster Manager.  Right click on the initial cluster that was created when creating the cluster.  Select More Actions, Move core Cluster Resources and Select Node.  Now, you can failover the quorum to the other node.  



    Saturday, March 21, 2015

    VADP with NetWorker 7.6.x

    I have talked about VADP with hotadd in previous posts.  Last month, I have completed testing on VADP with NetWorker 7.6.2.7.  Turn out I should upgrade to NetWorker 7.6.3.7 because of the following two issue.

    NW138379 - VADP : Save does not honor the VSS:*=off flag in Windows 2008
    This issue is seen if you proxy host is Windows 2008.

    Event 16, source: volsnap, Logged: 1/17/2012 6:25:51 PM
    The shadow copies of volume E: were aborted because volume, which contains shadow copy storage for this shadow copy, was force dismounted

    Another anonying issue is NW139877 - VADP: nsrvadp_save incorrectly reports status as success for aborted backups

    I have not tried NetWorker 7.6.4.  However, I have not encountered those issues after upgrading to NetWorker 7.6.3.7.

    Whether virtual or physical proxy, you can consult the following page Nuts and bolts in NetBackup for VMware: Transport methods and TCP ports to decide which transport mode you plan to use.  I don't prefer SAN mode even though it is the fastest option.  Presenting a VMFS lun to a Windows 2008 proxy is not an option in some sites.  If you want to use SAN mode, make sure to control who can login to the proxy.  You don't want Windows signature written to a VMFS lun by mistake. 





    Monday, January 5, 2015

    NetWorker Block Based Backup failed

    There is a new feature introduced in NetWorker 8.x called Block Based Backup.  It is completely rewritten.  So, it is not the same as SnapImage.  It supports Block Based Backup for Windows machine.  For some reason, backup is only successful with Full level backup.  I attempt to start synthetic full backup but it fails.  This is the first client we attempt to use Synthetic full.  We are trying to backup a drive with size of few TB.  Block Based Backup will save the backup time.  We make sure the OS is supported, and BBB is sent to the same media only.  Also, we have weekly full and rest of them are synthetic full.

    Eventually, my colleague works with DataDomain and NetWorker support and confirm it is required to enable synthetic backup on DataDomain.  Just login to DataDomain and run the command below.

    ddboost option set virtual-synthetics enabled

    run the following command to ensure virtual-synthetics is enabled.

    ddboost option show