Whitepapers

Moving Edit Storage

Moving Edit Storage

Upgrading your edit storage can be a fraught and worrying process for any media production facility. Now Marquis Broadcast can present a number of alternative strategies to help you do this without risk, and with transparency at every step.

In this white paper we present a number of different strategies. Which one you choose will depend upon the way you organise your Avid projects and media, how confident you are that your editors follow that organisation, and the resources you have available.

Within the three different strategies below we will reference two of our products, Project Parking and Workspace Parking.

Scenario One - Backup first, restore by project

Scenario Two - Synchronise Workspaces

Scenario Three - Archive Projects

Project Parking offers an intuitive toolset to analyse and manage media to optimise shared storage utilisation. In one single application Project Parking analyses all Avid projects and media to identify which projects are using up most space and take appropriate action to transfer, archive or delete.

Within these scenarios, Project Parking can be used for both its archive and restore capability and its edit storage analysis and management functions.

Workspace Parking includes two types of workflows which are useful in the scenarios discussed here.

Workspace Parking Backup jobs create a backup of your workspaces on tier 2 storage. It identifies which projects reference the media and adds the project files to the backup, along with any additional media that those projects need (AMA or on other workspaces). No media is duplicated, no matter how many projects use it.

Workspace Parking Synchronisation jobs identify the changes on local workspaces and pushes those changes to a remote system, including all file creations, modifications and deletions.

 

Scenario One - Backup first, restore by project

This scenario is most appropriate if:

  • Your projects are in a limited number of shared locations, and  
  • You have some tier 2 storage available for backup, and    
  • You know that you will not need to move all of your projects to the new storage, or    
  • You know that your current storage has a lot of unnecessary media on it, or  
  • You want to have a full backup even after the transfer, just in case.

In this scenario we will create a complete backup of your workspace and any projects that use it, before transferring active projects and their media to your new storage. The stages are pretty simple:

  1. Find tier 2 storage of sufficient space to hold a backup of your workspaces, say 50% bigger to be safe. Backup your workspaces
  2. Use Workspace Parking to create a tier 2 backup of the workspaces to be transferred. As part of the process it will scoop up any projects that reference that media, and any additional media on other workspaces that those projects require. If they reference media that is off-line (perhaps local AMA media), you will be warned of that.1.2      
  3. Setup a regular nightly job to update the workspace backup, so that you always know that the backup is up to date at the beginning of every day.      
  4. Bring your new storage on-line.      
  5. Use Project Parking to restore each active project just before you move the edit clients for that project from the old storage to the new.Project Parking      
  6. Disconnect the Edit Clients from the old storage so that you can be confident that everything they need is on the new storage.      
  7. Work through all your live projects like this, transferring just a few each day so that you can be confident that all is well. If there is a problem, you can just roll them back to the old storage without a hitch.Project Parking      
  8. Once all the projects are migrated you can now use Project Parking to create an archive of any projects that you have not transferred for long term storage.        
  9. Once all the projects are transferred or archived you can recommission the old storage as you see fit.    
  10. You may now wish to switch Workspace Parking to backing up the new storage, that way you can be confident that you have a backup in case disaster strikes.

The big benefits of this scenario are:

  • You can move each project and all the edit clients for it one at a time, and be sure that they are happy before moving on to the next.      
  • As far as the users are concerned the process should be transparent.      
  • You do not transfer non-active projects, their media, or the ‘dark matter’ that has been using up space on your high value edit storage.    
  • You have a complete backup as safety before you even start the process.    
  • You can roll back easily if there is a problem.

 

Scenario Two - Synchronise Workspaces

This scenario is most appropriate if:

  • Your projects are in many locations, or      
  • You have an Interplay system with a large number of files not held in Media Composer projects, or      
  • You want to be sure that you have moved the entire contents of your workspace to the new storage, or      
  • You know that you want a one-to-one mapping between current workspaces and new ones,      
  • You do not need a full backup.

In this scenario we will synchronise workspaces between the old and new edit storage. Again the stages are pretty simple:

  1. Connect your new storage to the network, but only allow Workspace Parking to connect to it at first.2 1    
  2. Use Workspace Parking Sync to start a synchronisation job between your old and new workspaces.2.2      
  3. Setup a regular nightly sync job so that you know that the workspaces are in sync every morning.      
  4. Switch each edit client, one at a time, from accessing the old storage, to accessing the new one. You can even switch each workspace that each client uses one at a time if that works better for you.Workspace Parking      
  5. Ensure that when each client switches, they can no longer access the old workspaces. That way you know that the new storage has everything that they need. If there is a problem, just roll them back, and investigate. They’ll not have to stop working.      
  6. When all the workspaces are synchronised and all the clients have moved, check that no one is accessing the old storage at all, before recommissioning it as you see fit.

The big benefits of this scenario are:

  • You can move each edit client for it one at a time, and be sure that they are happy before moving on to the next.    
  • As far as the users are concerned the process should be transparent.      
  • You can be sure that the old and new workspaces have identical contents.      
  • You can roll back easily if there is a problem.

Optional Addition: Before starting this process, run a Project Parking storage analysis on the existing system and tidy up any Duplicate or Orphan material.

This will ensure that only active material will be synchronised.

 

Scenario Three - Archive Projects

This scenario is most appropriate if:

  • You have a limited number of projects which are in shared locations, and      
  • You have some tier 2 storage or an archive available, and      
  • You know that you will not need to move all of your projects to the new storage, or      
  • You know that your current storage has a lot of unnecessary media on it, or      
  • You want to have a full archive of every project even after the transfer, just in case.

In this scenario we will archive projects from the old storage before restoring them to the new. Again the stages are pretty simple:

  1. Start by archiving each of your projects to the archive using Project Parking, remember to check for missing media in the archive reports. Project Parking     
  2. Setup a nightly update of the archive so that you are not pressurised into making the switch immediately.        
  3. Connect your new storage to the network.          
  4. Restore projects one at a time using Project Parking Restore.            
  5. Switch each project’s edit client, from accessing the old storage, to accessing the new one.Project Parking            
  6. Ensure that when each client switches, they can no longer access the old workspaces. That way you know that the new storage has everything that they need. If there is a problem, just roll them back, and investigate. They’ll not have to stop working.          
  7. Switch the Project Parking archive jobs to archive from the new storage.Project Parking        
  8. When all the projects are restored and all the clients have moved, check that no one is accessing the old storage at all, before recommissioning it as you see fit.

The big benefits of this scenario are:

  • You can move each project one at a time, and be sure that the editors are happy before moving on to the next.      
  • You will always have an archive just in case something goes wrong, including a complete history of the project metadata from the day of the first archive.      
  • None of the unused media or ‘dark matter’ that has been clogging up your edit storage will be transferred – you get a clean and tidy edit storage system as part of the process.

 

Summary

Whichever scenario you choose will depend very much on how you organise your storage, the number of workspaces, projects and edit clients you have. The Parking range of products have the functionality to help you, whatever your needs. We even build new functionality to help our customers when we hear about new needs!

With over 5 years’ experience of helping many different users, with very different requirements and procedures, to backup, archive, tidy and manage their Avid storage, Marquis Broadcast has a wealth of experience to help you. 

Read 2414 times

About Us

Marquis moves media and metadata between different systems in broadcast and post-production workflows.

Head Office: +44 (0) 118 984 4111

Email: info@