Manually Backing up and Restoring TFSI have encountered a great deal of companies that are at risk when it comes to backing up their TFS databases. Some just turn it over to the DBA team without any conversation about data loss risk or the periodicity of backups. Many of these customers put their databases in Simple recovery mode and perform weekly full backups. Others do the full backups daily, but still do not manage the transaction logs. Their assumptions are that if disaster strikes they will be able to reinstall TFS, restore the last backup of their databases and then TFS will magically start working again.
![]() How to Unlock Mobile Phones. When you purchase a phone from your carrier, it usually comes locked to their service. If you want to use the phone you purchased through.Their assumptions are wrong. TFS utilizes multiple databases to store data for source control, work item tracking, server configuration and reporting. In order for TFS to perform correctly, these databases must be kept in a synchronized state. This creates challenges for traditional disaster prevention strategies in regards to database backups. Since a backup of the collection database could be occurring while modifications are being made to the configuration database and vice versa. The time offset of the two backups could be significant either by design due to the backup plan or because the collection database is large. My current customer has a collection database that is over four terabytes (which is ridiculous by the way, since about half of the database is made up of old test attachments, but that is a subject for a different blog). It takes them about five hours to perform a full backup and before I arrived that was the only kind of backup they performed. To address the need to ensure, at a minimum, that the collection and configuration databases are kept synchronized, transaction log marks are employed. ![]() That way, if disaster strikes the databases can be restored to the same consistent point. My customer at least understood that the databases were supposed to be kept synchronized. Their answer was to take TFS offline once a week and perform the full backup which caused several hours of downtime every week. Just to be clear, the databases do not have to be taken offline or access restricted to users during the backup process. There is a better way (obviously). In fact there are a couple of better ways. The first alternative is to use the TFS scheduled backup utility that as of TFS 2. Update 2, is included in the base product. Previously, it was part of the TFS Power Tools. The built- in utility makes the process of creating backups of all the TFS related databases easy. The restore process is also straightforward when the tool is used to complete the backups. We can develop any win32 software for CDMA phones according to your custom requirements: To unlock SPC, MIN, PRL, Repair MEID, ESN, Akey, SSD, etc. How to Recover Backup Password to Restore iPhone Backup Files for Windows Step I. Key Container File Importing. Click "Open" to open the Key Container File which you. TFS Scheduled Backup Tool. However, the simplicity does not come without disadvantages: 1. There is no option for configuring alternative security credentials for accessing the backup folder. The TFS service account must be used. There is no option for specifying different backup retention policies for the different backup types. There is very little logging associated with the utility. Notification is limited to TFS administrators. The data team has no visibility in the progress of the job. It is managed completely with the TFS Admin console. Data recovery is limited to the periodicity of the transaction log backup. This is mostly trivial, since the log backup periodicity should be less than the acceptable data loss period. But having multiple log marks in a single log backup is not supported with the tool since the log marks are all named the same and performed in conjunction with the log backup. The full documentation on how to configure the TFS backup process can be found at: http: //msdn. It is well documented as long as you are using the built in tool. However, if you manually backup the databases, the tool will not work for the restore process. My colleague Martin Hinshelwood would tell you that is why you should just use the tool and he is probably right, but my background as a DBA cringes at the loss of control and visibility the tool costs for the gain of simplicity. That being said, if you are a small development shop and you are managing your own database deployment, by all means, just use the tool. Larger organizations and those with more structure and controls built around the database environment will most likely prefer to manage the TFS related databases the same way they manage all other database resources. The important issue is that the databases all get backed up and the interdependent TFS databases are synchronized. Since the backup process is already covered in detail, I will just show an implementation that I have used a few times that works well. Backup Plan Overview. For our discussion, the TFS backup plan is implemented by four distinct SQL Server Agent Jobs which also handle the backup file cleanup process: 1. TFS Weekly Full Backup Weekly full backup of all TFS associated relational databases (excluding Share. Point, which for the sake of this discussion is assumed to be managed separately): a. TFS Daily Analysis Database Backup. Daily backup of the TFS Analysis Services database: a. However, in most cases a restore will take significantly less time than a rebuild and will allow for instance access to TFS reporting. If TFS reporting is a high- value component for your organization, I would highly recommend including the Analysis database backup. Report. Server. Temp. DB*Additionally, the encryption key for reporting services also needs to be backed up. This can be done from the report server with either the Reporting Services Configuration utility or with the RSKEYMGMT command line tool. This key is required to attach reporting services to a restored Report. Server database and maintain the data source credentials. However, if the key is unavailable or lost, reporting services can still be configured, but the security credentials for any data sources (TFS just uses two out of the box) will need to be deleted and re- entered. Depending on their volatility, their backup periodicity could be longer with perhaps only a weekly full backup and the databases placed in Simple recovery mode. For the purpose of explanation we will use the following backup schedule: Backup Type. Periodicity. Schedule. Full. Weekly. 02: 0. Sundays. Analysis. Daily. 00: 0. 0Differential. Daily. 02: 0. 0 Monday – Saturday. Transaction Log. Hourly. Hourly. Backup file retention is managed by the backup jobs. Backup Type. Retention. Full. 3 Weeks. Analysis. Days. Differential. Weeks. Transaction Log. Weeks. Backup Plan Details. The SQL Agent jobs that implement the backup plan are broken down in to multiple steps as follows: 1. Execute full Backup of all databases (Transact- SQL Script). DECLARE @db. Name nvarchar(1. DECLARE db. Cursor CURSOR FOR. SELECT name FROM sys. WHERE name LIKE 'tfs. Delete all full backup files older than 2 weeks (Power. Shell). $dir = . Execute backup of Tfs. Overwrite existing backup file (SQL Server Analysis Services Command). Backup xmlns=. Execute differential Backup of all TFS specific databases (Transact- SQL Script). DECLARE @db. Name nvarchar(1. DECLARE db. Cursor CURSOR FOR. SELECT name FROM sys. WHERE name LIKE 'tfs. Delete all differential backup files older than 2 weeks (Power. Shell). $dir = . Execute the stored procedure msdb. If a new team project collection is added to TFS, the stored procedure will automatically add the required artifacts to the new database as long as the database is named with the default “TFS. Execute transaction log backup of all specific databases (Transact- SQL Script). DECLARE @db. Name nvarchar(1. DECLARE db. Cursor CURSOR FOR. SELECT name FROM sys. WHERE name LIKE 'tfs. Delete all transaction log backups older than 2 weeks (Power. Shell). $dir = . Record the log mark information in a file in the backup folder (SQLCMD). W - Q . Since all the log marks are named the same, why should we care? The answer is simple; I like documentation. Besides if you lose the entire SQL Server, or if someone drops a database without preserving the backup history, the MSDB database will have no record of log marks and when they were performed. Cleanup old log mark data for deleted transaction logs. DECLARE @db. Name nvarchar(1. DECLARE db. Cursor CURSOR FOR. SELECT name FROM sys. WHERE name LIKE 'tfs. Restore the most recent full backup of the databases. I have shown just the Configuration database as an example, but the steps would obviously need to be done for all the remaining databases. This restore is completed with the “NORECOVERY” option to facilitate the restoration of the differential and transaction log backups. If the files are not being restored to the same physical path that they originally resided on, the “MOVE” option must be specified. I add the “STATS = 1. I can monitor the restore progress. Restore the most recent differential backup with the “NORECOVERY” option. If no differential is available due to recovery being required prior to a differential backup, skip this step. Sequentially restore all transaction log backups that were performed since the last differential backup, or the last full backup if no differential backup is available. Restore the last transaction log in the sequence with the “RECOVERY” and “STOPATMARK” options to ensure that all databases are restored to the same point “transactionally” and not necessarily in time. Repeat these steps for all the specified databases. If for some reason it is desired to restore the databases to an earlier point than the latest transaction log, the RECOVERY and STOPATMARK options can be specified earlier in the chain. Be aware however, that once a database has been “Recovered” no additional backups can be applied. If the database is prematurely recovered, the restore sequence must be restarted at the beginning. If you choose to execute the log mark stored procedure before every Full and Differential backup, the STOPATMARK option can be used with those recover options as well. As a final unsupported option, in the case where no log marks are available for whatever reason the STOPAT option can be used as a last resort (STOPAT = . How to Update ASUS Zen. Fone 2 Laser to Marshmallow Manually. Good News for Zen. Fone 2 Laser users, Asus starts rolling out Android Marshmallow update for Zen. Fone 2 Laser. The update is an Official Beta which rolled out in phase wise manner. The update is rolling out via OTA (Over the Air) but for those who don’t want to wait for the OTA update can manually Update ASUS Zen. Fone 2 Laser to Marshmallow. If you don’t like the stock ROM then you can also download CM1. ROM for Asus Zenfone 2 laser. The ASUS Zen. Fone 2 Laser runs on Android Lollipop but now you can Update ASUS Zen. Fone 2 Laser to Marshmallow. The new Marshmallow update packed with features like Now on Tap, Doze Mode, App Permissions and more. The Android 6. 0 Marshmallow update for ASUS Zen. Fone 2 Laser available via OTA (over- the- air) and it is about 1. GB in size with build number V1. Here we provide you the OTA zip file with that you can Update ASUS Zen. Fone 2 Laser to Marshmallow manually via ADB. You check the ASUS Android M Update Timeline from below. List of Asus Phones to get Android Marshmallow Update –ASUS already posted an update on its Android 6. Marshmallow rollout plans, the list contains eight phones which will receive a Marshmallow update. ASUS Zen. Fone 2 Laser ZE5. KL receives the Marshmallow update and model numbers ZE5. KG/ZE5. 50. KL/ZE6. KL/ZE6. 01. KL would be next in line. Pad. Fone S (PF5. KL)Zen. Fone 2 (ZE5. ML, ZE5. 51. ML)Zen. Fone 2 Deluxe (ZE5. ML)Zen. Fone 2 Deluxe Special Edition (ZE5. ML)Zen. Fone 2 Laser (ZE5. KG, ZE5. 00. KL, ZE5. KL, ZE5. 51. KL, ZE6. KL, ZE6. 01. KL)Zen. Fone Selfie (ZD5. KL)Zen. Fone Max (ZC5. KL)Zen. Fone Zoom (ZX5. ML)Note: –Make sure you at least 2. GB of free space on your device. This process is only for ASUS Zen. Fone 2 Laser (ZE5. KL) so don’t try this on any other variant. Battery level should be 7. Update ASUS Zen. Fone 2 Laser to Marshmallow. It is recommended to take backup of your device and do a factory reset after installing the update if you are facing forced closed error. Download Marshmallow OTA File for ASUS Zen. Fone 2 Laser –Download ASUS Zen. Fone 2 Laser ZE5. KL Marshmallow update file – (Download). To enable Developer Options, go to About phone and tap the Build Number 7 times. To update Asus Zenfone 2 Laser to Marshmallow manually, you must be on software version 1. Check at Settings> about> software version). Download ADB and fastboot driver for windows or ADB and Fastboot for Mac and install it on your PC. Download the Android Marshmallow Beta for Asus Zenfone 2 laser ZE5. KL from above Copy ROM to a folder. Now Turn Off your phone and boot into recovery mode by pressing Power+Volume down. Choose Apply Update from ADB8) Now Connect your phone to Laptop/PC9) On Marshmallow beta ROM folder press shift+right click and click on open command here. Now check your connection by typing the below commandadb devices if your device is listed you’re ready to flash the ROM1. Flash the Marshmallow Beta ROM on Asus Zenfone 2 Laser by typing below commandadb sideload WW! If you have any questions, comment below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
August 2017
Categories |