Mhystique
Level 3
Joined 16 years ago
User Profile
User Widgets
Contributions
Re: Changing date on a scheduled full backup job for 1 or 2 times only
Not entirely, what I'm seeking is something like this. If I exclude a Friday which have a full backup, is should auto change the full to Thursday instead. If that is possible. If I understand it correct, when I exclude the job will just not run on that day.852Views0likes0CommentsChanging date on a scheduled full backup job for 1 or 2 times only
Hi Is it possiblein Backup Exec 2012, to get a full backup job to run on a diffenrent date then scheduled for 1 or 2 specific dates? My setup is this: Everyfriday night I'm running a full backup, Mondag to Thursday I'm running af differential backup. First I do it to disk, and when that's done a linked job is started which do the same backup to tape. New tape very day, switched by hand. I my country we have a national holiday next Friday, which means that no one are at the office, so the tape from Thursday can be switched, and Iwill notget a full backup for that week. Is there someway, I can set it up to understand that on specfic dates, the full backup should be executeted on Fridays, but Thursdays instead? I'm not found about switching it manually before and after each date, cause we got a lot at jobs, and the possiblility that we miss something is likely. Regards LarsRe: Database maintenance failure: Query timeout expired
Hi, just some extended info. I don't know that the ackup Exec embedded DB is in, but throught is was an SQL Express. With BEUtility I move this to another server with a full MS SQL 2005 on it. By default BEUtility placed the DB files in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data. I don't what that as we haven't got much space on drive c, so through SQL Server Management Studio I detached the DB, moved the files to drive D and attached it again. For some reason when I restart the SQL and backup services, the DB files is again placed on drive C. That is my headeag right now. How do I moved the DB, so it stays there?992Views0likes0CommentsDatabase maintenance failure: Query timeout expired
Hi, for the past 2 weeks, we have had some major issues with our backup, as the database got to the max size for an SQL Express. After some troubles we managed to move the database to an full SQL Server on another server. Finally resulting in backup jobs to work Again. But now I see that the database maintenance job isn't working, and I'm thinking that perhaps can explain why databse grown to max size. I need the maintenance job to Work, but can't find any solution, so here I am, hoping you guys can help. This is what the latest job said: * Saved contents of BEDB database * Optimized BEDB database size from 4338.63 MB to 4266.19 MB * Deleted expired data for BEDB database: 0 empty legacy backup-to-disk folders were deleted 0 expired reports were deleted 42 expired job histories were deleted 122 expired alert histories were deleted 45 expired job logs were deleted Maintenance has failed: -536837662, -536837662: :: -2147217871:Query timeout expired Total elapsed time: 00:09:31 How do I fix that?Re: Ability to bundle multiple servers in a single job
To answer our first problem, here is what we did. We simply made the jobs to start at a later time. BE will then queue it, and start when all the preceding jobs are done. EG: Server 1 starts at 10 Server 2 starts at 10:15 and so on If you what to change the order, you then have to do it by manipulating the time for the job, and the jobs around it.2.3KViews0likes0CommentsRe: Backup Exec 2012 licensing problem
Well first I received several slf files from my vendor, which didn't work. The number matched what was in the certificate. Then I finally got into the licensing portal for about 5 min and got it to send en combined slf file to me. But that didn't do the trick either. Now I can't get into the licensing portal again :-(1.4KViews0likes0Comments