8

That article you link is wrong. There is no way to specify the retention policy in Windows Server 2012 when backing up to external disks. I don't know why they lie like that... The configurable retention policy feature DOES, exist for the Windows Online Backup feature that you can use in Server 2012. Possibly this is where the confusion arises. AFAIK ...


8

OK, the reason Windows Server Backup is failing is because of the cluster size you're using on the volume. (And I'll explain exactly why that is at the end, after the important issue of your RAID array being a time bomb.) But before addressing the backup issue, we need to address the issue with your RAID setup. Don't use RAID5 with large disks. And don't ...


7

Take a look at the cloudbackup\operational event log on the client. Additional logs are in C:\program files\Microsoft Azure Recovery Services Agent\Temp. In that directory take a look at CBEngineCurr.errlog, which should contain the step by step details on issues.


5

Change your VSS for the system partition to use the C:\ at present it doesn't have enough space to create VSS for itself so fails the backup.


5

Yes, an iSCSI drive formatted with a given file system can be mounted by every system that can connect to the target and can understand the file system. On a logical level, the target is nothing else then any other block storage like a physical disk connected via e.g. SATA, SAS or USB. So, any system that can handle the Windows backup media format can use ...


5

For the case, it seems to be useful to mention 3-2-1 rule that should be used for planning Backup strategy. Since you want to have a full backup of Windows Server 2008 to be able to restore the entire system in case of any issue, I would suggest you virtualize your server and deploy/run its VM on virtual block level storage with the ability to replicate it ...


5

Ultimately, the most straightforward solution was to add a custom defrag task, with commandline parameters specifying a 'traditional' defrag. This consolidated the thousands of fragments into contiguous files, which in turn let the vhdx image avoid having to include all that empty space between fragments due to its 2MB BlockSize. Eventually the server ...


4

Basically, you have already anwered to you question by youown. You can mount the same iSCSI LUN from a different server without initializing and formatting it as a new drive, but unmounting LUN from previous host. It's correct, NTFS is not shared File System and only a single host can use it at same time. We are using cluster of two hosts with StarWind ...


3

This could be due to shadow copies of your backups. Run this command in elevated cmd to view reserved storage for shadow copies (replace X with your drive letter): vssadmin List ShadowStorage /On=X: To lists all existing shadow copies of a specified volume use: vssadmin List Shadows /For=X: You can delete shadow copies. If /Oldest argument is given, the ...


3

Personally, I would suggest Get a different backup program -- I don't know much about Windows Server Backup on SBS, but I know that dedicated backup programs are specifically designed for the kind of workflow you're describing. If you want to try to save costs I'd suggest you shelve your current backup drives and buy new ones, then configure a proper backup ...


3

I'm rather disappointed that I ran into this fairly serious problem 2 years after this question was posted - and this was on a new install of Windows 2012 Essentials with (I think) all updates installed. Fortunately, a HotFix was released last year: http://support.microsoft.com/kb/2833738 This worked for me. I was able to add a new disk to backup with the ...


3

Obviously @Tamerz problem has been resolved but the solution doesn't help other people since it just started working. I see many people struggling with this same problem and I found several things that may be helpful for others. If you look in Application Log of the Event View you will find entries with the backup failures. This will mention an error ...


3

Volume shadow copying may stop working at times for a number of reasons I don't really get. But I have had success in making the VSS service run correctly again by deleting all existing shadow copies on a particular volume. Do like this in an elevated command prompt: vssadmin delete shadows /for=c: /all I see that you tried to reset the VSS copies for your ...


3

In my case I just needed to set the Volume Shadow Copy Service (VSS) to manual and stop the service. I've seen before where forums will suggest setting this service to automatic; bad advice. I've never seen that fix anything related to VSS.


3

No. The way Windows Server Backup is designed1, it will only let you back up local drives. You can use network shares as a backup destination, but you cannot include a network share as a backup item. You might want to consider a robocopy script to your backup destination as an alternative. If you need a history similar to Windows Server Backup's, just add ...


