Hi Dojo,
quick info: are there any config files that can be used to finetune the backup options in a DMS?
As an admin, I’d like to specify different retention policies for the local and the network path
(e.g. 5 copies on the network drive and just 2 locally on the agent), so that I can save space on local disks but keep enough history in the network storage.
The DMA policy seems to be unique in the GUI:
Slightly related: when working with local drives, I seem to observe that despite specifying “D:” in the local path, the backup archive is written on the drive where DataMiner is installed (e.g. “C:”) before being transferred to the specified directory – I can understand why, but is it possible to tweak these settings (somewhere else) so that the archive is directly written on “D:”?
in this example, I could see that the disk usage for “C:” was almost the same across DMA1 & DMA2, despite specifying “D:” for DMA1:
Thanks
This question sheds some light on a workaround that changes the temporary location using symbolic links. Highly recommended to test this in a staging environment first.
Thanks for the hint, Wale: I’ve checked the comments in the thread and I’ve retrieved this from Alex:
“[…] As a workaround, you can create a symbolic link to change the actual location of “C:Skyline DataMinerBackup” to a different drive. The command to create a link should be something like this:
mklink /J “D:Skyline DataMiner Backups” “C:Skyline DataMinerBackup”
Please keep in mind that this is just a suggestion, not the official solution for this issue. […].”
I guess it’s safer to expand “C:” in VMs, where this is easily achievable;
for hardware servers, may need to check this or Bens’s suggestion.
As for the wider scope of the post, I’ve logged a feature suggestion so that the back-up retention policy for network storage can be different from the one for local back-up:
HTH
Hi Alberto – not entirely sure, so you may have to wait for more knowledgeable people to respond, but I do believe this might be running off a script triggered by the underlying Windows Task Scheduler. In which case you could probably modify that (check the Task Scheduler in Windows to find the script). Just a hunch / something I vaguely seem to recall. And if this is the case and you modify it, you might consider renaming that script and scheduling that one (and disable the one set via the System Center).
Thanks for the prompt feedback, Ben – will look into your hint while I wait for some more answers as you’ve suggested – ideally, looking for something that doesn’t need to be manually re-patched after DM upgrades (this might be beneficial especially for those who follow the “feature release” branch).
A feature suggestion was submitted to achieve this:
https://community.dataminer.services/new-feature-suggestions/backup-process-in-a-dma-ability-to-specify-more-options-than-what-is-currently-defined-in-the-gui/