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 BackUp and Recovery

Vishakha

Hi friends,
We want to setup a backup procedure for our production Teamsite Server.
This should be useful in the event of Server hardware failure.

We are using the Teamsite 6.7.1 version on the Windows server.

Need to clarify some doubts regarding the back ups and the recovery.
We identified the following areas that we need to back up.
1. The content store (iw-store)
2. The IW-HOME
3. The OD-HOME in case the Open Deploy is installed outside the IW-HOME.

Is there any other area/Path that I have missed out?

Also I searched a lot but could not find any documentation/article for the back up recovery. Can somebody help me with this, the recovery of the content store and the remaining paths described above?

Thanks,
Vishakha

Find more posts tagged with

Comments

santosh013

Enough if LiveSite(ls-home) is not there.

Thanks,

Adam Stoller

Hi friends,
We want to setup a backup procedure for our production Teamsite Server.
This should be useful in the event of Server hardware failure.

We are using the Teamsite 6.7.1 version on the Windows server.

Need to clarify some doubts regarding the back ups and the recovery.
We identified the following areas that we need to back up.
1. The content store (iw-store)
2. The IW-HOME
3. The OD-HOME in case the Open Deploy is installed outside the IW-HOME.

Is there any other area/Path that I have missed out?

Also I searched a lot but could not find any documentation/article for the back up recovery. Can somebody help me with this, the recovery of the content store and the remaining paths described above?

Thanks,
Vishakha

You might have to deal with OD AdminServer & CSF, LiveSite / SitePublisher, MetaTagger, MediaBin, etc.

Did you look in the TeamSite Administration Guide? It's had a chapter (albeit fairly small) on backups for a while now.

Vishakha

Yes, I have checked the Teamsite Admin manual for Windows for the backup procedure.
However there is nothing described as how we can recover this back up.

Can someone throw light on this?

santosh013

Vishakha,
You can only take back-up to secure yourself in case the teamsite gets corrupted.
1)If you have the idea that if teamsite gets corrupted,you will simply
install teamsite freshly and copy iw-home and it will work,then this is wrong because it throws several errors(in our case).
The best practice is to add the back-up step by step(directory wise).

Note:When Going for updation you should always update and you should never freshly install and put the back-ups,
this will again create problem.
This is what we learnt from our experiences.

If You have any specific query then you are welcome to raise.

Thanks,

Adam Stoller

Yes, I have checked the Teamsite Admin manual for Windows for the backup procedure.
However there is nothing described as how we can recover this back up.

Can someone throw light on this?

If you have a good backup of the iwstore/archive directory(ies) - you can recover from it by taking TeamSite down, completely replacing the existing archive directory with the backed up archive directory(ies), and then bringing TeamSite back up again.

An alternative is to restore the backed-up copy of the store to a different directory and configure this directory as a [temporary] additional store within your iw.cfg file and then use the iwstoreadm CLT to activate it.

Doing the restoration of the store from backup depends on how the backup was performed (whole-cloth, incremental layering, etc.) As long as you made the backup according to the documented procedures (such that it can be restored to its complete status as of a particular point in time) it should work.

Vishakha

Is it enough to zip the iw-store or we compulsorily need to use a backup tool as mentioned in the TS best practices?

Adam Stoller

Is it enough to zip the iw-store or we compulsorily need to use a backup tool as mentioned in the TS best practices?

It depends on your requirements. In either case though, you need to make sure that the store is frozen before you take you snapshot - and presumably you're not going to leave the snapshot on the same filesystem where you took it. You still cannot un-zip the backup onto the existing store unless there's an option in zip (not that I'm aware of, but I haven't looked that closely) to remove any files that are not contained in the zip.

Vishakha

At present I am assuming that we would have a test server where we have these back-ups stored. And restore them for checking.
In that case would it be enough that we unzip the store, add entry for the store in the iw.cfg and then activate the store?

Adam Stoller

At present I am assuming that we would have a test server where we have these back-ups stored. And restore them for checking.
In that case would it be enough that we unzip the store, add entry for the store in the iw.cfg and then activate the store?

That should work - though I question the validity of the term "backup" if it's only be stored on-line on another server.

Migrateduser

A store backup option I like and works wonderful and minimizes downtime.
(Conventional backups of the store can be very lengthy due to the amount of (small) files in the store)

Have a seperate disk you can mirror the iw-store data to.
use something like robocopy to mirror the iw-store data to the seperate disk.
You need to do that when the store is forzen (or teamsite stopped)
Make sure you exclude the store lockfiles in the mirroring

Customer has a batch job running every night that freezes the store, runs a mirror (only deltas) and unfreezes. This takes between 3 and 15 minutes on a 100GB store (depending on the amount of data changed per day)

Pretty fast compared to full backups using conventional backup software.
Downtime is therefor less and a tape backup can be take from the mirrored drive
(weekly, daily, full, incremental)

To restore the date if the primary data disk gets corrupted:
stop teamsite change the (windows registry) entry of the store location to the other drive and startup teamsite again.
You can bring the system backup with the previous day content within 15 minutes.

Needles to say that the backup and restore requirement of the customer allows this procedure and if an older backup is required, you still have to go back to your backup tapes which takes longer

Might be an option for you as well.

Ron

jed

One note about "incremental" backups...

As the backing store grows, it may not be feasible to restore based upon incremental backups. A restore of a "full" backup take ~5-6 hours for me. A restore based upon diffs takes...well, let's just say I gave up waiting around for it to complete. This is especially true of a backup to tape as an incremental may mean lots of seeking and tape changing.