Archiving files before status or replan

[Matt Steele]

In my system I have over 30 projects all heavily interconnected with task
logic that spans projects.

Is there a process by which I can archive (versions? save as?) the whole
group and have their interproject task linkages refer to the new version and
not the sources?

In this scenario, if I rename ProjectA.Published and ProjectB.Published to a
new version (say: ProjectA.LastPeriod and ProjectB.LastPeriod), wouldn't
their interproject linkages still refer back to the .Published files?

The intent is to have a restorable file for any/all projects in case either
the status process, or a what-if replan totally screws up the current plan.

I appreciate any help on tools or process.
Matt Steele

 

[john]

Hey Matt this is Eric

How is your disaster recovery plan set up. How often are your plans
backed-up and will that be sufficient if you screw up a plan?

Have you considered setting up an Archive Instance of your environment?

Talk to you later

 

[Matt Steele]

Eric, good to hear from you.
I am not really looking for total disaster recovery, because the IT group
has us covered there. I am looking more to the Planners being able to
throw-out a screwed up plan and re-insert the last good one on a moments
notice.

Maybe the tool that restores a single project from a back-up is the way to
go for that, but I wanted the planners to be able to access the second
version via MSP and do compares. I am not sure that the archive instance will
permit that. Do you know?

Thanks.
Matt