Category Archives: Posts

She said I’m Tragically Hip

Come on, just lets go!

She kinda bit her lip…geez I dont know

I’ve written non tech related posts here before – usually it takes something near and dear to my heart to spark them. Hockey and music was kinda my crutch throughout my life – In the spirit of share, and the spirit of getting 30 posts out in 30 days this one will deal with the latter


For those that don’t know there’s an iconic Canadian band called The Tragically Hip   Their lead singer, Gordon Downie announced earlier this year that he had incurable brain cancer, you know, the shitty kind, as if their was a kind that wasn’t. Instead of undergoing treatment and calling it quits The Hip announced a country wide tour, starting in Vancouver, 15 shows later ending in their hometown of Kingston, Ontario – a small quaint city not far from where I live now and a place I called home for some time during college!

God knows I tried to get tickets – I was online right at 10 o’clock the day they were released and I had four in my shopping cart but during check out something happened – I along with many, many other people, tremendous other people (see what I did there :)) doing the same thing were denied and the tickets were gone within seconds.  Sheesh, you’d think these ticket companies could get some better IT behind these types of things!  But this wasn’t just for the Kingston show but for every show they had planned!  Within minutes of that you could see tickets popping up on StubHub more than 500% their face value!   Needless to say I wasn’t going to this one.  As a tour started the band tried to accommodate this by releasing new shows and holding lotteries for new tickets available only to people who could pick them up at the door of the venue!   Again I tried but was left dissapointed again!

So, in the end we were left with a country trying to mourn someone they grew up with and couldn’t get into see his, what some called,  last show!  Then to my surprise CBC  picked up on this and worked out a deal that would have final show, August 20th in Kingston, live-streamed across the country.   Satellite, Internet, CBC Mobile, Facebook, YouTube –  it was going to be on every media channel across Canada. So with all that said projectors went up in backyards across Canada!   Market Square in Kingston packed in 30,000 people,  the most they have ever had gather downtown to see what many were calling the final concert.  One of those 30,000 – our newly minted Prime Minister Justin Trudeau.


Personally, I gathered in one of those backyards with some close friends to watch the concert, have some drinks, and celebrate the life of a man who had entertained me my entire life.  The music was great, the drinks were great (as always), but the biggest thing I took away from that warm night in August was the memories.  The whole night was full of friends reliving memories together – “Remember when?”  “This song reminds me of that time…”  Friends reminiscing, replaying times in their minds.  Seeing people whom I haven’t in quite a while, remembering times with some who are unfortunately no longer here.  This is what I took away from that night – memories, friendships, recollections of the handful of times I’ve saw them perform.

Before the show there was so much chatter on what he might be like, will he look ok?   And 15 seconds in I think we all saw the same ol’ Gord we have so many times before.  For nearly three hours he took us on a journey from that bar band that started out in Kingston to the national treasure they are now.  Even in his condition he used his time wisely, using the viewership of 11.7 million people to help spread the word about Canada’s struggles and ignorance towards the residential school issues of the past – that’s a whole other shameful post to be written though….

Though entertaining it was all but bittersweet seeing his interview a month or so after with Peter Mansbridge on CBC.  There, Downie declared he is indeed suffering, requiring 6 prompters on the stage in order to remember the lyrics of his own songs, having Mansbridges name written on his hand just so he can remember who he is talking to – even though they have known each other for some time…having to struggle to remember his kids names…

“For some reason every line, I just couldn’t, it’s the worst kind of punishment”, he said, “It was one savage kick in the pants, can’t remember peoples names and can’t remember lyrics”

A musician, an artist, a poet – who can’t remember lyrics.  A father, a husband, a friend – who can’t remember your name – Thinking of all this, it reminds to cherish, cherish what you have now, celebrate what you have now – someday it may no longer be there.

I mention “the country” a lot in this post – don’t get me wrong, it’s not all of Canada.  As with any music people have personal tastes and for some The Tragically Hip just isn’t their flavor of choice.  But, no one, no one can argue that something happened in our Country the night of August 20th – This group, this man, united our country and during that time their was not a sole that could claim they weren’t touched somehow by having been a part of it!  Personally, I feel more thankful having been part of that night – thankful for what I have and holding it tight – for someday it will all end and I’ll just be floating through Fiddler’s Green.

Friday Shorts – VMware, Veeam, Docker and Community

Dreams are important!  Otherwise, sleep is just 8 hours of nothing. – MacGyver

vSphere 6.5 is here!

VMware LogoNDA’s have been lifted and the flood gates have opened in terms of bloggers around the world talking about vSphere 6.5!  Now that the product has finally been declared GA we can all go ahead and download it today!  Certainly the new HTML5 client, the addition of a more functional vCenter Server Appliance and built-in disk level encryption are enough to make me want to make the jump…eventually 🙂  That said there is a lot that is new with vCenter and ESXi – you can check it all out here.

Veeam Backup & Replication 9.5 is here!

veeamlogoAnd just as VMware releases it’s flagship hypervisor software to the masses Veeam follows behind one day later with the support and availability back it all up with their updated release of version 9.5 of Backup & Replication.  There is a lot that’s new within this release – check it all out here!  With Nimble support and a ton of integration with other Veeam products such as the Veeam Agents this release has a lot – but perhaps some of my favourite enhancements will be the ones that will probably not be written about the most and that’s all of the engine enhancements and things like the vSphere inventory cache.  As with most Veeam releases I’m sure this one will be well adopted!

Tech Field Day 12 – that’s a wrap!

tfd-logo-100x100I’ve just returned home from Tech Field Day 12 in beautiful San Jose!  I say beautiful but I was told it was cold by multiple people there – that said, I’m Canadian, and 18C in the middle of November is not my idea of cold 🙂  Either way I sat with 11 of my peers around the TFD table for a couple of days and got blasted by the fire hose.  There was some great presenting companies there; think Dell-EMC, DriveScale, Rubrik, Cohesity, StorageOS, Docker, and Igneous.  Expect more in this space about what these guys had to talk about but for now if you want to check out the videos you can do so – links are all over here.

Fancy some community recognition!

Ah, November – cooler air, the transition from Halloween to Christmas – and of course, a flurry of forms to fill out if you’d like to be included in any vendor/community recognition programs.  Most of these things require you to nominate yourself – so suck up any pride as you may have to get a little self absorbed while you try and brag yourself up.  Recognition programs are a funny thing – Some are great, some are so-so – I’m not going to go into the details of each.  If you want a great spot to see a list of them all Jim Jones has a great post outlining everything here.  And to get a glimpse into one of my favourties, the Veeam Vanguard program – check out Matt Crapes post here.  I’ve also been invited to the KEMP VIP program – which is new to me so expect to see more about that as well in the future.

