Versions Compared

Key

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

...

1) Backup the DAM Database on Production & the destination DatabaseDatabase  (For Azure hosted servers, copy the backup files to the production storage drives) this will mitigate the need to transfer/copy the backup files to the Test server later in the process.
2) Stop Digibatch, digimonitor,website + application pools
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.

...

  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

...

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

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

...

Delete redundant (unattached) original test storage disk


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. Create a login for the SFTP server
  4. Configure Windows Firewall to allow Port 22
  5. Create a new Inbound rule for Port 22
  6. Start the SFTP server
  7. Install an FTP client on the Production Server, the recommended in WinSCP, it can be downloaded from here https://winscp.net/eng/index.php
  8. 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.
  9. Once connected you need to copy the contents of the following folders from Production to Test:
  10. Storage\DMM\Assets
  11. Storage\Frontend data

...