When I was doing SUP at my last employer, I was doing adding to packages each month for several months before moving on to a new package when old was say 5-10gb (which can be one month of several depending on what updates come out, I was also doing 9 languages.) The problem I had was when these were redeploying out to my 21 DP's worldwide, I always... 1. had errors and that required redistribution to at least a few and... 2. the distribution time got to be days on the slower sites. Sometimes they had not received the whole package before testing interval was over and the deployment went to everyone.
I went to monthly packages and the problem went away except for months with several large packages in them. But even then, it didn't take nearly as long. Also, if I didn't catch it, then SUPdates didn't install if the package was hung needing redistributed. Dave On Tue, Jun 2, 2015 at 10:37 AM, Beardsley, James < [email protected]> wrote: > I’ve heard several theories on this. I’d be interested in what everyone > is doing. I’ve been doing one package for an entire year but I think next > month, I’m going to start doing one package per 6 months to decrease the > size of the packages. My 2014 package is 14GB and I noticed it being a > problem when I launched a new DP last month and it had to copy that over > the WAN. > > > > Are others doing a new package every month? > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Roland Janus > *Sent:* Tuesday, June 02, 2015 2:27 AM > *To:* [email protected] > *Subject:* RE: [mssms] Is there a package version for SUP packages as for > all other? > > > > You’re doing monthly with new packages then? > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jason Sandys > *Sent:* Dienstag, 2. Juni 2015 01:40 > *To:* [email protected] > *Subject:* RE: [mssms] Is there a package version for SUP packages as for > all other? > > > > Using smaller packages isolations and limits the scope of issues though – > that’s specifically why I greatly prefer them. > > > > J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Roland Janus > *Sent:* Monday, June 1, 2015 1:55 PM > *To:* [email protected] > *Subject:* RE: [mssms] Is there a package version for SUP packages as for > all other? > > > > Actually, small or not, if that content is not getting there for whatever > reason, bad/dead connection or already pending distribution it would get > stuck. > > And ADRs using the same package, like definition updates or even just > regular updates as part of patch Tuesday. > > > > Although wondering if no one would have noticed that if it really happens. > > > > -R > > > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jason Sandys > *Sent:* Montag, 1. Juni 2015 19:32 > *To:* [email protected] > *Subject:* RE: [mssms] Is there a package version for SUP packages as for > all other? > > > > Yes, there is a package version number; however, the content of update > packages is a bit different in that it keeps track of individual updates. > Not sure if an in-progress package update will cause issues or not. Just > another reason to use smaller packages for updates though. > > > > J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Roland Janus > *Sent:* Monday, June 1, 2015 8:38 AM > *To:* [email protected] > *Subject:* [mssms] Is there a package version for SUP packages as for all > other? > > > > Updating a regular package increases the version by 1, requires the new > policy to be known to the client and if done during OSD for a required > package, it may fail the TS. > > So don’t change a live package. > > > > But what about software updates packages? > > The client isn’t downloaded everything, so if new content is added it > either can access it or not, right? > > > > Also is a software update package offline as all other packages are, while > new content is added and distributed? > > > > -R > > > > > > > > > > > > > ------------------------------ > > *Confidentiality Notice:* This e-mail is intended only for the addressee > named above. It contains information that is privileged, confidential or > otherwise protected from use and disclosure. If you are not the intended > recipient, you are hereby notified that any review, disclosure, copying, or > dissemination of this transmission, or taking of any action in reliance on > its contents, or other use is strictly prohibited. If you have received > this transmission in error, please reply to the sender listed above > immediately and permanently delete this message from your inbox. Thank you > for your cooperation. > >
