Posts

How to get llama 2 up and running , in a VM, with no GPU, and limited memory on Ubuntu

Image
OK I decided to write this up after unsuccessfully being able to find all the required info I needed in one place. In this setup we will be using Ubuntu Server 22.04.2 LTS as the OS. I have this running on a home lab ESXi server 8, on a HP Compaq Pro 6300 SFF CPU = Intel Core i7-3770 Installed Memory 16 GB I have some 10K SAS drives installed for the VM's If you have not already, navigate to  Get Ubuntu Server | Download | Ubuntu and download the 22.04.2 LTS ISO Next Lets create our VM that we are going to run this in. *Note Im using ESXi however you can probably do this in Workstation, Fusion, VirtualBox etc The main things to note on the VM creation. Set Ubuntu 64 bit as the guest OS Set your CPU relevant to the physicals CPU, I will be starting with 4 VCPU Set your Memory to as much as you can tolerate, I will be using 12 Disk Space - we are creating a 100G swap file, and the rest of the file can take up some room , so more is better if you can afford it Dont forget to add the U

DPM 2010 Tape Belongs to a DPM server sharing this library

I wrote a powershell script to fix this issue in 2010, it does not appear to be an issue in 2012. a full explanation i got from here.  Enjoy $ServerInstance = "DPMSERVER\MSDPM2012" $Database = "DPMDB" $ConnectionTimeout = 30 $Query = "select media.BarcodeValue, media.SlotNum, media.MediaId, gmedia.MediaPoolId from tbl_MM_Global_ArchiveMedia gmedia  inner join tbl_MM_Media media on gmedia.MediaId = media.GlobalMediaId " $QueryTimeout = 120 $conn=new-object System.Data.SqlClient.SQLConnection $ConnectionString = "Server={0};Database={1};Integrated Security=True;Connect Timeout={2}" -f $ServerInstance,$Database,$ConnectionTimeout $conn.ConnectionString=$ConnectionString $conn.Open() $cmd=new-object system.Data.SqlClient.SqlCommand($Query,$conn) $cmd.CommandTimeout=$QueryTimeout $ds=New-Object system.Data.DataSet $da=New-Object system.Data.SqlClient.SqlDataAdapter($cmd) [void]$da.fill($ds)  $conn.Close()

KB2718704 breaking DPM 2012 for non domain servers

If you an administrator you are aware of  KB2718704  and its exploits via the Flame software. After patching my DPM server it appears all non domain servers are no longer allowing the DPM 2012 server to connect. to fix the error re-attach the servers in DPM Management Shell attach-nondomainserver dpmservername   -psname remoteservername   -username remotelocalusername

Hyper-V clustering on 2008 R2 Server Core

So i thought id put in some notes on configuring a Hyper-V Cluster on 2008 R2 SP1 core. in my scenario i an using 4 nics team for Hyper-V data, 1 nic for management , one for cluster traffic and one for live migration data. I am also using 8GB FC clusters consists of 5 nodes (removing the need for a quorum drive) This is only connected to 1 VLAN , if you need mutiple VLANS, create them before creating your cluster as it will be easier. one tool you will need in this setup is nvspbind.exe , this allows for the configuration of network services tied to the adapters. first you will want to install all your cluster servers exactly the same with the same hardware etc. Then install the OS (im using 2008 R2 Datacenter) and select the Core installation once installed loginto the server , you will get a command prompt install the SNMP feature Dism /online /enable-feature /featurename:SNMP-S Enable Remote Administration of Firewall (optional) netsh advfirewall set currentprofil

DPM 2012 Upgrade from 2010..

Image
So upgrading is very simple, there are many different post on how to upgrade , and its mostly point and click, however there are some things you should do to "make it work", or maybe it was just me. also depending on how large your infrastructure is, now backups can run until the whole process is done, that means you need your dpm server on 2012, and client agents on on 2012 (2003 servers may require a reboot) 1st backup your 2010 database run your upgrade once completed reboot then BACK UP your 2012 DATABASE NOW! this will save you frustration later down the road, just put it on disk somewhere. FYI, if your using the SQL that came with DPM, it does not include SP1 (yeah that's right), update this later. everything will be out of sync begin sync them now. if you remember setting the tape write period ratio along time ago, guess what, it dosen't exist any more in powershell Set-DPMGlobalProperty –DPMServerName -TapeWritePeriodRatio you now get to set