Site Manager - Wish List


Author
Message
SchanzerIn
SchanzerIn
New Member
New Member (8 reputation)New Member (8 reputation)New Member (8 reputation)New Member (8 reputation)New Member (8 reputation)New Member (8 reputation)New Member (8 reputation)New Member (8 reputation)New Member (8 reputation)New Member (8 reputation)
Group: Forum Members
Posts: 1, Visits: 16
Good day,
I'm a Marcrium Site Manager FAN, but I still find the options for managing the backups very limited at the moment.

Here is a list of what I currently want:

1. No option to assign your own image name via the site manager.

All's example:
For better management, I would like the following information in the file name of the image file -> "Computer name" - "Windows version" - "Backup type"

With the Macrium Reflect Agent it is possible to give the image file a name including parameters ({PCNAME}-{WINVER}-{BACKUPTYPE}).

However, when creating a new backup job via the Site Manager, you cannot assign your own image name.


2. I can't find locally created backup jobs in the SiteManager at the moment.
I would like to be able to see and edit them here.


3. Backup jobs created by Macrium Refelct Agent can be exported to an XML file.
Here would be a nice way to import them into the Site Manager.


4. Ability to block processing of locally created backup jobs in the local agent.
  (Processing only after entering a password?)

5. Possibility to create SQL database jobs via the SiteManger.

6. Custom email delivery:
  So one possibility, for example, to send all emails relating to server 1 - server 20 to email address 1.
And server 20 - server 50, on the other hand, should send its mails to mail address 2.

7. A synchronization possibility of folders or files.
So no classic backup image of files but a way to sync a source folder with a target folder, for example every 1 hour.

Similar to what AOMEI Backupper already does: https://www.ubackup.com/help/file-sync.html

8. When backing up all hard drives in the system including the operating system / (full backup) exclude individual folders from the backup.

For example, we have a folder with event images in a production machine, which quickly grows to over 300 GB and does not have to be backed up.

9. In the case of defective sectors/blocks, the backup defined in the Site Manager is aborted.
One possibility here would be to be able to carry out a backup using the SiteManager despite the defective sectors.

Currently I only have the option to create a local backup definition.
Since there is only the possibility to allow backups in the case of defective sectors/blocks on the local client.




I hope these functions will soon be available in the SiteManager, since I have to say that the range of functions is currently very modest compared to the competition.

Currently I have to create the backup jobs locally on the client to get the desired image name.

My goal would be to be able to create all jobs directly and completely using the SiteManger.

Thanks for listening

Max
Edited 29 January 2023 5:07 PM by SchanzerIn
uit
uit
Talented Member
Talented Member (133 reputation)Talented Member (133 reputation)Talented Member (133 reputation)Talented Member (133 reputation)Talented Member (133 reputation)Talented Member (133 reputation)Talented Member (133 reputation)Talented Member (133 reputation)Talented Member (133 reputation)Talented Member (133 reputation)
Group: Forum Members
Posts: 68, Visits: 99
+1
drstimpson
drstimpson
New Member
New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)
Group: Forum Members
Posts: 2, Visits: 11
uit - 7 February 2023 5:37 AM
+1

Reiterate request for the improvements listed above, especially:
1. Custom file naming of the .mrimg files
2. Custom or per Agent (AKA backed up device) Email Notification contacts (so admins of specific devices can receive email for their devices but not all devices)

I would also like to add for at least on Local Repositories the ability to flatten the path for storage of the .mrimg files to the root of the target, and not the subfolder structure currently used. If I define a repo to write to a specific Agent's locally attached drive (say for a device across a VPN link), but defined at the Site Manager server level so I can monitor it live, as a drive letter and folder, I would like the mrimg files stored at the root of that folder.
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search