Hello,
I plan to deploy a W2012 HyperV with 2 VM : a File Server with DC and an Exchange Server.
However, I have many questions about backup using the standard tool Windows Server Backup 2012 :
1) Should the VM backups be initiated from the VM itself, or from the HyperV ?
2) Is it possible to backup the HyperV itself ? And will this backup include the VM ?
3) How is it possible to backup to an iSCSI drive ?
4) How is it possible to perform a full restore of a VM from a iSCSI drive ? Using the boot CD ? From the HyperV ?
5) The full restore of the only DC of the domain is it possible ? And how (will the HyperV start and allow restore without DC available) ?
6) Is it possible to tranfer VM from 1 HyperV to another, using this backup on iSCSI drive ?
Thanks in advance for your help.
Hi Team,
I have to migrate my Windows server from 2003 to 2008 on which VB/VC++ components are installed. Please tell me if there will be any compatibility issue if I do Windows server 2003 to 2008 upgradation and what all will be required for that upgradtion.
Windows server 2008 r2 is not starting in normal mode but it is starting in safe mode
so is there any option or possibility to start in normally or repair the window.
Please help
I know for domains that aren't at domain functional level 2012 you cannot recover from snapshots due to problems with USN rollbacks. With 2012 and newer hypervisor technologies that has been fixed.
We are looking at some different backup technologies that use VMware snapshots as part of their solution (Veeam and Unitrends to be precise). I want to make sure that I understand something correctly. Snapshots are a problem with Domain Controllers, but if the backup technology is VSS-aware, the USN rollback issues are taken care of. A more generalized statement would be: using snapshots on a DC is okay as long as the application taking the snapshot is VSS-aware. Is that a correct statement?
Hi guys,
I hope that you could help me.
I have a problem with the number of the visible Previous Versions. We already change the number of the copies to 256 following https://msdn.microsoft.com/en-us/library/windows/desktop/bb891959(v=vs.85).aspx#maxshadowcopies . What I found was that there is a limitations of the visible previous versions for Windows Server 2008, 2008 R2 and it is fixed in 2012 and 2012 R2. Is there any way to change the number of the visible previous versions? I found some suggestions to disable SMB2 but it's not recommended an I don't want to do it.
Thanks in advance
What is the solution to get past this Windows Server Backup (WSB) failure and error 2155348010? What is the correct process to have WSB use a 3TB external drive with 4096 sector size as the destination drive?
I am using a Western Digital (WD) Red 3TB drive in a usb 3.0 docking station as the WSB destination disk with the recommended destination setting (which appears to setup fine, but the schedule job fails after 385gb, so something worked).
The similar job works fine with WD Red 1TB drive, so it must be the 4096 sector size vs 512 size difference and VHD. I know there has been work done with 2012 to use 4096 sector size drives, but is this available in WSB with vhdx? Can vhdx be used instead of vhd with Windows Server 2012 Backup, and how to do it?
WD has a Quick Format tool which may work to emulate 512 sector size, but WSB reformats a new disk, so how to use the WD tool with WSB accepting the WD formatting?
There is a lengthy discussion at the following post (immediately scroll to the end), but not specific to Windows Server 2012. What is the MS recommendation for version 2012?
We set up a Scheduled Vss Copy Backup of several folders to copy to an empty volume that had 3.63 TB of free space. The backup was successful for the majority of the data, but several files failed with the following error:
Error in backup of <file path & file name> during write: Error [0x80070070] There is not enough space on the disk.
The odd thing is, the data transferred stopped at 1.99 TB even though the volume had more free space. We had 85,900 files that were not backed up and got this error.
Does Windows Server Backup have a limitation on a single backup 'data transfer' size? Why did it 'stop' writing data at 1.99 TB even though the drive had a capacity of 3.63 TB?
Thank you!
Elizabeth
We are planning to implement a backup solution in our environment using Windows Server Backup. Testing in our Test environment has been successful, but implementing a small-scale one-time test in our Production environment is not going as I expected.
Namely, as a test on our Production file server, I am using Windows Server Backup to back up a single folder with 6 files and is 512 KB in size (total). I used the Backup Once Wizard to back up this folder to another drive as a test. It has been running for almost 2 hours now on the "Scanning file system..." step. The drive that contains the small folder with the 6 files I am attempting to back up has 3.08 TB total of data (several thousands of files and folders).
Why is the "Scanning file system" step taking so long? Is it enumerating all files and folders in the drive, not just for the folder I want to back up?
When this "Scanning file system" step ends, will it take as long each subsequent time we try to do a "Backup Once" type of backup (using the GUI or using a Powershell cmdlet)? This was only a test, so I'm not going to set up any incremental backup based off of this small folder test.
Ultimately we are looking to do a weekly or monthly backup of a folder that contains about 1.5 TB in data total. If we were to kick this task off for the first time, generally how long can I expect it to take? Longer than 24 hours? The length of time it takes may dictate whether we end up using this tool for our backup solution or switch to something else.
We've been running out of space on our CSVs. I determined that the hidden System Volume Information directory is huge. It is huge because of large VSS files in the directory.
Path to CSVsHi Guys, trying to figure how to get the amount of data transfered during the last "ran" backup job .
i found get-wbjob -previous 1 and with that i get start and end, but not the ammount of data transfered.
I know it runs a differential backup, but it would be nice to know how much data was transfered :(
Anthony Cartier-Info
Hi all,
I'm remotely trying to configure a Windows Server Backup job.
We added new drives to the server but we need to ensure that the drive will be getting backed up. So I've tried to edit the current Windows Backup Job and received the following error message:
windows backup the filename directory name or volume label syntax is incorrect?
I've tried to research this error but alot of post refer to adding additional backup drives not resolving editing current backup jobs Ive also tried removing old drives but end up with the same error message.
Thanks in advance
Raghbir Sandhu
We have a Windows 2012 Domain Controller VM that we would like to backup the System State using DPM. Agent has been installed and the Windows Backup has been added.
When the backup runs in DPM, the job fails. Here is the error code:
When we try and create the backup using Windows Backup, the following error is in the log file:
We have tried attaching a separate drive and backup to a shared location. Both fail.
We have tried backup of just a few files on the DC instead of the System State, this fails as well.
All VSS Writers show as Stable with no errors
Server has the latest updates
Server has been rebooted, same issue
VM is Windows 2012 on a Windows 2008 R2 clustered host and is using Dynamic Disks (not fixed disks).
Anyone have any thoughts on what could be going on?
We are just upgrading from Server 2003 where we used ntbackup. As we have <75mb of data to backup I created a schedule to backup the data daily to a usb drive. Each days file was named to the day of the month, ie; Daily01-31 and the external drive was one of a set of 3 drives that were rotated monthly.
Is there a way to replicate this procedure in Server 2012?
I much prefer full, standalone backups to incremental backups.
Thanks
Hi, I have a problem when creating a scheduled task in Windows Server 2008 R2 Standard x64 which is client of Windows Server 2003 SBS.
When I click finish on scheduled taks wizard the following message appears: Task Scheduler cannot create the task. The user account is unknown, the password is incorrect,or the account does not have permission to create the task.
I tried both local administrator and domain administrator with no success.
P.S. According to other forum I tried to install subinacl and run these three commands from a cmd.
cd\
cacls c:\windows\tasks /T /E /P Administrators:F
cacls c:\windows\tasks /T /E /P SYSTEM:F
These commands grant full permissions to the tasks folder for the user group Administrators and the user System.
After these commands the situation is the same as I described above.
Based on the fact that Microsoft will be stopping the support for Windows 2003 servers, we are helping one of our client to migrate all the existing applications from Windows 2003 server to Windows server 2012 R2.
In the process, we have witnessed some of the legacy applications are having compatibility issues and need some remediation which we don't think we will be able to complete by July 14th 2015. so, If our client needs extended support from Microsoft for Windows 2003 servers, what will be the Premium charge that Microsoft will be charging the customer per server per annum ?
Thanks in advance.
HI,
When setting up windows server backup there are options for backup to disk and backup to volume. I have a usb drive to backup to. WHat is the difference between backing up to volume and disk when backing up to usb drive. Is there performance difference or difference in way backup is performed, copies, etc.?
Thanks