[00:00] Sometimes you may need to make a backup of an individual project instead of the entire gateway. There's a couple ways to do this, so let's go over them. First way is going to the gateway web page and go to the configure section and then we're going to want to go on the left here to the projects page. We can go and click on the more button, next to the project we want to export. There're couple of different options but we're mainly concern with copy and export. The copy option will make a copy of this project on the current gateway, while the export option will export this project into a file that can then be taken to another gateway and upload it there or can be saved if anything would've happened to the project on this gateway. I want to know that by default you'll just have an export option. But if you have already gone into the designer and set your project to manually save and publish, you will have an export staging and export publish options here on this menu. I'm going to go ahead and export my project. You'll notice that when I export it, it downloads a file that ends in .proj which are ignition standard project files. If I wanted to restore this project to this gateway or another gateway, I can simply come back to this page and click the upload project from a .proj backup file. I can then choose the file. And once I've chosen the file and can hit upload. Now if the project didn't already exists it would simply upload the project but since it recognizes that a project already exists called training, it's going to ask me to fix that. I can choose to either rename the project or overwrite it. I'm going to choose to rename mine to training_2 and go ahead and hit apply. You'll notice now that I have a third project called training_2. Project backups are different from gateway backups and that they only include things that are unique to that project, such as windows, templates and transaction groups that are a part of that project. They do not include any of your tags, which are globally scoped or any other globally scoped resources, such as alarm pipelines or shared scrips. They also don't include any of your gateway settings such as any database connections you may have made or any device connections you have. It is important to consider what else you may need to export or note down when taking a project backup, if there're other important things that you need to keep record of. The other way to do a project backup is within the designer, I already have a designer opened up to this project. Here on the designer we can go up to the file menu and click the export option, here you can see exactly what get saved with a project export, including any of the reports that you've created in this project, any transaction groups and even the project properties. One thing that makes this project export different from the project export that you can take in the gateway is that here we can actually pick and choose which things we don't want to export. We can then hit export and then it'll ask us where we want to save our project export. Now, you may have noticed that all of our globally scoped resources here on the project such as alarm pipelines, shared scrips and shared templates were not included in that project export as they are not included in the project export on the gateway as well. However, here in the designer we have the ability to also export globally scoped resources that are located here in the project. To do this we simply go up to the file menu and go to export global. Notice that we now only have the option to export our globally scoped resources here in the project, such as any of the shared templates that we may have and any of the shared scripts or sequential function charts, like exporting the project from the designer, we can also pick and choose which global scoped resources that I want to actually export, move forward and hit the export button and choose where I want to save those global resources.