Beetlejuice, Beetlejuice, Docker

docker-logo-300-71x60I feel like I can’t attend any presentation anymore without hearing the work Docker – honestly, containers and Docker is just popping up everywhere – with the oddest of technologies claiming they have support for Docker.  So, with all this my problem is, What the eff is Docker – I’ve never had a use-case to even start looking at containers within my day job – therefore, I don’t really have that much knowledge around the challenges and benefits of them.  After seeing them at TFD I can now say that I need to explore this further – and jump on this container bandwagon to learn what they are all about.  First stop, Mr Stephen Foskett’s blog where he tells us just “What the deal with containers are“.  If you are just learning, or just love containers – check it out!

Setting yourself up for success with Veeam Pre-Job Scripts

For a while Veeam has been able to execute scripts post-job, or after the job completes – but it wasn’t until version 8 of their flagship Backup and Replication product that they added the ability to run a pre-job script, or a script that will execute before the job starts.  When v8 first came out with the ability to do this I strived to try and figure out what in the world I would need a pre-job script for – and for the longest time I never used it in any of my environments.  If a job failed I would execute post job scripts to run and hopefully correct the reason for failure – but a while back it kind of dawned on me – and with a bit of a change in mindset I realized something – Why fail first?


Why fail when success is possible?

As I mentioned above I’d grown accustom to using post-job scripts to correct any failing jobs.  For instance, there were times when for whatever reason a proxy would hold on to a disk of one of my replica’s – subsequently, the next run of this job would fail trying to access this disk – and even more importantly consolidation of any VMs requiring it would fail as the original replica couldn’t access the disk mounted to the proxy.  What did I do to fix this?  Well, I added script that executed post-job looking to simply unmount any disks off of my Veeam proxies that shouldn’t be mounted.

Another scenario – I had some issues a while back with some NFS datastores simply becoming inaccessible.  The fix – simply remove and re-add them to the ESXi host.  The solution at the time was to run a post-job script in Veeam.  If the job failed with the error of not being able to find the datastore then I ran a script that would automatically remove and re-add the datastore for me – Next job run everything would be great!

“Fail and Fix” or “Fix and Pass”

So, the two solutions above, while they do fix the issues they do it after the fact – after we have already failed.  Even though it fixed everything up for the next run of the job I’d still lose that one restore point – and sure enough, the time WILL come where it’s that exact point in time you will need to recover from!  The answer to all this is pretty simple – migrate your post-job scripts to pre-job scripts.  Let’s set ourselves up for success before we even start our job!  Although this may seem like common sense – for whatever reason it took a while before I saw it that way.

So with all that – hey, let’s add some code to this post.  Below you will find one of my scripts that runs before each Veeam job – my proactive approach to removing non-veeam proxy disks from the proxies!

Add-PSSnapin VeeamPSSnapIn
Add-PSSnapin VMware.VIMAutomation.core
Connect-VIServer vcenter.mwpreston.local -u username -pass password 
# get job name out of parent process id
$parentpid = (Get-WmiObject Win32_Process -Filter "processid='$pid'").parentprocessid.ToString()
$parentcmd = (Get-WmiObject Win32_Process -Filter "processid='$parentpid'").CommandLine
$jobid = $parentcmd.split('" "')[16]
$vbrjob = get-vbrjob | where-object { $_.Id -eq "$jobid" }
#get some info to build replica VM names
$suffix = $vbrjob.options.ViReplicaTargetOptions.ReplicaNameSuffix
$vms = $vbrjob.getObjectsInJob()
#create array of replica names
$replicasinjob = @()
foreach ($vm in $vms)
 $replica = $$suffix
 $replicasinjob += $replica
#loop through each replica and check Veeam proxies for foreign disks
foreach ($replicaitem in $replicasinjob)
 $replica = $replicaitem.tostring()
 Get-VM -Location ESXCluster -Name VBR* | Get-HardDisk | where-object { $_.FileName -like "*$replica*"} | Remove-HardDisk -Confirm:$false

So as you can see this is a simple script that basically retrieves the job name it was called from (Lines 7-10) – By doing it this way we can reuse this block of code in any of our jobs.  Then simply searches through all of the disks belonging to Veeam proxies (Line 28) – if it finds one that belongs to one of our replica’s we are about to process, it removes it.  Simple as that!  Now, rather than failing our job because a certain file has been locked, we have set our self up for a successful job run – without having to do a thing!  Which is the way I normally like it 🙂  Thanks for reading!

VMCE v9 Study Guide – Module 10 – Veeam ONE Reporting


Just as was with the Veeam ONE dashboards post this post is a lengthy one – and quite honestly just created to help me remember all of the different reports and options available within Veeam Reporter.  Again, just as with Veeam ONE Monitor – Reporter is on the exam and you will need to know a little bit about what all it can provide.