3

This is possible and should work fine. If the local system fails you can also restore on the other server using this guide: https://blogs.technet.microsoft.com/askpfeplat/2012/12/24/windows-server-2012-how-to-import-a-storage-pool-on-another-server/ One thing though, 4 eSATA drives doesn't sound reliable and scalable. If you need to add more disks later ...


3

At its most basic: You put the files (the SQL Database and its transaction logs) somewhere that SQL can access them, and then you "attach" an existing database, pointing it to those files. You can do this through SSMS by right-clicking on Databases and choosing Attach.... However there is no guarantee that this database you are attaching will come up ...


3

I assume, it happens bacause of "computer credentials" change. Computer account password refresh is automatic process that happens between computer and domain controller without notification to or interaction with the user. Check 2-nd reason here Just login with local Admin and rejoin domain.


2

You are right in your assumption that WSB has created shadow copies. It uses these copies to maintain a backup history. If you still have backup versions (and thus shadow copies) of points in time before your dedup optimization job has run, you would not see any savings at all since the deduplicated blocks have not been freed - they are needed for an older,...


2

Windows integrated backup use VSS to snapshot the filesystem, then backup the files from this snapshot. As snapshot can not contain other snapshots, the answer to your question is no.


2

This issue is primarily connected with the installation of the Microsoft SharePoint Foundation 2010 Service Pack 1. To fix this, perform the following steps: Open an Administrative command prompt. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd ...


2

As Evan Anderson's comment says, Windows Server backup uses VSS to store backups unless it's writing to a network share. This is why your backup storage disk is hidden from Windows explorer (and you, unless you're using specialized tools): VSS wants to choose where to write the backups. Because VSS isn't supported on UNC destinations, you'll only be ...


2

The incremental backup will work when you assign a dedicated disk that will be formatted by the Windows Backup Software. If you use a shared location each time it will run will create a new full backup!


2

Another way you view the Microsoft Azure Backup Agent logs is accessing. Server Manager > Diagnostics > Event Viewer > Application and services log > CloudBackup > Operational. You will have a record of logs for the service


2

After googling a lot - I have found the answer. It seems that the performance hit is the whole time the server is running and not just during backups. This is because all writes to disk are made twice - once to the disk and once to a "copy of changes list" (to simplify). If the server is mainly readonly then that isn't a problem. if it is read/write then ...


2

It depends on if your SAN backups quiesce the data and log files (mdf and ldf files). A SAN backup solution that does support SQL Server will hook into the SQL Server VDI interface and quiesce the database prior to taking the backup. If you were to run such a backup and then look in the SQL error log, there will be messages stating that the IO was frozen ...


2

You should try to enable Inbound Rules "Remote Service Management" (NP In) in Windows firewall, as @kt 2000 wrote in this thread https://social.technet.microsoft.com/Forums/msonline/en-US/2c8e11f0-020e-459e-b4ed-b2fe30a17342/windows-server-2012-backup-blbmmcdll-mmc-has-detected-an-error-in-a-snapin-and-will-unload-it?forum=winserver8gen. Also, there are few ...


2

It doesn't care as long as the path includes WindowsImageBackup. When we were attempting a restore we created an ISO and the name of the CD was WindowsImageBackup - we re-burned it with the folder WindowsImageBackup as the root and it showed up in the wizard. I've done this via CD, mounted ISO, and UNC.


2

I would suggest ROBOCOPY, more information here: robocopy Use /z so if the transfer is interrupted it can be resumed. With some other good references: Here And Here Then to fix the issue of 15 minutes log out, one suggestion would be to run this as a scheduled task. That way it runs as a background process and doesn't require an interactive user session ...


2

Failover clustering, as you mention, is probably your best bet here. You need a minimum of 2 servers (not 3, thankfully). Your best options would be either to: Individually cluster the services running atop the 2 physical servers (i.e. install AD,DHCP,DNS on each of the physical servers and make them aware of one another using their native functionality) ...


Only top voted, non community-wiki answers of a minimum length are eligible