How to purge (permanently delete) a project from the archive


Warning: Using the Permanently Delete Project From Archive feature will fully delete all data associated with the project from the archive. This will remove all data and cannot be undone.


To permanently delete a project from the archive:

  1. Open CloudM Migrate.
  2. On the Projects page, ensure that you select the relevant project from drop down menu.


  1. Select the Cog icon underneath the drop down menu to expand the section, displaying some Actions that you perform on the Project.


  1. Select the Permanently Delete Project From Archive feature from the list of options.
  2. A warning box will pop-up, prompting you to confirm whether you want to continue with the process. This is to avoid any accidental deletion and warns that the project cannot be restored once the action has been confirmed. Select OK to continue.


  1. The project will be deleted from the archive.


For CloudM Migrate installations that use an existing standalone SQL Server instance, grant the VIEW SERVER STATE and ALTER ANY CONNECTION permissions to the PoweredBy account.

  1. From the SQL Server Management Studio via GUI, connect to the SQL instance as a System Admin,
  2. Navigate to Security > Logins,
  3. Right click on PoweredBy > Select Properties,


  1. Select the Securables page
  2. In the bottom panel, scroll to the top and grant the ALTER ANY CONNECTION permission.


  1. In the bottom panel, scroll to the bottom and grant the VIEW SERVER STATE permission.


  1. Select OK to confirm the changes.


From the SQL Server Management Studio via statement: 

  1. Connect to the SQL instance as a System Admin
  2. Select New Query
  3. Execute the following statements


While doing this, you may encounter an error: "Invalid Urn filter on server level: filter must be empty, or server attribute must be equal with the true server name"

This can happen if the host name (computer name) of the machine does not match SQL Server server name. For example, if the environment was cloned to another machine with a different name. 

One of the solutions, which can be used at your OWN RISK, may be renaming the existing SQL Server so it's name will match the host name.
  1. Obtain the host name by executing "hostname" in cmd. This will display the hostname of the machine without the domain,
  2. Obtain SQL Server name by executing new query "select @@servername" in SQL Management Studio.
  3. If the names don't match (and in the case of this error, they probably won't match), then execute:
sp_dropserver <old_name>;
sp_addserver <new_name>, local;
or, in case of named instance:
sp_dropserver <old_name\instancename>;
sp_addserver <new_name\instancename>, local;
  1. Restart the instance of the SQL Server


Was this article helpful?
0 out of 0 found this helpful