header 28

Migrating to Strawberry

One of the greatest advantages of Strawberry is that it can be installed onto existing storage infrastructures, no matter if based on gigabit ethernet, fiber channel or even a combination of the two. Because the media never has to pass the Strawberry hardware directly, you will never experience any loss in performance or redundancy on your existing storage systems.

Connectivity

The standard Strawberry appliance comes with two 1Gbit Lan ports to be connected to your storage system. Optionally, 10 gigabit ethernet or fiber channel interfaces are available.
For NAS/SAN (or mixed) workflows Strawberry can be connected in the following way:

In order to send commands to the file system, the Strawberry appliance should be connected to the storage device directly with gigabit ethernet or fiber channel. This connection is for the sole purpose of controlling the storage file system. No media files will ever be exchanged between the Strawberry appliance and the actual storage.

Editing systems are connected to the storage device via gigabit ethernet or fiber channel, and to the Strawberry appliance with gigabit ethernet. The exchange of media files takes place between the editing systems and the storage directly, so Strawberry causes no bottleneck effect.

Connectivity

Failover option

Strawberry provides an HA option for customers who desire high availability within their workflows. Customers requiring HA need two Strawberry appliances and a high availability license. In the unexpected occurrence that one appliance fails, the second will take over without any interruption to the work in progress.

Can media files be accessed without Strawberry?

Yes! With Strawberry you can access your media at any time with or without the Strawberry appliance. When you examine your storage device, you will find a clear project structure where each of your editing projects has a dedicated folder. From this lucid structure, files can be copied or moved to another storage device or local drive.

What happens to existing media files on Strawberry devices?

The simple answer is: Nothing. On the storage side, Strawberry simply creates a new folder where future editing projects will be organized in subfolders automatically. For migration, you don’t need to format any drives nor delete any media when using SAN or NAS storage. This characteristic of Strawberry is unique compared to other products on the market.

How will editing projects be migrated to Strawberry?

Strawberry only recognizes editing projects and media files that are in the Strawberry folders within the storage device. Projects that are not in this structure are not available for Strawberry’s collaborative editing or project management features. However, there are several ways to migrate your new and existing editing projects to Strawberry.

1. The Slow Migration

Slow migration means that Strawberry and your existing workflow are taking place side by side

Slow migration means that you need only move old editing projects onto Strawberry as needed, so that your old projects and new ones exist side by side. New projects will be created using Strawberry, so they will be available for project sharing and management, while old files will remain available to you until you are ready to transfer them to Strawberry. This migration method is recommended to companies that already have a very large production storage environment with a lot of editing projects that cannot migrated overnight.

1. The Slow Migration

Slow migration means that Strawberry and your existing workflow are taking place side by side

Slow migration means that you need only move old editing projects onto Strawberry as needed, so that your old projects and new ones exist side by side. New projects will be created using Strawberry, so they will be available for project sharing and management, while old files will remain available to you until you are ready to transfer them to Strawberry. This migration method is recommended to companies that already have a very large production storage environment with a lot of editing projects that cannot migrated overnight.

2. The Overnight Express“

In this migration process, all of your existing editing projects will be migrated en masse during an inactive production phase, for example overnight. The operator creates a folder in Strawberry for each editing project they wish to move. Then, he or she moves the media files of those projects into the related folders within Strawberry. Depending of the amount of existing projects, this can take quite a while to be completed. The enormous benefit of this method is that upon completion, all of your editing projects are ready for project sharing and project management.

FlavourSys recommends a mixture of both migration options. New projects should be created with Strawberry and old projects, if required, moved to the Strawberry operating system.

2. The Overnight Express“

In this migration process, all of your existing editing projects will be migrated en masse during an inactive production phase, for example overnight. The operator creates a folder in Strawberry for each editing project they wish to move. Then, he or she moves the media files of those projects into the related folders within Strawberry. Depending of the amount of existing projects, this can take quite a while to be completed. The enormous benefit of this method is that upon completion, all of your editing projects are ready for project sharing and project management.

FlavourSys recommends a mixture of both migration options. New projects should be created with Strawberry and old projects, if required, moved to the Strawberry operating system.