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

Unsuccessful deployment causing problems

iwkash

Hello All,

Recently we tried to push a few files through OpenDeploy (filelist depl.) using a script with single deployment name, single definition and multiple nodes within (transactional = yes).

Due to an improper filelist(the absolute path of the entire workarea was passed instead of a relative path), the OD settings started taking backup of the target parent folder "C:\A\ABC" as "abc.old" and "abc.new"(folder size being huge and hence the deployment was going on for about an hour). The OD services were stopped seeing this on the target servers and hence the entire process was interrupted in between.

There were some files/folders missing in the parent target folder. This may be due to incomplete restoration of the "abc.new" folder into original "abc" folder. However, more surprising was the deletion of a few files/folders on the source teamsite path. The files deleted on target and source are not similar.

Any help on this?
Teamsite - 6.7.1 || OD - 6.2.1 || Target- Windows/ IIS servers

Thanks!!!

Find more posts tagged with

Comments

Adam Stoller

If you still see the .iwold files and directories on the target side - I suggest you move them back into place (without the .iwold extension, removing anything that looks like that without the extension first) - and then retry your deployment.

iwkash

Hello,

OD is working fine since we restarted the services. This works well if we ensure that the filepath would always be relative.

However, the point of concern is that a few files/folders have been deleted from the source and we are trying to investigate the reason for the same. It may be the case that a complete rollback could not happen as we stopped the OD services in between. But the rollback doesn't delete any files from source and restore them with the archived version(.iwnew - our assumption). So the main question is - "why did the files/folders get deleted from SOURCE?"

We are lucky in this case to have a backup of the folders on our local machine and hence this isn't critical. However, it would be great if any of you could throw some light on how OD works end-to-end and the significance of .iwold and .iwnew folder with their actual stages of creation as well as the effect of the same on source and target folders.
Teamsite - 6.7.1 || OD - 6.2.1 || Target- Windows/ IIS servers

Thanks in advance.

Adam Stoller

... So the main question is - "why did the files/folders get deleted from SOURCE?"

We are lucky in this case to have a backup of the folders on our local machine and hence this isn't critical. However, it would be great if any of you could throw some light on how OD works end-to-end and the significance of .iwold and .iwnew folder with their actual stages of creation as well as the effect of the same on source and target folders.
Teamsite - 6.7.1 || OD - 6.2.1 || Target- Windows/ IIS servers

Thanks in advance.

I don't know how anything got deleted on the SOURCE side - my guess is that if it did, it had nothing to do with OD itself (though possibly a DNR script, even that seems unlikely).

.iwold and .iwnew files generally come into play with transactional deployments (I think it uses .iwtmp for non-transactional, but perhaps not - it's been a while since I've actually paid any attention to that).

In Non-transactional deployments - source file "foo" is deployed to the target system as "foo.iwnew" and once successfully written there, the pre-existing target side "foo" would be renamed to "foo.iwold", the newly deployed file is renamed into place as "foo", and the old file is deleted.

the files (this includes and DNR scripts that may run before the end of the deployment process that may signal failure to OD) - and it is for this reason, if you are doing multiple concurrent transactional deployments - that you should make sure to enable receiver-side queuing (read the manuals and KB articles for details) to allow for such deployments to occur in an orderly manner.Does that answer your question about iwold and iwnew?

iwkash

Yeah....Thanks for the prompt reply. I will keep the thread open for sometime in case anyone has something to add on this scenario.

Best Regards!!!