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

Backing up the Y: drive

Ottawa_IWOV

Can anyone explain the procedure for backing up the TeamSite Y: drive. From my understanding, the Y: drive is actually a virtual drive that is set up on the drive in which TeamSite is installed. For instance, if I installed TeamSite on a PC with one physical hard drive, the Y: drive will be a division of that. Therefore, when backing up, do you specify the Y: drive or the actual hard drive (i.e. C: or D Smiley Happy

. Or do you simply back up iw-store. Any clarification on this would be greatly appreciated.

Thanks.

Lucas Cochrane
lcochrane@dc.com

Find more posts tagged with

Comments

james1

Please read the fine manual. Do *NOT* back up Y:. Instead, back up the location of iw-store.

-- James

--
James H Koh
Interwoven Engineering

Migrateduser

You may want to backup some specific workareas on the Y: drive so that if a user loses a file you don't have to restore the whole backing store to get back the one file.

james1

Our consultants used to have a script that would recursively run "iwlistmod" on every workarea of every branch, so that modified files in workareas could be backed up without backing up entire workareas. I don't know if they still have that, and/or if they have something better.

-- James

--
James H Koh
Interwoven Engineering

Migrateduser

James is right, do not backup the Y: drive, it'll cause havoc on your disk i/o performance. You should backup the iw-store in a frozen state or deactiveate state (if you are using multi-store).

trevora

I recommend using a professional backup tool such as Robocopy that only backs up modified files.

I also backup the y: drive to allow for rapid content restores in case a user accidentally deletes something. I have had no problems so far.

ProfessorX

My 2 cents

There should be a posting or a KB article regarding this issue. What I do is back up {iw-store} (be careful..you need to freeze the store or shut down ts while doing this).

If I need only certain files from my backup. I shut down TS...swap out the stores. Bring TS back up...copy out the files I need. Bring TS down...swap em back. Bring TS back up copy those files to TS where needed.
Rinse and Repeat

The Professor-

Gregg Faus

As I stated in another thread. I do the following:

I wrote the following batch file and schedule it to run before the backup software grabs the data (in e:\iw-store-backup\):
@echo OFF
echo Copying Data...
rmdir e:\iw-store-backup\ /S /Q
mkdir e:\iw-store-backup\
iwfreeze +500
xcopy e:\iw-store e:\iw-store-backup /E /H /EXCLUDE:e:\exclusions.txt
iwfreeze --
echo Done Copying!

File: exclusions.txt
LOCKFILE

This works for us. Unfortunately it requires you to have double the disk space. I'm sure I could do incrementals with RoboCopy, but it is fairly fast.

ProfessorX

Thats great...unless your drive fails.

Would be better if you xcopied to a share drive.

The Professor-

Gregg Faus

Of course it'd be better if copied to a shared drive, but it wouldn't perform nearly as good, and we still have the data on tape in the event it ever fails. Even if you loose your drive, you'll still need to restore from the share.

So either tape or share, you're still loosing at most one day.

msrich

I'd like to have a look at that recursive script you mentioned.