Veeam Reporter contains a number of useful reports that can help us to monitor both our virtual infrastructure along with our backup infrastructure.

  • VMware Infrastructure Assessment
    • ensures that your VMs can be successfully backed up by looking for configuration and incompatibilities that may affect backup job
    • helps predict the amount of future changes on disks that may have an influence on your backup window, consumed backup capacities, or WAN bandwidth allocated
    • Contains the following reports
      • Datastore Performance Assessment – helps to assess current load on storage in order to best define values in Backup I/O control
      • VM Change Rate Estimation – helps to predict sizes of incremental backups by tracking change rate
      • VM Configuration Assessment – lists VMs that could face issues when getting backed up.
  • Veeam Cloud Connect Report Pack
    • Tracks our VCC Infrastructure
    • Contains following Reports
      • Cloud Connect Inventory – displays inventory information for VBR and Cloud Connect components including licensing
      • Cloud Connect Replication Provisioning – helps define whether existing plans for hardware match our hosts and datastore capabilities to avoid potential issues caused by over provisioning.
      • Over Provisioned Backup Repositories – tracks and calculates the number of days left before we will breach a specified threshold in terms of space utilization
      • Veeam Cloud Connect User Report – Allows providers to analyze configuration and quota usage on repositories.  Helps to prevent running out of space and keeps an eye on users activities and quotas
  • Veeam Backup and Replication Report  Pack
    • Analyzes health, performance and efficiency of VBR.
    • Contains the following reports…
      • Backup Alarms Overview –  displays most frequently triggered alarms and most affected VBR infrastructure objects
      • Backup Billing – allows MSPs to generate billing statements for customers.
      • Backup Copy Job – Helps to analyze traffic savings of Backup Copy Jobs and WAN Accelerators
      • Backup Copy Job GFS Backup Files – Allows administrators to easily track GFS restore points and when certain backups will be removed including the size and day they are to be removed.
      • Backup Infrastructure Assessment – helps to improve job configuration and implement necessary hardware and software recommendations.  Helps you attain a lower backup window, lower resource consumption and more efficiency throughout your whole VBR environment
      • Backup Inventory – displays information on the state of backup infrastructure components and licensing details
      • Backup Job Data Exclusions – reviews exclusion settings configured in jobs.
      • Backup Jobs Historical Information – exhaustive information on the state of recent jobs.
      • Capacity Planning for Backup Repositories – analyze configuration of space utilization of repositories to forecast how long until the repository reaches capacity.
      • Current Backup Alarms State Overview – detects and resolves current and most pressing issues with VBR
      • Delegated Restore Permissions Overview – audits restore permissions.
      • Job Configuration Change Tracking – reviews user activity and tracks changes made to jobs.
      • Job Configuration Dump – helps to review settings of the current configuration of VBR jobs.
      • Latest Backup Job Status – helps administrators monitor recent VM protection operations.
      • Orphaned VMs – discovers VMs present in existing backups, but missing within a VBR job.
      • Protected VMs – helps to discover which VMs in the environment have up to date restore points and which are set to be backed up, but do not have a recent restore point.
      • Protected VMs Job Schedule – publishes the time table for scheduled jobs and their respective VMs
      • Replica Billing – assesses storage management costs for replication and auto generate billing statements.
      • Restore Operator Activity – tracks restore activities across all different restore methods as well as most popular recovery items.
      • Scale-Out Backup Repository Configuration – shows configuration and utilization of SOBR and their respective extents
      • SQL Backup Job Historical Information – tracks historical stats of SQL Backup jobs
      • SureBackup Jobs Overview – validates completion status and results of verification tests for SureBackup jobs.
      • Tape Backups – Maintains a record of all VMs archived to tape
      • Tape Exportation – information in regards to backup files located on tapes that have been exported from tape libraries.
      • Tape GFS Configuration – Information about GFS Media Pools – what tapes are exported, where they are stored, what tapes are assigned to certain media sets.
      • Tape Media Retention Period – information on retention policy settings configured for tape media pools.
      • Tape Vaults Overview – what vaults do we have, what tapes are archived in the vaults and what was their previous location.
      • Unmapped datastore LUNS – which shared datastores are not mapped to a proxy, thus no Direct SAN mode.
      • Veeam Backup Files Growth – capacity planning to asses historical growth of backup files.
      • Verified VMs – allows for a quick view of SureBackup results and confirm backups are recoverable.
      • VM Backup Compliance Overview – lists VMs that do not meet the requirement of having a certain number of backup copies available.
      • VM Backup Status – provides info on the backup status of all protected VMs
      • VM Change Rate History – track jobs who’s backup files and replicas grow too fast.
      • VM Failover Plan Overview – analyzes failover plan configuration and provides information on how much data is consumed by replica VMs on the target datastores.
      • VMs Backed up by Multiple Jobs – Finds VMs which are included in more than one job.
      • VMs with no Archive Copy – helps to assess whether mission critical VMs have backup copies stored on secondary backup repositories or tape.
  • VMware Overview Report Pack
    • Contains the following reports
      • Cluster Configuration – allows you to keep an eye on the state of hardware resources provided to cluster and verify configuration settings of clusters
      • Datastore Capacity – shows information on the amount of used and free space on datastores, virtual and logical disks.
      • Datastore Configuration – helps to monitor storage capacities ensuring VMs have sufficient room to run.
      • Datastore space usage history –  analyzes amount of space consumed historically showing growth, both high and low on your datastores.
      • Guest Disk Free Space – Information on VM guest disks such as capacity, free space, etc.
      • Guest Disk Space Usage – evaluates disk health based on capacity, free and used space.
      • Host Configuration – documents host configuration in the environment
      • Hypervisor Version – evaluates what versions each host is running.
      • Infrastructure Overview – monitors health and state of objects within your virtual environment.
      • VMs Configuration – documents current configuration of VMs such as cpu, power state, usage, VMware tools, Guest OS, etc.
      • VMs Growth –  tracks number of VMs in the environment and how it has been changing.
  • VMware Monitoring Report Pack
    • Contains the following Reports
      • Alarms Current State Overview – shows unresolved alarms from Veeam ONE Monitor
      • Alarms Overview – Shows most common alarms and most affected virtual infrastructure objects
      • Cluster Hosts Performance – helps to tweak DRS settings, performance settings and cluster health – from a host point of view
      • Cluster Performance – Same as cluster hosts performance but from a cluster point of view
      • Datastore Performance – shows historical and current IOPS/errors, etc.
      • Host Performance – stats on CPU, memory, disk, and network.
      • Host Uptime –top and lowest uptime for hosts (top 5).  Also how long each host was down, etc.
      • Multiple Clusters Performance – aggregates historical data for clusters.  Top consuming hosts, VMS, usage trends, etc.
      • Resource Pool and vApp Performance – stats on resources for vApps and resource pools.
      • VM Performance – resource statistics on VMs and trending.
      • VM Uptime – Top/Lowest uptime for top 5 VMs.  Also shows how long each VM has been down.
  • VMware Optimization Report Pack
    • Contains the following reports
      • Active Snapshots – shows VMs with snapshots, when they were created, size of snapshot and how old they are.
      • Garbage Files – shows space consumed by files that do not belong to VMs
      • Idle Templates – shows templates that haven’t been utilized in a specified period, including location, size and last time accessed.
      • Idle VMs – shows VMs that have been idle for a specified period.
      • Inefficient Datastore Usage – shows amount of space consumed by VMs that have been inactive for one month, six month, and one week.
      • Orphaned VM Snapshots – Shows amount of space consumed by snapshots that are no longer in use by the VM.
      • Oversized VMs – detects VMs with more RAM/CPU than they require.
      • Powered Off VMs – shows VMs that were powered off for a specified period.
      • Undersized VMs – identifies VMs which require more CPU/Memory.
  • VMware Capacity Planning Report Pack
    • Contains the following reports
      • Capacity Planning –  forecasts how many days remain before we meet a specific threshold.
      • Host Failure Modeling – Simulates failover of one ore more hosts to forecast CPU/Memory usage on the remaining hosts.
      • How many more VMs can be provisioned – calculates how many more VMs we can support before we meet a specified threshold.
      • Over provisioned Datastores – assesses potential impact of over provisioning thin provisioned VMs on datastores.
  • VMware Configuration Tracking Report Pack
    • Contains the following reports
      • Infrastructure Changes Audit – analyzes recently infrastructure changes
      • Infrastructure Changes by Object – detailed information on changes to a specific object.
      • Permissions by Object –  audits permissions to specific objects.
      • Permissions by User – audits permission based on user
  • Hyper-V Infrastructure Assessment
    • Contains the following reports
      • Configuration Assessment – compares Hyper-V infrastructure against a set of recommended settings and best practices.  Mitigates issues that might prevent VMs from being backed up.
      • Performance Assessment – analyzes Hyper-V infrastructure to confirm its configured optimally.
  • Hyper-V Overview Report Pack
    • Contains the following reports
      • Alarms Overview – review the triggered alarms from Veeam ONE Monitor
      • Cluster Configuration – documents current configuration of clusters and reports on memory, cpu and storage utilization
      • Datastore Capacity – documents configuration of CSVs, SMB shares and local disk, reports on total capacity, free, used and provisioned and calculates trends.  Also includes top 3 VMs in terms of capacity usage.
      • Host Configuration – documents current configuration of hosts and reports on CPU, Memory, Network and storage utilization
      • Infrastructure Overview – Shows properties of SCVMM servers, clusters, CSVs, SMB Shares, local disks, hosts and networks.  Distribution of MV by power states, integration services status.
      • VMs Configuration – provides details on cpu, memory, power state, disk usage, etc.
      • VMs Growth – tracks how the number of VMs within the environment changes and how it influenced resources.
  • Hyper-V Monitoring Report Pack
    • Contains the following reports
      • Failover Cluster Performance – shows top consuming hosts within cluster as well as CPU, Memory, Disk and Network resource utilization
      • Host Performance – Shows top consuming VMs on a host as well as all CPU, Memory, Disk and network resource utilization
      • Local Datastore Performance – Lists top 3 consuming VMs as well as read/write latency, read/write rate, and IOP Statistics
      • VM Performance – Shows stats around CPU, Memory, disk and network as well as trending.
      • VM Uptime – shows top 5 VMs with most and least uptime, as well as all VMs whose uptime is lower than specific thresholds
      • Windows 2008 CSV Performance – Aggregates all Win 2008 CSVs to show read/write rates and IOPS as well as top 3 consuming VMs
      • Windows 2012 CSV Performance – same as Windows 2008 but the addition of directed/redirected access mode.
  • Hyper-V Optimization Report Pack
    • Contains the following reports
      • Active Snapshots – shows snapshot age and size for all VMs containing snapshots.
      • Idle VMs – Shows CPU, Memory, disk and network utilization of idle VMs
      • Oversized VMs – Shows oversized VMs by CPU and Memory as well as all VMs with static memory.
      • Powered Off VMs – Shows VMs that have been powered off between a specified time period.
      • Undersized VMs – Identifies VMs who need more CPU/Memory.
  • Hyper-V Capacity Planning Report Pack
    • Contains the following reports
      • Capacity Planning – allows you to project how many days you have remaining across all aspects of your environment
      • Host Failure Modeling – allows you simulate failures of one or more hosts.
      • Over-provisioned Datastores – shows top 5 over and under provisioned datastores as well as datastores with least amount of free space remaining.
  • Custom Report Pack
    • Contains the following reports
      • Custom Infrastructure – allows you drill down into infrastructure objects and data not covered in other reports.
      • Hyper-V Custom Performance – can define specific metrics to monitor in terms of CPU, memory, network and disk for Hyper-V, CSVs and SMB Shares
      • Hyper-V Raw Performance Data – can get detailed raw data of all Hyper-V Metrics
      • Inventory – provides the most complete and up to date configuration information of all objects in the virtual environment
      • Report Builder – Merges data generated by separate custom reports into a single document.
      • VMware Custom Performance – allows you to define specific metrics in terms of CPU, Memory, Network and Disk for vSphere.
      • VMware Raw Performance data – get detailed raw data in terms of CPU, memory, network and disk for vSphere.
  • vCloud Director Report Pack
    • Contains the following reports
      • Catalogs Overview – shows an inventory of catalogs for selected organizations
      • Multiple Organizations vDC Performance – aggregates historical data for selected organizations (CPU, disk, network)  Lists top consuming vApps and VMs
      • Multiple vApps Performance – shows performance and resource statistics for a specific time period in the scope of a vApp.  Rates VMs by resource usage level and trends.
      • Organization Configurations –shows current configuration of organizations within the vCloud Director Infrastructure
      • Organization vDC Performance – shows performance stats for a specific organization datacenter across a specific time frame.
      • Provider vDC Performance – shows provider virtual datacenter statistics over a specific timeframe
      • vApp Configuration – Shows vApp configuration as well as top 5 cpu consuming vapps, memory, storage, etc.  shows number of powered on/off/resolved/and suspended vApps.
      • vApp Performance – shows CPU, memory, disk, network stats for a specific vApp and shows top consuming VMs.
      • VM Performance – shows performance stats for specific VMs
      • VM Uptime – shows top 5 highest/least VMs in terms of uptime, as well as VMs who have uptime values lower/greater than a specified threshold.
  • Offline Report Pack
    • allows you to export raw data/inventory into a couple external formats.
    • Contains the following reports
      • Infrastructure Overview (visio) – exports your inventory and configuration specifics to visio format.
      • Raw Data Analysis – Creates an Excel workbook containing detailed raw data on all objects within VMware.

