nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Backup vs Edition

cc96ai

I create a auto Edition script, and I need my sys admin to turn on the "Schedula Task" for me.

however, his response is " we do have nightly backup and TS is version control software, why you still need to create edition"

I only can think is , when file is deleted on staging area, which is permanently delete, if we have Edition, we can/might retrieve back. (of coz we dont want to restore whole system to restore one file)

does anyone have offiical answer for this ?

Find more posts tagged with

Comments

nipper

Editions are not backuped per say. iw-store is. So if you need to get something from an old edition or revert to an old edition, you need to replace the backingstore. If that sounds like a good idea, go ahead.

Me, I prefer to have both.

I also suspect you sys admin thinks that each edition takes up a lot of disk space. That is not the case.

Adam Stoller

I create a auto Edition script, and I need my sys admin to turn on the "Schedula Task" for me.

however, his response is " we do have nightly backup and TS is version control software, why you still need to create edition"

I only can think is , when file is deleted on staging area, which is permanently delete, if we have Edition, we can/might retrieve back. (of coz we dont want to restore whole system to restore one file)

does anyone have offiical answer for this ?

Editions are snapshots-in-time of the contents of staging.
They are useful for rollback, for change verification, and potentially for litigation.
They are also useful for deployments both as a unit to act on, or as a baseline to compare against.
They are required for iwmigrate.
They provide the ability to retrieve historical versions of assets without requiring a complete restoration of the backing store (and all the disruptions that may require).

How's that?

13adam13

I also suspect you sys admin thinks that each edition takes up a lot of disk space. That is not the case.

a common misconception. that is why interwoven has taken to calling them "Named" editions. Every time you submit to staging, you are creating an edition. If you want to see that edition through the UI, you have to name it, otherwise the system hides it.

Regardless, the edition is there. Naming it just makes it easier to find.
If you want to see what I mean, run IWList on some {branch}/EDITION.

I need my sys admin to turn on the "Schedula Task" for me

Perhaps you could modify your script to fire when anyone submits, using the Event Subsystem(Chapter 4 of the TeamSite CLT Guide). Then, you would no longer require the assistance of your sys admin.

ConditionalTotals.rptdesign