Jump to content

Ergo_Computing_IS_Support

Members
  • Posts

    21
  • Joined

  • Last visited

Everything posted by Ergo_Computing_IS_Support

  1. In your particular scenario, I'd definitely advise having at least 2x NICs of whatever speed, preferably each on their on card (i.e. not a dual port card) for both NIC and card resiliency. 1x 10Gbe would be single point of failure. Additionally, if you opt for an aggregated approach, if the switches support it, you can have the aggregation span multiple switches so you not only have resiliency in the form of multiple NICs on the server but also in terms of connection the the core network. You could lose a switch and still carry on. I think based on this, I'd only opt for 10 Gbe if I was going to install 2 of them on separate cards.
  2. I'd strongly advise not altering the default domain policy, or at least taking a copy of the default domain policy and work on the copy if you must. Too many times have I seen corrupt default domain policies.
  3. From past experience, GPP drive mapping works really well and we try to steer away from scripts unless absolutely necessarily. Not only is is a much cleaner and recommended, it makes it a lot easier to troubleshoot with the likes of RSOP and GPresult. Generally speaking, GPP drive mapping usually fail to apply when they've been set as user settings but applied to an OU of machines, or vice verse.
  4. I think the general rule of thumb is to do a fresh install unless it really can't be avoided. Fresh installs just are a much cleaner installation and less likely to inherit problems.
  5. Reply from 10.150.4.3: destination host unreachable is correct, as 10.150.4.3 will be the IP address of the device from which you are running the command. Its also worth noting that the os firewall may deny ping responses and therefore it may not respond. Thanks.
  6. The documentation is here... http://h20564.www2.hp.com/hpsc/doc/public/display?docId=c03326739 I sense that because the b120 is (fitted as standard) is the basic RAID card it will most likely not support this functionality.
  7. Watchguard firewalls do this really well from past experience. In terms of what they offer functionality-wise vs. the price, they are hard to beat. Also, the management interfaces (webgui + software app) are really straight forward to use and administer on a day-to-day basis. No command line knowledge required! (but can be still be used for very advanced scenarios) Thanks.
  8. Hello, Do you know the particular RAID card fitted to your server? It is sometimes possible, but its normally RAID card dependant. Thanks.
  9. Hello, What method are you using to resolve device names? e.g. are you pinging them? or using nslookup? Also, in DNS Manager, what type of records have got stored? Are they A records (IPv4) or AAAA records (IPv6)? When you setup your new DHCP scope(s), did you enable DNS dynamic updates? In the DNS Manager check the server properties and check and see what interfaces the server is listening on.
  10. As mentioned above, Server 2012 now supports DHCP clustering/failover which has been long overdue, but now its here it works really well. Splitting scopes over multiple DHCP servers always felt like a bodge but now it seamless and very easy to set up. We always implement it now.
  11. I would start my investigating those 'BAD ADDRESSES' to see if they are actually being used i.e. try pinging them. If they respond, you could then begin trying to isolate them by looking at ARP tables on the server and the network switches. With a bit of digging you should be able to track a given IP to a MAC address, and then a MAC address to a switch port. If you find these devices you can then check their IP settings. If they are indeed static you could revert them to DHCP, if they are already DHCP perhaps try an ipconfig /release and then ipconfig /renew to obtain a new IP/lease from the DHCP server. I would also investigate if there is a 'rogue' dhcp server on your network. You can download tools to do this. Similarly, I'd check to see if there are any new devices on your network, maybe they are causing the problem. Thanks.
  12. Hello, Perhaps take a look at this article. Event ID 502, Windows 7 Folder Redirection
  13. Hello, If you haven't already tried - I'd do a re-scan of the HBA's, a refresh and then try and add new storage. If this doesn't work, it might be that the host needs a reboot before it detects the new RAID group. Thanks.
  14. Hello, I'm glad you have now installed it. There is some useful information available here ... http://h10032.www1.hp.com/ctg/Manual/c03934591.pdf from page 10, and the document links to a few other documents as well.
  15. Hello, If you have copied the offline bundle ZIP file to the data store, you can access the datastores from the following directory on the ESXi host: /vmfs/volumes/ So in theory the full path in your case would be /vmfs/volumes/Data_Store_02/VIBS/hp-HPUtil-esxi5.5-bundle-2.1-18.zip I believe VMware recommend copying the offline bundle to /var/log/vmware/ and then running the install command from his location rather than direct from the datastore. VMware KB: Installing async drivers on VMware ESXi 5.0, 5.1, and 5.5
  16. Hello, I can confirm that for virtual disks > 2TB, both VMFS5 and ESXi 5.5 or later are required. It also worth mentioning that upgrading VMFS3 datastores to VMFS5, doesn't alter the block size so if possible I'd recommend creating VMFS5 datastores from scratch to get the full benefits and features. Additionally, it might be worth considering the benefits of Windows Server 2012 and the inbuilt deduplication. By enabling deduplication on the volume you can achieve some quite impressive storage reductions (depending on the type of data) and as a result you may not need to exceed the 2 TB limit. That being said, VMware ESXi upgrades can be straight forward and non-disruptive if you have a clustered HA environment.
  17. Hello, I can see in the error message is refers to the directories of your backup files e.g. NEW2014-11-13T20024.vib Do these files still exist when you navigate to this location? It might be that the Veeam database is looking for files that do not exist any more (perhaps fell out of retention or deleted manually) or that they moved or they've even been renamed. Also, from within Veeam, have you tried 'Import Backup', selecting the backup files from the windows directory (D:\Veeam Backups\) and then restoring from these?
×
×
  • Create New...