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; } } }

Teamsite Archive Options

cyankhan

Hi All ,

We are in a process of decomissioning our Teamsite installation 6.7.1 SP1 on Solaris.

We just want to confirm the things we can archive .

We will take the event DB dump

We will take a Filesystem backup of solaris .

Now there is one quesion.

if in a hypothetical situation we have to re install teamsite and get back data ,

Will it be possible to recreate the branches from physical files?

Is there any other way to view the data?

Thanks

Find more posts tagged with

Comments

Rick Poulin

You won't have to "recreate" anything. If you reinstall TeamSite (the same version) on the same OS, then you can move your backed up content stores (the iwstore folder) onto the new one.

No, there's no way to "make sense" of the content store's contents without mounting it on a TS server.

nipper

And to follow up on Rick's post, you can only mount a Unix backingstore on other Unix (Solaris or Linux) servers and not on an NT server

cyankhan

Thanks , I really appreciate the input.

Just to conclude

If I re -nstall teamsite and just restore my backup copy of the directories . It will show up in teamsite UI right?

Thanks

Adam Stoller

cyankhan wrote:
Thanks , I really appreciate the input.
Just to conclude
If I re -nstall teamsite and just restore my backup copy of the directories . It will show up in teamsite UI right?

Thanks

Not "directories", "backing store" - e.g.: /iw-store/default

And you can either put it into place before re-installing TeamSite or after re-installing but before starting (or after stopping) the TeamSite services.

Understand?

cyankhan

Thanks for your input , so If i undertand I need to back up the contents of the iw-store folder from the back end ,

and restore the same at the time of installation , correct?

Adam Stoller

cyankhan wrote:
Thanks for your input , so If i undertand I need to back up the contents of the iw-store folder from the back end ,
and restore the same at the time of installation , correct?

There is more than one sub-directory within the iw-store folder - so you need to consider carefully about each one to determine what you need to backup/copy/transfer.

At a minimum (and often maximum) there will be:

"default" - your primary content store and thus extremely important
"iwadmin" - the product's backing store for things like WFM's, components and SitePublisher templates - reasonably important, especially if you created any custom versions of those types of things
"workflow" - this is where the information about executed/executing workflows resides - from an arhchival perspective this is probably not important

cyankhan

Thank you very much. Smiley Happy

shameem

We have kind of similar requirement. We are moving out of 6.5 (I know ancient) to latest version for some/all versions for some. But we want to archive the old content's latest version safe for compliance purpose (any time if required to restore).

We donot want to archive the full backing store as we found 50% as junk during migration. So planning to archive branch by branch.

What is the right procedure to archive the latest edition or with all editions.

EOD when I want to backup the branch,

Option 1: I should be able to backup the content with metadata (no need of versions).

Option 2: I should be able to backup the content with metadata (with versions).

Appreciate any thoughts

Rick Poulin

There are two separate questions there.

When you backup the content store, you satisfy option #2 (content+metadata+versions).

When you want to migrate the store to a new server, you'll want to use the iwmigrate CLT to copy only the editions you want to copy. This has nothing to do with backing up your content.

shameem

Option 1 (with versions): Due to 50% junk, we would like to go branch by branch. So, is there any option I can take the whole branch backup which consists of content, versions and MData.

Options 2 (withOUT versions): Is it possible to take the lates edition with metadata backup (in zip or any format) so that when I unzip in to a new workarea it works as similar to what it was (like copying over latest edition content with MD to a new workarea).

Hope I am clear what I am looking for.

Taking the full BStore backup is my last option due to huge store and also 50% junk.

Rick Poulin

Well then we're not actually talking about backups at all.

Option 1 sounds like you want to do a cleanup activity where you migrate the "good" 50% to a new store that then replaces the old one.

Option 2 sounds like you should just be using Edit > Copy To.

Adam Stoller

shameem wrote:
Option 1 (with versions): Due to 50% junk, we would like to go branch by branch. So, is there any option I can take the whole branch backup which consists of content, versions and MData.

Options 2 (withOUT versions): Is it possible to take the lates edition with metadata backup (in zip or any format) so that when I unzip in to a new workarea it works as similar to what it was (like copying over latest edition content with MD to a new workarea).

Hope I am clear what I am looking for.

Taking the full BStore backup is my last option due to huge store and also 50% junk.

Option 1 (with versions) - You can create a temporary second store, use iwmigrate to migrate the branch (or branches) to that temporary second store - and then backup that temporary second store (and then remove it - thus making it "temporary")

Option 2 (without [all] versions) - You can do the same thing as above - but specify that you want to start the migration from the last [named] edition - you may still get some versions (changes submitted since that edition was created) - but you won't get all the versions.