Moving files to another File Server

You may consider moving files to another File Server if you have multiple File Servers registered. If you would like to remove a File Server, but it still contains file that are referred to by blueprints, deletion is blocked.
You can move files to another File Server, which allows you to remove the original File Server.
Both File Servers must be registered in Platform Manager.

To move files from a source File Server to a destination File Server:

1. Copy the files manually from source to destination file server.

2. Update the file assignment in Platform Manager.

3. In the following example, there are two File Servers, OFS-1 and OFS-2. You want to remove OFS-1, but it contains files that are assigned to blueprints, so you want to move these files from OFS-1 to OFS-2.

   1. Assume that both OFS-1 and OFS-2 are registered with the same Platform Manager.

   2. Manually copy the desired files from OFS-1 to the user file location of OFS-2.

   3. After you have copied the files, restart OFS-2. This makes the OFS-2 database discover the new files.

4. To copy all files from super-user named PM_da16 on local File Server to user PM _da15 on a remote File Server.

   1. Log in to the Linux CLI of the source File Server and run the following command (replace the IP address with the address of the destination File Server):
      scp /home/tomcat/OFS1/files/PM_da16/* 10.46.27.15:/home/tomcat/OFS1/files/PM_da15
      Where:
      PM_da16 is the local super user
      PM _da15 is the remote super user
      OFS-1 is the source File Server
      OFS-2 is the destination File Server

5. Click Configuration > File Servers and select the source server name in the table. At the bottom of the page is a link to assign files to another server: Use this link to assign files on this server to another server.

6. On the Reassign File Server Files page, confirm your source File Server.

7. Select the destination File Server (OFS-2), and click Start File Reassignment. This command checks all files on the source File Server and, after confirming that the file now exists on the destination File Server, updates the database to change the assignment to the destination File Server.

To confirm the file reassignment has occurred as intended, check the system logs and look at the associated File Server listed in the file table.

• Navigate to Configuration > Files.

Register and upload required files

Resource blueprints require that certain files be registered with the Platform Manager. They are then supplied to the infrastructure, as needed.

To register and upload files:

• Upload a file.

• Indicate its type.

• Choose a file server to upload the file to.

For every uploaded file, you can click the filename to see detailed information about the file, including size and MD5 checksum. On the Platform Manager web panel, navigate to Configuration > Files. You can also delete a file on this page.
Your file supplier should provide you with its MD5 checksum. After uploading any file, verify the MD5 checksum found on the File Server with the MD5 that came with the file. If it does not match, confirm that your local copy of the file has the correct MD5. Then delete the file on Platform Manager and do the upload again.

When a file is associated with a Blueprint, the files are locked and the files can not be deleted. You may delete any file that is not associated with a blueprint, so deleting a blueprint unlocks any associated files.
File names must be unique. When uploading a file, Platform Manager verifies that this file name is not already listed in the Platform Manager database. If a match is found, the upload will not be permitted.

File types

When uploading a file, you indicate the file type. These types are used to categorize files for presentation in the Blueprint builder. Supported types are:

• MiVoice Business (MiVB) image: This is a specially packaged version of the MiVoice Business installation software, available on Mitel OnLine. These files are referred to by MiVoice Business Multi-Instance resource blueprints. An example filename is ICP3300_13.2.1.33.tar.gz.

A MiVoice Business image file contains a MiVoice Business software image suitable for installation into the software inventory of a MiVoice Business Multi-Instance server. You need a tar file containing the MiVoice Business installation software and an md5sum file containing the MD5 checksum of the file. Mitel supplies these files.

After uploading the file to Platform Manager (File Server), verify that the MD5 checksum of the file, as it exists in Platform Manager, matches the MD5 checksum supplied with the file.

• MiVoice Business (MiVB) backup file: This is a backup file produced by MiVoice Business in .tar format. These files are used by MiVoice Business Multi-Instance resource blueprints.

A MiVoice Business Multi-Instance Backup file is a golden MiVoice Business database file for use on MiVoice Business Multi-Instance servers. Following the creation of a resource on a MiVoice Business Multi-Instance server, this golden database can be restored to the MiVoice Business Multi-Instance tenant. This results in a configured MiVoice Business instance.

• Mitel Integrated Configuration Wizard (MiCW) config file: This is an MiCW-produced configuration file in either .xml or .zip format. These files are used by MiVoice Business Multi-Instance resource blueprints, They typically contain an initial MiVoice Business configuration for application to a newly created MiVoice Business instance.

You can apply a configuration wizard file during creation of MiVoice Business Multi-Instance tenants. This results in creation of a configured MiVoice Business instance.

Example
ICP3300_13.2.1.27.tar.gz
ICP3300_13.2.1.27.tar.gz.md5sum