Sign up for my weekly newsletter, its short and sweet.

Category : Uncategorized

NDMP SnapSure file system creation fails

I was setting up an NDMP accelerator node today to back up a new VNX and came across this error message when trying to backup a test volume for the first time:

Errors and Exceptions

2013-02-13 11:25:19 avndmp Error : [snapup-/NDMP_Test] NDMP: SnapSure file system creation fails (Log #2) 2013-02-13 11:25:19 avndmp Error :

[ndmp2avtar-/NDMP_Test/] Problem reading 65536 bytes from NDMP stream socket, at stream position 0: code 104: Connection reset by peer (Log #2) 2013-02-13

11:25:34 avtar FATAL : Backup aborted due to earlier errors. No backup created on the server. (Log #1) 2013-02-13 11:25:35 avndmp Error :

[snapup-/NDMP_Test] Backup for target /NDMP_Test had errors. (Log #2)

After I double checked that everything was setup correctly on both the NDMP Accelerator node and on the VNX, I decided to simply create a manual snapshot on the VNX first and see if I would run into trouble. The snapshot completed without an issue. I went ahead and just reran the backup and it ran successfully. I guess the VNX just needed a little manual intervention.

Reference Architecture Design for 5000 Seat Virtual Desktop Infrastructure

Great Citrix XenDesktop, Cisco UCS, and EMC VNX solution overview for deploying 5000 virtual desktops.

Citrix XenDesktop 5.6 Feature Pack Built on Cisco Unified ComputingSystem and EMX VNX

Reference Architecture-Based Design for 5000 Seat Virtual Desktop Infrastructure

Cisco Unified Computing System, Nexus 5500, Nexus 1000V, EMC VNX7500, and VMware ESXi 5

The NEW Internet Explorer

As someone who grew up in the 90’s this is a great commercial for microsoft to introduce the new Internet Explorer. I’m really liking the new look and feel of IE and even though I am a multi browser user I still typically spend most of my time on IE. I think with Microsoft’s lastest release of IE 10 and windows 8 we will start to see a jump in IE users.

browser wars over last 2 years

browser wars over last 2 years

Avamar Backup of a Windows VM fails with the error: Protocol error from VMX

Recently on a new install of Avamar version 6.1; I had a VMware Image based backup fail with error 10007. Upon further investigation of the backup job log I noticed that the snapshot failed with: A general system error occured: Protocol error from VMX. This is a good example of two very vague errors on both the backup system and the virtual infrastructure. So to further investigate we needed to look deeper into the vmware.log file…

DNS name does not exist Error Code 0x8007232B – Windows 8 Enterprise

I just installed my first GA instance of Microsoft Windows 8 in my lab, and I’m fairly impressed so far. I did however run into an issue where Windows would not activate. When I tried to activate I received the following error: DNS name does not exist Error Code: 0x8007232B

It appears that windows was looking for (by default) a Key Management Service (KMS) host on my internal lab network. Since my lab is merely a testing ground, I have not setup the KMS on any server.  So the solution in this scenario is to change the product key to a Multiple Activation Key (MAK).

EMC Data Domain - DD - DataDomain

Best Practices NFS Mount for Data Domain

I was recently setting up a DD160 for a small Oracle instance and came across an issue when trying to mount the data domain via NFS. I tried several variations of the mount command and realized that I needed to be very specific. Since I was simply using a basic mount command the OS was missing some vital information about how it should connect to the data domain. I also realized that even though this Oracle database is reletivily small, the NFS mount should still be optimized for performance. Below is the message I was receiving:

mount: wrong fs type, bad option, bad superblock on datadomain:/data/col1/OracleBackup, or too many mounted file systems

The statement BACKUP LOG is not allowed while the recovery model is SIMPLE

When backing up SQL databases using the incremental option the backup job fails with “The statement BACKUP LOG is not allowed while the recovery model is SIMPLE” This is because the recovery model of the database being backed up is currently set to “Simple”. To resolve this error you must either change the database backup type to full, or change the database recovery model in SQL to either “BulkLogged or Full”.
The new EMC Avamar 6.1 Microsoft SQL plugin feature actually detects the recovery model of the database and skips the incremental backup, places a message in the log and automatically promotes the backup from an incremental to a full backup. So you can also upgrade Avamar to version 6.1 to resolve this error as well.

1 2 3 4