Is there a way to configure the TFS Scheduled backups to perform a retry if the backup fails? Specifically for full backups.
We're having problems with contention for resources and it fails and gives up.
There isn't the feature in TFS backup, we cannot achieve that.
I help you submitted a user voice here:
https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/20070241-retry-the-backup-when-a-scheduled-backup-failed
You can go there and vote it up to achieve that in future.
Related
I have been trying out TFS 2017 on Prem Release Management.
For the most part I like it. I am having some frustrations with managing the status of each release.
There is an indicator in the overview panel to show if each environment's been deployed to (successful, failed, or in progress). That's fine, but how to we track the state of the overall release?
Customer's are fickle. I can have a customer ask me to delay a release, with a detailed explanation as to why. I can have our infrastructure team put our release on hold as well. I can think of several different status indicators for the release over all to track this information: TFS 2017 from what I can see does not track any of this.
Why not? Is tracking the status of each release not important? Am I just using the tools ineffectively?
I have managers who want to know what's going on with a release. They don't want to know what environment's are done, they want to know what's going on at a project level. I would imagine some sort of work item is in order here...
Am I missing something?
Sounds that you want to track the release like the process of Code Review/Pull request, introduce the communication process for release management. Record the comments/reasons for team communication and start the release when all the contributes agreed and approved.
There isn't such a mechanism introduced for now, you can Abandon/Delete the release and start new release if needed. You can track each release under the Release tab.
Whatever, you could submit the User Voice item to suggest the features you want: https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services
is it possible to configure a hard limit on the number of open changes for a given project in Gerrit?
When too many changes accumulate, rebasing them becomes an issue, especially when every rebase triggers a Jenkins job which takes some time to complete.
Hence I am looking for a way to force a limit on the open changes, so that Gerrit rejects new changes when too many are still open.
Thanks for help in advance.
You can start with git hooks. You can then use gerrit's ssh api or directly talk to gerrit's database to query outstanding gerrits.
Alternatively, consider using polling in jenkins instead of triggering a build on every change.
I have never written a windows service or any scheduler before so I couldn't figure out what to do.
I need to write a windows service. There is a Report table in my DB, and I need to check it every day to see if there are new reports added. Reports have receivers and the time settings, such as 15th of every month at 14:00, or daily at 12:35 or weekly on Wednesdays at 13:00. And I need to send emails with some reports at these times.
As I have decided, I will use Quartz.NET. But there are a couple of things I don't understand. So I will have 2 Jobs I think. One for checking the DB every day, to see if there are new reports that users want. And when I receive them, I'll create new different amount of Jobs with new triggers based on the times in the DB? Do I create new triggers in the job of the first daily check? I didn't understand it.
And when for example a time of one report is updated, or deleted, Do I need to delete the Job and the trigger from the scheduler? I'd appreciate the help. I am using VS 2015 with C#.
And when I do the windows service, I'll just initiate this Quartz thing that I have written? Sorry I couldn't understand what I have read so far.
I would recommend Hangfire IO over Quartz.net
http://hangfire.io/
Its a more modern approach to scheduled jobs. In the past I've used Quartz.net as well. First of all, using hangfire requires no service. The jobs are persistent, and retries are built in. The syntax is also easier.
I've used hangfire and its wonderful and simple.
however, Hangfire does not support Oracle db so far. Also Quartz provide more flexibility in terms of scheduling (calendars, end dates etc).
Our TFS2012 deployment is currently quite simple:
Virtual Windows Server with TFS, Sharepoint, Reporting, SQL Server and Builds all on the same machine!
Is using the TFS admin console backup tool and/or backup of the entire machine enough to recover from a disaster?
There is no clear-cut criteria, you may take a look at TFS planning and disaster recovery guidance for a more comprehensive answer.
Shortly, you must be sure at least that
Backups are saved on different hardware, and possibly copied to a remote location
Along with your backups you have the recover instructions and install packages
This guarantees that you are able to recover, but it can take a long time, depending on the disaster impact (someone deleted a record vs. the server room has burnt) and the size of your data.
I'm in the process of setting up a backup plan for a Team Foundation Server. I downloaded Power Tools for TFS and I'm using the Backup Plan Wizard that was included in that pack. I am now at the step where I'm supposed to decide how to schedule the backups and I have no idea what to choose for my setup.
I get what everything means, except Transactional Backup Interval.
I would appreciate suggestions for a good schedule. What I would like to achieve is being able to restore and still look back a few versions, if possible. The minimum backup I would like to have is the latest version.
It might be important to add that I got to choose "Backup retention days" earlier and set that to 30.
The transactional backup interval likely refers to how often transaction logs for your TFS databases are backed up. The schedule you choose will probably depend on how busy your repository is.
At my current client there are six developers, and we share some of the load for source control between VSS and TFS (we're transitioning). Corporate policy says we must backup transaction logs every hour during business hours, and an additional one at midnight. Our local backups are on a four-day retention cycle with off-site backups lasting years.
I would make a decision based on how much work you'd want to lose if your repository was lost and your working copy was destroyed simultaneously (natural disaster?).