Wonderware Backups

Just zip the application folder.

You can delete all of the *.wvw, *.avl, *.??k files -- they're not needed in the archive.
 
That's all we do. I created a short batch file called "WW app cleaner.bat" with the following lines...

CD C:\Wonderware\Applications\WW application cleaner\application folder
del *.wvw
del *.avl
del *.*bk
del retentiv.*

When I do our backups, I copy the entire app into that application folder, run the batch file, then zip up the files for backup on a server. I do backups once a month and more frequently if doing major revisions. We also keep a hard copy log of all changes made. This makes it fairly simple to go back to a good backup and redo work done since the backup date if the existing app fails, gets corrupted or changes did not work as planned.
 
I use the NAD(Network Application Development) option and keep the apps in a shared folder on a server that is backed up nightly. That way if my dev node crashes, no problem because apps are on the server.
 
jshiepe said:
I use the NAD(Network Application Development) option and keep the apps in a shared folder on a server that is backed up nightly. That way if my dev node crashes, no problem because apps are on the server.

I wish that was a real option for me --- I support approx 45 plants all over North America, UK, and the Caribbean. Zips seem to be the most effective for my situation (and it's what I always did when was supporting just one plant)
 
OZEE said:
I wish that was a real option for me --- I support approx 45 plants all over North America, UK, and the Caribbean. Zips seem to be the most effective for my situation (and it's what I always did when was supporting just one plant)

I'll second that. Zipping the app folder is more effective
 
Yes if your backing up many individual plants zipping each one and keeping a copy on the machine and somewhere in the plant is the way to go. I also keep a copy on my machine and thumb drive. Let's just say I've been burned before.

But if you have the NAD environment setup up for multiple nodes sharing an application that is the the way to go for sure. If it crashes you simply copy the app from one of the other NAD nodes. This probably one of my favorite Wonderware functions but of course it has it's problems as well but we wont get into that here.
 
On version 7.0- 7.1 you may need to delete some of these bak files + some others in the scripts, If you have a lot of scripts I seem to remember we had a problem where we did some mods off site, renamed the directory to xxxxold & copied the updated one onto the pc on site, this would crash on scripting, by deleting some would cure the problem, so beware of backups, make sure you save the old one by renaming it.
 

Similar Topics

Hi guys, I have experience with PLC to Excel etc...just starting on using intouch scada screens. I have an Excel sheet that uses mainly...
Replies
1
Views
178
Hello everyone, Recently, my Archestra IDE shut down while I was editing. After restarting the IDE, I noticed warning symbols under my opened...
Replies
1
Views
117
Good morning all. I'm working on a rehab where they had a standalone InTouch 2014 HMI that they called a SCADA, but it's really basic stuff. The...
Replies
4
Views
207
Hi, We are setting up an Aveva Plant SCADA node with the intention to connect it to a Wonderware Historian node. Everywhere I look online I see...
Replies
1
Views
197
Hola chicos. Tengo un problema con el driver de comucicacion dasabcip 5, y un plc controllogix v34, ya realice la comunicacion pero en ciertos...
Replies
2
Views
178
Back
Top Bottom