I'm using the latest stable version (3.0.3660) on a VM on Windows Azure and would like to enable period backup. Have tried to enable both local backup and backup to Azure but the GUI doesn't seem to persist the changes. Modal dialog says "Saving..." but nothing more.
Is there a log for this so that I can troubleshoot what doesn't work?
/Erik
I tried it too and the database is non-responsive for several minutes (a co-worker was waiting for tens of minutes). But after waiting a while it actually does something. I configured the Azure backup and that went wrong because it couldn't upload a blob of that large a size. The error was logged and can be found in the studio > status > logs.
Running the server standalone (instead of running as a service) doesn't give any additional feedback either.
Managed it to work by setting "Raven/AnonymousAccess" to Admin and then save the changes, not sure why. Connected with API key that should have full access.
Related
I lost my system drive a day ago and with it all my duplicati settings/jobs (not the backups - they are ok)
Restoring works fine but I'd like to restore/recreate my jobs from an existing backup and continue backing up to that location
Is there a way to do that (couldn't find it in the web interface nor online documentation)
I created the job with the same settings (default settings and same AES password) and tried to start a backup, duplicati complained about a missing database and suggeted a db repair.
After the db repair run everything was back to normal.
One of my backups has failed because seemingly the pass phase is corrupted.
I am attempting to re-register the server (I do not know if this will fix the problem but I do know that in this process the pass phrase is entered) and so need to re-download the Vault Credentials.
In the old Azure portal the download of the Vault Credentials link was right there as soon as you went to the particular vault.
In the new Azure portal I cannot find it anywhere. I have looked and looked and Googled and Googled.
I get the feeling that one has to start the whole backup setup again for the server in order to get the credentials via Getting Started > Backup.
So I am in vault that the server backs up to and I go to Getting Started > Backup and follow the steps and then I end up with a list of servers that I need to choose from but my server is not there because it says "VMs in same region as vault and not protected by another vault are shown....".
Anyway I am stuck.
Path to download the vault credential file: Home>Recovery Services vaults>Select your recovery services vault>Properties>Backup credentials
See the screenshot:
OK I fixed my problem but I did not resolve the "How to re-download Vault Credentials".
In the Azure Backup app on the server I went to Actions > Change Properties and re-entered the pass phrase and tried to save it.
I got a message that nothing was saved because the pass phrase had not changed.
So how the heck did it know that if my initial problem was that the pass phrase was corrupted???
I chanced my luck and tried a "Backup Now" and lo and behold it worked.
GO FIGURE AND THANK YOU TEAM AT MS FOR YET ANOTHER CONUNDRUM I HAD TO SOLVE WITH SMOKE AND MIRRORS.
Don't get me started...
I'm working on SQL 2012 Enterprise and I have a set of SSIS package exports which push data out to text files on a shared network folder. The packages aren't complex and under most circumstances they work perfectly. The problem I'm facing is that they do not work when scheduled - despite reporting that they have succeded.
Let me explain the scenarios;
1) When run manually from within BIDS, they work correctly, txt files are created and populated with data.
2) When deployed to the SSISDB and run from the Agent job they also work as expected - files are created and populate with data.
3) When the Agent job is scheduled to run in the evening, the job runs and reports success. The files are created but the data is not populated.
I've checked the reports on the Integration Services Catalogs and compared the messages line by line from the OnInformation. Both runs reports that the Flat File Destination wrote xxxx rows.
The data is there, the Agent account has the correct access. I cannot fathom why the job works when started manually, but behaves differently when scheduled.
Has anyone seen anything similar? It feels like a very strange bug....
Kind Regards,
James
Make sure that the account you have set up as the proxy for the SSIS task has read/write access to the file.
IMX, when you run an SQL Agent job manually, it appears to use the context of the user who initiates it in some way. I always assumed it was a side effect of impersonation. It's only when it actually runs with the schedule that everything uses the assigned security rights.
Additionally, I think when the user starts the job, the user is impersonating the proxy, but when the job is run via the schedule, the agent's account is impersonating the proxy. Make sure the service account has the right to impersonate the proxy. Take a look at sp_grant_login_to_proxy and sp_enum_login_for_proxy.
Here's a link that roughly goes through the process:
http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
I also recall this video being useful:
http://msdn.microsoft.com/en-us/library/dd440761(v=SQL.100).aspx
I had the same problem with Excel files. It was permission rights.
What worked for me was adding the SERVICE account to the folder's security tab. Then the SQL Agent can access the files.
In Windows Server 2003 SP2, I have removed all users (Anonymous Users, Authenticated Users, Everyone etc) under Component Services > Computers > My Computer > Properties > COM Security > Edit Limits.
After that, I couldn't access the server via remote desktop and terminal services also fails. I can still access it via VNC but when I attempt to open Component Services > Computers, the window stops responding.
Is there any way that I can restore COM permissions to their default settings at least? Or is there a way to enable access to the properties window so I can set it myself?
Thank you for your help.
Ianthe
=== Update: DCOMPERM.EXE ===
I found that the dcomperm.exe file that can alter permissions via the command line. It works on my local machine. My problem now is how to copy it over to the Win2k3 server since network services (netlogon etc) fails to start.
The idea I have right now is to access the Win2k3's VM hard disk and copy the file over. I have yet to find a way to do that.
If you guys have a better way, I hope you don't mind helpin.
Thanks again!
I found that the dcomperm.exe that can alter permissions via the command line. It works on my local machine. Please note that netlogon service also fails to start due to the permissions. I wasn't able to transfer the file through shared folder.
A workaround I did, is use subversion to transfer the file. Commit-Checkout/Update...
After I reset the permissions, the Component Services window worked as per normal.
I've been developing a winforms app tied to sql server. I haven't rebooted in a while. Today i rebooted and now I can't log into sql. I used every account I know and their passwords including one that was working just before i rebooted and i get a 'Login failed' . I did take the database I use offline just before starting and I do have backups before then.
thoughts on what happened? Is there a way to bring the database back online OR somehow find out what passwords are? I even tried using windows authenication with me as an admin on the box AND sa (Yes, bad) and still no dice.
:-/ That's a rough place to be ... I wish you luck. Check out this blog post, not sure if you're using sql 2k5 or not, but if so, it may be helpful:
http://blogs.msdn.com/raulga/archive/2007/07/12/disaster-recovery-what-to-do-when-the-sa-account-password-is-lost-in-sql-server-2005.aspx
Have you checked to make sure that the service is actually running? Also are you trying to connect using IPC, TCPIP or named pipes? Whichever way make sure it's enabled in the configuration tools.
Since admin's on the box are SQL admins the only thing I can think of is that the service is not running.