dynamic disk
On Mon, Jun 3, 2013 at 9:51 PM, Elias Leal <[email protected]> wrote: > I have often wondered if using server 2012 SIS (de-dupe) is wise with > SCCM. I mean, if you are using it because you don't have the actual disk > capacity....would anyone have the ability to do a smooth restore from > backup if you ran into disk or server crash? > > If I understand this correctly, performing a restore from backup would not > initially be in SIS form and you would have to give Server 2012 time to do > the de-dupe again. The question that comes up is...do you have enough disk > space to do your restore all at once? Which means...you have to restore > things slowly, perhaps in stages. This is assuming you are still dealing > with the same disk capacity constraints. If you are rushing to restore your > primary or a site system, would this be a good thing? > > But if you do have a disk capacity to do a full restore all at once, then > why use the SIS in the first place? > > Perhaps the SIS would be more ideal in file server situations, SCCM may > present challenges in restore situations. It may be worth considering. > > I am curious if anyone has considered this. Or perhaps I am wrong about > the capability to restore in SIS form. > > Elias > > > On Mon, Jun 3, 2013 at 2:40 PM, Russ Rimmerman < > [email protected]> wrote: > >> As a follow-up on this one, please be aware that you can run into >> issues with using server 2012 de-dupe. ConfigMgr does not currently >> support reparse points, so if you attempt to import a driver package or >> something else that has a reparse point in it, it will fail with something >> like:**** >> >> “Import failed as \\server\share\driverpath\* *is a Reparse Point that >> SMS does not support via downloads*. DriverCatalog >> 06-03-2013 14:24:23” **** >> >> ** ** >> >> ** ** >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Todd Hemsell >> *Sent:* Wednesday, May 22, 2013 12:37 PM >> >> *To:* [email protected] >> *Subject:* Re: [mssms] Server 2012 vs Server 2008 R2**** >> >> ** ** >> >> put your driver import source, package source, and content source all on >> the same volume and it will only be as big as the import source alone.*** >> * >> >> If you used to have driver packages that contained the same driver (say >> network) in 40 driver packages, and 40 import sources.. now you have it on >> the file system 1 time.**** >> >> **** >> >> That is phenomenal disk savings.**** >> >> ** ** >> >> On Wed, May 22, 2013 at 11:43 AM, Russ Rimmerman < >> [email protected]> wrote:**** >> >> Interesting, looks like I have a shiny new toy err feature to play with >> in the lab today J**** >> >> **** >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Jason Sandys >> *Sent:* Wednesday, May 22, 2013 11:14 AM >> *To:* [email protected] >> *Subject:* RE: [mssms] Server 2012 vs Server 2008 R2**** >> >> **** >> >> True but Server 2012 SIS is at a binary level whereas the ConfigMgr SIS >> is at a file level. I’ve seen reports of significant savings.**** >> >> **** >> >> J**** >> >> **** >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Russ Rimmerman >> *Sent:* Wednesday, May 22, 2013 8:46 AM >> *To:* [email protected] >> *Subject:* RE: [mssms] Server 2012 vs Server 2008 R2**** >> >> **** >> >> But you get SiS w/SCCM 2012 in the contentlib with or without Server 2012 >> **** >> >> **** >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Todd Hemsell >> *Sent:* Wednesday, May 22, 2013 8:39 AM >> *To:* [email protected] >> *Subject:* Re: [mssms] Server 2012 vs Server 2008 R2**** >> >> **** >> >> Single Instance Storage in Server 2012.**** >> >> Reduces Disk Space.**** >> >> **** >> >> On Tue, May 21, 2013 at 4:15 PM, Christopher Duszynski < >> [email protected]> wrote:**** >> >> Is there any benefits to install SCCM 2012 SP1 on Windows Server 2012 >> vs. Server 2008 R2. **** >> >> If so can you provide me with your justification?**** >> >> **** >> >> **** >> >> **** >> >> **** >> >> **** >> >> **** >> >> ** ** >> >> ** ** >> >> ** ** >> >> >> > >
