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

Restore Backing store to other server

makarand

Gang, I am looking for step by step documentation to restore backing store to another server (from prod to dev, solaris 8)

Thanks

Find more posts tagged with

Comments

Adam Stoller

What version(s) of TeamSite are you dealing with?
What steps do you think you already know (might help to start the ball rolling and let others fill in pieces for you)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

makarand

We are on 5.5.2 Build 14136 (Solaris 8)

Here is what I am thinking,

On Prod Box
==> Freeze backing store
==>Backup backing store
==>Unfreeze

On Dev
==> Create new backing store
==> Restore prod backup
==>Restart teamsite
==>run iwfsck

TJRees

Based on our experience, for the most part, your sequence of events seems right. Couple of comments though --

On the dev server...
-- make sure that you copy the backing store to the directory/path you specified during the TS install.

-- make sure you have TS stopped before starting the copy/backup.

-- I believe you should run iwfsck prior to restarting TS.

Hope this helps...

pjacintorees@leggmason.com

Adam Stoller

Is your intention to copy ALL the historical versions from the PROD server to the DEV server?

Most DEV servers are not decked out with as much diskspace - and thus taking a *cut* of the backing store rather than the *entire* backing store is often preferable.

To do that - you generally want to use the iwmigrate CLT (between 5.5.2 and 5.5.2 systems)

There are a number of ways one can do this, but probably the simplest is to backup the PROD backing store to an online mounted partition; then unmount it from PROD and mount it on DEV. You'll then have to play around with stopping/starting TeamSite and editing the /etc/defaultiwstore file to point to whichever store you want active PROD-copy or DEV-empty (I'm assuming that there's nothing that you need to preserve in the existing DEV backing store here - if there is, then the steps become a bit more complex)

Then you migrate the latest edition for each branch from the PROD-copy store to the DEV-empty store. When you're done, you again stop TS, edit the /etc/defaultiwstore file, start TS and check out the results.

Does that make sense? Please look [for] at documentation on iwmigrate before asking questions about it.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

ashokc

Hi,

I am attempting the same - that is, copy the entire backing store from server A to server B, identical Solaris 2.8 servers. I am contemplating the following procedure. Any red flags?

(1) Stop Teamsite on Server A

(2) Tar up /iw-store on Server A => get iwstore_a.tar

(3) Stop Teamsite on Server B

(4) DELETE everything under /iw-store on Server B

(5) ftp iwstore_a.tar to Server B, to the location /iw-store

(6) untar iwstore_a.tar at this location

(7) Start Teamsite on Server B

Thanks for your input!

- ashok

Missing PDFs 01-Control Centre.jpg

Missing PDFs 02 - Platform.jpg

Missing PDFs 03 - Queues and Threadsjpg.jpg

gwen1

Keep in mind that if you are going to put the tar file in the same partition on your server as the new backingstore, you will need enough space for both.

Gwen

ashokc

Gwen,

But I am going to DELETE everything in /iw-store on Server B before I drop the tarred iw-store (iwstore_a.tar) from Server A.

Additionally all our users & groups are centrally administered so permissions on Server B should automatically come out exactly as they are on Server A - right?

Thanks

- ashok

gwen1

Be certain to create the tar and extract with the p option. That will maintain permissions

Until the entire backingstore is extracted and you remove the tar file, space will be taking up by the tar file. So you need enough for the tar and the backingstore. tar file though could be located any where on the server. Just be in /local when you extract the tar. We have also in the past compressed tar file. This can be uncompressed and extracted at same time, which may find some space savings. (Depending on #pdf files, etc. this may not buy a lot)

Gwen