IT Services Support

The mount server is required if you restore VM guest OS files and application items to the original location or perform secure restore. The mount server lets you route VM traffic by an optimal way, reduce load on the network and speed up the restore process. When you perform file-level, application item or secure restore,  Veeam Backup & Replication  needs to mount the content of the backup file to a staging server (or the original VM for restore to the Microsoft SQL Server and Oracle VMs). Once the VM backup is mounted,  Veeam Backup & Replication  copies files or items to their destination via this mount server or VM.  The staging server must be located in the same site as the backup repository where backup files are stored. In this case, you will be able to keep the VM traffic in one site. If the staging server is located in some other site, the data will need to travel across the network between the sites.   Mount Server Deployment The mount server is created

Veeam Backup & Replication uses the mount server as a staging server for scanning machine data with antivirus software. By default, the mount server role is assigned to one of the following machines: the Veeam backup server or a repository that stores machine backups. However, you can assign the mount server role to any 64-bit Microsoft Windows machine in your backup infrastructure. For example, you may want to run the malware scan process on a different server for security reasons. For details on mount server deployment and requirements, see Mount Server . To run the malware scan, Veeam Backup & Replication performs the following actions: On the mount server, Veeam Backup & Replication runs Veeam Mount Service to check the antivirus configuration file and antivirus software: Veeam Mount Service verifies if the AntivirusInfos.xml configuration file is located in the %ProgramFiles%\Common Files\Veeam\Backup and Replication\Mount Service folder. Veeam

Sophos XG: How to config Source NAT rule (may use IP static or dynamic) April 16, 2019 Vincent Sophos 0 This article demonstrates how to create a Source NAT firewall rule so that outbound traffic from the local will use a different static IP address or you can use MASQUERADE to configure SNAT with dynamic IP address. In order to be flexible, businesses don’t need to buy static IP How to configure Login to Sophos XG Firewall by Admin account Create a LAN layer where you want NAT Network -> Interfaces -> Click Add Interface Choose Add Alias Fill in the information You can NAT 1-1 by select only one LAN IP address or multiple LAN IP addresses by selecting the network layer -> Click Save Select Host and Services -> IP Host -> Click Add to create a WAN IP address that you want to user to put NAT in Firewall Rule -> Click Save Firewall -> Click Add Firewall Rule -> Select Business application rule Ch

Guide to config Log on to Sophos XG by Admin account Authentication -> Group -> Click Add Create SSL VPN Group Group Name : Enter Remote SSL VPN Group Surfing Quota : Choose Unlimited Internet Access Access Time : Choose Allowed all the time -> Click Save Create SSL VPN users Username : Enter vpn’s user Password : Enter SSL VPN user’s password Email : Enter user’s email Group : Choose SSL VPN group which was created before -> Click Save Hosts and Services -> Choose IP Host With configuration define the intranet layer Name : Enter Local subnet Type : Choose Network IP Address : Import LAN’s IP -> Click Save With IP configuration defined for SSL VPN Clients Name : Enter Remote SSL VPN range Type : Choose IP range IP Address : Import IP range which you want -> Click Save VPN -> SSL VPN (Remote Access) -> Click Add Name : Enter Remote SSL VPN policy Policy members : Choose Remote SSL VPN Group Permitted

Step 1: Run VMware migration assistant Before beginning the migration, you must run the VMware Migration Assitant on the source vCenter server (I mean the Windows vCenter Server). You can find this tool in the vCSA ISO that you have previously downloaded in <Drive Letter>:\migration-assistant\VMware-Migration-Assistant.exe . This tool starts a web service on the Windows vCenter Server to communicate with the vCSA install program. Step 2: Deploy the vCSA Once you have executed the VMware Migration Assistant on the source, you can mount the vCSA ISO on your favorite Windows computer or server (it must have access to your vSphere infrastructure) and run <DriveLetter>:\vcsa-ui-installer\win32\installer.exe . You can also run the installer from Mac or Linux but I prefer Windows :). In the first window, just click on Migrate . The next screen introduces the migration process. Just click on Next . On the next screen, accept the license agreement