Fazza

Only import the one line you want to change, do not do the whole thing else it will take forever and may stop the computers working.

A regedit will be a lot shorted than your script as it's just a single line of code.

That could be it! Just run get-virtualdisk and it is indeed set to manually attach so I shall change it to False and reboot in a bit to prove it (just waiting for the backup to complete). [EDIT] The command in the screenshot shown in the above link didnt work for us and by the looks of things it didnt work for a lot of other people. It's seems on re-attaching a storage pool to a different/replacement server installation it is set to manually attach by default! The way to change it (that worked for us) is as follows: Get-VirtualDisk | Where-Object {$_.IsManualAttach –eq $True} Get-VirtualDisk | Where-Object {$_.IsManualAttach –eq $True} | Set-VirtualDisk –IsManualAttach $False

Connected to a Server 2016 Hyper-V host is an array of JBODs set up in Storage Pools. The server only had 1 hard disk drive for the OS so no redundancy. Recently purchased a second hard disk drive for the server so it is now mirrored. We have re-installed Server 2016 on to the server and attached the virtual disk to the server. The problem we have is after a reboot when we log back on we have to keep re-attaching the virtual disk: Surely it should do this automatically (like before the OS re-install) or am I doing something wrong?

Is this a new installation? If so then it will over-allocate disk space for future backups - this will settle down as it learns exactly how much you backup each day etc. If you are running out of space there is a manual way to force it to shrink the pre-allocated space or you can just leave it and it will sort itself out over the coming weeks/months.

Just ask Snipe-IT what it means. If i ever have a query with Snipe-IT I usually get a reply within a few minutes.

UPDATE: I've got upgrading SQL to a version supported by both DPM 2016 and DPM 2019 down to a T but I have a problem with the upgrade to DPM 2019 not working... When I try and upgrade DPM 2016 to DPM 2019 it fails the prerequisites as it says that the version number of the DPMDB database withing SQL (not to be confused with the SQL version) does not match the version of the currently installed version of DPM. If I take a look at the DPMDB version number within SQL I get 5.0.158.0 (which is the RTM version of 2016). When I go in to DPM 2016 the version number that is on is 5.0.409.0 which is the Update Rollup 7 version which was installed via Windows Updates. So it seems that when the Update Rollup 7 was installed it either: 1) hasn't upgraded the version of the DPMDB database. 2) it has upgraded it but not changed the version number or 3) there are in fact no upgrades/changes to make so it didnt bother to change the database number within the database in SQL! If it's the last option (that Update Rollup 7 didn't need to upgrade/change the database so it didn't bother to change the database number within the database in SQL) then from Microsofts' own website they provide an SQL script to simply enable you to manually change the database number so you can continue with the upgrade - I'm just concerned in case it's not the third option but one of the other two and by simply changing the database number manually to trick DPM in to upgrading will cause the integrity of the data to not be right?

Have I won it yet?!

Having to put this on hold seems DPM 2019 will not backup anything less than 2012 and we have 1 2008R2 file server:( https://docs.microsoft.com/en-us/system-center/dpm/dpm-protection-matrix?view=sc-dpm-2019 Unless I'm misunderstanding of course?! The 2008R2 File Server in question is a VM on a Server 2016 Hyper-V Host so how would DPM 2019 know the OS of the VM as all it's doing is backing up the VM (i.e. the VHD file) isn't it? We dont have the remote agent installed on any of our VMs just the Hyper-V host itself.

The only real issue is, we buy DPM cheaply and dont buy any support so everything we know about DPM comes from trial and error and the internet! Our issue is that we're not just upgrading DPM but need to upgrade SQL 2012 as it's not supported by DPM 2019 so we've got to go through that pain first! I've read lots of guides and as with a lot of things there are several ways to do this and sometimes it works for people and other times it doesnt! If we had a supported version of SQL installed that works with both DPM 2016 and DPM 2019 then it would be a straight-forward upgrade of DPM but I've got to faff around with SQL as well and get the database versions to match etc.

I finally managed to get our DPM server back in the state it was originally in (only took 3 solid days) so back to square one at the moment. I have nicked a 2nd CPU and a bunch of RAM from my SCCM server and stuck it in a server we were keeping for spares and have just installed SQL 2012 on it ready to install DPM 2016 to match our current DPM server. I will then export the DPM database at the command line and then import it in to my test server and once I've got it working on that I will go through the motions of upgrading it the way I now think will work - if it does I will post what I did on here.

I think that should be the strap-line in DPM's advertising!!

The only 'issue' I had with SSRS with SQL 2017 is that each section appears to have automatically been configured as it has been pre-populated with data but you have to click on each one in turn and press Apply until all the Apply buttons are greyed out - only then is it fully configured and ready for use with DPM 2019!

Upgrade failed as for some reason it didnt upgrade the DPM2016 database during the install! Didnt roll back or anything so when I try and open the DPM console it doesnt open up DPM! The DPM server wont start, it just stops straight away. Event viewer says that the DPM service wont start as the database version isnt compatible with DPM2019, thus proving that the DPM database did not get upgraded! I've got loads of backups but cant access them or create any new ones!

No increase or decrease in premium as well? A colleague had to change some details on his car insurance and it went down by 10p but had to pay a £25 admin fee so £15 is quite reasonable!

As soon as you get back off of honeymoon or before you next drive your vehicles after getting married as you never know when an idiot driver will pull out in front of you causing you to crash. If in doubt, give your insurance company a call and ask them, also ask for confirmation in an email to you and a reference number for the call.

It's half term so there's nobody here!!! Anyway I think I should win it because I am here and have been all last week too!

After we've stopped laughing and realise they are being serious, we would ask why they need to turn the power off and then make a decision after that. As it can take anywhere from 45 minutes to 2hrs (bloody pending Windows Updates) we'd email out and let people know that 2hrs before the power is going to be cut we will be gracefully shutting down the servers and then get on with it at the agreed time.

Are any of the disks showing as being bad? I.e. are there any red LEDs or error lights flashing on just one of the disks?

We found it slows the computers down tremendously so only ended up deploying it to one computer suite and recommended staff uninstall it as 90% of people complaining about slow laptops had the Teams app installed. Never managed to get it to stop autostarting on the computers that need it. I think it's to do with the way it installs for each and every user.

If you leave it and it tries to PXE boot then that normally means that it cant detect any hard disk drive volumes. I'd try going in to the RAID card settings (it should tell you what key combination to pressing during the POST/BOOT). If you had to reset the time/date etc. then you may have to import the disks back in to the RAID controller too so that's why i'm saying to look at your RAID card.

It's half-term for a lot of places so they're all on annual leave or on 42wk contract so not in so wont see it for another week or so!

They will happily take your money without you telling them of any changes, try and make a claim though and they'll tell you that your insurance is null and void as you wont have updated them. Tell them ASAP.

You dont say if the PC is a Desktop or Laptop PC - if it's a Desktop PC could you not buy a firewire card for it?

We asked O2 about this at my last place as in the warehouse there was no signal but plenty as soon as you went outside. They said £10,000 was a starting price and we stopped listening after that!