SQUADRE 41 (Torneo a squadre online su BBO)
In attesa di tempi più propizi per giocare dal vivo, proponiamo ai nostri soci (e non solo) una nuova formula di torneo a squadre curiosa e dinamica, da giocarsi su bbo.
Le squadre iscritte si incontreranno in un unico girone con formula SWISS (prima contro seconda e così via).
Alla fine di ogni turno i VP conquistati sarrano il ‘fardello’ da passare al proprio avversario.
Ad esempio: chi vince 17-3 segna 3 punti mentre il perdente ne prende 17 Quando una squadra avrà accumulato 41 punti … verrà eliminata.
Se dopo un turno rimarranno squadre dispari verrà recuperata l’ultima squadra
eliminata col minor punteggio
Si proseguirà in questo modo finchè non rimarrano le 4 squadre che si affronteranno in semifinale e finale.
In ottemperanza alle raccomandazioni del DPCM del 24/10 vi informiamo che il Circolo di Monza resterà chiuso a partire da lunedì 26 ottobre.
Non è una scelta obbligata (almeno per il momento) ma, crediamo, doverosa visto l’aggravarsi della situazione con la ripresa della diffusione del Covid-19.
Naturalmente appena le condizioni permetteranno una riapertura in relativa sicurezza, daremo avviso ai nostri soci.
NAS Backup allows managing the protection of the environment where files and folders are a focus point for a company.
This article does not cover how a Nas Backup job works or how to set it up. Please refer to the official documentation to have all details.
What is the scope of the next lines?
It will show how easy it is to realize a script to create dummy files before launching an incremental backup. Why? Because the scope of this article is showing how fast a backup job can be.
1. The script is composed of four parts (in every box line 1 describes the actions that will be performed after).
The next pictures will show the Nas Backup job wizard pointing out the main point (picture 3, 4 and 5)
Pictures 1 and 2 show one of my favorite advance options: the possibility to select the file topology to save. For example, protecting the pdf files only. It supports wild-cat character so it’s very flexible and useful.
Picture 1
Picture 2
From picture 3 to 5, highlighted in yellow the step to set-up the script:
Picture 3
Picture 4
Picture 5
Pictures 6 and 7 show the result of the job modified in this way. Please put your attention to the last yellow line where 195 MB of the source data is processed in 20 seconds. (In my small lab it’s a great result !!!)
Picture 6
Picture 7
Note: If you need to change the script time execution from default 15 mins (900 secs), just add a REG-DWORD named “PreJobScriptTimeoutSec”(Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication). The amount has to be in seconds (Picture 8)
New articles to show which are the common business models that leverage the Veeam cloud technologies.
Today I’m going to cover two kinds of services:
A) Remoting Backup Data (RBD)
B) Disaster Recovery as a Service (DRaaS)
For every above service, the article will show the two options available:
1) Un-managed Service
2) Managed Service
The scope of these articles is to explain Roles, Tasks, Responsibilities, license management to have a big picture of the service models.
Note-1: If you need technical details on how to deploy and how to use these functions please refer to the official documentation and ask the local Veeam representative.
It’s the way in which the service provider installs, maintains and manages hardware and software in its “sites” providing a reliable service.
The customer must handle all his configuration tasks to use the services bought from Service Provider.
The following example is an easy way to fix in mind what an un-managed service is.
Office365 (now Microsoft 365) provides e-mail, SharePoint, teams, one drive services. Microsoft itself is responsible to maintain the service up and running, but all the tasks to use it are in charge of the customer.
If you need more details about data & service responsibility on Microsoft 365 environment just take a look at the following pdf, if you want to know more about how to implement a service, please click here
AB-1) Un-managed Service & Remoting Backup Data & DRaaS
The technology supplying a Veeam Service is named cloud connect. The idea is creating a private and secure connection from the Tenant to the Service Provider side that makes shared resources available.
Picture 1 shows the backup flows and resources (Repositories) for RDB. Picture 2 shows the DRaaS flows and resources (Virtual Hosts).
Picture 1
Picture 2
Tasks and responsibilities:
SP administrator (Cloud Connect):
Deploying the front-end CC Architecture (Gateway)
Deploying the back-end CC architecture (Backup Server/Repository/Wan-Accelerator/vCD/VSPC/SQL…)
For each Tenant, defining the resources to be provided (multi-tenant model)
Using the VSPC to monitor and report on resource use
Tenant Administrator (From VBR console):
Adding the Service Provider service discovering the purchased resources
Setting up local backup jobs
Setting up the backup copy job where the repository is the SP site
Setting up the Replica job for DRaaS
Performed Restore activities
Performed Partial and Full Failover
How is it possible to measure the services?
Is it possible to show both the use to service provider & Tenant?
The answer is yes just using the Veeam Service Provider Console (if you are a Service Provider please take your life easier deploying the VSPC).
Which sort of measure can I get from it? Very detailed usage report that can be automatically sent to a Reseller and to the tenant (via e-mail also).
VCSP can be used also to create and manage invoices.
Note-2: VSPC is the license manager focal point where you can see through reports the license Status (Approved, Waiting for Approval) for a specific period of time (details available clicking toVCSP license and to the last article of this serie)
2) What is a managed service?
Managed services are the practice of outsourcing the responsibility for maintaining, and anticipating the need for a range of processes.
The schema used for 1AB can be used for 2AB as well
Tasks and responsibilities:
SP administrator (Cloud Connect):
Deploying the front-end CC Architecture (Gateway)
Deploying the back-end CC architecture (Backup Server/Repository/Wan-Accelerator/vCD/VSPC/SQL…)
For each Tenant, defining the resources to be provided (multi-tenant model)
Using the VSPC to monitor and report on resource use
SP administrator for Tenant Administrator (From VBR console):
Adding the Service Provider service discovering the purchased resources
Setting up local backup jobs
Setting up the backup copy job where the repository is the SP site
Setting up the Replica job for DRaaS
Performed Restore activities
Performed Partial and Full Failover
Here also the VSPC can be used as a central point of service management
Note-3:
The service providers using the pairing vCloud Director (vCD) technology and Veeam Cloud connect, can replicate production VMs directly inside the tenant virtual Data Center (vDC) as shown in Picture 3.
Picture 3
This approach simplifies not just network management (NSX) but also the cloud Service provider adoption.
A natural extension is the migration services of the tenant workload from on-premises to Cloud through Cloud Connect.
Is there a different way if a Service Provider/Tenant does not implement/use the Replicas job?
The answer is sure, and I named the use case as “Cold Disaster Recovery“.
The idea behind itis restoring the backup tenant files on SP virtual architecture.
To allow it to work it’s necessary:
a.The tenant has provided the backup file encryption password.
b. Since from the VBR console the SP can’t browse the tenant backup files (The VBR SP console in fact can just show if a backup is running), the SP has to implement a script to import backup data to SP Backup Server. Luckily you can get the script from Github (Thx to an Andrea Borella works).
c. Just now from the SP-VBR console at the menu “imported backup copy” will appear all backup copy job of the tenant, and the SP can restore VMs.
That’s all for today guys.
My next article will cover topics about vCLOUD DIRECTOR backup as an un-managed service.
The last one will talk about all you need to know about the licensing.
In the previous article, I wrote a small pill about vCloud Director.
Today I’m going to expand the Business model that can be deployed through this great VMware technology.
Picture 1 shows the main components (VBR, Repository, Enterprise Manager and vCloud Director) mandatory to provide services.
As usual please refer toofficial guides to deploy correctly the Veeam technologies.
Picture 1
On the corners of the above picture, it’s possible to observe two funny images. The scope of those pictures is to show the services that the Serice Provider can sell: Managed, and un-managed.
Let’s start !!!!
a) Managed Service: Backup as a service on vCloud Director
In this scenario, the service provider will install VBR components and it will take care of all the backup and restore activities.
The tenant will open a ticket to Service Provider for asking backup policies changes and for restore tasks.
b)Un-managed Service: Backup as a Service vCloud Director
Tasks and responsibilities:
SP administrator (backup for vDC):
Deploying the backup end architecture (VBR, Repository)
Defines templates for Backup jobs of the tenants (by selecting Repository and Quota) (picture 2)
If necessary apply schedule restrictions (picture 3)
Tenant Administrator (by Enterprise Manager):
Tenant through his vCD credentials can:
Create new backup jobs based on templates
Edit / Delete / Enable / Disable Jobs
Start, stop, restart jobs
View backup statistics
Restore VMs and vApps
Restore the VM guest files
Restore SQL Server and Oracle objects
Picture 2
Picture 3
That’s all for today folks.
The next article will show you all about licensing