How much space to allocate on a GUP for x days of definitions

[ℬrίαη]

How much space should I allocate on a GUP for keeping:

7 days worth of definitions

14 days

21 days

28 days

 

Is there a formula available or a Symantec recommendation?

How does everyone go about this?

Any thoughts would be greatly appreciated.

[pete]

it depends on the number of clients requesting the GUP for updates and the delta that has been passsed on by SEPM to GUP. consider in bad situation if there is full.zip ( i.e. around 180 MB) for 32 bit 180*7 would be space consumed.

 

[ℬrίαη]

So roughly we'd be looking at

7 days - 2gb

14 days - 3gb

21 days - 4gb

28 days - 5gb

[Mithun Sanghavi]

Hello,

The Above Figures may be approx as pete was stating about only 32 Bit Definitions and a rare case scenario.

As per the Best Practices of Sizing and Scalability document, it states:

Typically, a client configured as a GUP will require an additional 50MB of disk space to store content updates. This number can vary depending upon the age of the clients connecting for updates, and the size of the delta created to update them.

If you need to deploy updates to more than 10,000 nodes, Symantec recommends you consider an alternative update method, such as:

• Additional GUPs

• Additional Symantec Endpoint Protection Managers

• A Symantec LiveUpdate Server

 

Reference: Best Practices of Sizing and Scalability

http://www.symantec.com/docs/TECH123242

 

Hope that helps!!

[pete]

assuming the full.zip which is rarely the case. becuase the SEPM will be genearting the delta for clients based on content revision it keeps.

[SMLatCST]

As I'm a little unclear on why you would need to configure a GUP to retain definitions for prolonged periods of time.

As the GUP acts as a proxy, and cannot calculate delta updates itself, any definitions that are cached on it are obsolete the moment a new definition is released.

[ℬrίαη]

My understanding was that if you configured the GUP to hold 2 weeks worth of definitions and the client was off the network for a week, when it came back on, it would only get a delta but if it were off more than 2 weeks, it would grab the full file.

Is this not correct?

[pete]

well , the delta request and generation is role of SEPM, GUP just acts as a content distribution. If SEPM is able to generate delta that will be passed on to GUP

The Symantec Endpoint Protection Manager (SEPM) can create delta definition packages for distributing just the changes made in the definitions since the last time a client was updated. This ability relies on the amount of content revisions maintained by the SEPM, which is configurable

check this link

http://www.symantec.com/business/support/index?page=content&id=HOWTO53175

[ℬrίαη]

So it sounds like there isn't much point in keeping more than few days worith of revisions on the GUP?

[pete]

it depends on the clients at the location getting the updates , if the clients are outdated for 2 weeks ( kind of pattern) then have SEPM to store 45 revsion and on GUP save for 45 revision as well.

[ℬrίαη]

Typically, they will never be. And if they are off the network for that long, if they have Internet access, SEP will update via the Internet.

[pete]

great :-). then you can start to keep a 1o days revision to start with