Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Questions Regarding Content Migration

  Asked By: Sekhar    Date: Dec 15    Category: MOSS    Views: 807

I have a couple of questions.
1. When we migrate a Page using Content Deployment, what versions of the
Page will move?
2. If there is a Version mismatch of an existing Page in Authoring and
Production, what will happen? Will it migrate successfully? The scenarios
are a. Authoring Page (v4) needs to migrate to Production and the Production
Page is v2.

Please explain. Also, the SPList.GetChanges() needs a ChangeToken to
retrieve all the changes that happened before that Token was created. The
SPList has a CurrentChangeToken property. There doesn't seem to be
PreviousChangeToken. Can anyone throw any light on this?

Share: 

 

2 Answers Found

 
Answer #1    Answered By: Lorenzo Steele     Answered On: Dec 15

Content Deployment will always copy the most highest major version and the
most recent minor version. Depending on the timing of the jobs some major
and minor versions may be skipped. Depending on Security users will view
either the major version or the minor (draft) version on the production
site. But not all versions will be on the production site. This isn't a
problem because you wouldn't want to try to revert to a previous version on
the production site anyway. Any changes, including rollbacks, need to be
driven from the authoring/staging environment.



As the remarks on this site point out, the change token is used to limit a
query of the change log to either get all the newer changes or all the older
changes. It establishes a point in time. I assume you are looking for a
previous token so you can figure out a point in time to roll a list entry
back to. The change token really doesn't support that. You can revert a
list item to a previous version, but that is considered a new change, not a
rollback.

 
Answer #2    Answered By: Divakar Naik     Answered On: Dec 15

Forgot the link...

msdn.microsoft.com/.../...arepoint.spchangetoken.a
spx



Content Deployment will always copy the most highest major version and the
most recent minor version. Depending on the timing of the jobs some major
and minor versions may be skipped. Depending on Security users will view
either the major version or the minor (draft) version on the production
site. But not all versions will be on the production site. This isn't a
problem because you wouldn't want to try to revert to a previous version on
the production site anyway. Any changes, including rollbacks, need to be
driven from the authoring/staging environment.



As the remarks on this site point out, the change token is used to limit a
query of the change log to either get all the newer changes or all the older
changes. It establishes a point in time. I assume you are looking for a
previous token so you can figure out a point in time to roll a list entry
back to. The change token really doesn't support that. You can revert a
list item to a previous version, but that is considered a new change, not a
rollback.

 
Didn't find what you were looking for? Find more on Questions Regarding Content Migration Or get search suggestion and latest updates.




Tagged: