Skip to main content
  • EN

We are currently managing a Windows Agent backup policy configured in "Managed by Agent" job mode. The policy is set to perform a "File-Level Backup" and is configured to include the following objects:

  • E:\
  • C:\Windows\System32\LogFiles

We need to modify the policy to include the operating system volume in the backup. To test this, we cloned the job and made changes to the policy using a test machine. However, we encountered an issue: when we add the "Operating System" as an object in the "File-Level Backup" mode, running the job triggers a new active full backup of all volumes.

We observed the same behavior when changing the job mode to "Volume-Level Backup" or "Entire Computer"—an active full backup of all volumes is triggered on the next run.

Our primary concern is avoiding the need for an active full backup of the E:\ drive, which contains around 6TB of data. The servers are located at remote sites with slow links, making it impractical to re-seed the entire E:\ drive.

Could you please advise if there is a way to include the OS volume in the backup without triggering an active full backup of the E:\ drive?

Have you tried to include the OS drive and then use the “Map Backup” option on the Destination section of the Edit Job wizard?  That is the only thing I can think of to try and get the E drive to remap back to the existing backup files.

If you were to change the included C drive path you have now which is LogFiles to just C:\ (root) does that do what you need?  I don’t think you would need to change the job type just update the path included currently for the C drive to the root.

Try that and see if it works.

Have you tried to include the OS drive and then use the “Map Backup” option on the Destination section of the Edit Job wizard?  That is the only thing I can think of to try and get the E drive to remap back to the existing backup files.

If you were to change the included C drive path you have now which is LogFiles to just C:\ (root) does that do what you need?  I don’t think you would need to change the job type just update the path included currently for the C drive to the root.

Try that and see if it works.

Hi Chris,

Cheers for responding. 

The ‘map backup’ option doesn’t appear to be available - perhaps due to this being an agent managed policy? 

Changing the already included C: path to C:\ has the same impact in that an active full is triggered on the next run.  

I’ve logged a case with support as well to see if they have any clever ideas :)

Have you tried to include the OS drive and then use the “Map Backup” option on the Destination section of the Edit Job wizard?  That is the only thing I can think of to try and get the E drive to remap back to the existing backup files.

If you were to change the included C drive path you have now which is LogFiles to just C:\ (root) does that do what you need?  I don’t think you would need to change the job type just update the path included currently for the C drive to the root.

Try that and see if it works.

Hi Chris,

Cheers for responding. 

The ‘map backup’ option doesn’t appear to be available - perhaps due to this being an agent managed policy? 

Changing the already included C: path to C:\ has the same impact in that an active full is triggered on the next run.  

I’ve logged a case with support as well to see if they have any clever ideas :)

Yeah I think Support is the right road now to see why.  There has to be some logical reason for it to want to run a Full again.  Looking forward to seeing what response and solution you get so others can see as well.

Comment


Terms & Conditions