Tag Info

Hot answers tagged

12

Volume Shadow Copy Service. It takes a snapshot of files so they can be backed up even while they're in use. It ensures that the file is not modified between the start and end of the backup, but can't ensure that the file is in an actually usable state should it need to be restored (for instance, a database file may be in mid-row modification when the ...


8

So… I have been working on a little VBScript that can: take persistent VSS snapshots mount them to a folder (from which you can then backup the files) unmount VSS snapshots It relies on vshadow.exe (documentation), part of the Volume Shadow Copy Service SDK 7.2 as available from Microsoft. I've been working with this version: "VSHADOW.EXE 2.2 - Volume ...


8

So in the spirit of reinventing the wheel, I present to you Tomalak's excellent script (see above) but completely rewritten in Powershell!!! The main reason I did this was to evangelise the awesome powers of Powershell, but also because I despise vbscript with my entire being. It's mostly feature to feature identical, but I did implement some things a ...


8

I had the exact same problem in Srv2008 R2 and this is how I solved it: Right click on the folder your trying to restore from shadow copy and chose 'Previous versions'. Chose a date and click on open. Right click on any file or folder within the previous folder and chose 'properties'. Under 'General' copy what reads in 'location' - .e.g.: ...


7

Below are sample scripts used to backup Hyper-V using VSS to create a snapshot. Guest operating systems that do not support VSS will be put into a saved state during the snapshot period. This sample backs up images located on the E:\VS directory to a local directory at F:\VS Backups. These locations will need to be adjusted to fit your needs. For each ...


7

I've performed file-level clones (using the Linux NTFS Tools ntfsclone utility) of Windows 2000 and Windows XP. I haven't tried ntfsclone with Windows Vista or newer versions but I wouldn't expect any problems. I use Microsoft's file-level cloning tool, ImageX, quite regularly with Windows XP and Windows 7 and have no problems there, either. I generally ...


7

You'd think this should be easy, wouldn't you? Well, you'd be wrong. It's not. Shadow Copies of Shared Folders is available in all editions of Windows Server 2008 R2. However, the user interface is not available for the Server Core installation option. To create shadow copies for computers with a Server Core installation, you need to manage this feature ...


6

No, DFS-R will not replicate the VSS shadow copies. Each server would maintain their own shadow copies. However, if you have bi-directional replication and you restore from a local shadow copy on server B, it would replicate that change to Server-A as long as that file doesn't already exist identically. If the folder hash is different, meaning the file ...


6

Yes you can change the limit up to 512 shadow copies per volume, by using the MaxShadowCopies registry key. You will probably also need to adjust the amount of storage space VSS is allowed to use with vssadmin.exe Resize ShadowStorage. (You may configure Shadow Copies for a volume to back up to a separate volume, such as one with more space. Again, ...


6

Short answer: they don't play very well together unless you've got SQL server configured appropriately (and even then I wouldn't recommend it). There's a lot of information about VSS & MSSQL playing together here. One word of warning though: presumably the SQL Server data format is robust enough that such a snapshot would be guaranteed to be ...


6

You can create a Shadow copy on a specific drive using WMI object like it's explained in Microsoft Article. Enable volume shadow copy on specific drive (D:, E:,...) is two things Creating a shadow copy as shown in the preceding article Creating a scheduled task to create shadow copy


6

It took me a little while to get this to worked (after finding the simple error causing it to fail), and the function is incomplete. I want to add the ability to enable it on a remote computer, which will probably have to be done via a task that is ran once. If anybody modifies this and adds that, let me know! function Enable-ShadowCopies { param( ...


5

Backup software should run as "a user with the lowest privilege level required in order for it to read & back up all of the files you want backed up". Typically this means root (or some other UID 0 account) on Unix systems, and a member of the Backup Operators group on recent versions of Windows. Some Windows backup software that doesn't take advantage ...


5

Assuming you stored your volume shadow copies on the same disk that you just moved the 100GB file onto you're probably out of luck. Undelete on NTFS, especially after making changes to the volume, is iffy at best. Shadow copies aren't backup. They're a nice crutch to help you recover files in some situations, but they shouldn't be relied upon as existing ...


5

Since you are able to get to the login screen but the shell doesn't actually come up, I would suspect that something in the user profiles is not being copied properly. You can try deleting (or not copying) the profile directory that you are trying to log into before starting the copied system. Winlogon should create a fresh profile from the default, ...


5

In general, the BEGIN BACKUP / END BACKUP block would signal Exchange to truncate the logs. But in order for it to work, you should have created a snapshot of all volumes with Exchange-related data - so if you have separated data and transaction logs, you would need to snapshot both - the data and the Tlog volume. Also, you should make sure that your script ...


5

Mathias R. Jessen got me pointed in the right direction, the ever famous WinSxS folder. However I did not see any of the VSS errors in the Event Log which made me a little hesitant to just nuke all the NTFS permissions lest I break something else. I went back and read Event ID 513 TechNet reference again and noted that under the Verify section it was ...


4

(upfront, I'll say hopefully you aren't using Previous Versions as your backup) Couple of ideas come to mind: First, search Microsoft's KB here: http://technet.microsoft.com/en-us/ms772425.aspx for any VSS updates that might be applicable to your OS revision level. Second check that the VSS writers are working correctly: Open an administrative cmd ...


4

Don't do this the way you're doing it. Classic example of "backups are useless without restores." If you have two different products doing incrementals, heaven help you trying to do a restore, because each one breaks the other's log chain. So, change at least one of these tools to be doing fulls, and evaluate your need to be doing incrementals at all.


4

Shadow copy is a point in time snapshot of the volume. It is not a file versioning tool. You can increase the frequency of your VSS snapshots, but you will never get one-snapshot per file write. As for tools built-into Windows that permit file versioning. You can get this to a certain degree with the Windows Sharepoint Services.


4

The problem with copying a live filesystem from VSS is that that the existing Windows instance will probably have the signature of the new disk already in it's registry. When you boot the copy, the signature of the partition it is booting from is matched to the registry and mounted as D: or E:, rather than the C: it should be. You can sort this out by ...


4

No, it doesn't. If you get a VSS snap of it, you'll get it as it is at the time of the snap.


4

You can use the Get-WMIObject cmdlet to remotely remove shadow copies. The example below demonstrates how it might work. It should be noted that the Get-WMIObject cmdlet returned a null object in the case where there were not any remote shadow copies available. This means that might still need a combination of PowerShell remoting and the vssadmin tool to ...


4

I've been using vSphere replication recently... There are only two options for guest quiescing: Microsoft VSS and none. If your system being replicated supports quiescing, use it. Otherwise, you don't have any other options. Systems without a quiescing option become crash-consistent snapshots. But there are only two options offered, so please use what makes ...


4

I used Robocopy to synchronize website content across 9 web servers. Here's a sample of the batch file that ran robocopy.exe. This batch file was scheduled to run every 5 or 10 minutes or could be run manually to push changes immediately. robocopy.exe d:\inetpub\wwwroot\ \\webserver1\d$\inetpub\wwwroot\ *.* /E /PURGE /SEC /NP /NJH /NJS /XF keepalive_*.* ...


4

If it's a lone domain controller (the only one in the forest) then you are usually OK to use cloning tools on it, provided the server is shut down at the time it's cloned. The original server must be destroyed if the clone is ever brought online, however, as the two cannot co-exist. The cloned server will also only be valid for a short time, because domain ...


4

This Technet article on VSS scalability indicates that the issue probably relates to exhaustion of the nonpaged memory pool which is limited to 256MB on Windows 2003 32bit (x86). VSS uses more resources during snapshot creation and the article specifically states that a 5TB snapshot would require 200MB for that snapshot alone. Depending on what else is ...


3

You never backup MDF and LDF files. You run backups (plans, SQL, SMO, whatever) then backup these backup files. Frankly, I don't get a fig what any vendor says about VSS. I also dislike any vendor that has a SQL Server plugin for backups. You use SQL Server native backups only FYI: you also exclude MDFs and LDFs from virus scanning too.


3

It seems like you have done a lot of research on this and every service has been found to come up wanting :( Thinking of this in another way, is there a reason why you'd like to use an online service like this? I wonder if a more suitable option for you might be to have a remote cloud server running your favourite flavour of Linux with bacula installed? Your ...



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