This system is capable of converting the backup of a physical machine to a standard virtual machine, as well as just clone a hard disk. They even support a simultaneous send to an off-site target, as well as the pre and post script execution. They can be full every time, or incremental at any defined interval imaginable. The backups can be granularly restored, mounted as a drive letter, restored as a complete image to same or disimilar hardware. This is to insure high availability of the application to the sales department and to my Las Vegas plant. The SQL server is a Marathon Technologies Everrun HA mirrored pair. I am also able to do the same with a workstation while the user is using it. I have been able to completely back up my SQL server and my separate SBS server in the middle of the day with users active with very little performance impact. The manager is not required, but is nice when multiple servers and workstation need to be centrally managed. It does not have to be a server and can be a workstation. All servers and systems that back up target external USB drives attached and shared on this server. I run the manager on a backup domain controller. I am using Backup Exec System Restore Server V8.51. The concept is great, but the execution is horrible. Even doing an inventory from a tape takes around 6 hours. I recommend strongly against using these units as they have caused nothing but pain. The DDT unit itself is a stand alone HP D2d120 device with an internal Ultrium LTO3 drive that is connected to the main network via iSCSI. the first Friday of the year is kept for at least 7 years (as required by law) and has a tag set in Backup Exec to "never overwrite" and is labelled "Year End 2008" or whatever.the first Friday of the month a special full backup is taken and stored off-site and kept for 12 months and labelled "January Monthly", ect.Friday night backups are kept for a month and labelled "Friday Week 1", Friday Week 2", "Friday Week 3", "Friday Week 4", "Friday Week 5".week day nights last for 7 days and are rewritten every week and are labeled "Monday nightly", "Tuesday nightly", "Wednesday nightly", "Thursday nightly".Once a week there is a full backup of everything other than the system volumes. All essential data (finance, SQL, customer databases, AD, etc) but not archived data or non-essential IT stuff (isos, WSUS database, archived documents, useful for IT but not irreplaceable) is backed up nightly. Procedure-wise, the information on the servers are broken into two arbitrary 'chunks'. Tapes are taken off-site every night with the weekly full backups kept in a secure off-site storage facility. There it is then burnt onto tape during a separate batch job. This would make for a better recovery point and faster restores in case of system failure.Īll backups use a disc to disc to tape setup with Backup Exec piping and compressing the data to a Tier 3 SAN during the normal backup tasks overnight. As our servers are virtualised, this is being reviewed with the aim of replacing the system volume snapshots with snapshots of the virtual machine vmk files. Shadow Protect's snapshots are copied onto a removable 1Tb USB HDD and stored off-site in a secure off-site storage facility. That being said, if you don't trust this method, there is nothing stopping you from setting up a backup job and just having Mozy backup your *.bak files.Backup is done using Backup Exec 12.0 for all data on all servers, and using Shadow Protect to take monthly snapshots of all system volumes. Here is the MozyPro manual (PDF), which describes how to restore SQL Server backups that were made using VSS. Here is a white paper on how the SQL Server 2005 SQL Writer works with VSS. So this is definitely a valid way to back up SQL Server databases. SQL Server 2005 has been engineered so that VSS backups are consistent. MozyPro uses the Volume Shadow Service (VSS) to create backups for SQL Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |