Backing up best practices?

Wanted to get a sense from all of you Teamsite masters out there in regards to publishing, backing up, and restoring best practices.

Currently I do infrequent filelist deployments and have no procedure in place for frequency of edition publishing. I've got ts being backed to tape nightly.

What are your proceedures? Looking for input.
Thanks,
Nico

Find more posts tagged with

Comments

tvaughan

I've got a similar situation -- semi-frequent file list publishing without a coordinated web office to drive large, scheduled site publishing.

I've got a cron running every Wed at noon to publish an edition for all of my branches.

I've also got a nightly incremental backup running that's completely out of my jurisdiction. The sad thing is, that nightly backup is backing up the backing store, not the virtual /default filesystem, which means I'm "limited" to the file history and edition frequency within TeamSite for rapid data recovery.

I say "limited' with quotes because TeamSite is quite good, but its just that in a bad scenario, I'd have to restore the entire backing store for to recover what might be a small amount of data.

Tom

Adam Stoller

If you're using TeamSite 5.5.2, every submit operation creates a 'hidden' edition (iwlist -k /default/main/branch/EDITION) - as long as your backing store isn't corrupted you can retrieve versions of files from those editions (although you can do pretty much the same thing through the GUI View History, or the iwrevert CLT (if you know the version number).

Also, in 5.5.2 - publishing does not represent a significant overhead like it used to in pre-5.5.2 releases (which is why the hidden editions can be created) - so don't be afraid to create daily editions rather than weekly ones, if that will make your life easier.

--fish
(Interwoven Senior Technical Consultant)