...
Transfer steps v4.zip Transfer steps v3.zip
Step-by-step guide
- Most of the scripts need inputs before you can run them!
Backup the DAM Database on the production server & the DAM database on the test server that will be overwritten
...
1) Backup the DAM Database on Production & the destination Database (For Azure hosted servers, these are normally saved in H:\SQLBackups) this will mitigate the need to transfer/copy the backup files to the Test server using FTP later in the process.
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)
3. Restore the databases
4. Check the ownership of the databases
...
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.
...
Once all searches have been repopulated, it´s time to test your DAM
How to Copy the Production Storage disk to the test server in Azure.
Steps:
- On the Test server, copy the following folders to one of the SQL disks (Webs, DZInstall & SQL Backups) ensure to cleanup the SQL Backups folder before copying
- Take a snapshot of the Production storage disk: (must be managed disks)
- Create a new disk from the snapshot (must be created in the test resource group)
- Remove the current storage disk from the test app server
- Mount the newly created storage disk on to the test app server
- RDP onto the test server and use disk management to ensure the disk is present and online.
- Restore the folders you copied in step 1 to their original location (Webs, DZInstall &SQL Backups) ensure that the production Database backup is not overwritten)
- Recreate the Storage share and set the permissions accordingly
Commence the database restoration process
Login to the Azure portal and search for virtual machines
Select the production app server
Select disks
Select the storage disk, which will be a standard hdd of at least 1TB is size
Select Create Snapshot
Create the snapshot in the Test resource group, ensure the snapshot is a standard hdd and give the snapshot an easily recognizable name
Click Review + Create, Once validation is passed then click create
Once the deployment if finished click Go to resource
Now click Create disk
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
Change the type to standard hdd and click OK
Click Review + Create and after Validation is passed, click Create
After creation click Go to resource
And check all is as it should be, correct resource group, size, type and unattached.
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.
Remove the current storage disk by clicking on the X and click save.
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
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
After the console has opened we need to add the disk management snap in, click File, Add/Remove Snap-In
Then select Disk Management and click Add
Ensure This computer is selected then click Finish
Then click OK, next double click on Disk Management (Local)
Ensure the disk is online and healthy, once confirmed you can close the mmc console
It important to check that the SQLDATA & SQLLOGS have the same drive letters as production, if not 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
Delete redundant (unattached) original test storage disk
How to Copy Assets from Production to Test using FTP. (Non Azure hosted Servers)
- 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
- Once installed on the Test server, configure the root folder to be Storage folder on the server
- Create a login for the SFTP server
- Configure Windows Firewall to allow Port 22
- Create a new Inbound rule for Port 22
- Start the SFTP server
- Install an FTP client on the Production Server, the recommended in WinSCP, it can be downloaded from here https://winscp.net/eng/index.php
- 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.
- Once connected you need to copy the contents of the following folders from Production to Test:
- Storage\DMM\Assets
- Storage\Frontend data
...
| Info |
|---|
Related articles
| Page Properties | ||
|---|---|---|
|
...