Showing posts with label backup. Show all posts
Showing posts with label backup. Show all posts
Saturday, August 27, 2016
Backup and Restore ESXi Host Configuration
Backup and Restore ESXi Host Configuration
Todays post involves something I havent done before which is backing up and then restoring an ESXi hostss configuration.
In my examples today I am going to use the tools directly built into ESXi and vSphere to get this done. Im going to use PowerCLI 5.5 (latest version as of this writing) to get this done.
PowerCLI is one of the many tools that are bundled for free with the vSphere environment. I highly recommend you have it installed on your management server or workstation and if youre running vCenter on Windows its even better to place it there. You can download PowerCLI from the VMware website.
The process of backing up and restoring the configuration is pretty simple so here we go.
Before running any of these commands you should run this command in PowerShell on Windows to make sure PowerCLI has the ability to execute the commands needed for this process to work.
Set-ExecutionPolicy RemoteSigned
Open PowerCLI and use the Connect-VIServer IPAddress command to connect to the server.
Next run the command below to backup your hosts configuration. Make sure you create the backup location folder before you run the command.
Get-VMHostFirmware -VMHost ESXi_host_IP_Address -BackupConfiguration -DestinationPath “Output_Directory”
When the process completes youll have files that look like this:
Thats all there is to backing up the configuration of your ESXi host. Now for the really cool part.
If youre upgrading hosts to new hardware there a couple of things Ive done and the restore has went off without a hitch. Make sure you have the VMware install on the new host at the exact same version as the host you backed up. If not this isnt a supported process but you can use the "-force" command at the end of the restore to make it do it anyway. The next thing is to ensure you have the network cables in the exact same port numbers as the old host. In other words port 0 on the old host should get the cable for port 0 on the new.
If youre unsure which cables correspond to which port, once youve migrated all VMs off of the old host you can look at the network configuration in the vSphere client and pull the cables one at a time. From there just label each one so you know where to put it in the new server.
Once youve got the new box cabled up, on the same build of VMware as the old server, and powered on heres all you need to do.
First put the host into maintenance mode. This is required or the next step will not work. You can use the hostname, IP address, or FQDN if you want.
Set-VMHost -VMHost esx1 -State “Maintenance”
Next enter the restore command.
Set-VMHostFirmware -VMHost -Restore -Force -SourcePath
Once you do this the host will immediately restart. During the restart it will import the backed up configuration prior to completing the loading process.
After the host has fully restarted you will be able to see that all of your prior settings have been restored including those many times complicated network, VLAN, and MTU settings.
On the hosts I have performed this on if they have local storage I have had to configure the large datastore again but given how much time this saves thats a minor thing to get the new server online much, much quicker.
Good luck with your upgrades!
Thursday, August 25, 2016
Configure Two Ironport C Series Devices Where the Backup Hosts the Quarantine
Configure Two Ironport C Series Devices Where the Backup Hosts the Quarantine
These steps come straight from Cisco and it works like a charm. This allows the primary device to focus on email filtering and the second device to take care of the quarantine work. I have another post on how to sync the SLBL on these two devices since users will be getting their information from the backup IronPort.
How to configure two C-Series devices where the backup hosts the Quarantine
Question: How to configure two C-Series devices where the backup hosts the Quarantine Answer All-in-one-plus-one IronPort Spam Quarantine Configuration
Note: This approach will not work if using Centralized Management.
Many sites will run two IronPort appliances, one that is designated as the "Primary MX" server and processes the majority of mail, and a second appliance as a hot spare that is designated as the "Secondary MX." If the Primary MX should become unavailable for any reason, then the normal SMTP protocol will redirect traffic to the Secondary MX until the primary is available again. For sites that wish to deploy the IronPort Spam Quarantine feature for their end-users but do not have enough traffic to justify a dedicated M-Series appliance, we offer the below configuration hints to allow you to configure the Secondary MX system to act as a centralized quarantine for both appliances, and to tell the Primary MX that messages detected as spam should be sent to that central quarantine on the Secondary MX system.
Please note that this configuration should only be used by sites that are not at or near the peak performance throughput on their Primary MX server, or doing equal-weighted load balancing between two appliances, as the additional load of processing end-user quarantined messages could result in reduced throughput in the event of a Primary-to-Secondary fail-over. For high-volume sites whose multiple appliances are running at or near peak throughput, we recommend deployment of the M-Series appliance to offload quarantine duties from your C-Series appliances.
The second IronPort MGA that will contain the IronPort Spam Quarantine, must be able to identify messages coming from the Primary MTA and force the messages to the Quarantine. This can be accomplished by using an X-Header once a messages is identified as spam.
To avoid having two IronPort C-Series MGAs scanning the same message be sure to perform the following steps.
Procedure overview:
1. On the Primary
1. Ensure messages received from Primary MX MGA are scanned for Anti-Spam filtering
2. When Spam Positive and/or Suspect Positive, send to the IronPort Spam Quarantine and add X-Header: X-Ironport-Quarantine
2. On the Secondary
1. add a Mail Flow Policy which by-passes Anti-Spam scanning
2. Add a new Sender Group called "Quarantine_From_Primary", set the order # to 1.
3. Configure this Sender Group to accept messages from the Primary appliance
4. Configure this Sender Group to use the Mail Flow Policy created previously
5. Configure the local quarantine on the "secondary" MGA
6. Edit Log Global Settings to monitor the X-header: X-Ironport-Quarantine
3. Test
If this is not setup correctly one message will actually be scanned by both MGA’s before ending up in the quarantine.
(The following example is using a Sender Group on the secondary MX MGA called "QUARANTINE_FromMail2")
Primary Server
Thu Apr 27 15:05:45 2006 Info: New SMTP ICID 1348 interface Mail (192.168.1.2) address 1.1.1.1 reverse dns host pproxy.gmail.com verified yes
Thu Apr 27 15:05:45 2006 Info: ICID 1348 ACCEPT SG SUSPECTLIST match sbrs[-2.0:-0.5] SBRS -1.4
Thu Apr 27 15:05:45 2006 Info: Start MID 1661 ICID 1348
Thu Apr 27 15:05:45 2006 Info: MID 1661 ICID 1348 From:
Thu Apr 27 15:05:45 2006 Info: MID 1661 ICID 1348 RID 0 To:
Thu Apr 27 15:05:45 2006 Info: Start MID 1661 ICID 1348
Thu Apr 27 15:05:45 2006 Info: MID 1661 ICID 1348 From:
Thu Apr 27 15:05:45 2006 Info: MID 1661 ICID 1348 RID 0 To:
Thu Apr 27 15:05:45 2006 Info: MID 1661 Message-ID <16ac64320604271305o755483cdx28677153c5e4032@mail.spammer.com>
Thu Apr 27 15:05:45 2006 Info: MID 1661 Subject Fwd: Impotenc-e hellp no doc visilt
Thu Apr 27 15:05:45 2006 Info: MID 1661 ready 13559 bytes from
Thu Apr 27 15:05:45 2006 Info: MID 1661 matched all recipients for per-recipient policy DEFAULT in the inbound table
Thu Apr 27 15:05:51 2006 Info: MID 1661 using engine: CASE spam positive
Thu Apr 27 15:05:51 2006 Info: EUQ: Tagging MID 1661 for quarantine
Thu Apr 27 15:05:51 2006 Info: MID 1661 antivirus negative
Thu Apr 27 15:05:51 2006 Info: EUQ: Tagging MID 1661 for quarantine (X-Ironport-Quarantine)
Thu Apr 27 15:05:51 2006 Info: MID 1661 queued for delivery
Thu Apr 27 15:05:51 2006 Info: Delivery start DCID 4789 MID 1661 to RID [0] to offbox IronPort Spam Quarantine
Thu Apr 27 15:05:51 2006 Info: Message done DCID 4789 MID 1661 to RID [0]
Thu Apr 27 15:05:51 2006 Info: MID 1661 RID [0] Response ok: Message 22017 accepted
Thu Apr 27 15:05:51 2006 Info: Message finished MID 1661 done
Secondary Server
Thu Apr 27 15:05:50 2006 Info: New SMTP ICID 121070 interface Mail (192.168.1.2) address 192.168.1.2 reverse dns host unknown verified no
Thu Apr 27 15:05:50 2006 Info: ICID 121070 ACCEPT SG QUARANTINE_FromMail2 match 192.168.1.2 SBRS rfc1918
Thu Apr 27 15:05:50 2006 Info: Start MID 22017 ICID 121070
Thu Apr 27 15:05:50 2006 Info: MID 22017 ICID 121070 From:
Thu Apr 27 15:05:50 2006 Info: MID 22017 ICID 121070 RID 0 To:
Thu Apr 27 15:05:55 2006 Info: ICID 121070 close
Thu Apr 27 15:05:50 2006 Info: Start MID 22017 ICID 121070
Thu Apr 27 15:05:50 2006 Info: MID 22017 ICID 121070 From:
Thu Apr 27 15:05:50 2006 Info: MID 22017 ICID 121070 RID 0 To:
Thu Apr 27 15:05:50 2006 Info: MID 22017 Message-ID <16ac64320604271305o755483cdx28677153c5e4032@mail.spammer.com>
Thu Apr 27 15:05:50 2006 Info: MID 22017 Subject [SPAM] Fwd: Impotenc-e hellp no doc visilt
Thu Apr 27 15:05:50 2006 Info: MID 22017 ready 13907 bytes from
Thu Apr 27 15:05:50 2006 Info: MID 22017 matched all recipients for per-recipient policy DEFAULT in the inbound table
Thu Apr 27 15:05:50 2006 Info: EUQ: Tagging MID 22017 for quarantine (X-Ironport-Quarantine)
Thu Apr 27 15:05:50 2006 Info: MID 22017 queued for delivery
Thu Apr 27 15:05:54 2006 Info: RPC Delivery start RCID 10882 MID 22017 to local IronPort Spam Quarantine
Thu Apr 27 15:05:54 2006 Info: EUQ: Quarantined MID 22017
Thu Apr 27 15:05:54 2006 Info: RPC Message done RCID 10882 MID 22017
Thu Apr 27 15:05:54 2006 Info: Message finished MID 22017 done
Detailed Steps for Primary Server
1. Ensure messages received from Primary MX MGA are scanned for Anti-Spam filtering
1. Ensure that Anti-Spam scanning is enabled
2. Configure the appropriate Anti-Spam policies on the Incoming Mail Policies page to send Positive and/or Suspect spam to the IronPort Spam Quarantine (now hosted on the Secondary MX appliance)
1. (Mail Policies -> Email Security Manager -> Incoming Mail Policies)
2. Configure the default Mail Policies: Anti-Spam settings ; Positively-Identified Spam Settings actions also to include additional X-header:
1. Header Name: X-Ironport-Quarantine
2. header Text: offbox (any text value will work)
3. If desired, repeat the above for Suspected Spam Settings
4. Setup an External Quarantine
1. Designate the Secondary MX appliance as an External Quarantine host by navigating to Monitor -> Quarantines -> External Quarantines
2. Click the "Add Quarantine..." button
3. Enter a descriptive name so you know you are routing to your Secondary MX appliance
4. Enter the IP address of the Secondary MX appliance
5. Change the default port from 6025 to 25
6. Submit
7. Commit changes
Detailed Steps for Secondary Server
1. On IronPort that will host the Quarantine (Secondary) add a Mail Flow Policy
1. Select the Mail Flow Policies, beneath the HAT Overview
2. Click the Add Policy, button
3. Name the policy, example: SpamQuarantine
4. Connection Behavior set to Accept
5. In the Security Features, turn off Virus Protection and Spam Protection
6. Turn Off Sender Verification
7. Select Submit
2. Add a new Sender Group called "Quarantine_From_Primary", set the order # to 1.
1. Open the HAT Overview, add a new Sender Group
2. Click Add Sender Group
3. Name: Quarantine_From_Primary
4. Set Order to 1
5. Add comments
6. Select the new Policy created, example SpamQuarantine
7. Leave other fields, unchecked
8. Click the Submit and Add Senders, at the bottom right.
9. Enter the IP of the Primary IronPort.
10. Add comments
11. Check Submit
12. Configure Local Quarantine
13. Enable Local quarantines
14. Monitor-> Quarantines-> Local Quarantines
3. Edit Log Settings
1. System Administration > Log Subscriptions -> "Global Settings" box,
2. click "Edit Settings..."
3. In the "Headers (Optional)" text box add: X-Ironport-Quarantine
4. Test
1. Send messages that have spam (use X-header: X-Advertisement: spam)
2. Send messages that do not contain spam
3. Review the logs
Monday, August 15, 2016
Backup Cisco Configs Using Putty
Backup Cisco Configs Using Putty
You can easily capture the configuration file from any network devices like Cisco Routers, Switches etc.. with putty. Follow below steps..
1. Launch putty and connect to your Cisco router/switch
2. Enter the user exec mode (router> enable)
3. Enter the terminal length 0 command (router# terminal length 0) in order to force the router to return the entire response at once, rather than one screen at a time. This allows you to capture the configuration without extraneous ??more?? prompts generated when the router responds one screen at a time.
4. Right-click on the menu bar of the Putty screen and select “Change Settings”
5. Go to Session and click on Logging, select “Log all session output”
6. Click on Browse and choose the location and name of the file (I like to place my config file on my desktop – C:Documents and SettingsAdministratorDesktopconfig.txt)
7. Click apply.
8. Now enter the show run command (router# show run), then log out and see the output in config.txt on your desktop (or the location you chose).
This is a pretty simple thing to do and can be a real life saver if you happen to lose the config on a device. It sure is a lot easier to copy and paste it back in instead of recreating it from scratch. Cisco equipment is great but I have seen instances where the running config wasnt saved to the memory and after a restart it reset back to an old startup config or back to brand new (worst case).
You now have the power!
1. Launch putty and connect to your Cisco router/switch
2. Enter the user exec mode (router> enable)
3. Enter the terminal length 0 command (router# terminal length 0) in order to force the router to return the entire response at once, rather than one screen at a time. This allows you to capture the configuration without extraneous ??more?? prompts generated when the router responds one screen at a time.
4. Right-click on the menu bar of the Putty screen and select “Change Settings”
5. Go to Session and click on Logging, select “Log all session output”
6. Click on Browse and choose the location and name of the file (I like to place my config file on my desktop – C:Documents and SettingsAdministratorDesktopconfig.txt)
7. Click apply.
8. Now enter the show run command (router# show run), then log out and see the output in config.txt on your desktop (or the location you chose).
This is a pretty simple thing to do and can be a real life saver if you happen to lose the config on a device. It sure is a lot easier to copy and paste it back in instead of recreating it from scratch. Cisco equipment is great but I have seen instances where the running config wasnt saved to the memory and after a restart it reset back to an old startup config or back to brand new (worst case).
You now have the power!
Sunday, August 14, 2016
Backup Cisco WLC Configuration Without Cisco Prime
Backup Cisco WLC Configuration Without Cisco Prime
This article is part of a new mini-series here on my blog as I work toward obtaining my Cisco Wireless 640-722 CCNA certification.
The official way Cisco wants you to do this is to buy and implement Cisco Prime.
One way you can get around this is to use SolarWinds CatTools to send commands to your devices.
Using this I configured a job to connect to the WLC via SSH and push a backup of the config to my TFTP server. Heres how:
>transfer upload mode tftp
>transfer upload datatype config
>transfer upload filename WLC-Config-Backup_%DateISO%.txt
>transfer upload path .
>transfer upload serverip 192.168.1.5
>transfer upload start
Once you select "Y" to begin the backup youll see in the text a warning that file encryption is disabled. Solarwinds CatTools can answer this Y or Yes if needed. After this the config will push to your TFTP directory.
The variable in the command %DateISO% will automaticaly fill out the date of the file for you. As of now the freeware version is limited to 5 devices and 5 activities only.
If you need more it can scale up from there.
Tuesday, August 9, 2016
Download Mini Windows 7 Sistem Operasi Darurat Untuk Backup Data
Download Mini Windows 7 Sistem Operasi Darurat Untuk Backup Data
Download Mini Windows 7, Sistem Operasi Darurat Untuk Backup Data
Halo, saya kembali lagi untuk nulis blog ini, sebetulnya ide untuk membuat artikel mengenai Mini Windows 7 ini sudah ada dari dulu, namun sekali lagi karena saya sibuk (baca: malas) jadi ahirnya terbengkalai sampai saat ini, hehe. Tanpa basa basi mari kita simak ulasan mengenai Download Mini Windows 7, Sistem Operasi Darurat Untuk Backup Data, dibawah ini
Download Mini Windows 7, Sistem Operasi Darurat Untuk Backup Data
Okeh, artikel ini berdasarkan pengalaman saya pribadi sebagai seorang teknisi komputer, ada beberapa kondisi yang menyebabkan sistem operasi tidak bisa berjalan dengan normal, bisa diakibatkan oleh virus, BSOD, ataupun beberapa kondisi lainnya, dan dalam beberapa kasus sebelum kita meng-install sistem operasi ada beberapa user yang datanya ingin dibackup terlebih dahulu ke drive lain sebelum diinstall ulang, sedangkan data yang dimaksud berada di partisi C atau partisi sistem. Bila kondisi sistem operasi nya baik-baik saja, langkah untuk backup data bisa dilakukan dengan mudah, namun bagaimana apabila sistem operasi tersebut rusak, dalam artian kita tidak bisa masuk ke dalam sistem operasi dikarenakan oleh satu dan lain hal dan tidak bisa melakukan backup data yang diinginkan user tersebut?
 |
| BSOD, kamu gak bisa masuk ke Windows untuk backup data |
 |
| Virus sialan yang mengganggu proses berjalan sistem operasi |
atau yang paling parah seperti gambar dibawah ini
 |
| Missing Opering System |
Untuk solusi kasus di atas sebelum memutuskan untuk merelakan data yang tersimpan di drive C saya menggunakan Mini Windows 7. Mini Windows 7 tersebut tidak perlu kita install sebagaimana kita menginstall sebuah sistem operasi, namun Mini Windows 7 dijalankan secara portable dengan media Flash Disk atau DVD, Mini Windows 7 itu sendiri sama layaknya kita menginstall secara utuh sebuah sistem operasi, dari segi fungsi pun sama, namun sekali lagi Mini Windows 7 ini tidak perlu kita install karena dijalankan secara penuh melalui Flash Disk ataupun kepingan DVD.
Karena Mini Windows 7 tidak perlu kita install otomatis kita tidak menghapus partisi C yang ada di komputer tersebut jadi kita bisa melakukan proses backup data dengan aman tanpa harus takut ada beberapa data dalam partisi C yang diubah. Oya untuk Mini Windows 7 ini biasanya terdapat dalam paket Rescue DVD Hirens Boot, saya menggunakan Hirens BootCD 2012 Rebuild By DLC v1.0. Untuk artikel ini pun saya menggunakan versi hirens tersebut. Edit: setelah nyari-nyari link nya ternyata udah banyak yang koid link Hirens BootCD 2012 Rebuild By DLC v1.0 jadi saya ganti link menggunakan Ultimate DLCD Boot 2014 v2.1, fungsi tetap sama silahkan Download Ultimate DLCD Boot 2014 v2.1 >>Disini<<
Dibawah ini saya jelaskan langkah-langkah untuk menggunakan Mini Windows 7 ini, eh bentar-bentar pada bisa ga nih bikin Bootable USB Hiren nya? Kalo ada yang belum bisa, cek dimari cara Bikin Hirens Boot CD Booting Lewat Flash Disk Yuk ! :D
langkah-langkah penggunaan Mini Windows 7
- Siapkan flash disk yang sudah ada Hirens BootCD 2012 Rebuild By DLC v1.0
- Atur booting di BIOS untuk boot pertama di arahkan ke flashdisk
- Akan muncul menu seperti dibawah ini
 |
| Menu Utama |
- Pilih Mini Windows 7
 |
| Pilih Mini Windows 7 |
- Tunggu sesaat sampai sukses booting dan masuk ke tampilan desktop mini windows 7
 |
| Proses Booting ke Mini Windows 7 |
- Taraaa Mini Windows 7 sudah sukses booting dan bisa digunakan, silahkan backup data penting yang ada di Drive C dengan masuk ke Windows Explorer dan copy-paste ke drive lain.
 |
| Tampilan Desktop Mini Windows 7 |
 |
| Segera Backup Data Penting Dari Drive C |
Sekian artikel mengenai Download Mini Windows 7, Sistem Operasi Darurat Untuk Backup Data semoga bisa bermanfaat untuk semua pengunjung blog saya. Silahkan baca-naca juga artikel bermanfaat dari saya yang lainnya di related post dibawah ini.
asd
Monday, August 1, 2016
Backup SLBL on IronPort C160 Devices
Backup SLBL on IronPort C160 Devices
How do I backup and restore my safelist / blocklist?
Making a backup of the safe list, block list:- Go to the Configuration File option under the System Administration tab on the GUI.
- Near the bottom of this screen you will find the section labeled: End-User Safelist/Blocklist Database (IronPort Spam Quarantine).
- Press the button labeled "Backup Now". This will save a copy as a .csv file in the configuration directory on your appliance.
Moving the backup to another box:
- Make certain that you have the FTP service enabled on one of your network interfaces. This would typically be the management interface. You can check this in the IP Interfaces section under the Network tab on the GUI.
- From your file server, FTP to the IronPort appliance on the above mentioned interface.
- Login as an admin user.
- The backup file you made earlier should be right there in the root directory.
- This is basically the reverse procedure of the backup.
- FTP the file from your file server back to the IronPort appliance in the configuration directory.
- Go back into the Configuration File section under the System Administration tab.
- Press the "Select File to Restore" button.
- Select from the list of valid backup files.
Subscribe to:
Posts (Atom)