Presentation is loading. Please wait.

Presentation is loading. Please wait.

After completing this topic, you will be able to explain the Agent for Hyper-V: backup flows Agent for Hyper-V: Backup flows.

Similar presentations


Presentation on theme: "After completing this topic, you will be able to explain the Agent for Hyper-V: backup flows Agent for Hyper-V: Backup flows."— Presentation transcript:

1 After completing this topic, you will be able to explain the Agent for Hyper-V: backup flows Agent for Hyper-V: Backup flows

2 Backup Exec ServerHyper-V ServerInside VM Backup to disk/PDDE 1.Snapshot is taken 2.Used disk blocks determined 3.Used disk block optimization (NTFS) 4.Disk blocks sent to the BE server 6.Snapshot deleted 5.Disk blocks written to BKF files 7.Verify

3 Backup Exec ServerHyper-V ServerInside VM Backup to disk / PDDE with file and folder GRT (backup job cataloging) 1.Snapshot is taken 2.Used disk blocks determined 3.Used disk block optimization (NTFS) 4.Disk blocks sent to the BE server 9.Snapshot deleted 5.Disk blocks written to “new” VHD or VHDX 6.Disks mounted 7.File structure is read – logical sets created (NTFS agent) 8.Disks dismounted 10.Verify

4 Backup Exec ServerHyper-V ServerInside VM Backup to disk / PDDE with file and folder plus App GRT (backup job cataloging) 2.Snapshot is taken at the host level 3.Used disk blocks determined 4.Used disk block optimization (NTFS) 5.Disk blocks sent to the Backup Exec Server 6.Disk blocks written to “new” VHD or VHDX 1.Metadata collected Agent for Windows / Connection / trust / authenticate Copy snapshot taken Metadata laid down inside the VM by the application agents Snapshot deleted

5 Backup Exec ServerHyper-V ServerInside VM Backup to disk / PDDE with file and folder plus App GRT (backup job cataloging) (continued) 12.Snapshot deleted 7.Disks mounted 8.File structure read – logical sets created (NTFS agent) 9.Virtual Application PDI infrastructure created 10.Application agent used to walk application - logical sets created 11.Disks dismounted 13.Verify

6 Backup Exec ServerHyper-V ServerInside VM Backup to disk / PDDE with file and folder plus App GRT (separate catalog job) 2.Snapshot is taken 3.Used disk blocks determined 4.Used disk block optimization (NTFS) 5.Disk blocks sent to the Backup Exec Server 6.Disk blocks written to “new” VHD or VHDX 1.Metadata collected Agent for Windows / Connection / trust / authenticate Copy snapshot taken Metadata laid down inside the VM by the application agents Snapshot deleted

7 Backup Exec ServerHyper-V ServerInside VM Backup to disk / PDDE with file and folder plus App GRT (separate catalog job) (continued) 12.Snapshot deleted 7.Disks mounted 8.Drives discovered – empty logical sets created (NTFS agent) 9.Virtual Application PDI infrastructure created 10.Application agent used to discover – empty logical sets created 11.Disks dismounted 13.Verify 14.Delayed catalog job created Runs immediately When scheduled

8 Backup Exec ServerHyper-V ServerInside VM Backup to disk / PDDE with file and folder plus App GRT (separate catalog job) (continued) 15.Delayed catalog job starts Repeat until done Disks mounted One logical set processed A file system volume An application instance Disks dismounted

9 Backup Exec ServerHyper-V ServerInside VM Backup to disk / PDDE with SQL log truncation (separate catalog job) 3.Snapshot is taken 4.Used disk blocks determined 5.Used disk block optimization (NTFS) 6.Disk blocks sent to the Backup Exec Server 1.Metadata collected Agent for Windows / Connection / trust / authenticate Copy snapshot taken Metadata laid down inside the VM by the application agents Snapshot deleted Database names returned 2.SQL added to job for database names returned

10 Backup Exec ServerHyper-V ServerInside VM Backup to disk / PDDE with SQL log truncation (separate catalog job) (continued) 13.Snapshot deleted 7.Disk blocks written to “new” VHD or VHDX 8.Disks mounted 9.Drives discovered – empty logical sets created (NTFS agent) 10.Virtual Application PDI infrastructure created 11.Application agent used to discover – empty logical sets created 12.Disks dismounted

11 Backup Exec ServerHyper-V ServerInside VM Backup to disk / PDDE with SQL log truncation (separate catalog job) (continued) 14.SQL logs backed up Uses SQL agent You will see a “LOG” set in the restore view 18.Verify 19.Delayed catalog job created 15.Agent for Windows / Connection / trust / authentication 16.Log data sent to the Backup Exec Server server 17.Logs truncated

12 Backup Exec ServerHyper-V ServerInside VM Backup to disk / PDDE with SQL log truncation (separate catalog job) (continued) 20.Delayed catalog job starts Repeat until done Disks mounted One logical set processed A file system volume An application instance Disks dismounted

13 Backup Exec ServerHyper-V ServerInside VM Backup to tape with file and folder plus App GRT 2.Snapshot is taken 3.Used disk blocks determined 4.Used disk block optimization (NTFS) 5.Disk blocks sent to the Backup Exec Server 6.Disk blocks written to tape 1.Metadata collected Connection / trust / authenticate Copy snapshot taken Metadata laid down inside the VM by the application agent Snapshot deleted

14 Backup Exec ServerHyper-V ServerInside VM Backup to tape with file and folder plus App GRT (continued) 7.Disks mounted 8.File structure walked – logical sets created (NTFS agent) 9.Virtual Application PDI infrastructure created 10.Application agent used to read the application - logical sets created 11.Disks dismounted 12.Snapshot deleted 13.Verify

15 After completing this topic, you will be able to explain the Agent for Hyper-V: Restore flows. Agent for Hyper-V: Restore flows

16 Backup Exec ServerHyper-V ServerInside VM VM Restore from tape 2.A “new” VHD / VHDX file is created 3.The disk blocks are written to the VHD / VHDX file Repeat until done 5.Disk blocks are written to the VHD / VHDX file. 1.Data is read from the tape and sent to the Hyper-V host Repeat until done 4.Read data from incremental backups

17 Backup Exec Server Hyper-V ServerInside VM VM Restore from disk / PDDE 1.A “new” VHD / VHDX file is created 4.Disk blocks are written to the VHD / VHDX file 2.Disk blocks are read from the tail of the chain A disk block is only read / sent once Parent disks will be read as necessary 3.Disk blocks are sent to the Hyper-V host

18 Backup Exec Server Hyper-V ServerInside VM Application GRT restore from tape 1.Repeat until done Restage each set to disk Equivalent to the restore side of a backup job 2.Link the disks from each set together 3.Disks mounted 4.Virtual Application PDI infrastructure created 6.Application agent used to read data for restore 5.Connection made to target

19 Backup Exec Server Hyper-V ServerInside VM Application GRT restore from tape (continued) 7.Application data sent to target 9.Disks dismounted 10.Staging area deleted 8.Target does a normal agent restore


Download ppt "After completing this topic, you will be able to explain the Agent for Hyper-V: backup flows Agent for Hyper-V: Backup flows."

Similar presentations


Ads by Google