This is a quick tip on using a Synology NAS to backup with Time Machine in OSX Lion / Mountain Lion. If you have installed and are running the Synology Antivirus Essentials app, it is advisable to exclude the Time Machine backup location. You can do this by creating and running a ‘custom scan’ instead of running a ‘full scan’. If the antivirus makes any changes to the time machine sparsebundle it will likely cause the backup to become ‘corrupted’ from OSX’s standpoint, which will cause OSX to need to create a full backup again causing the loss of your backup history.
Sophos Antivirus for Mac is a good real-time scanning platform that you can use to protect your OSX based machines and it’s free. http://www.sophos.com/en-us/products/free-tools/sophos-antivirus-for-mac-home-edition.aspx
Bit Defender for Mac is also offered in the Mac app store and as with all Bit Defender products I’ve come across offers solid and superior protection. It’s free and can be used to scan your drives, however I did not see the ability to conduct specific items scans or provide live protection.
Good luck and hope this helps someone out.
I’ve been running a vSphere lab of my since ESX 2.x. Over the years, I’ve used both local and NAS based storage with varying degrees of satisfaction with the results. In the case of NAS storage, which is required since I can’t afford a SAN, I looked at Synology devices over the last year trying to gain the motivation to make the investment.
Needless to say, I dove in with both feet, and maxed out a Synology DS1511+ with 3TB drives. I purchased my Synology DS1511+ from SimplyNas with the drives included, including their burn-in testing, and I haven’t looked back. The device has been up and running since October 2011.
Continue reading My Experience: The Synology DS1511+ NAS is Purely Rock Solid
I’ve been using a few Iomega StorCenter IX4-200D’s as storage targets for vSphere 4 ESXi and have been a little disappointed at the performance. This disappointment really only comes when VMs are booting, I’m using Storage VMotion, or consolidating snapshots. For the price point, it’s still a great piece of equipment and I can honestly say that I’ve had 17+ active VMs running off the unit with no problem once the VMs are up and running. Keep in mind this is a lab implementation and those VMs weren’t under heavy utilization.
I’ll keep this post updated with anything else I come up with or that is submitted in comments.
Edited 10/23/2011 – No longer recommending use of NFS as a vSphere target on this unit.
Continue reading Squeezing Maximum Performance Out Of Your Iomega IX4-200D as a vSphere Storage Target
I’ve been using an Iomega IX4-200D as a storage target for vSphere and have to say that for the most part it works well. I’ve used it both as an iSCSI target and as NFS storage.
You can and should expect it to suffer typical storage performance issues. It runs on 4 hard drives, mine in a RAID 5 array which is not the most performant, but best in case of disk failure and who wants to lose VMs. It’s still a limited set of spindles to work with and keeping that in mind will save you troubles down the road.
At one point, I had 17 VMs running on a single IX4-200D.
Still interested? Keep reading…
Continue reading Using the Iomega IX4-200D as a Storage Target for vSphere (ESX and ESXi) Lessons Learned
Is your Iomega NAS iSCSI drive locked by vSphere and you don’t want to reboot? This works with vSphere 4.1 (using ESXi but should be the same for ESX versions), and an Iomega StorCenter ix4-200d (firmware 22.214.171.12494). If you encounter issues with another version, please let me know.
I’ve had some trouble off and on with iSCSI on my Iomega IX4 series NAS. The trouble exists around removing the iSCSI target from vSphere but not releasing the hold on the NAS typically requiring a reboot of both the NAS and the host to remove the lock. As I don’t like taking my host(s) or NAS down, through a little experimentation, I’ve come up with the steps necessary to remove the target allowing for the editing or deleting of the iSCSI drive on the NAS. While something is connected to it, the IX4 will not allow editing or deletion. This also works for removing a single target drive while vSphere is still pointing to other targets on the NAS.
Let’s get to it!
Continue reading Remove iSCSI Drive Lock From Iomega IX4 Series NAS and vSphere Without Rebooting Either
UPDATED 12/5/2009 to include vSphere commands.
This is a quick note, mostly to help remind me and hopefully help someone else out.
You can use standard Linux commands to connect an ESX host to a NAS (Network Attached Storage) device. You can use a NAS to store things like ISO’s and backups. I have many gig’s of ISO’s and I really don’t like them taking up valuable storage on my ESX host. In production, they’d be taking up SAN space, so I offload them to a Buffalo Terastation, and use Linux commands to mount the Terastation so that ESX can utilize it.
First you can make a directory under vmimages.
ISO2 is the directory that you are creating. For me, ISO already points to a local directory on my server where I keep one or two ISO’s that I am continually using. Then you can run the command:
(ESX 3.5) mount –t smbfs //[nas]/[folder] /vmimages/ISO2
(vSphere) mount –t cifs //[nas]/[folder] /vmimages/ISO2
Continue reading Use Console to Connect ESX to a NAS
Windows 7, along with Windows Vista, both have issues interacting with Buffalo Terastation and similar Buffalo products. This is due to updated NTLM security settings in both Windows 7 and Vista. The un-patched behavior is continued prompts to log in / authenticate to the NAS.
Buffalo has released a registry patch that allows Windows 7 and Vista to connect to their Terastation NAS products, by lowering the security level to Windows XP compatible NTLM security. This is a downgrade, but I have thus far had no problem with it. Check out the readme below that’s included in the download:
This registry patch files enables Windows(R) Vista(TM) PCs to
work with Buffalo NAS products. This patch is installed
directly onto Windows Vista PCs.
WARNING: This file is only for use on Vista PCs, it is NOT
required or supported on any other operating system.
This patch is only required when using one of the following
Buffalo NAS products:- LinkStation (HD-HLAN)
– Gigabit LinkStation (HG-HGLAN)
– LinkStation Home Server (HS-DGL)
– TeraStation (HD-DTGL/R5)
– TeraStation Home Server (HS-DTGL/R5)
– TeraStation Pro (TS-TGL/R5)
1) Double click on the Buffalo_NAS_Vista_Support.reg file
2) Press the ‘Yes’ button when prompted.
3) Press the ‘OK’ button to exit the patch file.
4) Restart your Vista computer.
Applying this patch lowers the NTLM authentication
level to be compatible with some of Buffalo’s NAS products.
This NTLM authentication level is equivalent to the level
used in Windows XP.
Continue reading Get Windows 7 Working with your Terastation