Versions Compared

Version Old Version 28 New Version Current
Changes made by

Norman Cummins (Unlicensed)

Morten Boisen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Start by unzipping the content of this the relevant zipped folder - it contains all the needed scripts and the guide in PDF format. (Version 3 is for older DAMS pre DC5)

Transfer steps v4.zip       Transfer steps v3.zip

Step-by-step guide

  • Most of the scripts need inputs before you can run them!

...

FOR AZURE HOSTED SERVERS CREATE A SNAPSHOT AND DISK OF THE PRODUCTION STORAGE DISK, ATTACH THE NEWLY CREATED PRODUCTION STORAGE DISK TO THE TEST SERVER (this process is detailed further down this page, steps 5 & 6 are not needed for azure hosted servers)
2) Stop Digibatch, digimonitor,website + application pools (PLEASE NOTE THAT IN NEWER VERSIONS OF THE DAM DIGIMONITOR AND THE JOBS DATABASE ARE NO LONGER PRESENT)
4) Delete the logfiles for Digibatch, Digimonitor and websites (Optional)
5) Copy the .bak file to the database you want to overwrite. (Only for non azure hosted servers)
6) restore the databases
6b) Check the ownership of the databases (dam and dam_jobs). It should be an SA user.

...

NB: Step 15 + 16 + 17 + 18 + 19 is Only on older DAM Versions (pre DAM 5.02)
15) Login with admin_database name_dam (password =admin_database name_dam)
16) Run scripts for SB (2b_RebuildServiceBroker.sql + 2c_ServiceBrokerItemLastChanged.sql)

...

NB; Skip step 21 if DAM does not have the table install_config_actualsite
21) run the updateinstallAcctuallsite script (ONLY PRESENT IN OLDER VERSIONS OF THE DAM)
22) Edit the stored procedures you get from running the script: 5_GetSPs.sql replace the old database name (old DB name_dam_Jobs) with the new (new DB name_dam_Jobs)

...

23d) Start the Digizuite website and check you can log in
24) Update Digimonitor instances by running the script 6_UpdateDMInstance.sql (before running this script you should check if the environment is using an Ingest folder) you achieve this by logging into the DAM and looking at 2 workflows to check if they are in use. (ONLY PRESENT IN OLDER VERSIONS OF THE DAM)

Navigate to system tool, workflows select DigiFileWatcher, select Edit, then Edit on the Standard Import.

...

28b) Check for CDN configuration in Destinations. Make sure to change them to the enviornment environment if there are any. 
29) Configure Digibatch and re-enroll the job engines.
30) Start Digibatch
31) Check the jobs created by the "Repopulate the searches" are being processed.
32) Recreate and publish any SOLR searches - clean up the old ones. To clean up the solr searches perform the following steps

...

Once all searches have been repopulated, it´s time to test your DAM

How to Copy the Production Storaged disk to the test server in Azure.

Steps:

  1. Take a snapshot of the Production storage disk: (must be managed disks)
  2. Create a new disk from the snapshot (must be created in the test resource group)
  3. Remove the current storage disk from the test app server
  4. Mount the newly created storage disk on to the test app server
  5. RDP onto the test server and use disk management to ensure the disk is present and online.
  6. Rename the web folders to the Test folder website names, do the same for the log files UNC
  7. Recreate the Storage share and set the permissions accordingly

Commence the database restoration process

Login to the Azure portal and search for virtual machines

Image Removed

Select the production app server 

Select disks

Image Removed

Select the storage disk, which will be a standard hdd of at least 1TB is size

Image Removed

Select Create Snapshot

Image Removed

Create the snapshot in the Test resource group, ensure the snapshot is a standard hdd and give the snapshot an easily recognizable name

Image Removed

Click Review + Create, Once validation is passed then click create

Image Removed

Once the deployment if finished click Go to resource

Image Removed

Now click Create disk

Image Removed

Ensure the resource group is the test resource group, give the disk a name and change the type to standard hdd by clicking on Change size

Image Removed

Change the type to standard hdd and click OK

Image Removed

Click Review + Create and after Validation is passed, click Create

Image Removed

After creation click Go to resource

Image Removed

And check all is as it should be, correct resource group, size, type and unattached.

Image Removed

The next step is to attach the newly created disk to the test app server. Browse to the test app server in the azure portal and select disks.

Image Removed

Remove the current storage disk by clicking on the X and click save.

Image Removed

Once the virtual machine has been updated, you can now attach the newly created Production storage disk to the test app server by clicking Attach existing disks and selecting the disk from the dropdown box, ensure the host caching matches the other disks and click save

Image Removed

Once the virtual machine is updated, we are ready to logon to the test server over rdp.

Once logged into the server open an mmc console by clicking on the start button and typing mmc

Image Removed

After the console has opened we need to add the disk management snap in, click File, Add/Remove Snap-In

Image Removed

Then select Disk Management and click Add

Image Removed

Ensure This computer is selected then click Finish

Image Removed

Then click OK, next double click on Disk Management (Local)

Image Removed

Ensure the disk is online and healthy, once confirmed you can close the mmc console

Image Removed

It important to check that the SQLDATA & SQLLOGS have the same drive letters as production, if now SQL will not load until this is rectified. (Drive letters can be changed using Disk Management)

Rename the following folders: websites, Digimonitor and Log files to reflect the Test environment URLs 

Recreate the storage share and apply the relevant permissions

Rerun the Powershell installation for the current version (This will ensure all the passwords, usernames, urls and storage locations are correct

Now we are ready to commence with the database restoration process.

After completing the copy process, log back into the azure portal and clean up IE delete the snapshot you created and the redundant storage drive (original test storage drive)

Delete snapsot

Image Removed

Delete redundant (unattached) original test storage disk

Image Removed

How to Copy Assets from Production to Test using FTP. (Non Azure hosted Servers)

  1. Ensure FTP server software is installed on the Test environment, the recommended software is SolarWinds, it can be found here https://www.solarwinds.com/free-tools/free-sftp-server
  2. Once installed on the Test server, configure the root folder to be Storage folder on the server
  3. Image Removed
  4. Create a login for the SFTP server
  5. Image Removed
  6. Configure Windows Firewall to allow Port 22
  7. Image Removed
  8. Create a new Inbound rule for Port 22
  9. Image Removed
  10. Start the SFTP server
  11. Image Removed
  12. Install an FTP client on the Production Server, the recommended in WinSCP, it can be downloaded from here https://winscp.net/eng/index.php
  13. Once installed on the Production server, use this to connect to the Test server with the FTP login you created previously on the Test server.
  14. Once connected you need to copy the contents of the following folders from Production to Test:
  15. Storage\DMM\Assets
  16. Image Removed
  17. Storage\Frontend data
  18. Image Removed

Once the copying of Assets is complete they should be visible in both the DAM & Media Manager.




Info


Page Properties


Related issues


...