Nope, that works also. The SIS will happily adapt itself to multiple volumes. 
You'll need to restart the SMS_EXECUTIVE service for it to see the new volume.

J

From: [email protected] [mailto:[email protected]] On 
Behalf Of Miller, Todd
Sent: Thursday, June 12, 2014 4:44 PM
To: [email protected]
Subject: [mssms] RE: Recover DP from package volume failure

Duh moment...

Can't I just add another volume rather than make a larger volume?   DPs will 
happily spread themselves over multiple volumes, right? Or does the SIS stuff 
in SCCM 2012 change that?

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jason Sandys
Sent: Wednesday, June 11, 2014 4:00 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Recover DP from package volume failure

Simple backup and restore should work fine. Stop the SMS_EXECUTIVE, backup up 
the volume, expand the volume, restore, restart SMS_EXECUTIVE. As long as the 
backup and restore preserves permissions and you use the same drive letter, 
ConfigMgr won't know anything has changed - it can't because technically 
nothing has changed - the files are all still in the same logical/relative 
location.

Also, did you know that you can directly remove all content from a DP in that's 
DP's properties or removing it from the DP group? And you can re-add content to 
a DP using either DP groups or by multi-selecting in the console? Or PowerShell 
ffor either task also?

J


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Miller, Todd
Sent: Wednesday, June 11, 2014 3:43 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Recover DP from package volume failure

Running SCCM 2012 R2 w/CU1

My (only) DP is running low on space so I am going to add a couple more drives 
and expand it to Raid 10.  I am pretty sure this will be destructive to the 
data on the volume.  The DP's OS is not on this volume, but the packages and 
the SiS for the DP is.

I am not sure what I should do to prepare before or what to do after.

This is the only DP on the site.  The site is not currently servicing any 
production clients.

My current thinking is to use the Cory Becht tool to remove all packages from 
the DP, delete the server as a DP in the console, then expand the package share 
drive, then setup DP as a DP in the console again, then use the Becht tool 
again to distribute all the packages to that DP.  Is that a good/bad idea?


Some better way?  I suppose I could copy the data somewhere, redo the drives 
and then copy the data back, but I think that is probably just as much load on 
the network and not really any faster or safer, right?


________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and 
may be legally privileged.  If you are not the intended recipient, you are 
hereby notified that any retention, dissemination, distribution, or copying of 
this communication is strictly prohibited.  Please reply to the sender that you 
have received the message in error, then delete it.  Thank you.
________________________________



________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and 
may be legally privileged.  If you are not the intended recipient, you are 
hereby notified that any retention, dissemination, distribution, or copying of 
this communication is strictly prohibited.  Please reply to the sender that you 
have received the message in error, then delete it.  Thank you.
________________________________




Reply via email to