HPE StoreOnce Chain Length limit to 7

[bdunington]

Good Afternoon Everyone,

I was reading the new V9 doc's. I came across this only 7 restore points ........really?

http://helpcenter.veeam.com/backup/hype ... tions.html

The length of backup chains (chains that contain one full backup and a set of subsequent incremental backups) on HPE StoreOnce cannot be greater than 7 restore points. The recommended backup job schedule is the following: not more than 1 incremental backup once a day, not fewer than one full backup (active or synthetic) once a week.

Brent

[Gostev]

Hi, Brent

Yes, really. This has to deal with a [very low] maximum amount of open files limitation of StoreOnce. From what I know, HP was going to lift this number in future firmware releases.

Thanks!

[bdunington]

Hi Gostev,

Thank you for your quick reply. We will have a chat with our friendly HP team

Brent

[Gostev]

This won't hurt for sure

[kte]

if we use it to put only full backup copy GFS, or active full copy , is this limitation also there?

[nefes]

This number only limits length of full-increment-increment chain, so you may have any number of such chains simultaneously, or a GFS with lots of fulls.
It will work good for two reasons:
1. Since two fulls are totally independent from each other, you need to open only a full to restore from it, while for increments chain you need to open all the chain for restore from latest point.
2. GFS fits deduplication storage well, you can make more GFS point taking less space, just because of deduplication.

[emachabert]

With Storeonce, number of simultaneous opened files for a deduplicated share is related to the size of the Appliance.
And like Anton said, the numbers will get bigger in future firmware.

By the way, when using dedupe Appliances, having a weekly full is not a bad thing at all. It provides good restore speed by not having to open a long incremental chain. The only drawback is the load it puts on the source storage because when you have hundreeds of TBs it can quickly become difficult to fit the backup Window.

[dellock6]

Only if you do active fulls and thus you need to retrieve data everytime from the production storage, but I'd honestly suggest synthetic fulls for a dedupe appliance, especially for storeonce (and datadomain) where we support their native protocol, so we can do the transform operation of the synthetic in a very short time. In this way, even during a "full" day you just retrieve another incremental from the production storage.

[cjack03]

From the docs:

Limitations apply only if you use HPE StoreOnce in the integration mode, not the shared folder mode.

What is integration mode? Catalyst?

and just another quick question, if using a HPE StoreOnce in a SOBR i guess this limitation doesnt matter as we only store the fulls here?

Thanks

[Gostev]

Yes, this is talking about Catalyst.

If you are only storing fulls on StoreOnce extent, then this limitation should not apply.

[crazycommando]

Hi.
I'm looking to setup Backup copy job to remote site to HP StoreOne Catalyst Store.
I'm guessing the limitation of 7 restore point chains still applies here as per the guide? So in the case of a Backup Copy job you would HAVE to use the GFS weekly selection to be consistent? Any tips here?

Thanks.

User Guide - Limitations for HP HtoreOnce
"The length of backup chains (chains that contain one full backup and a set of subsequent incremental backups) on HP StoreOnce cannot be greater than 7 restore points. The recommended backup job schedule is the following: not more that 1 incremental backup once a day, not fewer than one full backup (active or synthetic) once a week"

[foggy]

Limitation applies to backup copy jobs, however, there's no requirement to enable GFS and read the entire restore point data from source backup, you can leave it to be forever forward incremental with 7 restore points retention.

[pdimarco]

Looks like if you enable BCJ active full, you can overcome this limit of 7 restore points for non GFS retention.

Pascal

[Gostev]

Except you cannot enable BCJ active full for non-GFS retention but anyway, even with GFS retention does not change anything, as the limitation described in the second post of this topic sits in the storage itself and will not magically disappear with enabling BCJ active full.