VMCE Study Guide – Module 10 – Veeam ONE Dashboards


I apologize for the repetitiveness between this post and the Veeam ONE user guide, but honestly I learn a lot by writing things down – and since I wrote it down I’ll share it.  There isn’t alot of information here about each and every dashboard – there is a lot of them and to go through them would be very exhausting.  That said, Veeam ONE Dashboards is on the course outline for the VMCE exam, and there is a good chance you will end up getting some questions around them – so best to go through them all….  With that said, here’s a portion of Module 10 of the VMCE Study Guide.

Veeam ONE Dashboards

Veeam ONE contains many different dashboards dealing with both your infrastructure and your Backup Infrastructure.

Backup Infrastructure Dashboards

  • Backup Infrastructure Summary – shows the latest state of the backup operations in your virtual environment and indicates the most used resources in the backup infrastructure with the following charts.
    • Backup Jobs by  Status, Replication Jobs by Status, SureBackup Jobs by Status
    • Top Repository Servers by Used Space
    • Top Proxy Servers by Weekly processed disks
  • Backup Repositories Overview – overview and performance analysis for repositories.
    • Repositories Overview (# of repos, # of VM backups in repos, space occupied by full/incremental backups)
    • Top Repositories by used space
    • Top Repositories by days left
    • Top Repositories by weekly backup window
  • Backup Repository Summary – information about an individual repository
    • Repository Overview
    • Capacity Planning (# of days before no space)
    • Free space usage (amount of used storage vs amount of available storage.
  • Proxy Servers Overview – configuration and performance overview for proxies
    • Proxy Server Overview – break down of proxies by transport mode
    • Top proxies by processed VMs – top 5 backup proxies that process the greatest number of VMs over the past 7 days
    • Top Proxy by Transferred Data – top 5 backup proxies that transferred the greatest amount of data over the past 7 days
    • Top Proxies by Weekly Backup Window – detect the most busy proxy servers over the last 7 days
  • Proxy Server Summary – details on an individual proxy
    • Proxy Server Overview (number of task currently processing, transport mode, number of VMs processed over the last 7 days, number of VM disk processing task that can be assigned at the same time.
    • Number of processed disks – how many VM disk the proxy processed over the past 7 days
    • Transferred data – amount of backup data the proxy has transferred over the past 7 days.
    • Backup Window Utilization – estimates how busy the proxy was during the past 7 days.
  • WAN Accelerators Overview
    • WAN Accelerator Overview – number of WAN Accelerators, number of VMs stored in restore points that were transferred using acceleration, total network traffic sent by accelerators, amount of saved traffic.
    • Top Accelerators by Acceleration Efficiency – shows 5 accelerators that save the greatest amount of traffic over the past 7 days.
    • Top Accelerators by Transferred Data – top 5 accelerators that transferred the greatest amount o VM data over the past 7 days.
  • WAN Accelerator Summary
    • Overview – number of vms stored in restore points or received by the accelerator, amount of network traffic/saved traffic
    • Accelerator Efficiency – accelerators that save the greatest amount to traffic.
    • Transferred Data by day – shows the amount of VM data that was read from the source and the amount that was actually transferred.
  • Tape Servers Overview
    • Overview – shows number of tape servers and the tape libraries connected to them
    • top Tape servers by processed VMs – top 5 tape servers that process and archive to tape the greatest number of VMs over the last 7 days
    • Top tape servers by transferred data – top 5 tape servers that archived the greatest amount of data to tape over the past 7 days
    • Top tape servers utilization – detect the most busy tape servers over the past 7 days (cumulative time it was retrieving, processing and transferring data)
  • Tape Servers Summary
    • Overview – number of libraries connected to the server
    • Number of Processed VMs – how many VMs the tape server processed over the past 7 days
    • Processed Data – amount of data the tape servers has archived over the past 7 days
    • Backup Window Utilization – estimates how busy the tape server was over the past 7 days.
  • Cloud Repositories Overview
    • Overview – The number of repositories created for cloud connect users, number or repository leases expiring in the next 30 days, number of VMs in backups on repositories, cumulative amount of storage occupied by VM backups on all managed repositories
    • Top Cloud Repositories by Utilization – 5 cloud repositories that have the greatest amount of used storage
    • Top Cloud Repositories with least days left – top 5 repos that can run low on storage space sooner than others
    • Top repositories by daily utilization growth – How fast the amount of space on the repositories has grown over the past 7 days.
  • Cloud Repository Summary
    • Overview – name of user owning repository, date when expires, number of VMs stored in the repository, amount of space occupied
    • Capacity Planning – user quota, amount of free space, number of days before the repo runs out of space.
    • Space Utilization by Day – amount of used storage space against the amount of available space
    • Number of VMs by day – number of VMs whose backups were written to the repository during the past period.
  • Cloud Gateways Overview
    • Overview – number of cloud gateways managed, number of connections to gateways over the past 24 hours, amount of backup data that was transferred through all gateways, average amount of time during which the gateways were utilized over the past 24 hours.
    • User Connections – most loaded cloud gateways in terms of user connections
    • Data Transferred – amount of transferred data by most utilized gateways
  • Cloud Gateway Summary
    • Overview – number of users that have been connected over the past day, week, or month, TCPIP port used for external connections, Amount of backup data processed over the past day, week, or month, Amount of time that the gateway was retrieving, processing and transferring data
    • User Connections/Sessions – how many times the connection to the gateway was established to transfer backup traffic
    • Data Transferred/Processed Data – amount of backup data that the cloud gateway transferred to the cloud repo over the past period
    • Weekly/Monthly Summary – estimates just how busy the gateway was during the period.

VMware Infrastructure Dashboards

  • Virtual Infrastructure Summary – provides the health state overview for the selected object, available on the root node, as well as folders, resource pools, hosts clusters, datacenters or the vCenter Server.
    • Host State, Datastore State, VM State – healthy objects are green, those with warnings are yellow, and errors are red
    • Latest Alarms – the last 15 alarms that were triggered on the selected object
    • Alarms by Object – shows the last 15 objects with the highest number of alarms.  Displayed in an X/X format – i.e. 3/1 means 3 alarms, 1 warning.
  • ESXi Host Summary
    • Datastore State/VM State – health of the objects on the host
    • Resource Usage – capacity and performance summary for the hosts CPU and Memory
    • Latest Alarms – last 15 alarms for the host and all its child objects
    • Alarms by Object – 15 child objects with the greatest number of alarms
  • Virtual Machine Summary
    • Selected Object – shows the health state for the selected VM\
    • CPU/Memory Usage – amount of CPU/Memory resources the VM is consuming
    • Guest Disk Usage – amount of available and used guest disk usage – broke down by disk  By default the top 5 utilized disks of the VM are shown.  Requires VMware tools
    • Latest Alarms – last 15 alarms for the VM
    • Parent Object Health Status – shows current state of the host where the VM is running, as well as the state of the datastore where the VM resides.
  • Datastore Summary
    • Hosts State/VM state – shows health of hosts attached to datastore and VMs residing on datastore
    • Disk Space Usage – amount of available, used, and provisioned disk space
    • Latest Alarms – last 15 alarms for datastore and objects working with this datastore
    • Latest Disk Latency – current read/write latency values and the average

Hyper-V Dashboards

  • Virtual Infrastructure Summary
    • Host/Datastore/VM States – displays health of associated objects
    • Latest Alarms – last 15 alarms for respective objects
    • Alarms by Object – 15 objects with highest number of alarms
  • Host Summary
    • Datastore/VM state – health of associated objects
    • Resource Usage – capacity/usage summary for CPU/Memory on host/overview of volumes connected to host (capacity, free space
    • Latest Alarms – last 15 alarms
    • Alarms by object – 15 objects with highest level of alarms
  • VM Summary
    • CPU/Memory Usage – Dynamic memory VMs show usage, static memory show 100% all the time
    • Datastore Usage – amount of storage available/consumed where the VMs reside
    • Latest alarms – last 15 alarms for the VM
    • Parent Object Health Status – health of the host VM is running on.
  • Local Storage Summary
    • Hosts/VM State – health of hosts connected, VMs hosted.
    • Disk Space Usage – amount of available/used disk space
    • Latest Alarms – last 15 alarms for local storage
    • Latest Disk Latency – current read/write as well as average
  • SMB Share Summary
    • Hosts/VM state – health of connected hosts, VMs residing on share
    • Disk Space Usage – amount of available/used capacity
    • Latest Alarms – last 15 alarms for share/hosts that work with share
    • Latest Disk Speed – current read/write rate, along with average over the past hour
  • Cluster Shared Volume Summary
    • Host/VM State – I’ve typed what this is enough Smile
    • Disk Space usage – free/available capacity on CSVs
    • Latest Alarms – last 15 alarms for CSVs
    • Latest Disk Speed – current direct and redirected I/O values as well as average for past hour

vCloud Director Dashboards

  • vCD Infrastructure Summary
    • Top 5 orgs by VM Errors/Warnings /Healthy– orgs with greatest number of errors/warnings/no alarms
    • Latest Alarms – last 15 alarms for vCD segment
    • Alarms by Object – 15 objects with greatest number of alarms
  • Provider vDCs Overview
    • Error/Warning/Health Objects – provider vDCs by state (error/warning/healthy)
    • Latest Alarms – last 15 alarms triggered for vDCs
    • Alarms by Object – 15 objects with the greatest number of alarms
  • Provider vDC Summary
    • CPU/Memory/Storage Usage – amount of currently consumed CPU, memory and storage resources for the vDC
    • Latest Alarms – last 15 alarms associated with vDC and its underlying objects
    • Alarms by Object – current state of hosts/datastores providing resources to the vDC
  • Organizations Overview
    • Error/Warning/Healthy Objects – groups VMs by orgs by health status
    • Latest Alarms – last 15 alarms triggered for orgs
    • Alarms By Object – 15 objects with greatest number of alarms.
  • Organization Summary
    • VMs by State – summary health of VMs in the organization
    • Latest Blocking Tasks – last 15 suspended operations that require approval
    • Latest Alarms – last 15 alarms for orgs, org vDCs, VMs and vApps associated with orgs
    • Alarms by Object – 15 objects with greatest number of alarms
  • Organization vDC Summary
    • VMs by State – typed this too much Smile
    • Expired vApps – vApps whose runtime/storage lease is expired.
    • Latest Alarms – last 15 alarms for org vDC and child objects
    • Alarms by Object – 15 objects with greatest number of alarms
  • vApp Summary
    • VMs by State – see previous dashboard
    • VMs by Tools State – groups VMs in the vApp by VMware Tools State.
    • VMs by Power State – groups VMs in the vApp by their power status
    • Latest Alarms – last 15 alarms for the vApp and VMs within it.
    • Alarms by Object – 15 objects with the greatest number of alarms
  • VM Summary
    • CPU/Memory Usage – show the amount of CPU/Memory resources VM is consuming
    • Guest Disk Usage – amount of available and used guest disk usage (needs VMware Tools)
    • Latest Alarms – last 15 alarms for the VM
    • Parent Object Health Status – current health state of host

VMCE v9 Study Guide- Module 9 – Tape Device Support


I’ve taken a little break from the VMCE Study Guide creation but truth be told participating in the #VDM30in30 will probably help get me back into the swing of things.  Today we will continue along with the guide, jumping ahead slightly to Module 9 and tape support.  I’ve not used tape at all within Veeam so this was definitely a good excercise for me to go through before going and writing the VMCE certification.

Requirements and Configurations

As far as support goes, Veeam Backup & Replication supports the following devices…

  • LTO3 or later tape libraries
  • Physical and Standalone drives, along with virtual tape libraries
  • Partitions of physical or VTLs which are presented to VBR
  • Drives can be connected via FC, SAS, or SCSI when connecting directly, iSCSI remote connections are also supported.
  • If multiple driver installation modes are supported for the storage device, then the driver that supports multiple open handles must be utilized.

When determining which block size to use, VBR will scan all the drives within the same library or all the standalone drives which are connected to one tape server.  It compares all of the available sizes which the drives support and then uses the maximum size available that is supported among all of them.

Deploying tape support within Veeam

The Veeam tape environment contains a number of components required to make it work…

Veeam Tape Server

The first step in configuring VBR to utilize tape is deploying a tape server.  A tape server, like a lot of other Veeam Infrastructure components can be any Windows-based machine that has been added to VBR, including the Backup Server itself in small environments.  For larger environments, to balance traffic load with a lot of data processing, or to configure remote data archiving a dedicated tape server should be utilized.  Once connected to the tape server, Tape devices are automatically discovered by VBR.  Keep in mind, although we can connect many different tape devices to one tape server, we can only connect the tape server to one Veeam Backup Server.  That said, if we remove a tape server from one instance of VBR and connect it to another, VBR will recognize all of the library settings automatically, however you will need to reconfigure jobs to point to the new library.

Veeam Backup Database

Veeam catalogs all of the information about its archived data and stores this in the Veeam Backup Database.  Tapes will stay in the database until you manually remove it.  The information available about the tape, such as backups which are written to it is always available, even if the tape isn’t inserted into the library.  Having all off this information stored “offline” allows administrators to quickly find the location of required information to restore.  When the restore task is started, VBR will prompt administrators to insert the required tape.  The following catalogs are utilized by VBR

  • Tape Catalog – contains information in regards to files and folders which have been archived to tape with the File To Tape jobs, along with backup files which have been produced by Backup to Tape jobs.  This information is available within the FILES view.
  • Backup Catalog – This contains information in regards to the VMs that have backups archived to tape media with Backup To Tape jobs.  This is available by selecting Backups->Tape.

Veeam supports the following technologies within a tape infrastructure

  • Media Pools
    • Logical container created by VBR to organize and administer tapes
    • Tapes must be placed into a media pool before we can utilize it, therefore we must have at least one manually created custom media pool before we can write data to tape.  We can have as many custom media pools as required.  A media pool can be a target for any number of tape jobs as well.  A custom media pool can have a number of different rules associated with it.
      • Tape Replenishment – can manually specify particular tapes, or have the pool pull from the “Free” pool as required.
      • Media Sets – assign sets of tapes to hold data from a particular time frame.
      • Data Retention – Choose the period for which the data on the tapes will be protected from overwriting.
      • Parallel Processing – allows the media pool to use multiple tape devices simultaneously.  Can process several tape jobs or split data within one job across different drives.
      • Encryption – Software encryption
      • Export tapes to vault
    • Another type of media pool is a GFS media pool.
      • used to store data to tape in the GFS format, common for long time archiving.
      • Contains 4 predefined media sets tied to a tiered retention scheme; Weekly, Monthly Quarterly, Yearly
      • Predefined media sets can be disabled if you do not need them, for example if you don’t keep quarterly jobs we can disable the Quarterly media set.
      • One GFS media pool can support multiple tape GFS jobs.
      • GFS media pools contain only FULL backups
    • There are a number of “service” media pools which are created by default in VBR.  These cannot be modified or removed in any way.
      • Free – all newly introduced tapes are placed into this pool.  Used to replenish any custom pools when needed.
      • Unrecognized –  contains tapes that have been loaded to a device but require further identification from the user.  Normally require the user to run an inventory or catalog job.
      • Imported – contains non-empty tapes that have been identified by the tape catalog job.
      • Retired – contains tapes that have been retired and reached the maximum number of re-writes.  Also can contain tapes that have had some sort of mechanical malfunction.In order to create backups in the GFS (Grandfather, father, son) mode, we must create a GFS Media Pool
    • Once a tape has been allocated to a custom media pool it wall always be tied to it.  When a tape with expired data comes back online, VBR automatically places it into its corresponding custom media pool.
    • When a tape is manually moved to another media pool it will be marked as free and data lost
    • Media pools are global, meaning we can use tapes in different libraries without the need to re catalog them – meaning we can restore data from tapes inserted into any tape library, regardless of the media pool they belong to
      • The only exception to this rule is when hardware encryption is utilized.  When this is utilized we must insert the encrypted tape into a device with the same encryption standard.
    • If a media pool (custom or GFS) uses multiple tape libraries we are able to set up Tape Library Failover.  The failover order is user defined, and the job always reverts back to the primary library on the next run.  One tape library within the media pool will always be marked as the primary however can failover to the next library if the following occurs.
      • The tape library is offline
      • The tape library has no free tapes
      • The tape library as no free drives.
  • Media Sets
    • A media set is a set of tapes that is used for continuously writing backup data.
    • Media sets always starts with a free tape, and data blocks are always appended to the previous one and rely on the following configuration options available
      • Create a new media set for each backup session – VBR will produce a separate set of tapes for each backup session.
      • Starting a new media set for a certain period of time – Can define a new set of tapes for a given time frame, for instance, each week use a different set of tapes. – normally used to move certain backup timeframes offsite.
      • Always continuing one media set – Will continuously use tapes in the media set, not splitting archives on to separate sets of tapes – Normally used when tapes are not exported from libraries.
    • Media sets are convenient if we need to move certain timeframes of data offsite as it allows us to ensure certain backup retention points are on certain tapes.  That said, depending on the configuration it can cause inefficiencies in your tape utilization.
    • Some instances will cause VBR to forcibly start a new media set, overriding any media pool settings, for instance
      • a required tape is offline
      • a required tape is hardware or software protected
      • a library is offline and all drives are busy.
  • Backup Sets
    • Backup sets are a set of files that have been archived to tape during one tape job session.  If there is a large amount of data being archived to tape, a backup set can most certainly span multiple tapes.
  • Media Vaults
    • Media Vaults are logical containers that help to organize offline tapes.
    • Created by end user.
    • Basically allow you to specify that certain tapes belong to a vault, meaning they have been moved offsite, etc.
    • Allows for a convenient representation of the tapes available within VBR, and those that are offline and in storage.
    • Can be set to be moved to a vault automatically after a tape goes offline.
    • Tapes can be moved between vaults.
    • Show up as “offline” within their media pool.
    • VBR stores the following information in regards to tapes in a media vault
      • What tapes are stored in a particular location
      • Which tapes have expired and can be overwritten
      • Which tapes comprise a particular media set that is needed for a restore.
    • Media Vaults normally are created to mimic physical storage locations.
  • Data Retention
    • Configured on the media pool and applied to all tapes which belong to it.
    • Can choose between the following policies
      • Never Overwrite Data
      • Define a particular time period to protect data
      • Not to protect data at all.
    • If a tape contains several backup sets, it will not be expired until the backup set with the longest retention period expires.
  • Tape Protection
    • Software option to prohibit overwriting, erasing, or appending data to a protected tape
    • This OVERRIDES any Data Retention settings on the media pool
    • Can be overridden at any time, at which point the data retention settings will be applied again.
    • When tapes are protected the following are disabled; appending data to tapes, erasing tapes, marking tapes as free, and removing tapes from the catalog.
    • If using forward or reverse incremental backup chains you must ensure that the retention period for the tape archive is not less than that of the backup to disk job.

The Virtual Synthesized Full Backup for Tapes

When utilizing the Forever incremental backup chain you may end up being left with long chains of increments.  Having these long chains of increments can require loading a large number of tapes during a restore depending on how it needs to chain the data together.  To help combat this Veeam allows for creating a Virtual Synthesized Full Backup.   Basically Veeam will periodically synthesize a full backup using the respective incremental located on the repository directly on the tape (Directly on tape, not requiring additional repository space).  Some requirements/limitations of the Virtual Synthesized full backup are

  • The source backup job must not have a scheduled synthetic or active full.  If it does, the tape will not run the virtual full even if it is configured.
  • The virtual full is created automatically once a week if the job produces forever forward incremental – the day of week this happens is customizable, but it cannot be disabled.

The Synthesized Virtual Full Backup process is as follows…

  • On the day the tape job runs it creates a (.vsb.) file and stores this on the backup repository – the vsb file contains only pointers to data blocks inside the files of the backup chain located on disk.
  • Depending on the file pointers, the tape job detects what backup chain and what data blocks located on the repository are required to synthesize a full backup.  It then takes these blocks and writes the directly to tape as a full backup file (.vbk)
  • Once the full backup has been written, the vsb file is removed from the repository.

Backing up to tape with Veeam.

Veeam contains a couple of different jobs that will write data to tape

  1. Backup To Tape Job
    • Archives Veeam backups created on disk to tape
    • Doesn’t create new backups, simply locates already existing backups produced by both backup/backup copy jobs and copies them to tape.
    • One tape job can have an unlimited number of source jobs linked to it.
    • Backup jobs can have the following source jobs
      • Backup Jobs – when a backup job is a source it scans the proper repositories and picks restore points created by the backup job.  When the configuration of the source backup job is changed, the tape job automatically updates to reflect those changes
      • Backup Copy Jobs – When using a backup copy job as a source the tape job will copy the full backup file once, then, only increments after that.  Since the latest restore point of a backup copy jobs are marked as active until another restore point has been created, the backup to tape job will not copy them.  Therefore, backup to tape jobs with a backup copy job as the source will always be one restore point behind.
      • Backup Repositories – When a backup repository is used as a source for a Backup to Tape job, Veeam will archive new Veeam Backup files (created by the same backup server) as soon as they appear on disk.   Explicit windows can be set for the tape job instead of continuously monitoring and archive in the background.
      • Endpoint Backup Jobs – Backup files created by endpoint backup jobs can also be used as the source to a Backup to Tape job.
    • Linked Jobs – Rather than linking backup jobs to tape jobs you can also setup  a tape device as a secondary destination in your backup job.  In this case, Veeam waits for the backup job to create a new backup file and then copies it to tape.
    • Backup to tape works as follows
      • Backup to Tape job addresses the backup catalog to detect backups matching job criteria
      • Files are queued for archiving
      • Veeam connects to the data movers and starts transfer process
      • source data move gets data from repository, target data mover sends data to tape
      • Tape job retrieves a list of tapes for writing from the media pool.
      • Data is processed and Backup Catalog is updated.
  2. GFS Tape Jobs
    • GFS jobs can use any backup job as a source that is processed in forever forward incremental, forward incremental, or reversed incremental.
    • Full backups are processed depending on when the individual media sets within the media pool have been setup.
    • If two periods overlap, the backup with the longest retention is archived.
    • If the source job creates more than one full backup within 24 hours the tape job only copies the first one.
    • If the restore point has been locked, GFS job will wait up to 7 days for it to become available.
    • If the job is manually cancelled it will automatically start again the next day (00:00)
    • If there is a technical issue the GFS job will archive the two most recent missed backups for each media set once it has been fixed.
  3. File to Tape jobs
    • File to Tape jobs allow you to copy any Windows or Linux files to tape.
    • Can be used to process Veeam backups as well, but treats them as simple files rather than backups.
    • File To Tape compresses sources files to files which have been stored on tape and copies just the changes.  Both full and incremental modes can be used with the File To Tape job.
    • Can copy files from any server which has been added to the VBR infrastructure
    • File to tape jobs are more efficient when copying fewer larger files than a lot of smaller files
    • jobs will timeout if they fail to complete within three weeks.
    • The process of File to Tape is as follows
      • Job detects files that match the job criteria
      • Files are queued for archive
        • If it is a first run or scheduled full, all files are queued
        • If it is an incremental, the tape catalog is addressed to detect if any data has been modified since the last backup.
      • Connects to the data mover and begins the transfer
      • Tape job addresses media pools associated with the job, media pool allots proper tapes for writing.
      • Catalog is updated as job is processing with new data.

Restoring from tape

Veeam supports a few different options for restoring from tape

  • Restore VM backups to repository or disk
    • Allows to copy VM backups from tape to a disk or repository of your choice.
    • The restored backup is registered within VBR console so you are able to perform any other type of restore operation to it later on.
    • You can restore from any restore point on the tape, at which VBR will restore the VM to the selected point in time.
  • Restore VM to Virtual Infrastructure
    • Process includes all of the options that a restore VM from disk does
    • Can select a restore point, change VM configuration settings, etc.
    • It first copies the VM to a temporary location such as a repository or folder on disk and then performs a standard VM restore back to your virtual environment.
  • Restore Files from Tape
    • This is used for restoring files and folders that were backed up using the Files to Tape backup job
    • Can be restored directly to their original location or to another location.
    • All ownership and permissions are preserved.
    • Can be restored from any restore point on tape.

No matter which restore method is selected, Veeam will scan the backup catalog and get all of the required tapes that need to be available to perform the process.  If all the tapes are online Veeam will begin the restore – if some are offline, VBR will list the names of the required tapes and wait for them to come online.

Interesting and testable tidbits around tape

  • Tape helps administrators implement the 3-2-1 rule; 3 copies of your data, 2 types of media, 1 copy offsite.
  • VBR uses MTF (Microsoft Tape Format) to write data to the tape
  • VBR DOES NOT support WORM (Write Once, Read Many)
  • When determining a block size, Veeam will use the maximum size available supported within the tape library.
  • Veeam does not write data directly to tape – the backups are first created on disk and then copied to the tape.
  • Synthesized Virtual Full backups are written directly to tape, utilizing full and incrementals from the repository
  • Synthesized Virtual full backups utilize a data pointer file on the repository with a .vsb extension
  • Synthesized virtual full backups will not run if the source job has an active/synthesized full scheduled
  • If a synthesized virtual full backup is scheduled the same day that a full backup has run, it simply copies the full backup to tape without generating the .vsb file.
  • Tape protection overrides any Data Retention settings which have been set on the media pool
  • Parallel processing cannot be enabled for jobs writing to a GFS Media Pool
  • Backup to Tape Jobs which use Backup Copy jobs as the source will always be one restore point behind since the latest restore point from a backup copy job is marked as active and Backup to Tape jobs will not process active restore points.
  • Tape Servers automatically get the Data Mover service installed on them, just like proxies.