Assuming you performed your reevert testing and decided to deploy reevert in production, what would it take to achieve that goal?
Here is a breakdown of main steps you need to take to deploy your reevert instances in production. If you have past experience migrating data from one file server to another, this will be an easy task for you.
Determine what needs to be migrated
Depending on how large your environment is, how many shares will be served or how different departments access their files, you may need to deploy more than one virtual appliance. This really is a choice that you, as a systems administrator, need to make. Following your current pattern of file server deployments may be a good place to start. You can review your current allocated file server resources and see if you need to make any changes, increase or decrease resource allocations. An important thing to remember: reevert is an all-in-one solution that will serve your files just like a file server, will handle your backups & recovery and will most probably do your offsite cloud backups as well. That being said, it may need more resources than a plain file server. To get more information regarding resource allocation, see here.
Deploy and Setup the virtual appliance
Once you know how many virtual appliances you need, your next step is to start deploying them. You can reuse your existing reevert test appliance. If your testing and production environments are isolated, you will need to re-deploy your new instances in your production infrastructure. You can redownload the appliance or reuse the copy of OVA file that you already have. There is no need to redownload the OVA file even if you need to deploy multiple instances. Import the appliance into your virtualization platform and go through the setup process to integrate it into your network. See detailed instructions to deploy and setup your reevert virtual appliance. See our administration documentation for steps you need to take once your instances are set up.
Layout a migration plan
Create a migration plan to migrate your data in phases. This is very important, especially if you have a lot of shares or multiple virtual appliances. If this is your first time, start with a less important share or file server. This will help you gain experience and minimizes any end-user impact in case there are issues. Remember to consider everything you need including automatic user drive mappings, etc.
Since this is an important matter, I’m dedicating a separate section to it. If your reevert appliances will be handling your cloud based offsite backups, it is best to get them connected to your Amazon AWS accounts and determine what type of backup policy you would like to use. See here and here for more useful information.
What tools to use?
There are several different tools out there that can be used to perform the actual data migration. We recommend using robocopy. It is a native Microsoft product and is included with Windows. It is a powerful tool to migrate your data from one location to another. The good thing about robocopy is that you can resume the copy process if it was cancelled for any reason. It will also only copy the changes if you need to rerun the process. In a nutshell, it works similar to rsync tool that comes with different UNIX flavors. There is an older Microsoft tool called xcopy that can be used to migrate your files; however, we recommend using robocopy. Read the robocopy documentation and create some batch files to make the migration process easier. Make sure to go over all needed options to migrate all file attributes including ownerships and permissions.
Post Migration Considerations
We recommend closely monitoring your appliances for a week or two. Pay attention to automated weekly usage reports that you receive from reevert to find out if you need to make any resource allocation adjustments.
For a hassle free 30 day trial, click the "Free Trial" button, download and deploy a copy of the appliance. No Credit Card required.